Re: [VOTE] Graduate Buildr as TLP
+1 it is great project Carl. Luciano Resende wrote: [X] +1 Approve graduation of Buildr as a Top-Level Project (non-binding) On Mon, Nov 10, 2008 at 11:54 AM, Niklas Gustavsson [EMAIL PROTECTED] wrote: On Thu, Nov 6, 2008 at 6:03 PM, Alex Boisvert [EMAIL PROTECTED] wrote: [X] +1 Approve graduation of Buildr as a Top-Level Project Non binding. /niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
On Nov 10, 2008, at 2:44 PM, Jan Lehnardt wrote: [ ] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. +1, go go gO GO! Dw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
+1 Craig On Nov 8, 2008, at 6:17 AM, Jan Lehnardt wrote: Dear Incubator General List, dear IPMC, thank you all for your comments on whether CouchDB should graduate from the Incubator to a top level project. I think we have your support. On behalf of the Apache CouchDB PPMC I am now calling a vote: [ ] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. [ ] No, CouchDB is not yet ready, it should stay in the Incubator. Thank you. Cheers Jan -- On Nov 3, 2008, at 18:19, Jan Lehnardt wrote: Dear Incubator General List, The community and developers of Apache CouchDB deem the project ready for graduation to a top level Apache project. [EMAIL PROTECTED] vote summary: http://mail-archives.apache.org/mod_mbox/incubator-couchdb-dev/200810.mbox/[EMAIL PROTECTED] Message IDs for informal(*) PPMC vote to appoint Damien Katz to become Vice President, CouchDB: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] (* Sorry we didn't to a formal vote and hence no formal [RESULT] message) -- We would like to ask the IPMC to discuss the following Board resolution to be recommended to the Board. Once your feedback is collected and integrated, we will ask you to vote on the final resolution. Thank you! -- Proposed Board Resolution: Establish the Apache CouchDB project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software implementing a distributed, fault- tolerant and schema-free document-oriented database for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CouchDB Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CouchDB Project be and hereby is responsible for the creation and maintenance of software related to implementing a distributed, fault-tolerant and schema-free document-oriented database; and be it further RESOLVED, that the office of Vice President, CouchDB be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache CouchDB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CouchDB Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CouchDB Project: * J Chris Anderson ([EMAIL PROTECTED]) * Damien Katz ([EMAIL PROTECTED]) * Christopher Lenz ([EMAIL PROTECTED]) * Jan Lehnardt ([EMAIL PROTECTED]) * Noah Slater ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Damien Katz be appointed to the office of Vice President, CouchDB, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache CouchDB Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the CouchDB Project; and be it further RESOLVED, that the initial Apache CouchDB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CouchDB podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator CouchDB podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Again, thanks for your cooperation! For the Apache CouchDB PPMC, Jan -- PS: Thanks to Noah Slater for proofreading. - 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: [VOTE] Graduate Buildr as TLP
+1 Craig On Nov 6, 2008, at 9:03 AM, Alex Boisvert wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a votehttp://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.html to gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate 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: [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
+1 On Sat, Nov 8, 2008 at 6:17 AM, Jan Lehnardt [EMAIL PROTECTED] wrote: Dear Incubator General List, dear IPMC, thank you all for your comments on whether CouchDB should graduate from the Incubator to a top level project. I think we have your support. On behalf of the Apache CouchDB PPMC I am now calling a vote: [ ] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. [ ] No, CouchDB is not yet ready, it should stay in the Incubator. Thank you. Cheers Jan -- On Nov 3, 2008, at 18:19, Jan Lehnardt wrote: Dear Incubator General List, The community and developers of Apache CouchDB deem the project ready for graduation to a top level Apache project. [EMAIL PROTECTED] vote summary: http://mail-archives.apache.org/mod_mbox/incubator-couchdb-dev/200810.mbox/[EMAIL PROTECTED] Message IDs for informal(*) PPMC vote to appoint Damien Katz to become Vice President, CouchDB: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] (* Sorry we didn't to a formal vote and hence no formal [RESULT] message) -- We would like to ask the IPMC to discuss the following Board resolution to be recommended to the Board. Once your feedback is collected and integrated, we will ask you to vote on the final resolution. Thank you! -- Proposed Board Resolution: Establish the Apache CouchDB project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software implementing a distributed, fault- tolerant and schema-free document-oriented database for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CouchDB Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CouchDB Project be and hereby is responsible for the creation and maintenance of software related to implementing a distributed, fault-tolerant and schema-free document-oriented database; and be it further RESOLVED, that the office of Vice President, CouchDB be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache CouchDB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CouchDB Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CouchDB Project: * J Chris Anderson ([EMAIL PROTECTED]) * Damien Katz ([EMAIL PROTECTED]) * Christopher Lenz ([EMAIL PROTECTED]) * Jan Lehnardt ([EMAIL PROTECTED]) * Noah Slater ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Damien Katz be appointed to the office of Vice President, CouchDB, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache CouchDB Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the CouchDB Project; and be it further RESOLVED, that the initial Apache CouchDB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CouchDB podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator CouchDB podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Again, thanks for your cooperation! For the Apache CouchDB PPMC, Jan -- PS: Thanks to Noah Slater for proofreading. - 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: [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
On Nov 10, 2008, at 2:44 PM, Jan Lehnardt wrote: [ ] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
On Sat, Nov 8, 2008 at 2:17 PM, Jan Lehnardt [EMAIL PROTECTED] wrote: Dear Incubator General List, dear IPMC, thank you all for your comments on whether CouchDB should graduate from the Incubator to a top level project. I think we have your support. On behalf of the Apache CouchDB PPMC I am now calling a vote: [X] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. [ ] No, CouchDB is not yet ready, it should stay in the Incubator. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Need one more binding vote to release Apache UIMACPP-2.2.2-incubating
Hi - Please see this email thread in the general list: http://markmail.org/message/ris3bjm5sq6xxpo3 We would sincerely appreciate an additional person reviewing the release. UIMACPP is the C++ version of the Apache UIMA (incubating) framework, supporting components written in C++. Thanks! -Marshall Schor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Buildr as TLP
[X] +1 Approve graduation of Buildr as a Top-Level Project Dan On Thursday 06 November 2008 12:03:45 pm Alex Boisvert wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a votehttp://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.html to gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate --- Begin Proposed Board Resolution --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Buildr Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Buildr Project be and hereby is responsible for the creation and maintenance of a software project related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration. RESOLVED, that the office of Vice President, Apache Buildr be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of The Apache Buildr Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Buildr Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of The Apache Buildr Project: - Assaf Arkin ([EMAIL PROTECTED]) - Alex Boisvert ([EMAIL PROTECTED]) - Victor Hugo Borja ([EMAIL PROTECTED]) - Antoine Contal ([EMAIL PROTECTED]) - Matthieu Riou ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Boisvert be and hereby is appointed to the office of Vice President, Apache Buildr, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Buildr PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Buildr Project; and be it further RESOLVED, that the initial Apache Buildr Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Buildr podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Buildr podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trouble creating tashi status page
Sorry for mailing the general list, but I was trying to create the incubation status page for tashi and ran into a few snags and am looking for some help. I was following the directions on http://incubator.apache.org/guides/website.html and believed that I fit into the category of any committer on a current podling in incubation and thus should be able to commit changes, but when I tried to commit, I got a 403 Forbidden error. This same guide says to ask for help on the incubator's general list if you have problems with updating the website. I'd like to apologize in advance if I missed something obvious or if I misunderstood something. - Michael Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble creating tashi status page
Hi Michael, Can you post what went wrong, exactly? Did you check out the site with https? Craig On Nov 11, 2008, at 1:59 PM, Ryan, Michael P wrote: Sorry for mailing the general list, but I was trying to create the incubation status page for tashi and ran into a few snags and am looking for some help. I was following the directions on http://incubator.apache.org/guides/website.html and believed that I fit into the category of any committer on a current podling in incubation and thus should be able to commit changes, but when I tried to commit, I got a 403 Forbidden error. This same guide says to ask for help on the incubator's general list if you have problems with updating the website. I'd like to apologize in advance if I missed something obvious or if I misunderstood something. - Michael Ryan - 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: Trouble creating tashi status page
Hi Michael, I found a problem that might be the problem. Can you try it now? Craig On Nov 11, 2008, at 1:59 PM, Ryan, Michael P wrote: Sorry for mailing the general list, but I was trying to create the incubation status page for tashi and ran into a few snags and am looking for some help. I was following the directions on http://incubator.apache.org/guides/website.html and believed that I fit into the category of any committer on a current podling in incubation and thus should be able to commit changes, but when I tried to commit, I got a 403 Forbidden error. This same guide says to ask for help on the incubator's general list if you have problems with updating the website. I'd like to apologize in advance if I missed something obvious or if I misunderstood something. - Michael Ryan - 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
[jira] Created: (INCUBATOR-102) Request account from hama project
Request account from hama project - Key: INCUBATOR-102 URL: https://issues.apache.org/jira/browse/INCUBATOR-102 Project: Incubator Issue Type: Task Components: subversion Reporter: Edward J. Yoon Following committers have resigned from the hama project after receiving a reminder about vote and extended period of inactivity. Please remove them from hama project. SVN-ID, Name hongtebari, Hong Teahui yoonjoosun, Yoon Joo Sun bluesvm, Suh ChangHee -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-102) Remove account from hama project
[ https://issues.apache.org/jira/browse/INCUBATOR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon updated INCUBATOR-102: - Summary: Remove account from hama project (was: Request account from hama project) Remove account from hama project Key: INCUBATOR-102 URL: https://issues.apache.org/jira/browse/INCUBATOR-102 Project: Incubator Issue Type: Task Components: subversion Reporter: Edward J. Yoon Following committers have resigned from the hama project after receiving a reminder about vote and extended period of inactivity. Please remove them from hama project. SVN-ID, Name hongtebari, Hong Teahui yoonjoosun, Yoon Joo Sun bluesvm, Suh ChangHee -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646784#action_12646784 ] Niclas Hedhman commented on INCUBATOR-86: - Codebase is imported. I have requested from PMC Chair to have the Authorization updated. Request SVN from INFRA -- Key: INCUBATOR-86 URL: https://issues.apache.org/jira/browse/INCUBATOR-86 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Joe has expressed that the SVN directory to be created when the original codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
STATUS page confusion.
Gang, The STATUS template says; quote Ask infrastructure to create source repository modules and grant the committers karma. /quote But I have also been told on lists that the PMC Chair is responsible for Authorization. So what is it? Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble creating tashi status page
On Wed, Nov 12, 2008 at 7:22 AM, Craig L Russell [EMAIL PROTECTED] wrote: Hi Michael, I found a problem that might be the problem. Can you try it now? Hmmm I thought the STATUS page was a Mentor headache. What a relief! Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Craig On Nov 11, 2008, at 7:02 PM, Niclas Hedhman wrote: Gang, The STATUS template says; quote Ask infrastructure to create source repository modules and grant the committers karma. /quote But I have also been told on lists that the PMC Chair is responsible for Authorization. So what is it? Cheers Niclas - 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: STATUS page confusion.
On Wed, Nov 12, 2008 at 11:32 AM, Craig L Russell [EMAIL PROTECTED] wrote: There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Ok. My vote is still to have a JIRA Task template (with subtasks pre-populate) instead. So much more accessible, flexible and accurate. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved INCUBATOR-86. - Resolution: Fixed Authorization has been setup. Request SVN from INFRA -- Key: INCUBATOR-86 URL: https://issues.apache.org/jira/browse/INCUBATOR-86 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Joe has expressed that the SVN directory to be created when the original codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-86: --- Assignee: Niclas Hedhman Request SVN from INFRA -- Key: INCUBATOR-86 URL: https://issues.apache.org/jira/browse/INCUBATOR-86 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Assignee: Niclas Hedhman Joe has expressed that the SVN directory to be created when the original codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-86) Request SVN from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-86. --- Request SVN from INFRA -- Key: INCUBATOR-86 URL: https://issues.apache.org/jira/browse/INCUBATOR-86 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Assignee: Niclas Hedhman Joe has expressed that the SVN directory to be created when the original codebase is in our hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-98) Request Confluence from Infra
[ https://issues.apache.org/jira/browse/INCUBATOR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-98: --- Assignee: Niclas Hedhman Request Confluence from Infra - Key: INCUBATOR-98 URL: https://issues.apache.org/jira/browse/INCUBATOR-98 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Assignee: Niclas Hedhman First step is to create a Confluence space for Etch. Felix is using Confluence to also generate the static website. So, I think it makes sense to layout Etch website similarly to what Felix has done, so we can easily copy their method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-98) Request Confluence from Infra
[ https://issues.apache.org/jira/browse/INCUBATOR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-98. --- Resolution: Fixed Etch space has been set up, with Niclas Scott as Space admins. Request Confluence from Infra - Key: INCUBATOR-98 URL: https://issues.apache.org/jira/browse/INCUBATOR-98 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman Assignee: Niclas Hedhman First step is to create a Confluence space for Etch. Felix is using Confluence to also generate the static website. So, I think it makes sense to layout Etch website similarly to what Felix has done, so we can easily copy their method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-101) Migration of public web/wiki content to apache
[ https://issues.apache.org/jira/browse/INCUBATOR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-101: Assignee: Niclas Hedhman Migration of public web/wiki content to apache -- Key: INCUBATOR-101 URL: https://issues.apache.org/jira/browse/INCUBATOR-101 Project: Incubator Issue Type: Sub-task Components: site Reporter: James Dixson Assignee: Niclas Hedhman Etch maintains a public wiki at http://developer.cisco.com/web/cuae/etch this content needs to be migrated to Apache -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-101) Migration of public web/wiki content to apache
[ https://issues.apache.org/jira/browse/INCUBATOR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-101. Resolution: Fixed See ETCH-2. Migration of public web/wiki content to apache -- Key: INCUBATOR-101 URL: https://issues.apache.org/jira/browse/INCUBATOR-101 Project: Incubator Issue Type: Sub-task Components: site Reporter: James Dixson Assignee: Niclas Hedhman Etch maintains a public wiki at http://developer.cisco.com/web/cuae/etch this content needs to be migrated to Apache -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
Hi Niclas, On Nov 11, 2008, at 7:02 PM, Niclas Hedhman wrote: Gang, The STATUS template says; quote Ask infrastructure to create source repository modules and grant the committers karma. /quote But I have also been told on lists that the PMC Chair is responsible for Authorization. The authorization to add projects to the incubator svn is granted to members and incubator pmc members. The authorization to change the authorization file (to create a new project) is granted to pmc-chair, svnadmins, and board members. So, Mentors can create the podling svn repository but a pmc chair (incubator or friendly helper) needs to update the authorization file. HTH, Craig So what is it? Cheers Niclas - 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
[jira] Closed: (INCUBATOR-83) Set up the Etch Podling
[ https://issues.apache.org/jira/browse/INCUBATOR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-83. --- Resolution: Fixed Assignee: Niclas Hedhman All the essentials has now been set up. Set up the Etch Podling --- Key: INCUBATOR-83 URL: https://issues.apache.org/jira/browse/INCUBATOR-83 Project: Incubator Issue Type: Task Reporter: Niclas Hedhman Assignee: Niclas Hedhman The Etch podling has been approved to enter Incubation. We need to go through a set of tasks to get the podling going. This issue is the master issue for these subtasks. Champion; Niclas Hedhman Mentors; Niclas Hedhman Doug Cutting Yonik Seeley -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Stonehenge
Microsoft is happy to support Stonehenge. We believe that the intent of the project is to focus on building a set of sample applications based on approved W3C and OASIS standard protocols with a goal of helping increase interoperability between different implementations on various platforms. We think that such a project could provide developers with a helpful starting place for their tasks by providing guidelines and reference implementations on various platforms representing industry best practices. In addition, the project may also help identify ways to improve interoperability and industry collaboration to help improve and promote cutting-edge architecture related to multi-tier SOA applications. Our customers have told us that their developers value sample applications that may be used to help improve complex web services implementations, and that they need more information and access to best practices related to such sample applications. The Stonehenge project proposal offers an exciting opportunity for industry participants to build sample applications that could lead to increased interoperability between different platforms. We are enthusiastic about the potential of the Stonehenge project, and are optimistic that the scope of the project will allow for our continued participation and support of the project. I look forward to helping other participants define the scope of the project in a manner that encourages others to participate as well. Kamaljit Bath Principal Program Manager Microsoft Interoperability Strategy [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] 425-703-3419
Re: [VOTE] Graduate Buildr as TLP
The vote to approve the graduation of Buildr as a top-level project has now ended with 13 +1 votes (incl. 8 binding) and no other votes. Binding: * Martijn Dashorst * Bertrand Delacrétaz * Paul Fremantle * Jim Jagielski * Gianugo Rabellino * Matthieu Riou * Craig L. Russell * Yoav Shapira Non-binding: * Niklas Gustavsson * Erik Hatcher * Daniel Kulp * Luciano Resende * Carl Trieloff Thank you for your participation and congratulations to the Buildr project for this important milestone! alex On Thu, Nov 6, 2008 at 9:03 AM, Alex Boisvert [EMAIL PROTECTED] wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a votehttp://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.htmlto gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate --- Begin Proposed Board Resolution --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Buildr Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Buildr Project be and hereby is responsible for the creation and maintenance of a software project related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration. RESOLVED, that the office of Vice President, Apache Buildr be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of The Apache Buildr Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Buildr Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of The Apache Buildr Project: - Assaf Arkin ([EMAIL PROTECTED]) - Alex Boisvert ([EMAIL PROTECTED]) - Victor Hugo Borja ([EMAIL PROTECTED]) - Antoine Contal ([EMAIL PROTECTED]) - Matthieu Riou ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Boisvert be and hereby is appointed to the office of Vice President, Apache Buildr, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Buildr PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Buildr Project; and be it further RESOLVED, that the initial Apache Buildr Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Buildr podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Buildr podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution ---
any Incubator committer can edit the site
Niclas Hedhman wrote: Craig L Russell wrote: Hi Michael, I found a problem that might be the problem. Can you try it now? To decrypt: The Subversion authorisation was missing the section that enabled the tashi group to edit Incubator pages. Hmmm I thought the STATUS page was a Mentor headache. What a relief! Yes, this is a very important point. Each podling's group of committers can edit the Incubator site, including their status page under i.a.o/projects/ and the general guides documentation. This gets them used to acting as a PMC and not relying on others. If anyone notices documentation that is out-of-date or unclear, then jump in and fix it. http://incubator.apache.org/guides/website.html -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
Please add your reports at http://wiki.apache.org/incubator/November2008 Real Soon. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Stonehenge
On Tue, Nov 4, 2008 at 5:34 PM, Paul Fremantle [EMAIL PROTECTED] wrote: ...The full proposal is here: http://wiki.apache.org/incubator/StonehengeProposal.. That says future contributions could depend on proprietary systems such as Microsoft .Net or commercial JEE servers, which IIUC means that some parts of Stonehenge might not be buildable or testable using open source tools. We certainly already have some such code in our projects, and I'm no against that - but I'd like the Stonehenge people to keep such parts well separated, to allow people who only use open source tools to benefit from the project as well. As the project is about interoperability, that's somewhat obvious anyway, but still worth mentioning IMHO. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Buildr as TLP
Actually Daniel K's vote is binding, but that doesn't change the outcome. Congratulations! Paul On Wed, Nov 12, 2008 at 5:50 AM, Alex Boisvert [EMAIL PROTECTED] wrote: The vote to approve the graduation of Buildr as a top-level project has now ended with 13 +1 votes (incl. 8 binding) and no other votes. Binding: * Martijn Dashorst * Bertrand Delacrétaz * Paul Fremantle * Jim Jagielski * Gianugo Rabellino * Matthieu Riou * Craig L. Russell * Yoav Shapira Non-binding: * Niklas Gustavsson * Erik Hatcher * Daniel Kulp * Luciano Resende * Carl Trieloff Thank you for your participation and congratulations to the Buildr project for this important milestone! alex On Thu, Nov 6, 2008 at 9:03 AM, Alex Boisvert [EMAIL PROTECTED] wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a votehttp://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.htmlto gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate --- Begin Proposed Board Resolution --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Buildr Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Buildr Project be and hereby is responsible for the creation and maintenance of a software project related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration. RESOLVED, that the office of Vice President, Apache Buildr be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of The Apache Buildr Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Buildr Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of The Apache Buildr Project: - Assaf Arkin ([EMAIL PROTECTED]) - Alex Boisvert ([EMAIL PROTECTED]) - Victor Hugo Borja ([EMAIL PROTECTED]) - Antoine Contal ([EMAIL PROTECTED]) - Matthieu Riou ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Boisvert be and hereby is appointed to the office of Vice President, Apache Buildr, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Buildr PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Buildr Project; and be it further RESOLVED, that the initial Apache Buildr Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Buildr podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Buildr podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
