Re: [VOTE] Graduate WebWork 2 to Apache Struts
On May 2, 2006, at 7:06 PM, Don Brown wrote: On 5/2/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote: Don, "All those issues have been resolved, but are not listed specifically in that status page." Please do. And have all of Martin's issues also been cleared? I added the specific IP tasks we accomplished. As I later in that thread, I indicated all Martin's issues were resolved, or I assure you, we wouldn't be having this conversation :) Also, I saw a lot of contention on the mailing list last month. Anything to worry about vis-a-vis the WebWork community joining the ASF? I'm not sure what contention you are referring to. The WebWork developers have jumped right in fixing bugs, participating in design discussions, and fitting right in. We do have some trolls that like to try to stir things up, but we've had those since Shale was born :) I should note that the Struts PMC vote did include +1's from all mentors: Ted, Martin, and myself. Don Other than Noel's comments about community, and whether it's ready, I vote +1. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Board Report, April 2006
On 4/25/06, Justin Erenkrantz <[EMAIL PROTECTED]> wrote: Comments inline. On 4/22/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > It appears that Felix may apply for TLP status at the May Board meeting. Look forward to it. > ActiveMQ ... > Currently working to accept a donation from Amazon for the ActiveMQ C++ API I assume that there'll be a software grant filed for this? The software grant had been faxed and UPS'd some time go - we've been waiting patiently for it to show up in grants.txt before going ahead and using the code. Today I notice its now on file - yay! So we will commence using the software soon. -- James --- http://radio.weblogs.com/0112098/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Contributing and Starting A New Project With Apache
May be my last mail was misdirected. Request please go through my email below and respond. -- Forwarded message -- From: Suman Ray <[EMAIL PROTECTED]> Date: May 3, 2006 2:28 AM Subject: Contributing and Starting A New Project With Apache To: [EMAIL PROTECTED] Hi, Let me introduce myself. I am Suman Ray.Over a period of 11 years in IT industry, I spend quiet a good amount of years in implementing solutions in financial messaging, payments STP, anti-money laundering and investment banking. Delivering, architecting and implementing projects involving complex enterprise application integration is my core arena. I recently came across an RFP from OMG ( http://www.omg.org/cgi-bin/doc?finance/2005-11-01) . I want to start an open source project which may contribute towards solving the business problem as stated in the RFP. Can you please share with me how I may start a project with ASF. To share, 1 > I am not an ASF member and had not contributed earlier in any projects of ASF. I don't know any members of ASF so that they may invite me to open the project or join in ASF. 2 > I will be favoured if you list down simple steps which would help me to start this open source project. Is it so that I need to submit a working code base before the projects start ? In case my above statements does not sound good to answer my queries request to please ask more informations you want. Thanks for your time. regards Suman Ray
Re: Contributing and Starting A New Project With Apache
Hi, My understanding is that the Apache incubator accepts outside projects if they are already in a working shape and have a developer and user community around them (although I think the community part is something that is not a condition for entering the incubator, but is required for graduation, as is often the case with open sourced commercial products). For the list of criteria that the incubator looks at you may browse through existing accepted proposals: http://wiki.apache.org/incubator/ As for how you can start, you may register a project on SourceForge or a similar free open source dev site and start developing it there using Apache license. This is the most straightforward way to learn how the open source process works and to build a community around the code. Also I think you did the right thing posting your idea here, as this way you may find supporters from within Apache. Cheers, Andrus On May 3, 2006, at 2:57 PM, Suman Ray wrote: May be my last mail was misdirected. Request please go through my email below and respond. -- Forwarded message -- From: Suman Ray <[EMAIL PROTECTED]> Date: May 3, 2006 2:28 AM Subject: Contributing and Starting A New Project With Apache To: [EMAIL PROTECTED] Hi, Let me introduce myself. I am Suman Ray.Over a period of 11 years in IT industry, I spend quiet a good amount of years in implementing solutions in financial messaging, payments STP, anti-money laundering and investment banking. Delivering, architecting and implementing projects involving complex enterprise application integration is my core arena. I recently came across an RFP from OMG ( http://www.omg.org/cgi-bin/doc?finance/2005-11-01) . I want to start an open source project which may contribute towards solving the business problem as stated in the RFP. Can you please share with me how I may start a project with ASF. To share, 1 > I am not an ASF member and had not contributed earlier in any projects of ASF. I don't know any members of ASF so that they may invite me to open the project or join in ASF. 2 > I will be favoured if you list down simple steps which would help me to start this open source project. Is it so that I need to submit a working code base before the projects start ? In case my above statements does not sound good to answer my queries request to please ask more informations you want. Thanks for your time. regards Suman Ray - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Contributing and Starting A New Project With Apache
> My understanding is that the Apache incubator accepts outside > projects if they are already in a working shape and have a > developer and user community around them The Incubator accepts projects if our Members commit to helping to mentor them. No Member support, no project. Member support, project. Pretty much as basic as that, when it comes down to it. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Contributing and Starting A New Project With Apache
Fair enough. This is not the first time I am misinterpreting a procedural issue. Things are confusing at times here... Andrus On May 3, 2006, at 7:03 PM, Noel J. Bergman wrote: My understanding is that the Apache incubator accepts outside projects if they are already in a working shape and have a developer and user community around them The Incubator accepts projects if our Members commit to helping to mentor them. No Member support, no project. Member support, project. Pretty much as basic as that, when it comes down to it. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Contributing and Starting A New Project With Apache
Andrus Adamchik wrote: > Fair enough. This is not the first time I am misinterpreting a > procedural issue. Things are confusing at times here... :) And there may even be something somewhere that says what you said, but when you cut through to the bottom line, it really is a simple approach. If we have Members who commit to Mentor something, we are pretty much going to do it, else we won't. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[STATUS] (incubator) Wed May 3 23:58:09 2006
APACHE INCUBATOR PROJECT STATUS: -*-indented-text-*- Last modified at [$Date: 2006-02-05 04:40:19 -0500 (Sun, 05 Feb 2006) $] Web site: http://Incubator.Apache.Org/ Wiki page: http://wiki.apache.org/incubator/ [note: the Web site is the 'official' documentation; the wiki pages are for collaborative development, including stuff destined for the Web site.] Pending Issues == o We need to be very very clear about what it takes to be accepted into the incubator. It should be a very low bar to leap, possibly not much more than 'no problematic code' and the existence of a healthy community (we don't want to become a dumping ground). o We need to be very very clear about what it takes for a podling to graduate from the incubator. The basic requirements obviously include: has a home, either as part of another ASF project or as a new top-level project of its own; needs to be a credit to the ASF and function well in the ASF framework; ... See also: https://issues.apache.org/jira/browse/INCUBATOR Resolved Issues === o The policy documentation does not need ratification of changes if there seems consensus. Accordingly, the draft status of these documents can be removed and we will use the lazy "commit first, discuss later" mode common across the ASF for documentation (http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=517190) o Coming up with a set of bylaws for the project (http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=517190) o All projects under incubation must maintain a status Web page that contains information the PMC needs about the project. (http://incubator.apache.org/guides/website.html) o Projects under incubation should display appropriate "disclaimers" so that it is clear that they are, indeed, under incubation (http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=504543) o Clearly and authoritatively document how to edit, generate, and update the Web site (three separate functions) (http://incubator.apache.org/guides/website.html). The Incubation Process == TODO: this does not belong in the STATUS file and probably was integrated into other documentation a while ago. That should be double-checked and then this section should be removed. This tries to list all the actions items that must be complete for a project before it can graduate from the incubator. It is probably incomplete. Identify the project to be incubated: -- Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. -- If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. -- If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. -- If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted. Interim responsibility: -- Who has been identified as the mentor for the incubation? -- Are they tracking progress on the "project status" Web page? Copyright: -- Have the papers that transfer rights to the ASF been received? It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. -- Have the files been updated to reflect the new ASF copyright? Verify distribution rights: -- For all code included with the distribution that is not under the Apache license, do we have the right to combine with Apache-licensed code and redistribute? -- Is all source code distributed by the project covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms? Establish a list of active committers: -- Are all active committers listed in the "project status" file? -- Do they have accounts on cvs.apache.org? -- Have they submitted a contributors agreement? Infrastructure: -- CVS modules created and committers added to avail file? -- Mailing lists set up and archived? -- Problem tracking system (Bugzilla)? -- Has the project migrated to our infrastructure? Collaborative Development: -- Have all of the active long-term volunteers been identified and acknowledged as committers on the project? -- Are there three or more independent committers? [The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, s
