Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Am 05.09.13 07:09, schrieb Kureem Rossaye:
> Thank you very much,
> I have not included the proposal to the Incubator wiki yet.
> How can I do that?
Create an account here:
http://wiki.apache.org/incubator/

Then mail your username to this list, askinf for access. You'll be
granted then.

Then you can add your proposal here:
http://wiki.apache.org/incubator/ProjectProposals

I assume you know this link already:
http://incubator.apache.org/guides/proposal.html

Please try to make the proposal look similar to the others on the wiki.

Cheers!

Christian
> Thanks
> Kureem
>
>
> On 5 September 2013 00:09, Christian Grobmeier  wrote:
>
>> Nice!
>>
>> Have you included your proposal to the Incubator wiki?
>> I would like to forward it to the Struts team, some might be interested.
>>
>> I have no time to actually code, but I might help with incubation
>> (mentoring or championing). Before deciding on that, I would like to
>> hear if there is interest of others here.
>>
>> Am 04.09.13 15:04, schrieb Kureem Rossaye:
>>> "*once could use Castafiore
>>> in conjunction with Struts. In other terms, Castafiore could be used as
>>> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
>>> whatever. Is that correct?*"
>>>
>>> Correct!
>>> Actually I myself did not get the idea that it could be used like that.
>> Yes
>>> it can be used like that.
>>> Actually, a castafiore application (which can be a simple table) can be
>>> included on a page using a simple javascript or a jsp tag. So why not a
>>> struts plugin.
>>> Actually I have tried it as an echo2 framework component. It works just
>>> nice.
>>>
>>>
>>> Thanks for your interest
>>>
>>> Ragards,
>>> Kureem
>>>
>>>
>>> On 4 September 2013 15:32, Christian Grobmeier 
>> wrote:
 Kureem,

 this sounds nice. As far as I understood it, once could use Castafiore
 in conjunction with Struts. In other terms, Castafiore could be used as
 a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
 whatever. Is that correct?

 Cheers



 Am 04.09.13 10:01, schrieb Kureem Rossaye:
> Hi,
> Indeed, I have read the incubation proposal guide. The only thing I
>> could
> not figure out is how to recruit a champion.
> However, after re-reading the guide, I missed something. I should have
> prefixed the subject of the mail with [PROPOSAL]. So I am resending the
> proposal with the proper subject.
>
> **
> PROPOSAL
> Abstract
>
> Castafiore framework is a web frameworks, fully component oriented,
>> ajax
> based, one page appplication. Although the framework can be viewed as a
> classical component oriented web framework like GWT, it has been
>> designed
> and implemented with a particular goal in mind. It is to be able to
>> make
> existing javascript libraries "java-able". Meaning that the framework
> allows to easily take a javascript library like e.g jquery ui and use
>> the
> components and features via java. The integration of the javascript
> libraries need to be easy and natural.
>
> Actually companies like ext js and smartgwt have made their components
> "java-able" using GWT. I wish to provide an alternative to gwt that is
 much
> easier, fast, lightweight, and much more productive.
> Proposal
>
> Castafiore framework has been designed and implemented with the
>> following
> goals in mind
>
>1.
>
>Fully object oriented
>2.
>
>Simple API that is very close to html itself
>We wanted an API that is closer to html markup and javascripts event
>model. I believe that this would help web developers easily
>> visualize
 the
>rendering when reading source code.
>3.
>
>Write a full application with only java
>4.
>
>No need for compiler to convert to javascript like gwt.Javascript is
>rendered at runtime.
>5.
>
>The same API can be used to make an software that is server centric
 and
>or client centric. Meaning that the user can make part of his
 application
>server centric and part of his application client centric. He can of
 course
>choose to make the whole application client centric or server
>> centric
>depending on the requirement. All of this using the same API.
>6.
>
>Low memory footprint
>7.
>
>Easy packaging of application. Everything can be packaged in a
>> single
>jar. This includes images, css or javascript as well
>8.
>
>Same API used to create custom components. No need to external set
>> of
>API or specific programming technique to create custom components.
 Creating
>a custom components should be done only the same way as writing an
>applicatio

Re: Followup to VXQuery July 2013 report

[ant elder]

Thanks for doing that so promptly Till.

   ...ant


On Thu, Sep 5, 2013 at 4:00 AM, Till Westmann  wrote:

> Just for the record: The website is updated (from the branch that will
> hopefully be released soon).
>
> Till
>
> On Sep 4, 2013, at 12:11 AM, Marvin Humphrey 
> wrote:
>
> > On Tue, Sep 3, 2013 at 11:42 PM, David Crossley 
> wrote:
> >> ant elder wrote:
> >>> Hi Marvin, I had a look, that README being pointed to is just build
> >>> instructions on how to build the svn trunk isn't it, so not to some
> >>> released artifacts. Thats allowed isn't it, i'm pretty sure other
> projects
> >>> and podlings have done something similar anyway. Is it that the website
> >>> describes it as user installation instructions rather than developer
> build
> >>> instructions thats the issue?
> >>>
> >>>   ...ant
> >>
> >> I reckon so. To clearly refer developers to developer resources
> >> is fine, but users no. They need to be referred to user instructions.
> >
> > In VXQuery's case, there's nothing to refer users to because in four
> years,
> > VXQuery has never made an incubating release.
> >
> > If developer instructions for accessing version control are added to the
> > website in accordance with ASF guidelines, of course that's fine -- so
> > long as all "user installation" instructions are removed.
> >
> > Here's more background from the legal-discuss list regarding the current
> policy,
> > this time from a different Board member, Doug Cutting:
> >
> >http://markmail.org/message/pelvob23vrzuzws5
> >
> >Each PMC should attempt to ensure that every commit is in accord with
> >Apache's intellectual property policies. Releases are a double-check
> of
> >this. We hope that source code repositories are not legally considered
> >publications, but we don't know that courts will in fact always treat
> them
> >that way, so it's best to guard against that too. Note that the extra
> >scrutiny around releases both serves to double-check (belt and
> suspenders)
> >as well as to provide evidence that we do not consider the source code
> >repository as a publication. But again, we cannot depend on others to
> >agree with that, and must guard against other interpretations as best
> we
> >can.
> >
> > If VXQuery finds it uncomfortable not to have anything they can show
> users,
> > they can solve that by making a release.
> >
> > Marvin Humphrey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Followup to VXQuery July 2013 report

[ant elder]

Dropping the vxquery mailing list...

To me VXQuery looks like an example of a project being let down by the
Incubator PMC. This labeling issue was just an honest attempt at trying to
be helpful not some underhanded attempt to try to circumvent the ASF
release policy, if they were getting adequate mentoring it would have just
been an opportunity to teach them more about the ASF release policies and
processes. Similarly with the no releases in 4 years - they've attempted to
release twice and both times it stalled getting the votes, what they need
are mentors who can show them whats necessary to push releases and voting
through the Incubator. In the past they've asked us for more mentors to
help and got nothing. Its a small project but its managed to survive for 4
years here and still have some active committers and as they've just shown
now when a problem is reported they fixed it in less than a day, so all
credit to them for keeping on trying.



On Thu, Sep 5, 2013 at 9:46 AM, ant elder  wrote:

> Thanks for doing that so promptly Till.
>
>...ant
>
>
> On Thu, Sep 5, 2013 at 4:00 AM, Till Westmann  wrote:
>
>> Just for the record: The website is updated (from the branch that will
>> hopefully be released soon).
>>
>> Till
>>
>> On Sep 4, 2013, at 12:11 AM, Marvin Humphrey 
>> wrote:
>>
>> > On Tue, Sep 3, 2013 at 11:42 PM, David Crossley 
>> wrote:
>> >> ant elder wrote:
>> >>> Hi Marvin, I had a look, that README being pointed to is just build
>> >>> instructions on how to build the svn trunk isn't it, so not to some
>> >>> released artifacts. Thats allowed isn't it, i'm pretty sure other
>> projects
>> >>> and podlings have done something similar anyway. Is it that the
>> website
>> >>> describes it as user installation instructions rather than developer
>> build
>> >>> instructions thats the issue?
>> >>>
>> >>>   ...ant
>> >>
>> >> I reckon so. To clearly refer developers to developer resources
>> >> is fine, but users no. They need to be referred to user instructions.
>> >
>> > In VXQuery's case, there's nothing to refer users to because in four
>> years,
>> > VXQuery has never made an incubating release.
>> >
>> > If developer instructions for accessing version control are added to the
>> > website in accordance with ASF guidelines, of course that's fine -- so
>> > long as all "user installation" instructions are removed.
>> >
>> > Here's more background from the legal-discuss list regarding the
>> current policy,
>> > this time from a different Board member, Doug Cutting:
>> >
>> >http://markmail.org/message/pelvob23vrzuzws5
>> >
>> >Each PMC should attempt to ensure that every commit is in accord with
>> >Apache's intellectual property policies. Releases are a double-check
>> of
>> >this. We hope that source code repositories are not legally
>> considered
>> >publications, but we don't know that courts will in fact always
>> treat them
>> >that way, so it's best to guard against that too. Note that the extra
>> >scrutiny around releases both serves to double-check (belt and
>> suspenders)
>> >as well as to provide evidence that we do not consider the source
>> code
>> >repository as a publication. But again, we cannot depend on others to
>> >agree with that, and must guard against other interpretations as
>> best we
>> >can.
>> >
>> > If VXQuery finds it uncomfortable not to have anything they can show
>> users,
>> > they can solve that by making a release.
>> >
>> > Marvin Humphrey
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

[ANNOUNCE] Ben Hindman as Apache Incubator PMC member!

[Chris Mattmann]

Hi Folks,

The IPMC has VOTEd to add Ben Hindman as an Apache Incubator PMC
member. Welcome Ben!

Please feel free to say a bit about yourself.

Cheers,
Chris



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Storm for Apache Incubator

[Benjamin Hindman]

Proposal looks great Nathan, I'd like to volunteer as a mentor if you're
looking for more help!


On Wed, Sep 4, 2013 at 1:07 AM, Nathan Marz  wrote:

> Hi everyone,
>
> I'd like to propose Storm to be an Apache Incubator project. After much
> thought I believe this is the right next step for the project, and I look
> forward to hearing everyone's thoughts and feedback!
>
> Here's a link to the proposal:
> https://wiki.apache.org/incubator/StormProposal
>
> The proposal is also pasted below.
>
> -Nathan
>
>
> = Storm Proposal =
>
> == Abstract ==
>
> Storm is a distributed, fault-tolerant, and high-performance realtime
> computation system that provides strong guarantees on the processing of
> data.
>
> == Proposal ==
>
> Storm is a distributed real-time computation system. Similar to how Hadoop
> provides a set of general primitives for doing batch processing, Storm
> provides a set of general primitives for doing real-time computation. Its
> use cases span stream processing, distributed RPC, continuous computation,
> and more. Storm has become a preferred technology for near-realtime
> big-data processing by many organizations worldwide (see a partial list at
> https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source
> project, Storm’s developer community has grown rapidly to 46 members.
>
> == Background ==
>
> The past decade has seen a revolution in data processing. MapReduce,
> Hadoop, and related technologies have made it possible to store and process
> data at scales previously unthinkable. Unfortunately, these data processing
> technologies are not realtime systems, nor are they meant to be. The lack
> of a "Hadoop of realtime" has become the biggest hole in the data
> processing ecosystem. Storm fills that hole.
>
> Storm was initially developed and deployed at BackType in 2011. After 7
> months of development BackType was acquired by Twitter in July 2011. Storm
> was open sourced in September 2011.
>
> Storm has been under continuous development on its Github repository since
> being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7,
> 0.8) and many minor ones.
>
> == Rationale ==
>
> Storm is a general platform for low-latency big-data processing. It is
> complementary to the existing Apache projects, such as Hadoop. Many
> applications are actually exploring using both Hadoop and Storm for
> big-data processing. Bringing Storm into Apache is very beneficial to both
> Apache community and Storm community.
>
> The rapid growth of Storm community is empowered by open source. We believe
> the Apache foundation is a great fit as the long-term home for Storm, as it
> provides an established process for community-driven development and
> decision making by consensus. This is exactly the model we want for future
> Storm development.
>
> == Initial Goals ==
>
>   * Move the existing codebase to Apache
>   * Integrate with the Apache development process
>   * Ensure all dependencies are compliant with Apache License version 2.0
>   * Incremental development and releases per Apache guidelines
>
> == Current Status ==
>
> Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor
> ones. Storm 0.9 is about to be released. Storm is being used in production
> by over 50 organizations. Storm codebase is currently hosted at github.com
> ,
> which will seed the Apache git repository.
>
> === Meritocracy ===
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. Several companies have already expressed
> interest in this project, and we intend to invite additional developers to
> participate. We will encourage and monitor community participation so that
> privileges can be extended to those that contribute.
>
> === Community ===
>
> The need for a low-latency big-data processing platform in the open source
> is tremendous. Storm is currently being used by at least 50 organizations
> worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and
> is
> the most starred Java project on Github. By bringing Storm into Apache, we
> believe that the community will grow even bigger.
>
> === Core Developers ===
>
> Storm was started by Nathan Marz at BackType, and now has developers from
> Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies.
>
> === Alignment ===
>
> In the big-data processing ecosystem, Storm is a very popular low-latency
> platform, while Hadoop is the primary platform for batch processing. We
> believe that it will help the further growth of big-data community by
> having Hadoop and Storm aligned within Apache foundation. The alignment is
> also beneficial to other Apache communities (such as Zookeeper, Thrift,
> Mesos). We could include additional sub-projects, Storm-on-YARN and
> Storm-on-Mesos, in the near future.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The risk of the Storm project being abandoned is minimal. There are at
> least 50 organizations (Twitter, Yahoo

request for write access to incubator wiki

[Kureem Rossaye]

Hi,
Is it possible to grant me access to the wiki in order to submit a proposal.


Regards,
-- 
Kureem Rossaye
Managing Director

ArchNet ltd
R. Tagore Avenue, Mesnil
Mauritius
Mobile :+230 7159028 / Tel :+230 6867326
Skype : arkureem
http://www.archnetltd.com

Re: request for write access to incubator wiki

[Christian Grobmeier]

Am 05.09.13 12:07, schrieb Kureem Rossaye:
> Hi,
> Is it possible to grant me access to the wiki in order to submit a proposal.
>
>
> Regards,
Just need your Wiki name :-)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: request for write access to incubator wiki

[Kureem Rossaye]

oops sorry
The wiki name : KureemRossaye


On 5 September 2013 14:35, Christian Grobmeier  wrote:

>  [image: Boxbe]  This message is eligible
> for Automatic Cleanup! (grobme...@gmail.com) Add cleanup 
> rule|
>  More
> info
>
> Am 05.09.13 12:07, schrieb Kureem Rossaye:
> > Hi,
> > Is it possible to grant me access to the wiki in order to submit a
> proposal.
> >
> >
> > Regards,
> Just need your Wiki name :-)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>


-- 
Kureem Rossaye
Managing Director

ArchNet ltd
R. Tagore Avenue, Mesnil
Mauritius
Mobile :+230 7159028 / Tel :+230 6867326
Skype : arkureem
http://www.archnetltd.com

Re: request for write access to incubator wiki

[Christian Grobmeier]

you are in!

Am 05.09.13 12:59, schrieb Kureem Rossaye:
> oops sorry
> The wiki name : KureemRossaye
>
>
> On 5 September 2013 14:35, Christian Grobmeier  wrote:
>
>>  [image: Boxbe]  This message is eligible
>> for Automatic Cleanup! (grobme...@gmail.com) Add cleanup 
>> rule|
>>  More
>> info
>>
>> Am 05.09.13 12:07, schrieb Kureem Rossaye:
>>> Hi,
>>> Is it possible to grant me access to the wiki in order to submit a
>> proposal.
>>>
>>> Regards,
>> Just need your Wiki name :-)
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>>
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Done!
Kureem
Am 05.09.13 07:09, schrieb Kureem Rossaye:
> Thank you very much,
> I have not included the proposal to the Incubator wiki yet.
> How can I do that?
Create an account here:
http://wiki.apache.org/incubator/

Then mail your username to this list, askinf for access. You'll be
granted then.

Then you can add your proposal here:
http://wiki.apache.org/incubator/ProjectProposals

I assume you know this link already:
http://incubator.apache.org/guides/proposal.html

Please try to make the proposal look similar to the others on the wiki.

Cheers!


On 5 September 2013 12:47, Christian Grobmeier  wrote:

> Am 05.09.13 07:09, schrieb Kureem Rossaye:
> > Thank you very much,
> > I have not included the proposal to the Incubator wiki yet.
> > How can I do that?
> Create an account here:
> http://wiki.apache.org/incubator/
>
> Then mail your username to this list, askinf for access. You'll be
> granted then.
>
> Then you can add your proposal here:
> http://wiki.apache.org/incubator/ProjectProposals
>
> I assume you know this link already:
> http://incubator.apache.org/guides/proposal.html
>
> Please try to make the proposal look similar to the others on the wiki.
>
> Cheers!
>
> Christian
> > Thanks
> > Kureem
> >
> >
> > On 5 September 2013 00:09, Christian Grobmeier 
> wrote:
> >
> >> Nice!
> >>
> >> Have you included your proposal to the Incubator wiki?
> >> I would like to forward it to the Struts team, some might be interested.
> >>
> >> I have no time to actually code, but I might help with incubation
> >> (mentoring or championing). Before deciding on that, I would like to
> >> hear if there is interest of others here.
> >>
> >> Am 04.09.13 15:04, schrieb Kureem Rossaye:
> >>> "*once could use Castafiore
> >>> in conjunction with Struts. In other terms, Castafiore could be used as
> >>> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> >>> whatever. Is that correct?*"
> >>>
> >>> Correct!
> >>> Actually I myself did not get the idea that it could be used like that.
> >> Yes
> >>> it can be used like that.
> >>> Actually, a castafiore application (which can be a simple table) can be
> >>> included on a page using a simple javascript or a jsp tag. So why not a
> >>> struts plugin.
> >>> Actually I have tried it as an echo2 framework component. It works just
> >>> nice.
> >>>
> >>>
> >>> Thanks for your interest
> >>>
> >>> Ragards,
> >>> Kureem
> >>>
> >>>
> >>> On 4 September 2013 15:32, Christian Grobmeier 
> >> wrote:
>  Kureem,
> 
>  this sounds nice. As far as I understood it, once could use Castafiore
>  in conjunction with Struts. In other terms, Castafiore could be used
> as
>  a Struts plugin which then calls Struts Actions and replaces Tiles,
> JSP
>  whatever. Is that correct?
> 
>  Cheers
> 
> 
> 
>  Am 04.09.13 10:01, schrieb Kureem Rossaye:
> > Hi,
> > Indeed, I have read the incubation proposal guide. The only thing I
> >> could
> > not figure out is how to recruit a champion.
> > However, after re-reading the guide, I missed something. I should
> have
> > prefixed the subject of the mail with [PROPOSAL]. So I am resending
> the
> > proposal with the proper subject.
> >
> >
> **
> > PROPOSAL
> > Abstract
> >
> > Castafiore framework is a web frameworks, fully component oriented,
> >> ajax
> > based, one page appplication. Although the framework can be viewed
> as a
> > classical component oriented web framework like GWT, it has been
> >> designed
> > and implemented with a particular goal in mind. It is to be able to
> >> make
> > existing javascript libraries "java-able". Meaning that the framework
> > allows to easily take a javascript library like e.g jquery ui and use
> >> the
> > components and features via java. The integration of the javascript
> > libraries need to be easy and natural.
> >
> > Actually companies like ext js and smartgwt have made their
> components
> > "java-able" using GWT. I wish to provide an alternative to gwt that
> is
>  much
> > easier, fast, lightweight, and much more productive.
> > Proposal
> >
> > Castafiore framework has been designed and implemented with the
> >> following
> > goals in mind
> >
> >1.
> >
> >Fully object oriented
> >2.
> >
> >Simple API that is very close to html itself
> >We wanted an API that is closer to html markup and javascripts
> event
> >model. I believe that this would help web developers easily
> >> visualize
>  the
> >rendering when reading source code.
> >3.
> >
> >Write a full application with only java
> >4.
> >
> >No need for compiler to convert to javascript like gwt.Javascript
> is
> >rendered at runtime.
> >5.
> >
> >The same API

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Perfect!

I will now ask on the Struts list if there are some people interested

Thanks!

Am 05.09.13 14:42, schrieb Kureem Rossaye:
> Done!
> Kureem
> Am 05.09.13 07:09, schrieb Kureem Rossaye:
>> Thank you very much,
>> I have not included the proposal to the Incubator wiki yet.
>> How can I do that?
> Create an account here:
> http://wiki.apache.org/incubator/
>
> Then mail your username to this list, askinf for access. You'll be
> granted then.
>
> Then you can add your proposal here:
> http://wiki.apache.org/incubator/ProjectProposals
>
> I assume you know this link already:
> http://incubator.apache.org/guides/proposal.html
>
> Please try to make the proposal look similar to the others on the wiki.
>
> Cheers!
>
>
> On 5 September 2013 12:47, Christian Grobmeier  wrote:
>
>> Am 05.09.13 07:09, schrieb Kureem Rossaye:
>>> Thank you very much,
>>> I have not included the proposal to the Incubator wiki yet.
>>> How can I do that?
>> Create an account here:
>> http://wiki.apache.org/incubator/
>>
>> Then mail your username to this list, askinf for access. You'll be
>> granted then.
>>
>> Then you can add your proposal here:
>> http://wiki.apache.org/incubator/ProjectProposals
>>
>> I assume you know this link already:
>> http://incubator.apache.org/guides/proposal.html
>>
>> Please try to make the proposal look similar to the others on the wiki.
>>
>> Cheers!
>>
>> Christian
>>> Thanks
>>> Kureem
>>>
>>>
>>> On 5 September 2013 00:09, Christian Grobmeier 
>> wrote:
 Nice!

 Have you included your proposal to the Incubator wiki?
 I would like to forward it to the Struts team, some might be interested.

 I have no time to actually code, but I might help with incubation
 (mentoring or championing). Before deciding on that, I would like to
 hear if there is interest of others here.

 Am 04.09.13 15:04, schrieb Kureem Rossaye:
> "*once could use Castafiore
> in conjunction with Struts. In other terms, Castafiore could be used as
> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> whatever. Is that correct?*"
>
> Correct!
> Actually I myself did not get the idea that it could be used like that.
 Yes
> it can be used like that.
> Actually, a castafiore application (which can be a simple table) can be
> included on a page using a simple javascript or a jsp tag. So why not a
> struts plugin.
> Actually I have tried it as an echo2 framework component. It works just
> nice.
>
>
> Thanks for your interest
>
> Ragards,
> Kureem
>
>
> On 4 September 2013 15:32, Christian Grobmeier 
 wrote:
>> Kureem,
>>
>> this sounds nice. As far as I understood it, once could use Castafiore
>> in conjunction with Struts. In other terms, Castafiore could be used
>> as
>> a Struts plugin which then calls Struts Actions and replaces Tiles,
>> JSP
>> whatever. Is that correct?
>>
>> Cheers
>>
>>
>>
>> Am 04.09.13 10:01, schrieb Kureem Rossaye:
>>> Hi,
>>> Indeed, I have read the incubation proposal guide. The only thing I
 could
>>> not figure out is how to recruit a champion.
>>> However, after re-reading the guide, I missed something. I should
>> have
>>> prefixed the subject of the mail with [PROPOSAL]. So I am resending
>> the
>>> proposal with the proper subject.
>>>
>>>
>> **
>>> PROPOSAL
>>> Abstract
>>>
>>> Castafiore framework is a web frameworks, fully component oriented,
 ajax
>>> based, one page appplication. Although the framework can be viewed
>> as a
>>> classical component oriented web framework like GWT, it has been
 designed
>>> and implemented with a particular goal in mind. It is to be able to
 make
>>> existing javascript libraries "java-able". Meaning that the framework
>>> allows to easily take a javascript library like e.g jquery ui and use
 the
>>> components and features via java. The integration of the javascript
>>> libraries need to be easy and natural.
>>>
>>> Actually companies like ext js and smartgwt have made their
>> components
>>> "java-able" using GWT. I wish to provide an alternative to gwt that
>> is
>> much
>>> easier, fast, lightweight, and much more productive.
>>> Proposal
>>>
>>> Castafiore framework has been designed and implemented with the
 following
>>> goals in mind
>>>
>>>1.
>>>
>>>Fully object oriented
>>>2.
>>>
>>>Simple API that is very close to html itself
>>>We wanted an API that is closer to html markup and javascripts
>> event
>>>model. I believe that this would help web developers easily
 visualize
>> the
>>>rendering when reading source code.
>>>3.
>>>
>>>Write a full application 

Re: KEYS and keys

[Tim Williams]

On Wed, Sep 4, 2013 at 7:18 PM, sebb  wrote:
> On 4 September 2013 02:31, Tim Williams  wrote:
>> I notice that Chris just pointed[1] spark to the nifty keys
>> listing[1].  Our docs still imply manual maintenance of the typical
>> KEYS file[2].  Honestly, I didn't even know the ldap-driven one was
>> around.  I assume its fair for projects to just point to the
>> p.a.o/keys/groups/${project}.asc file nowadays vs. copying that over
>> periodically to KEYS?
>
> The KEYS file has historically been manually maintained.
> As new keys are used for signing releases, they are added to the file.
> However entries should not be deleted if they have ever been used to
> sign a release, otherwise it may not be possible to check the sigs of
> archived artifacts.
>
> LDAP does not have all historic keys, or even all historic RMs.
>
> So replacing the KEYS file with a copy from LDAP may lose keys needed
> for validating archived files.
>
> Directing users to the p.a.o/keys/groups/${project}.asc files should
> work for current releases.
> But even that has an problem - if the RM leaves a project whilst the
> release is still current, the project.asc file will no longer contain
> the RM's key
>
> The problem is even worse for older releases.
> People may create new keys and drop old ones which have been used for signing.
> People leave a project or the ASF and the LDAP entry is changed.
>
> I don't think the LDAP keys are really suitable for use as a KEYS file
> at present.

Great points, makes total sense, thanks for the clarification sebb!

--tim

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Thank you.

hope this works out.
If there is anything I can do, please ask.

Kureem


On 5 September 2013 16:55, Christian Grobmeier  wrote:

> Perfect!
>
> I will now ask on the Struts list if there are some people interested
>
> Thanks!
>
> Am 05.09.13 14:42, schrieb Kureem Rossaye:
> > Done!
> > Kureem
> > Am 05.09.13 07:09, schrieb Kureem Rossaye:
> >> Thank you very much,
> >> I have not included the proposal to the Incubator wiki yet.
> >> How can I do that?
> > Create an account here:
> > http://wiki.apache.org/incubator/
> >
> > Then mail your username to this list, askinf for access. You'll be
> > granted then.
> >
> > Then you can add your proposal here:
> > http://wiki.apache.org/incubator/ProjectProposals
> >
> > I assume you know this link already:
> > http://incubator.apache.org/guides/proposal.html
> >
> > Please try to make the proposal look similar to the others on the wiki.
> >
> > Cheers!
> >
> >
> > On 5 September 2013 12:47, Christian Grobmeier 
> wrote:
> >
> >> Am 05.09.13 07:09, schrieb Kureem Rossaye:
> >>> Thank you very much,
> >>> I have not included the proposal to the Incubator wiki yet.
> >>> How can I do that?
> >> Create an account here:
> >> http://wiki.apache.org/incubator/
> >>
> >> Then mail your username to this list, askinf for access. You'll be
> >> granted then.
> >>
> >> Then you can add your proposal here:
> >> http://wiki.apache.org/incubator/ProjectProposals
> >>
> >> I assume you know this link already:
> >> http://incubator.apache.org/guides/proposal.html
> >>
> >> Please try to make the proposal look similar to the others on the wiki.
> >>
> >> Cheers!
> >>
> >> Christian
> >>> Thanks
> >>> Kureem
> >>>
> >>>
> >>> On 5 September 2013 00:09, Christian Grobmeier 
> >> wrote:
>  Nice!
> 
>  Have you included your proposal to the Incubator wiki?
>  I would like to forward it to the Struts team, some might be
> interested.
> 
>  I have no time to actually code, but I might help with incubation
>  (mentoring or championing). Before deciding on that, I would like to
>  hear if there is interest of others here.
> 
>  Am 04.09.13 15:04, schrieb Kureem Rossaye:
> > "*once could use Castafiore
> > in conjunction with Struts. In other terms, Castafiore could be used
> as
> > a Struts plugin which then calls Struts Actions and replaces Tiles,
> JSP
> > whatever. Is that correct?*"
> >
> > Correct!
> > Actually I myself did not get the idea that it could be used like
> that.
>  Yes
> > it can be used like that.
> > Actually, a castafiore application (which can be a simple table) can
> be
> > included on a page using a simple javascript or a jsp tag. So why
> not a
> > struts plugin.
> > Actually I have tried it as an echo2 framework component. It works
> just
> > nice.
> >
> >
> > Thanks for your interest
> >
> > Ragards,
> > Kureem
> >
> >
> > On 4 September 2013 15:32, Christian Grobmeier 
>  wrote:
> >> Kureem,
> >>
> >> this sounds nice. As far as I understood it, once could use
> Castafiore
> >> in conjunction with Struts. In other terms, Castafiore could be used
> >> as
> >> a Struts plugin which then calls Struts Actions and replaces Tiles,
> >> JSP
> >> whatever. Is that correct?
> >>
> >> Cheers
> >>
> >>
> >>
> >> Am 04.09.13 10:01, schrieb Kureem Rossaye:
> >>> Hi,
> >>> Indeed, I have read the incubation proposal guide. The only thing I
>  could
> >>> not figure out is how to recruit a champion.
> >>> However, after re-reading the guide, I missed something. I should
> >> have
> >>> prefixed the subject of the mail with [PROPOSAL]. So I am resending
> >> the
> >>> proposal with the proper subject.
> >>>
> >>>
> >> **
> >>> PROPOSAL
> >>> Abstract
> >>>
> >>> Castafiore framework is a web frameworks, fully component oriented,
>  ajax
> >>> based, one page appplication. Although the framework can be viewed
> >> as a
> >>> classical component oriented web framework like GWT, it has been
>  designed
> >>> and implemented with a particular goal in mind. It is to be able to
>  make
> >>> existing javascript libraries "java-able". Meaning that the
> framework
> >>> allows to easily take a javascript library like e.g jquery ui and
> use
>  the
> >>> components and features via java. The integration of the javascript
> >>> libraries need to be easy and natural.
> >>>
> >>> Actually companies like ext js and smartgwt have made their
> >> components
> >>> "java-able" using GWT. I wish to provide an alternative to gwt that
> >> is
> >> much
> >>> easier, fast, lightweight, and much more productive.
> >>> Proposal
> >>>
> >>> Castafiore framework has been designed and implemented with the
>  follo

Re: Followup to VXQuery July 2013 report

[Marvin Humphrey]

On Thu, Sep 5, 2013 at 2:01 AM, ant elder  wrote:
> To me VXQuery looks like an example of a project being let down by the
> Incubator PMC.

Regardless, they will have to overcome their challenges themselves.

> Similarly with the no releases in 4 years - they've attempted to
> release twice and both times it stalled getting the votes, what they need
> are mentors who can show them whats necessary to push releases and voting
> through the Incubator.

VXQuery received guidance on pushing releases back in July[1].  It seems to
have had no effect[2].

The Incubator is not a hosting service.  If VXQuery wants to be part of
Apache, they must release.

Marvin Humphrey

[1] http://s.apache.org/9Sg
[2] http://s.apache.org/rkn

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Followup to VXQuery July 2013 report

[ant elder]

I don't see the need or point in being so draconian with the poddling
especially given its history, so if you really do want to initiate
retirement discussions if they've not released by their next report
(which is just a few weeks away right?) I'll be voting against it and
will volunteer to be a mentor to help try to keep them alive if they
want to keep trying.

   ...ant


On Thu, Sep 5, 2013 at 3:18 PM, Marvin Humphrey  wrote:
>
> On Thu, Sep 5, 2013 at 2:01 AM, ant elder  wrote:
> > To me VXQuery looks like an example of a project being let down by the
> > Incubator PMC.
>
> Regardless, they will have to overcome their challenges themselves.
>
> > Similarly with the no releases in 4 years - they've attempted to
> > release twice and both times it stalled getting the votes, what they need
> > are mentors who can show them whats necessary to push releases and voting
> > through the Incubator.
>
> VXQuery received guidance on pushing releases back in July[1].  It seems to
> have had no effect[2].
>
> The Incubator is not a hosting service.  If VXQuery wants to be part of
> Apache, they must release.
>
> Marvin Humphrey
>
> [1] http://s.apache.org/9Sg
> [2] http://s.apache.org/rkn
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Aurora for Incubation

[Brian McCallister]

Aurora is aimed at long-running stateless services (like app servers)?

-Brian


On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester wrote:

> Hi All,
>
> We're pleased to share a draft ASF incubation proposal for Aurora, a
> service scheduler used to schedule jobs onto Apache Mesos that we've
> developed at Twitter. Aurora provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter. The complete proposal can be found:
> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
>
> In particular, we'd love to add additional mentors to the project. Your
> feedback is appreciated.
>
> Dave
>
> = Abstract =
>
> Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
>
> = Proposal =
>
> Aurora is a scheduler that provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter.
>
> Aurora builds on top of Apache Mesos and provides common features that
> allow any site to run large scale production applications. While the
> project is currently used in production at Twitter, we wish to develop a
> community to increase contributions and see it thrive in the future.
>
> = Background =
>
> The initial development of Aurora was done at Twitter, and is planned to be
> open sourced. This proposal is for Aurora to join the Apache Incubator.
>
> = Rationale =
>
> While the Apache Mesos core focuses on distributing individual tasks across
> nodes in a cluster, typical services consist of dozens or hundreds of
> replicas of tasks. As a service scheduler, Aurora provides the abstraction
> of a "job" to bundle and manage these tasks. Aurora provides many key
> functionalities centered around a job, including: definition, the concept
> of an instance and the serverset, deployment and scheduling, health
> checking, and introspection. It also allows cross-cutting concerns to be
> handled like observability and log collection.
>
> = Current Status =
>
> == Meritocracy ==
>
> By submitting this incubator proposal, we’re expressing our intent to build
> a diverse developer community around Aurora that will conduct itself
> according to The Apache Way and use meritocratic means of accepting
> contributions. Several members of the Aurora team overlap with Apache
> Mesos, which successfully graduated from the Incubator and has embraced a
> meritocratic model of governance; we plan to follow a similar path forward
> with Aurora and believe that a synergy between both projects will make this
> even easier.
>
> == Community ==
>
> Aurora is currently being used internally at Twitter. By open sourcing the
> project, we hope to extend our contributor base significantly and create a
> vibrant community around the project.
>
> == Core Developers ==
>
> Aurora is currently being developed by a team of seven engineers at
> Twitter.
>
> == Alignment ==
>
> The ASF is a natural choice to host the Aurora project, given the goal of
> open sourcing the project and fostering a community to grow and support the
> software. Additionally, Aurora integrates with Apache Mesos, and Apache
> ZooKeeper for service discovery.
>
> We believe that inclusion within Apache will build stronger ties between
> these projects, and create further alignment between their goals and
> communities.
>
> = Known Risks =
>
> == Orphaned Products ==
>
> The core developers plan to continue working full time on the project, and
> there is very little risk of Aurora being abandoned since it is running
> hundreds of services as part of Twitter’s infrastructure. Additionally,
> members of the Mesos community beyond Twitter have expressed interest in an
> advanced scheduler like Aurora (see “Interested Parties” section); we
> believe that need will drive some of the community involvement necessary
> for the project to incubate successfully.
>
> == Inexperience with Open Source ==
>
> Initial Aurora committers have varying levels of experience using and
> contributing to Open Source projects, however by working with our mentors
> and the Apache community we believe we will be able to conduct ourselves in
> accordance with Apache Incubator guidelines. The close relationship between
> the Aurora team and Apache Mesos means there is an awareness of the
> incubation process and a willingness to embrace The Apache Way.
>
> == Homogenous Developers ==
>
> The initial set of committers are from a single organization, however we
> expect that once approved for incubation the project will attract
> contributors from more organizations. We have already had conversations
> with other companies who have expressed an interest in Aurora.
>
> == Reliance on Salaried Developers ==
>
> Initial Aurora committers are salaried developers at Twitter, however
> shortly after open sourcing the code we plan to diversify the project’s
> core committers and contributors.
>
> == Relationships with Other Apache Products ==
>
> Initially, Aurora has been 

Re: [ANNOUNCE] Ben Hindman as Apache Incubator PMC member!

[Dave Lester]

Congrats, Ben!

On Wed, Sep 4, 2013 at 11:52 AM, Chris Mattmann  wrote:

> Hi Folks,
>
> The IPMC has VOTEd to add Ben Hindman as an Apache Incubator PMC
> member. Welcome Ben!
>
> Please feel free to say a bit about yourself.
>
> Cheers,
> Chris
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Write permission on Wiki

[Michael Joyce]

Hi,
Would it be possible for me to get permissions on the wiki so I can submit
a report?

Username is MichaelJoyce

Thanks much!!

-- Joyce

Re: Write permission on Wiki

[Marvin Humphrey]

On Thu, Sep 5, 2013 at 5:16 PM, Michael Joyce  wrote:

> Would it be possible for me to get permissions on the wiki so I can submit
> a report?
>
> Username is MichaelJoyce

Done.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Jake Farrell joins the Incubator PMC

[David Nalley]

Hi Folks,

The IPMC has VOTEd to add Jake Farrell as an Apache Incubator PMC.

Welcome Jake!

--David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [ANNOUNCE] Jake Farrell joins the Incubator PMC

[Alan D. Cabrera]

Congrats!

Regards,
Alan

On Sep 5, 2013, at 5:54 PM, David Nalley  wrote:

> Hi Folks,
> 
> The IPMC has VOTEd to add Jake Farrell as an Apache Incubator PMC.
> 
> Welcome Jake!
> 
> --David
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Followup to VXQuery July 2013 report

[Till Westmann]

Ant,

I think that everybody in the VXQuery podling would be very happy to have you 
on board as a mentor, even if we manage to release before the next report 
(which I still think we will). 
Please let us know if you would be willing to spend a few cycles helping 
VXQuery.

Thanks,
Till

On Sep 5, 2013, at 7:58 AM, ant elder  wrote:

> I don't see the need or point in being so draconian with the poddling
> especially given its history, so if you really do want to initiate
> retirement discussions if they've not released by their next report
> (which is just a few weeks away right?) I'll be voting against it and
> will volunteer to be a mentor to help try to keep them alive if they
> want to keep trying.
> 
>   ...ant
> 
> 
> On Thu, Sep 5, 2013 at 3:18 PM, Marvin Humphrey  
> wrote:
>> 
>> On Thu, Sep 5, 2013 at 2:01 AM, ant elder  wrote:
>>> To me VXQuery looks like an example of a project being let down by the
>>> Incubator PMC.
>> 
>> Regardless, they will have to overcome their challenges themselves.
>> 
>>> Similarly with the no releases in 4 years - they've attempted to
>>> release twice and both times it stalled getting the votes, what they need
>>> are mentors who can show them whats necessary to push releases and voting
>>> through the Incubator.
>> 
>> VXQuery received guidance on pushing releases back in July[1].  It seems to
>> have had no effect[2].
>> 
>> The Incubator is not a hosting service.  If VXQuery wants to be part of
>> Apache, they must release.
>> 
>> Marvin Humphrey
>> 
>> [1] http://s.apache.org/9Sg
>> [2] http://s.apache.org/rkn
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org