Re: [VOTE] Pig graduation to hadoop subproject
+1 On Oct 6, 2008, at 3:32 PM, Olga Natkovich wrote: Pig Developers and Mentors, Pig has been incubating for over a year now. In this period of time, we had extended our community with 2 new committers, had a release, resolved 300 issues. We have made some significant code improvements including pipeline redesign, addition of streaming and limit functionality, grunt shell improvements and significant performance speedup. We have a constant traffic and lively discussions on both pig-dev and pig-user mailing lists and we conduct our business in the open by publishing proposals and discussing them in the mailing lists. As of now, we have completed graduation requirements as described in http://incubator.apache.org/guides/graduation.html. I would like to call for a graduation vote at this time. I would also propose that we graduate as a subproject of Hadoop. There are several advantages to this approach. First, this would allow us to extend both our user and developer base. Second, it would bring benefits to the Hadoop community by providing a higher level interface and easier entry point for new users. Third, having an established project to provide guidance, would help Pig to become a mature participant in the open source community. Please, vote by the end of the day on Thursday, 10/9. Thanks, Olga PS: I am ccing hadoop and incubator general mailing lists; however, no action is required from them at this time. This step is for Pig community only. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: status of PGP support in Maven
Jason van Zyl wrote: > Noel, your comments are completely out of whack with reality. You are > asking Maven to enforce something that no one does. Pretty much > almost no one. > Checking PGP signatures is obviously not something the vast majority of people do. Really? Try following the instructions at http://www.medibuntu.org/ for adding the repository without adding the PGP key, and see how well it works. Not that I am suggesting a single, centralized, master key for the entire repository. And, again, RedHat takes it so seriously that they shutdown their distribution network when they had even the slightest concern that the signing keys were compromised. If you are saying that we don't have signed packages, I agree with you that more projects should be signing. I have signed JAMES releases for years. But the problem is much worse when using Maven, since users haven't a clue as to the provanance of the artifacts they don't even realize that they are loading onto their systems. In any event, this discussion should be moved to eithe repository@ or [EMAIL PROTECTED] --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: status of PGP support in Maven
Niklas Gustavsson wrote: > Is the idea to do this in the POM or similar? Having something like: Can we please move this discussion to [EMAIL PROTECTED] or [EMAIL PROTECTED] --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: status of PGP support in Maven
The current plugin stores the checksum in a checksum.txt file that sits alongside of the pom.xml in the source code. Doing it in separate file makes adding new checksums a little easier, plus I'm not sure it would be valid to extend the pom XML schema in the way you described. Another reason that putting it in the pom might not be a good idea, is that we also include all the checksums for transitive dependencies that are not explicitly listed in the pom. On Tue, Oct 7, 2008 at 10:13 AM, Niklas Gustavsson <[EMAIL PROTECTED]> wrote: > On Tue, Oct 7, 2008 at 3:21 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: >> Because we would be including the checksum in the source code of the >> project that needs the dependency. > > Is the idea to do this in the POM or similar? Having something like: > >commons-lang >commons-lang >2.3 >ABC...123 > > > /niklas > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
The central repository is not an Apache project's resource. We've always discussed issues of the central repository in private (except for technical details of syncing other project repositories) and as far as policy goes it's the Maven PMC that will sets it. Members can see the list and we're fine with that. We already know what everyone and their uncle wants and it's unlikely a productive discussion will ensue. You just have to look here to see that. We're not wasting our time in endless debate. We'll decide, take feedback, adjust, and move on. We're actually going to setup a group call to discuss the issues on the table. So by next week we'll stuff for people to discuss. As far as Maven development goes, we work like just like every other project, the repository is different and affects every project and organization. What we are deciding is beyond the realm of Apache. On 7-Oct-08, at 11:23 AM, Doug Cutting wrote: Jason van Zyl wrote: The central repository is the Maven PMC's business. What results will be public policy but we'd like to avoid the banter of the misinformed so we can arrive at a decision quickly. I'd love to avoid the banter of the misinformed too, but that's not the way Apache projects are supposed to work, is it? Private lists should only be used for things which cannot be discussed in public, e.g., personnel issues, security breaches, etc. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Allow incubator releases? [was: way too wordy]
Hi All,
FWIW in my experience, the release process is a key driver for a podling
community to get it's collective act together.
On Qpid, we've done 3 major releases now. Until we worked towards the first,
one couldn't guarantee that the code would compile from trunk every day. Our
project really took shape during this process, and it was a good way to
start getting a handle on the Apache Way.
Having a focus, in the shape of a release, is a really useful way to move a
community towards a clear goal. Even better, it forces the podling to agree
targets (JIRAs etc) and work together to achieve them in a bounded way.
The other major plus is that iirc it took about 6 weeks of to+fro on our
first release to get a viable RC out (with all the necessary bits etc). The
process gets easier each time (at least the Apache bits do). On incubator
projects get oversight etc while all this happens and so they get better at
doing it, fairly early on.
In my view, without releases there wouldn't be any podling projects (as
Aidan suggested earlier).
Trust me, there are plenty of incentives to graduate :-)
Hth,
Marnie
On Tue, Oct 7, 2008 at 5:18 PM, Henning Schmiedehausen <
[EMAIL PROTECTED]> wrote:
>
> On Mon, 2008-10-06 at 13:45 -0500, William A. Rowe, Jr. wrote:
> > How about a brand new idea?
> >
> > Lay down a Milestone-style chart of what it takes to operate as an ASF
> > project. Demonstrate community of meritocracy, add committers or ppmc
> > members based on contributions, complete IP review, and then... and only
> > then... they hit the release milestone. One or two releases later, they
> > are ejected from the Incubator - either to the target PMC or as a TLP.
>
> While I like that idea, it is hard for a podling that comes from a
> corporate environment (where the initial committer base is basically a
> development team) to build a developer community without a release.
>
> Giving a podling a defined exit strategy (e.g. "Three incubator
> releases") is nice, but it will be subverted by projects doing "rc,
> alpha and beta" releases ("Oh no, that is not our second release, this
> is 2.0-alpha-1" Which is followed by 2.0-alpha-2 up to 2.0-alpha-8, then
> -beta-1 and so on).
>
> Then again, some podlings could use a kick in their collective ass to do
> at least one release (Hello Shindig).
>
>Ciao
>Henning
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: [Proposal] Kato - mentors needed etc
Steve Poole wrote: > William A. Rowe, Jr. wrote: >> Sonal Goyal wrote: >>> >>> 2. Is it necessary for a mentor to be an Apache member or part of the >>> Incubator PMC? How do I join otherwise ? >> >> There might be a disconnect here in the word Mentor. Mentorship here is >> strictly talking about organizing projects around the ASF development >> and community model. If you want to help, you would just offer to be >> one of the initial contributors (and contributor here doesn't have to >> mean coder - it might be in documentation or design or whatever you have >> to bring to the table.) >> >> Yes, in answer to 2) above, you must be an Incubator PMC member. The only >> candidates really entertained are either already ASF members, or we have >> also voted in IPMC members who have served on a project PMC for some time. >> The idea is that IPMC members are already familiar with how PMCs work at >> the foundation. >> > Thanks Bill. So unfortunately Sonal can not be a mentor for this project. Well, not unfortunate at all; Sonal can definitely be added to the initial list of committers/contributors! Just don't confuse the phrase "Mentoring" as about the code base or the spec. If you are consultative help, you are contributing just like your other peers. The ASF is flat; everyone technologically around a project has parity with their fellow contributors. It's a meritocracy; you contribute, you gain commit access, and then project committee membership, but you remain one contributor among your peers. There are no "team leads" or "project leads". Only people doing things, and people who have stepped back from doing things, at a given time. So we have no technological "mentors" per say. The "Mentors" are there for one reason, to help the project get up to speed about the ASF's processes and meritocracy based development, and graduate the podling as a full-fledged project (or sub-project). If your ASF "Mentor" offers technical advise, it's no more or less valid than any other contributor. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Kato - mentors needed etc
William A. Rowe, Jr. wrote: Sonal Goyal wrote: I am an independent consultant interested in mentoring this project. A few things are not clear to me: 1. The Apache site http://www.apache.org/foundation/how-it-works.html states that a working codebase is essential for incubation. How do we start if we are at the specification level ? 2. Is it necessary for a mentor to be an Apache member or part of the Incubator PMC? How do I join otherwise ? There might be a disconnect here in the word Mentor. Mentorship here is strictly talking about organizing projects around the ASF development and community model. If you want to help, you would just offer to be one of the initial contributors (and contributor here doesn't have to mean coder - it might be in documentation or design or whatever you have to bring to the table.) Yes, in answer to 2) above, you must be an Incubator PMC member. The only candidates really entertained are either already ASF members, or we have also voted in IPMC members who have served on a project PMC for some time. The idea is that IPMC members are already familiar with how PMCs work at the foundation. Thanks Bill. So unfortunately Sonal can not be a mentor for this project. And in answer to 1), no there needs to be no codebase before entering the incubator. Although if theres no plan to produce any code, but only a specification, the http://openwebfoundation.org/ might be a good landing place because it's organized similar to the ASF, but is designated to foster specifications and not concerned with code. Just to be clear IBM is offering to contribute its existing DTFJ code. So there would be an existing working codebase for this project to use as a seed. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Kato - mentors needed etc
Sonal Goyal wrote: > > I am an independent consultant interested in mentoring this project. A > few things are not clear to me: > > 1. The Apache site http://www.apache.org/foundation/how-it-works.html > states that a working codebase is essential for incubation. How do we > start if we are at the specification level ? > > 2. Is it necessary for a mentor to be an Apache member or part of the > Incubator PMC? How do I join otherwise ? There might be a disconnect here in the word Mentor. Mentorship here is strictly talking about organizing projects around the ASF development and community model. If you want to help, you would just offer to be one of the initial contributors (and contributor here doesn't have to mean coder - it might be in documentation or design or whatever you have to bring to the table.) Yes, in answer to 2) above, you must be an Incubator PMC member. The only candidates really entertained are either already ASF members, or we have also voted in IPMC members who have served on a project PMC for some time. The idea is that IPMC members are already familiar with how PMCs work at the foundation. And in answer to 1), no there needs to be no codebase before entering the incubator. Although if theres no plan to produce any code, but only a specification, the http://openwebfoundation.org/ might be a good landing place because it's organized similar to the ASF, but is designated to foster specifications and not concerned with code. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Kato - mentors needed etc
Hi Sonal, On Oct 7, 2008, at 11:25 AM, Sonal Goyal wrote: Hi, I am an independent consultant interested in mentoring this project. Great to hear of your interest in this proposed project. A few things are not clear to me: 1. The Apache site http://www.apache.org/foundation/how-it-works.html states that a working codebase is essential for incubation. How do we start if we are at the specification level ? It's not a hard requirement. Most projects start with a working-but- not-finished code base. It's been shown that an existing code base makes it easier to attract a community, but an existing specification might be sufficient to motivate a community. The response to the proposal is probably a good indicator as to the level of interest. So if you know of others, talk it up and have them participate in this discussion thread. 2. Is it necessary for a mentor to be an Apache member or part of the Incubator PMC? How do I join otherwise ? "Mentor" is an official role in Apache. It's necessary for a Mentor to be part of the existing Apache community and to have experience with "The Apache Way". I assume you're not already an Apache committer. If that's the case, you can participate as a committer if the Kato project is accepted. Best regards, Craig Thanks and Regards, Sonal On Wed, Oct 1, 2008 at 2:23 PM, Steve Poole <[EMAIL PROTECTED]> wrote: A couple of weeks ago I posted the existence of a draft proposal for a new project. (For those of you who missed it it's here -> http://wiki.apache.org/incubator/KatoProposal) I've only had one comment so far, so I'm assuming that either I'm missing something, the proposal is not clear, or (most likely) its not greatly interesting :-) Anyone like to give a novice a helping hand and explain what it is I need to do to stimulate some discussion? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: Graduation Checklist , was Re: [VOTE] Pig graduation to hadoop subproject
Luciano Resende wrote: Have you guys looked at the "Creating an Open and Diverse community" section on the graduation checklist ? Pig wishes to become a subproject of Hadoop, not a TLP. Hadoop's PMC is listed at: http://hadoop.apache.org/who.html Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Kato - mentors needed etc
Hi, I am an independent consultant interested in mentoring this project. A few things are not clear to me: 1. The Apache site http://www.apache.org/foundation/how-it-works.html states that a working codebase is essential for incubation. How do we start if we are at the specification level ? 2. Is it necessary for a mentor to be an Apache member or part of the Incubator PMC? How do I join otherwise ? Thanks and Regards, Sonal On Wed, Oct 1, 2008 at 2:23 PM, Steve Poole <[EMAIL PROTECTED]> wrote: > A couple of weeks ago I posted the existence of a draft proposal for a new > project. > (For those of you who missed it it's here -> > http://wiki.apache.org/incubator/KatoProposal) > > I've only had one comment so far, so I'm assuming that either I'm missing > something, the proposal is not clear, or (most likely) its not greatly > interesting :-) > > Anyone like to give a novice a helping hand and explain what it is I need to > do to stimulate some discussion? > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
Jason van Zyl wrote: The central repository is the Maven PMC's business. What results will be public policy but we'd like to avoid the banter of the misinformed so we can arrive at a decision quickly. I'd love to avoid the banter of the misinformed too, but that's not the way Apache projects are supposed to work, is it? Private lists should only be used for things which cannot be discussed in public, e.g., personnel issues, security breaches, etc. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Pig graduation to hadoop subproject
+1 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2008 6:17 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; general@incubator.apache.org Subject: Re: [VOTE] Pig graduation to hadoop subproject +1 2008/10/7 Santhosh Srinivasan <[EMAIL PROTECTED]> > +1 > > Santhosh > > -Original Message- > From: Olga Natkovich [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2008 3:33 PM > To: [EMAIL PROTECTED] > Cc: general@incubator.apache.org; [EMAIL PROTECTED] > Subject: [VOTE] Pig graduation to hadoop subproject > > Pig Developers and Mentors, > > Pig has been incubating for over a year now. In this period of time, we > had extended our community with 2 new committers, had a release, > resolved 300 issues. We have made some significant code improvements > including pipeline redesign, addition of streaming and limit > functionality, grunt shell improvements and significant performance > speedup. We have a constant traffic and lively discussions on both > pig-dev and pig-user mailing lists and we conduct our business in the > open by publishing proposals and discussing them in the mailing lists. > > As of now, we have completed graduation requirements as described in > http://incubator.apache.org/guides/graduation.html. > > I would like to call for a graduation vote at this time. > > I would also propose that we graduate as a subproject of Hadoop. There > are several advantages to this approach. First, this would allow us to > extend both our user and developer base. Second, it would bring benefits > to the Hadoop community by providing a higher level interface and easier > entry point for new users. Third, having an established project to > provide guidance, would help Pig to become a mature participant in the > open source community. > > Please, vote by the end of the day on Thursday, 10/9. > > Thanks, > > Olga > > PS: I am ccing hadoop and incubator general mailing lists; however, no > action is required from them at this time. This step is for Pig > community only. > -- jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Allow incubator releases? [was: way too wordy]
On Mon, 2008-10-06 at 13:45 -0500, William A. Rowe, Jr. wrote:
> How about a brand new idea?
>
> Lay down a Milestone-style chart of what it takes to operate as an ASF
> project. Demonstrate community of meritocracy, add committers or ppmc
> members based on contributions, complete IP review, and then... and only
> then... they hit the release milestone. One or two releases later, they
> are ejected from the Incubator - either to the target PMC or as a TLP.
While I like that idea, it is hard for a podling that comes from a
corporate environment (where the initial committer base is basically a
development team) to build a developer community without a release.
Giving a podling a defined exit strategy (e.g. "Three incubator
releases") is nice, but it will be subverted by projects doing "rc,
alpha and beta" releases ("Oh no, that is not our second release, this
is 2.0-alpha-1" Which is followed by 2.0-alpha-2 up to 2.0-alpha-8, then
-beta-1 and so on).
Then again, some podlings could use a kick in their collective ass to do
at least one release (Hello Shindig).
Ciao
Henning
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: status of PGP support in Maven
On Tue, Oct 7, 2008 at 3:21 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: > Because we would be including the checksum in the source code of the > project that needs the dependency. Is the idea to do this in the POM or similar? Having something like: commons-lang commons-lang 2.3 ABC...123 /niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
On Tue, Oct 7, 2008 at 3:29 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > Hi Matthias, > > Yeap, no need to rush. Who is responsible for initiating the VOTE mail? It is > ok for me to start a vote begining of the next week. I'd expect it is you :-) Since you are the founder / father of OpenWebBeans :-) -M > > Thanks for clearly explaining what is NDA and what is used for. > > Gurkan > > > > - Original Message > From: Matthias Wessendorf <[EMAIL PROTECTED]> > To: general@incubator.apache.org > Sent: Tuesday, October 7, 2008 11:48:42 AM > Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > > On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >> How to get or sign this NDA to view current draft spec? Is it required to be >> part of the EG? > > no, that is an Apache thing. You need to be committer to sign the NDA. > The NDA on the other hand gives you access to TCK etc. In case of WebBeans... > this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. > > When this project is accepted, you will be an Apache committer and we can > work on the NDA. > > @Vote: You asked about the vote, why not planing to start a vote > beginning of next > week ? This will give some folks some more time to read the proposal > etc. No need > to rush, isn't it ? > > -M > >> >> Gurkan >> >> >> >> - Original Message >> From: Matthias Wessendorf <[EMAIL PROTECTED]> >> To: general@incubator.apache.org >> Sent: Monday, October 6, 2008 10:23:22 PM >> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >> >> I am part of the EG, but I can't share the draft PDFs. >> You need a NDA for that. >> >> -M >> >> On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >>> Hi Kevan, Matthias; >>> >>> The project current code base is in the sourceforge --> >>> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. >>> I am developing the remaining pieces of the specification continuously. >>> >>> About Implementation : So far, only Web Beans specification that is >>> published is EDR-1, in this EDR-1 there is no API contract of the >>> specification. So when I started to implement the specification, I created >>> my own API. But now, I looked at the http://seamframework.org/WebBeans >>> address and it defines the API contracts and some of the concerns explained >>> in the EDR-1 are changed. I am trying to adapted my implemented API >>> contracts with this unpublished API. I explicitly commented on these >>> changes in the source code. I think there is no so much differences. >>> >>> There are two folder in the implementation, webbeans-api is the API and >>> webbeans-impl is the implementation. All the unit test are contained in the >>> webbeans-impl folder. >>> >>> Thanks; >>> >>> Gurkan >>> >>> >>> >>> >>> >>> - Original Message >>> From: Matthias Wessendorf <[EMAIL PROTECTED]> >>> To: general@incubator.apache.org >>> Sent: Monday, October 6, 2008 3:34:34 PM >>> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >>> >>> On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: > Hi to all; > > I have posted a proposal about the project, named OpenWebBeans. > > It is in the WIKI, its address is > http://wiki.apache.org/incubator/OpenWebBeansProposal I made a few minor editorial updates (spelling/grammar) and one wording change "Geronimo will include" ==> "Geronimo may include". Can you point us to the current project? I couldn't find it on sourceforge. Last I recall Guice was planning on an Apache licensed WebBeans implementation. Is that still their plan? Any discussions with their project? >>> >>> really ? Interesting. >>> The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it >>> looks like their TCK will be as well) >>> >>> See here: >>> http://seamframework.org/WebBeans >>> >>> -Matthias >>> --kevan >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > ---
Re: [PROPOSAL - OpenWebBeans Project Proposal]
Hi Matthias, Yeap, no need to rush. Who is responsible for initiating the VOTE mail? It is ok for me to start a vote begining of the next week. Thanks for clearly explaining what is NDA and what is used for. Gurkan - Original Message From: Matthias Wessendorf <[EMAIL PROTECTED]> To: general@incubator.apache.org Sent: Tuesday, October 7, 2008 11:48:42 AM Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > How to get or sign this NDA to view current draft spec? Is it required to be > part of the EG? no, that is an Apache thing. You need to be committer to sign the NDA. The NDA on the other hand gives you access to TCK etc. In case of WebBeans... this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. When this project is accepted, you will be an Apache committer and we can work on the NDA. @Vote: You asked about the vote, why not planing to start a vote beginning of next week ? This will give some folks some more time to read the proposal etc. No need to rush, isn't it ? -M > > Gurkan > > > > - Original Message > From: Matthias Wessendorf <[EMAIL PROTECTED]> > To: general@incubator.apache.org > Sent: Monday, October 6, 2008 10:23:22 PM > Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > > I am part of the EG, but I can't share the draft PDFs. > You need a NDA for that. > > -M > > On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >> Hi Kevan, Matthias; >> >> The project current code base is in the sourceforge --> >> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. >> I am developing the remaining pieces of the specification continuously. >> >> About Implementation : So far, only Web Beans specification that is >> published is EDR-1, in this EDR-1 there is no API contract of the >> specification. So when I started to implement the specification, I created >> my own API. But now, I looked at the http://seamframework.org/WebBeans >> address and it defines the API contracts and some of the concerns explained >> in the EDR-1 are changed. I am trying to adapted my implemented API >> contracts with this unpublished API. I explicitly commented on these changes >> in the source code. I think there is no so much differences. >> >> There are two folder in the implementation, webbeans-api is the API and >> webbeans-impl is the implementation. All the unit test are contained in the >> webbeans-impl folder. >> >> Thanks; >> >> Gurkan >> >> >> >> >> >> - Original Message >> From: Matthias Wessendorf <[EMAIL PROTECTED]> >> To: general@incubator.apache.org >> Sent: Monday, October 6, 2008 3:34:34 PM >> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >> >> On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: >>> >>> On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: >>> Hi to all; I have posted a proposal about the project, named OpenWebBeans. It is in the WIKI, its address is http://wiki.apache.org/incubator/OpenWebBeansProposal >>> >>> I made a few minor editorial updates (spelling/grammar) and one wording >>> change "Geronimo will include" ==> "Geronimo may include". >>> >>> Can you point us to the current project? I couldn't find it on sourceforge. >>> >>> Last I recall Guice was planning on an Apache licensed WebBeans >>> implementation. Is that still their plan? Any discussions with their >>> project? >> >> really ? Interesting. >> The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it >> looks like their TCK will be as well) >> >> See here: >> http://seamframework.org/WebBeans >> >> -Matthias >> >>> >>> --kevan >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: status of PGP support in Maven
On Mon, Oct 6, 2008 at 11:39 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Mon, Oct 6, 2008 at 10:08 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: > >> There are maven plugins that can validate the checksums of 3rd party >> dependencies. > > Uhhh... Call me stupid, but how can checksum solve anything other than > assuring that the download worked?? AFAIK, Maven does not pick up the > checksums from the "authorative" server and validates it against the > mirrored one. Perhaps that has changed since "back then"... And even > then, how hard can it be to get the same 1024/2048/65536/... bit > checksum by modifying that many 'extra' or 'unused' bits? > Because we would be including the checksum in the source code of the project that needs the dependency. I guess I failed to say that the checksum needs to a cryptographic checksum and not one of your CRC variates. That way it's computationally difficult to figure out which bits you need to pad to get the same checksum. So like I said, once you start doing that maven is about as secure as any other build tool that we currently use at the ASF. > > Cheers > Niclas > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
On Tue, 2008-10-07 at 04:51 -0400, James Carman wrote: > A non-disclosure agreement (NDA) is required to be an apache > committer? Since when? No. The other way around. If you want to sign an NDA agreement in relation to gaining access to a TCK or something, you need to be a committer. Only committers are allowed to sign them. That is what is being said. A blanket all committers must sign an NDA would be the death of Apache, eh? Upayavira > On Tue, Oct 7, 2008 at 4:48 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > >> How to get or sign this NDA to view current draft spec? Is it required to > >> be part of the EG? > > > > no, that is an Apache thing. You need to be committer to sign the NDA. > > The NDA on the other hand gives you access to TCK etc. In case of > > WebBeans... > > this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. > > > > When this project is accepted, you will be an Apache committer and we can > > work on the NDA. > > > > @Vote: You asked about the vote, why not planing to start a vote > > beginning of next > > week ? This will give some folks some more time to read the proposal > > etc. No need > > to rush, isn't it ? > > > > -M > > > >> > >> Gurkan > >> > >> > >> > >> - Original Message > >> From: Matthias Wessendorf <[EMAIL PROTECTED]> > >> To: general@incubator.apache.org > >> Sent: Monday, October 6, 2008 10:23:22 PM > >> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > >> > >> I am part of the EG, but I can't share the draft PDFs. > >> You need a NDA for that. > >> > >> -M > >> > >> On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > >>> Hi Kevan, Matthias; > >>> > >>> The project current code base is in the sourceforge --> > >>> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. > >>> I am developing the remaining pieces of the specification continuously. > >>> > >>> About Implementation : So far, only Web Beans specification that is > >>> published is EDR-1, in this EDR-1 there is no API contract of the > >>> specification. So when I started to implement the specification, I > >>> created my own API. But now, I looked at the > >>> http://seamframework.org/WebBeans address and it defines the API > >>> contracts and some of the concerns explained in the EDR-1 are changed. I > >>> am trying to adapted my implemented API contracts with this unpublished > >>> API. I explicitly commented on these changes in the source code. I think > >>> there is no so much differences. > >>> > >>> There are two folder in the implementation, webbeans-api is the API and > >>> webbeans-impl is the implementation. All the unit test are contained in > >>> the webbeans-impl folder. > >>> > >>> Thanks; > >>> > >>> Gurkan > >>> > >>> > >>> > >>> > >>> > >>> - Original Message > >>> From: Matthias Wessendorf <[EMAIL PROTECTED]> > >>> To: general@incubator.apache.org > >>> Sent: Monday, October 6, 2008 3:34:34 PM > >>> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > >>> > >>> On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: > > > Hi to all; > > > > I have posted a proposal about the project, named OpenWebBeans. > > > > It is in the WIKI, its address is > > http://wiki.apache.org/incubator/OpenWebBeansProposal > > I made a few minor editorial updates (spelling/grammar) and one wording > change "Geronimo will include" ==> "Geronimo may include". > > Can you point us to the current project? I couldn't find it on > sourceforge. > > Last I recall Guice was planning on an Apache licensed WebBeans > implementation. Is that still their plan? Any discussions with their > project? > >>> > >>> really ? Interesting. > >>> The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it > >>> looks like their TCK will be as well) > >>> > >>> See here: > >>> http://seamframework.org/WebBeans > >>> > >>> -Matthias > >>> > > --kevan > > > >>> > >>> > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> > >> > >> -- > >> Matthias Wessendorf > >> > >> blog: http://matthiaswessendorf.wordpress.com/ > >> sessions: http://www.slideshare.net/mwessendorf > >> twitter: http://twitter.com/mwessendorf > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >>
Re: [PROPOSAL - OpenWebBeans Project Proposal]
On Tue, Oct 7, 2008 at 10:51 AM, James Carman <[EMAIL PROTECTED]> wrote: > A non-disclosure agreement (NDA) is required to be an apache > committer? Since when? that is my understanding. The NDA to get access to the TCK for instance ? I always thought you need to be a committer. At least in MyFaces we were doing that (to get access to the TCK). I am only talking here about the TCKs, no other (more general) things. -M > > On Tue, Oct 7, 2008 at 4:48 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: >> On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >>> How to get or sign this NDA to view current draft spec? Is it required to >>> be part of the EG? >> >> no, that is an Apache thing. You need to be committer to sign the NDA. >> The NDA on the other hand gives you access to TCK etc. In case of WebBeans... >> this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. >> >> When this project is accepted, you will be an Apache committer and we can >> work on the NDA. >> >> @Vote: You asked about the vote, why not planing to start a vote >> beginning of next >> week ? This will give some folks some more time to read the proposal >> etc. No need >> to rush, isn't it ? >> >> -M >> >>> >>> Gurkan >>> >>> >>> >>> - Original Message >>> From: Matthias Wessendorf <[EMAIL PROTECTED]> >>> To: general@incubator.apache.org >>> Sent: Monday, October 6, 2008 10:23:22 PM >>> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >>> >>> I am part of the EG, but I can't share the draft PDFs. >>> You need a NDA for that. >>> >>> -M >>> >>> On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: Hi Kevan, Matthias; The project current code base is in the sourceforge --> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. I am developing the remaining pieces of the specification continuously. About Implementation : So far, only Web Beans specification that is published is EDR-1, in this EDR-1 there is no API contract of the specification. So when I started to implement the specification, I created my own API. But now, I looked at the http://seamframework.org/WebBeans address and it defines the API contracts and some of the concerns explained in the EDR-1 are changed. I am trying to adapted my implemented API contracts with this unpublished API. I explicitly commented on these changes in the source code. I think there is no so much differences. There are two folder in the implementation, webbeans-api is the API and webbeans-impl is the implementation. All the unit test are contained in the webbeans-impl folder. Thanks; Gurkan - Original Message From: Matthias Wessendorf <[EMAIL PROTECTED]> To: general@incubator.apache.org Sent: Monday, October 6, 2008 3:34:34 PM Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: > >> Hi to all; >> >> I have posted a proposal about the project, named OpenWebBeans. >> >> It is in the WIKI, its address is >> http://wiki.apache.org/incubator/OpenWebBeansProposal > > I made a few minor editorial updates (spelling/grammar) and one wording > change "Geronimo will include" ==> "Geronimo may include". > > Can you point us to the current project? I couldn't find it on > sourceforge. > > Last I recall Guice was planning on an Apache licensed WebBeans > implementation. Is that still their plan? Any discussions with their > project? really ? Interesting. The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it looks like their TCK will be as well) See here: http://seamframework.org/WebBeans -Matthias > > --kevan > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitte
Re: [PROPOSAL - OpenWebBeans Project Proposal]
A non-disclosure agreement (NDA) is required to be an apache committer? Since when? On Tue, Oct 7, 2008 at 4:48 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >> How to get or sign this NDA to view current draft spec? Is it required to be >> part of the EG? > > no, that is an Apache thing. You need to be committer to sign the NDA. > The NDA on the other hand gives you access to TCK etc. In case of WebBeans... > this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. > > When this project is accepted, you will be an Apache committer and we can > work on the NDA. > > @Vote: You asked about the vote, why not planing to start a vote > beginning of next > week ? This will give some folks some more time to read the proposal > etc. No need > to rush, isn't it ? > > -M > >> >> Gurkan >> >> >> >> - Original Message >> From: Matthias Wessendorf <[EMAIL PROTECTED]> >> To: general@incubator.apache.org >> Sent: Monday, October 6, 2008 10:23:22 PM >> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >> >> I am part of the EG, but I can't share the draft PDFs. >> You need a NDA for that. >> >> -M >> >> On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >>> Hi Kevan, Matthias; >>> >>> The project current code base is in the sourceforge --> >>> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. >>> I am developing the remaining pieces of the specification continuously. >>> >>> About Implementation : So far, only Web Beans specification that is >>> published is EDR-1, in this EDR-1 there is no API contract of the >>> specification. So when I started to implement the specification, I created >>> my own API. But now, I looked at the http://seamframework.org/WebBeans >>> address and it defines the API contracts and some of the concerns explained >>> in the EDR-1 are changed. I am trying to adapted my implemented API >>> contracts with this unpublished API. I explicitly commented on these >>> changes in the source code. I think there is no so much differences. >>> >>> There are two folder in the implementation, webbeans-api is the API and >>> webbeans-impl is the implementation. All the unit test are contained in the >>> webbeans-impl folder. >>> >>> Thanks; >>> >>> Gurkan >>> >>> >>> >>> >>> >>> - Original Message >>> From: Matthias Wessendorf <[EMAIL PROTECTED]> >>> To: general@incubator.apache.org >>> Sent: Monday, October 6, 2008 3:34:34 PM >>> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >>> >>> On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: > Hi to all; > > I have posted a proposal about the project, named OpenWebBeans. > > It is in the WIKI, its address is > http://wiki.apache.org/incubator/OpenWebBeansProposal I made a few minor editorial updates (spelling/grammar) and one wording change "Geronimo will include" ==> "Geronimo may include". Can you point us to the current project? I couldn't find it on sourceforge. Last I recall Guice was planning on an Apache licensed WebBeans implementation. Is that still their plan? Any discussions with their project? >>> >>> really ? Interesting. >>> The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it >>> looks like their TCK will be as well) >>> >>> See here: >>> http://seamframework.org/WebBeans >>> >>> -Matthias >>> --kevan >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
On Tue, Oct 7, 2008 at 10:40 AM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > How to get or sign this NDA to view current draft spec? Is it required to be > part of the EG? no, that is an Apache thing. You need to be committer to sign the NDA. The NDA on the other hand gives you access to TCK etc. In case of WebBeans... this shouldn't be a big deal (TCK) since it is actually Apache 2.0 licensed. When this project is accepted, you will be an Apache committer and we can work on the NDA. @Vote: You asked about the vote, why not planing to start a vote beginning of next week ? This will give some folks some more time to read the proposal etc. No need to rush, isn't it ? -M > > Gurkan > > > > - Original Message > From: Matthias Wessendorf <[EMAIL PROTECTED]> > To: general@incubator.apache.org > Sent: Monday, October 6, 2008 10:23:22 PM > Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > > I am part of the EG, but I can't share the draft PDFs. > You need a NDA for that. > > -M > > On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: >> Hi Kevan, Matthias; >> >> The project current code base is in the sourceforge --> >> http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. >> I am developing the remaining pieces of the specification continuously. >> >> About Implementation : So far, only Web Beans specification that is >> published is EDR-1, in this EDR-1 there is no API contract of the >> specification. So when I started to implement the specification, I created >> my own API. But now, I looked at the http://seamframework.org/WebBeans >> address and it defines the API contracts and some of the concerns explained >> in the EDR-1 are changed. I am trying to adapted my implemented API >> contracts with this unpublished API. I explicitly commented on these changes >> in the source code. I think there is no so much differences. >> >> There are two folder in the implementation, webbeans-api is the API and >> webbeans-impl is the implementation. All the unit test are contained in the >> webbeans-impl folder. >> >> Thanks; >> >> Gurkan >> >> >> >> >> >> - Original Message >> From: Matthias Wessendorf <[EMAIL PROTECTED]> >> To: general@incubator.apache.org >> Sent: Monday, October 6, 2008 3:34:34 PM >> Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] >> >> On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: >>> >>> On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: >>> Hi to all; I have posted a proposal about the project, named OpenWebBeans. It is in the WIKI, its address is http://wiki.apache.org/incubator/OpenWebBeansProposal >>> >>> I made a few minor editorial updates (spelling/grammar) and one wording >>> change "Geronimo will include" ==> "Geronimo may include". >>> >>> Can you point us to the current project? I couldn't find it on sourceforge. >>> >>> Last I recall Guice was planning on an Apache licensed WebBeans >>> implementation. Is that still their plan? Any discussions with their >>> project? >> >> really ? Interesting. >> The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it >> looks like their TCK will be as well) >> >> See here: >> http://seamframework.org/WebBeans >> >> -Matthias >> >>> >>> --kevan >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
How to get or sign this NDA to view current draft spec? Is it required to be part of the EG? Gurkan - Original Message From: Matthias Wessendorf <[EMAIL PROTECTED]> To: general@incubator.apache.org Sent: Monday, October 6, 2008 10:23:22 PM Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] I am part of the EG, but I can't share the draft PDFs. You need a NDA for that. -M On Mon, Oct 6, 2008 at 8:27 PM, Gurkan Erdogdu <[EMAIL PROTECTED]> wrote: > Hi Kevan, Matthias; > > The project current code base is in the sourceforge --> > http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. > I am developing the remaining pieces of the specification continuously. > > About Implementation : So far, only Web Beans specification that is > published is EDR-1, in this EDR-1 there is no API contract of the > specification. So when I started to implement the specification, I created my > own API. But now, I looked at the http://seamframework.org/WebBeans address > and it defines the API contracts and some of the concerns explained in the > EDR-1 are changed. I am trying to adapted my implemented API contracts with > this unpublished API. I explicitly commented on these changes in the source > code. I think there is no so much differences. > > There are two folder in the implementation, webbeans-api is the API and > webbeans-impl is the implementation. All the unit test are contained in the > webbeans-impl folder. > > Thanks; > > Gurkan > > > > > > - Original Message > From: Matthias Wessendorf <[EMAIL PROTECTED]> > To: general@incubator.apache.org > Sent: Monday, October 6, 2008 3:34:34 PM > Subject: Re: [PROPOSAL - OpenWebBeans Project Proposal] > > On Mon, Oct 6, 2008 at 2:30 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: >> >> On Oct 3, 2008, at 4:48 PM, Gurkan Erdogdu wrote: >> >>> Hi to all; >>> >>> I have posted a proposal about the project, named OpenWebBeans. >>> >>> It is in the WIKI, its address is >>> http://wiki.apache.org/incubator/OpenWebBeansProposal >> >> I made a few minor editorial updates (spelling/grammar) and one wording >> change "Geronimo will include" ==> "Geronimo may include". >> >> Can you point us to the current project? I couldn't find it on sourceforge. >> >> Last I recall Guice was planning on an Apache licensed WebBeans >> implementation. Is that still their plan? Any discussions with their >> project? > > really ? Interesting. > The "JBoss WebBeans RI" is Apache 2.0 licensed as well (and it > looks like their TCK will be as well) > > See here: > http://seamframework.org/WebBeans > > -Matthias > >> >> --kevan >> >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Pig graduation to hadoop subproject
+1 Daniel - Original Message - From: "Olga Natkovich" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: ; <[EMAIL PROTECTED]> Sent: Monday, October 06, 2008 6:32 PM Subject: [VOTE] Pig graduation to hadoop subproject Pig Developers and Mentors, Pig has been incubating for over a year now. In this period of time, we had extended our community with 2 new committers, had a release, resolved 300 issues. We have made some significant code improvements including pipeline redesign, addition of streaming and limit functionality, grunt shell improvements and significant performance speedup. We have a constant traffic and lively discussions on both pig-dev and pig-user mailing lists and we conduct our business in the open by publishing proposals and discussing them in the mailing lists. As of now, we have completed graduation requirements as described in http://incubator.apache.org/guides/graduation.html. I would like to call for a graduation vote at this time. I would also propose that we graduate as a subproject of Hadoop. There are several advantages to this approach. First, this would allow us to extend both our user and developer base. Second, it would bring benefits to the Hadoop community by providing a higher level interface and easier entry point for new users. Third, having an established project to provide guidance, would help Pig to become a mature participant in the open source community. Please, vote by the end of the day on Thursday, 10/9. Thanks, Olga PS: I am ccing hadoop and incubator general mailing lists; however, no action is required from them at this time. This step is for Pig community only. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Pig graduation to hadoop subproject
+1 2008/10/7 Santhosh Srinivasan <[EMAIL PROTECTED]> > +1 > > Santhosh > > -Original Message- > From: Olga Natkovich [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2008 3:33 PM > To: [EMAIL PROTECTED] > Cc: general@incubator.apache.org; [EMAIL PROTECTED] > Subject: [VOTE] Pig graduation to hadoop subproject > > Pig Developers and Mentors, > > Pig has been incubating for over a year now. In this period of time, we > had extended our community with 2 new committers, had a release, > resolved 300 issues. We have made some significant code improvements > including pipeline redesign, addition of streaming and limit > functionality, grunt shell improvements and significant performance > speedup. We have a constant traffic and lively discussions on both > pig-dev and pig-user mailing lists and we conduct our business in the > open by publishing proposals and discussing them in the mailing lists. > > As of now, we have completed graduation requirements as described in > http://incubator.apache.org/guides/graduation.html. > > I would like to call for a graduation vote at this time. > > I would also propose that we graduate as a subproject of Hadoop. There > are several advantages to this approach. First, this would allow us to > extend both our user and developer base. Second, it would bring benefits > to the Hadoop community by providing a higher level interface and easier > entry point for new users. Third, having an established project to > provide guidance, would help Pig to become a mature participant in the > open source community. > > Please, vote by the end of the day on Thursday, 10/9. > > Thanks, > > Olga > > PS: I am ccing hadoop and incubator general mailing lists; however, no > action is required from them at this time. This step is for Pig > community only. > -- jim
RE: [VOTE] Pig graduation to hadoop subproject
+1 Santhosh -Original Message- From: Olga Natkovich [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2008 3:33 PM To: [EMAIL PROTECTED] Cc: general@incubator.apache.org; [EMAIL PROTECTED] Subject: [VOTE] Pig graduation to hadoop subproject Pig Developers and Mentors, Pig has been incubating for over a year now. In this period of time, we had extended our community with 2 new committers, had a release, resolved 300 issues. We have made some significant code improvements including pipeline redesign, addition of streaming and limit functionality, grunt shell improvements and significant performance speedup. We have a constant traffic and lively discussions on both pig-dev and pig-user mailing lists and we conduct our business in the open by publishing proposals and discussing them in the mailing lists. As of now, we have completed graduation requirements as described in http://incubator.apache.org/guides/graduation.html. I would like to call for a graduation vote at this time. I would also propose that we graduate as a subproject of Hadoop. There are several advantages to this approach. First, this would allow us to extend both our user and developer base. Second, it would bring benefits to the Hadoop community by providing a higher level interface and easier entry point for new users. Third, having an established project to provide guidance, would help Pig to become a mature participant in the open source community. Please, vote by the end of the day on Thursday, 10/9. Thanks, Olga PS: I am ccing hadoop and incubator general mailing lists; however, no action is required from them at this time. This step is for Pig community only. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: status of PGP support in Maven
Niclas Hedhman wrote: > On Mon, Oct 6, 2008 at 10:08 PM, Hiram Chirino <[EMAIL PROTECTED]> wrote: > >> There are maven plugins that can validate the checksums of 3rd party >> dependencies. > > Uhhh... Call me stupid, but how can checksum solve anything other than > assuring that the download worked?? AFAIK, Maven does not pick up the > checksums from the "authorative" server and validates it against the > mirrored one. Perhaps that has changed since "back then"... And even > then, how hard can it be to get the same 1024/2048/65536/... bit > checksum by modifying that many 'extra' or 'unused' bits? You're not stupid[1][2]. Practically speaking, SHA384++ are still "strong enough" but as you point out, unless the checksum values are taken from a trusted[3][4] reference server separate from the distribution server, immune from mitm channels. All of this is simply idle chatter until a repository server is compromised at which point half will be scolding the other half "I told you so". But none of this has anything to do with "Incubator" best practices, unless you want to prohibit incubator projects from assembling releases from Maven. [1] http://en.wikipedia.org/wiki/Md5#Vulnerability [2] http://en.wikipedia.org/wiki/Sha1#Cryptanalysis_and_validation [3] http://www.apache.org/info/20010519-hack.html [4] http://news.cnet.com/8301-1009_3-10023565-83.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Allow incubator releases? [was: way too wordy]
Niclas Hedhman wrote: > On Tue, Oct 7, 2008 at 2:45 AM, William A. Rowe, Jr. > <[EMAIL PROTECTED]> wrote: > >> How about a brand new idea? >> >> Lay down a Milestone-style chart of what it takes to operate as an ASF >> project. Demonstrate community of meritocracy, add committers or ppmc >> members based on contributions, complete IP review, and then... and only >> then... they hit the release milestone. One or two releases later, they >> are ejected from the Incubator - either to the target PMC or as a TLP. >> >> So releases would reflect the project is probably ready to graduate, the >> only difference would be that the incubator PMC wants to see this done >> right before calling the podling baked. > > Works for me, although you say nothing about whether that release is > an ASF release or not. IMHO, it is an Incubator PMC release, just like > any other PMC operated umbrella project. ;-) Right - I pointed out earlier that it's a binary condition at the ASF, either released or not released. I'm not even picky if they would rather release an alpha or beta (not a bad idea if they followed your org.apache.incubator.foo naming convention) or wanted to call it a GA/Gold release. That wasn't my point, it was simply that ratifying their release would be the "last checkmark" on the steps to graduation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
