Re: [REPORTS DUE] Status reports of Incubating Projects
Nicola Ken Barozzi wrote: The Incubator project board report is due in a bit more than a week, as the board meeting should take place on Wed, 21 Jan 2004, 10am Pacific [1]. Thus all Mentors should ensure that every Incubating Project sends in their project report during this week, so that we have time to review it and see if anything has to be presented to the board. Just a final reminder before I send in the Incubator board report next morning CET. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Import jUDDI archives from SourceForge.net lists to Apache?
Title: Import jUDDI archives from SourceForge.net lists to Apache? jUDDI's been around quite a while now and we've got a couple years of list activity for both the juddi-user and juddi-dev lists archived at SourceForge.net. I can obtain these in mbox file format ... would it be possible to import this into the current archives at Apache? We're asking because we've received a few requests for this from the jUDDI user base. MARC did it for us but it would be great if all that history was available via the Apache archives as well. Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS DUE] Status reports of Incubating Projects
Nicola Ken Barozzi wrote: Just a final reminder before I send in the Incubator board report next morning CET. Below you find the JaxMe status file. In a private discussion the PPMC members have expressed their opinion, that the tasks required for incubation are performed and we would like to request graduation to ws.apache.org. Questions: - Any reasons that prevent graduation? - If not: What is required to start the vote on [EMAIL PROTECTED] Is an informal mail sufficient or do we need a vote from the PPMC first that triggers the actual vote? Jochen !!!JaxMe Project Incubation status This page tracks the project status, incubator-wise. Items marked __DONE__ have been completed. !!!Project Website The website for JaxMe is at http://ws.apache.org/jaxme/ !!!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. On 20-Dec-2003 we have checked for the name JaxMe on www.nameprotect.com using the free online research form. The domain name search found the following names, none of which seems to be in conflict: jaxmed.com jaxmetro.(com|net) jaxmetals.com jaxmeier.com jaxmerc.com jaxmedicalinjury.com jaxmediator.com jaxmedal.com jaxmetrolive.com jaxmedical.com jaxmedia.com jaxmediaweb.com jaxmenusonline.com jaxmetroforddealers.com jaxmenus.com jaxmedicalpractice.com jaxmetal.com jaxmediaonline.com jaxmetroford.com ajaxmetal.com viajaxmenos.com ajaxmedia.com ajaxmetalstamping.com krackerjaxmedia.com Search for US federal or canadian trademarks found no results. DONE *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. See http://marc.theaimsgroup.com/?t=10619838661&r=1&w=2 __DONE__ !!!Interim responsibility *Who has been identified as the shepherd for the incubation? Davanum Srinivas, [EMAIL PROTECTED] __DONE__ *Are they tracking progress? Progress is tracked in incubator/site/projects/jaxme.cwiki __DONE__ !!!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. According to [jaxme/JaxMe2/docs/Design.html|http://cvs.sourceforge.net/viewcvs.py/*checkout*/jaxme/JaxMe2/docs/Design.html?rev=1.6#pastvotes] the ASF is the legal owner of all sources that have been checked in initially. New code and updates are produces by committers only who have signed a CLA. __DONE__ *Have the files been updated to reflect the new ASF copyright? All Java source files have an ASF copyright notice included. __DONE__ 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? The distribution includes the JaxMe jar files and the following files: ant.jar (Ant) junit.jar (Jakarta JUnit) log4j.jar (Jakarta Log4J) xercesImpl.jar (XML Xerces) xml-apis.jar xmldb-api-*.jar (XML Xindice) Proper license files are also included. The build process (test case) depends on hsqldb.jar, which is not included in the distribution, for license issues. __DONE__ *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? __DONE__ !!!Establish a list of active committers *Are all active committers in the STATUS file? Active committers are: Davanum Srinivas, [EMAIL PROTECTED] Jochen Wiedmann, [EMAIL PROTECTED] Ias, [EMAIL PROTECTED] Inactive committers are: Robert Burell Donkin, [EMAIL PROTECTED] __DONE__ -*Do they have accounts on cvs.apache.org? Yes __DONE__ *Have they submitted a contributors agreement? Yes __DONE__ !!!Infrastructure *CVS modules created and committers added to avail file? The CVS module is ws-jaxme and in active use. __DONE__ *Mailing lists set up and archived? The mailing list is [EMAIL PROTECTED] It receives notifications from CVS and Bugzilla. Mailing list is archived in Eyebrowse and on marc.theaimsgroup.com. __DONE__ *Problem tracking system (Bugzilla)? Bugzilla is up and running, a project ws-jaxme and associated components have been created. __DONE__ *Has the project migrated to our infrastructure? See above. __DONE__ !!!Collaborative Development *Have all of the active long-term volunteers been identified and acknowledged as committers on the project? All active committers and contributors of JaxMe 2 (sf.net) are now active committers on ws-jaxme. There are active committers left which a
[status report] Directory Project
Nicola, Here's our status report for the Directory Project according to the format you have specified: 1). Is the STATUS file up to date? No we need to work on this as well as our site documentation. Here's the link to the status file: http://cvs.apache.org/viewcvs.cgi/incubator/site/projects/directory.cwiki 2). Any legal, cross-project or personal issues that still need to be addressed? None. 3). What has been done for incubation since the last report? * Code transferred from LDAPd project CVS repositiory at source forge to the Apache subversion repository. * Packages changed and license information updated for Apache 1.1 License * IANA number for the LDAPd Group transfered to Apache. The ASF wide IANA number now and forever is 18060 and can be looked up in the IANA enterprise number listing here: http://www.iana.org/assignments/enterprise-numbers * Naming commons moved from the jakarta CVS repository to directory subversion repository. * Added Brett Porter and Vince Tence to the team. * Taking on some security written by Vince from his AAA endeavors. 4). Plans and expectations for the next period? * Add Vince Tence to the group along with security code * Complete at a bare minimum a simple site about us and our goals * Bring status file upto date * Complete documentation on existing Eve code base to make it easier to attract and inform new developers coming on board. * Complete clean up and reorg of SVN repo for Eve code base. 5). Any recommendations for how incubation could run more smoothly for you? Feed back on how the project is going from the incubator would be greatly appreciated. We don't have a good health meter for the project. Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS DUE] Status reports of Incubating Projects
Jochen Wiedmann wrote: Questions: - Any reasons that prevent graduation? from looking at your status file, no :D - If not: What is required to start the vote on [EMAIL PROTECTED] Is an informal mail sufficient or do we need a vote from the PPMC first that triggers the actual vote? what does the PPMC think? If the PPMC thinks that it needs to vote it should. IMHO, the PPMC needs to agree but I'm not sure a vote for that is needed: it seems you're already in agreement. Other than that... we have a rule that the Incubator PMC must vote on the release, and the PMC further agrees that vote should be on [EMAIL PROTECTED] No other rules exist. Do you think we need one? What's usually the case at apache is that anyone who's actively involved with something can start a vote. Take some time to gauge general opinion, and if things seem in order, get the mentor to summarize things, present an argument, run and tally the vote, etc. -- cheers, - Leo Simons - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RT] How to graduate
Preface --- Since there were some questions lately, here's some of my thoughts about what projects in incubation should be doing to graduate. We haven't graduated that many projects before, so what exactly it entails is not set in stone. Nor do I think it will be anytime soon, as setting things in stone is hard work! When are you ready? --- Before you graduate, you need to be confident... * ...that the people tracking your progress actively get an idea of what you're up to (and have gotten a chance to point you at some i's to dot and t's to cross). You need to get the feeling there's a consensus around the incubator that you're ready. * ...in your own abilities to function well within apache without the help of the incubator. If you don't know yet what all that entails, you're not ready. * ...that your status file reflects reality, that everyone involved agrees on its contents, and that there are no action items left. * ...that you've followed all parts of the incubation procedure (and where they're vague, the intentions behind them) and that you know what to do upon graduation, procedure-wise. * ...that everyone actively involved with the project (committers, (P)PMC members, mentors, ...) agrees that the project is ready for graduation. If you're confident in all of this, you're likely ready to graduate. If you're not, it's probably not very likely the PMC will be :D The Actual Graduation Procedure --- The important formal part is that the Incubator PMC votes (which happens according to the 'standard' apache policy of simple majority on non-technical votes, a roughly 72 hour voting period unless someone requests otherwise, etc; the vote is done on the [EMAIL PROTECTED] list and non-PMC members are welcome to express their opinion) on the project graduation. In order to make the vote go smoothly, talk about it before you actually hold one, include a summary of all important info in the call to vote, including links to status files, significant reports or bits of info, etc etc. Basically, the standard "common sense" applies. And if you're a graduation candidate, you should know what that common sense is, actually :D Once the vote passes, tally the result, move the status file to the succes subdirectory, update links, update website, post a vote summary, announce the happy news to the appropriate lists, notify the appropriate pmc, take care of any infrastructural things that need to happen (subdomain config for a TLP, for example), and do other things that need doing (if you don't know what those are, see above). Besides those hopefully rather obvious things, a new TLP requires a board resolution, which requires a basic project charter, a list of PMC members, a proposal for a PMC chair, and probably some nice and formal words just for fun. You can find examples in the board meeting minutes (http://www.apache.org/foundation/board/calendar.html). You will probably want a PPMC vote on the draft resolution before you submit it to the board. It's your own responsibility The PMC is not likely to decide on its own that you should graduate, nor is it likely to take the neccessary steps to make it happen. You should take those steps and ask the PMC to decide when you think they will decide in favour. The PMC is not for "doing" things, just for oversight and approval. Regardless of the fact, of course, that there are lots of people on the PMC who do things (like write this e-mail :D), it's not what the PMC does. ASF projects do self-management...and once you are managing yourself, the Incubator PMC will probably be very happy to transfer responsibility. Disclaimer -- This is just my understanding of basic procedures and my own opinion. It's not representative of an "official" PMC or board opinion or decision. Also, don't wait for official positions, opinions, or decisions. We're not laywers, so we don't do a lot of things "officially" if we don't really need to. Just take a look at what people have said, what consensus seems to be, etc. Moreover, take a look at what *you* think. -- cheers, - Leo Simons - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Status Report for Geronimo
Apologies for the last minute update. Status report for the Incubator Geronimo Project * is the STATUS file up to date? (also post link) Yes /home/cvs/incubator/site/projects/geronimo.cwiki * any legal, cross-project or personal issues that still need to be addressed? A serious legal issue was raised by JBoss Group LLC in a letter dated 10/31/2003. This issue has been thoroughly investigated and the conclusion of the community is that the issues raised in the letter are unfounded. A question has arisen whether it is permissible to include XML Schema documents for J2EE deployment descriptors in CVS. We have raised the issue with Sun and are awaiting a response. * what has been done for incubation since the last report? The establishment of a PPMC has aided the organization of the project. Added Gianny D'Amour as committer. The community voted to keep the name "Geronimo" The ASF has become a J2EE licensee, allowing us to start the certification process. * plans and expectations for the next period? To start testing with the J2EE TCK. To work with the Incubator PMC to provide an interim release allowing people to use Geronimo without building from source making it available to a larger community. To address any remaining issues before applying to leave the Incubator. * any recommendations for how incubation could run more smoothly for you? The establishment of the PPMC has been a great help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
