[PROPOSAL] 3 month deadline on CLA item
As can be seen elsewhere, I'm on a self-given mission to clean up the history of podlings by getting them to sign off on the following checklist item: "Check and make sure that 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. " I view this as the first item that a podling should be dealing with, along with setting up the committers and getting that first codebase in. By comparison, a website is a nice to have and community is just icing. Proposal time. In parallel to cleaning up history, I'd like to stop the rot going forward. I'd like to propose that each new podling has 3 months (or another calendar length if that feels too short/too long) to get the checklist item signed off. I'm partial to 3 months as we would make them report monthly until they have the item signed off, perhaps with 6 months as a 'do we retire the podling?' checkpoint. Thoughts? Hen - Incubator Bad Cop - - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podlings needing copyright sign-off
rfrovarp@ is going to take care of Droids. I've pinged rgass@ and stroucki@ as recent Tashi committers to get it sorted, and fitzner@ as the recent Etch committer. Olio sounds like a subject of its own to discuss. Hen On Sat, Jul 23, 2011 at 12:50 PM, Henri Yandell wrote: > Noting that vcl have signed off on the first copyright item. > > That leaves 2008 with: > > * etch > * olio [sounds like this might be retired] > * droids > * tashi > > From 2009: > > * kato > * stonehenge > * ace > * socialsite > * wink > * vxquery > * hise > * clerezza - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Last Bluesky report
Complete action items: * Moved to retired table on Incubator project page. * JIRA now read-only. * SVN now read-only. To be deleted. * Project page indicates retirement. * Dropped from Incubator website RHS nav. * Removed from reporting schedule. To do: * Make wiki read-only. * Close mailing lists. * Keep website or remove? Hen On Mon, Aug 1, 2011 at 9:01 AM, Christian Grobmeier wrote: > Hi, > > just added a few words to the august report on Bluesky. Guess it might > be of interest for the board what happend. Please add your lines and > modify mine to your likings. I will remove it now from the schedule > > Cheers > Christian > > > Bluesky > > The incubator community voted to retire the Bluesky podling. It will > be closed in near future and reporting will stop with this period. > > See here for the vote results: > http://s.apache.org/7oo > > Some more context: > http://s.apache.org/4Q2 > > Signed off by mentor: > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Libcloud (Was: Incubator PMC/Board report for August 2011)
This one is because the Libcloud project has not tidied up after graduating from the Incubator. See some tips at http://incubator.apache.org/clutch.html#h-Graduate -David On Mon, Aug 01, 2011 at 02:00:07PM +, no-re...@apache.org wrote: > Dear Libcloud Developers, > > This email was sent by an automated system on behalf of the Apache Incubator > PMC. > It is an initial reminder to give you plenty of time to prepare your quarterly > board report. > > The board meeting is scheduled for Wed, 17 August 2011, 10 am Pacific. The > report > for your podling will form a part of the Incubator PMC report. The Incubator > PMC > requires your report to be submitted one week before the board meeting, to > allow > sufficient time for review. > > Please submit your report with sufficient time to allow the incubator PMC, > and > subsequently board members to review and digest. Again, the very latest you > should submit your report is one week prior to the board meeting. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of the > project >or necessarily of its field > * A list of the three most important issues to address in the move towards >graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be aware > of > * How has the community developed since the last report > * How has the project developed since the last report. > > This should be appended to the Incubator Wiki page at: > > http://wiki.apache.org/incubator/August2011 > > Note: This manually populated. You may need to wait a little before this page > is > created from a template. > > Mentors > --- > Mentors should review reports for their project(s) and sign them off on the > Incubator wiki page. Signing off reports shows that you are following the > project - projects that are not signed may raise alarms for the Incubator PMC. > > Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release HCatalog 0.1-incubating (RC1)
There are two kind of jar files. One which HCatalog is adding itself and others we are inheriting from Hive project. Since Hive is TLP and has multiple releases I am going to assume I need not to worry about any of those jars and sources. I have verified all the HCatalog dependencies are ASL. ./lib/libthrift.jar ./ivy/ivy-2.2.0.jar ./build/ivy/lib/hcatalog/commons-cli-1.0.jar ./build/ivy/lib/hcatalog/pig-0.8.0.jar ./build/hcatalog/hcatalog-0.1.0.jar So, I think I need not to bother about Notice.txt either since anything other then Hive dependencies are ASL. Patrick, correct me if I am wrong. Thanks, Ashutosh On Fri, Jul 29, 2011 at 10:25, Patrick Hunt wrote: > On Thu, Jul 28, 2011 at 4:28 PM, Ashutosh Chauhan > wrote: >> Thanks for checking out HCatalog. This is my first time in the >> incubator, so I will be glad if you can help me out here. > > Hi Ashutosh, no worries, that's what the incubator is here for. I saw > that you weren't getting the vote and figured I'd help out. :-) > > I'd encourage you to work through the incubator release page, it's a > very useful reference: > http://incubator.apache.org/guides/releasemanagement.html > >> 1. Is Disclaimer a must? I checked out few other projects. Pig, HIve, >> Hadoop, Avro none of those projects have it. Another incubator project >> Chukwa has it neither and they had few releases as well. >> > > According to this Incubator doc it is a requirement. (It's not a > requirement for projects outside the incubator) > http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer > IIRC we had a similar comment/issue in Whirr. FWIW Whirr's gotten alot > of good feedback and gone through a number of incubator releases, you > might look there for insight. > >> 2. "Verify distribution rights". Can you point me to some >> documentation on how do I proceed to make this verification ? >> > > I think you just need to follow the description on this, from your status > page: > > -..-.. Check and make sure that for all code included with the > distribution that is not under the Apache license, we have the right > to combine with Apache-licensed code and redistribute. > -..-.. Check and make sure that all source code distributed by the > project is 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. > > There's a section of the incubator on this as well: > http://incubator.apache.org/guides/releasemanagement.html#release-legal-audit > although I think you hit most of these already (headers for example). > > So really, afaict, you need to go through this exercise and mark on > the page that you've done it (ie list the date(s)). > >> 3. Is there a guideline somewhere about what needs to go in NOTICE.txt >> Particularly, we svn extern hive project which already has NOTICE.txt >> for those dependencies do we stil need to worry about them. > > Honestly I have trouble groking this one myself. ;-) Here's the > incubator docs on this: > http://incubator.apache.org/guides/releasemanagement.html#best-practice-license > specifically: > http://www.apache.org/legal/src-headers.html#notice > an httpd example: > http://www.apache.org/licenses/example-NOTICE.txt > > Perhaps some other incubator member would have more insight or a > better description? > > Regards, > > Patrick > >> >> On Wed, Jul 27, 2011 at 11:39, Patrick Hunt wrote: >>> -1, I found a few issues that need to be cleaned up. >>> >>> On the plus side the md5 checked out and "ant test" was successful >>> >>> I then looked through: >>> http://incubator.apache.org/guides/releasemanagement.html#check-list >>> >>> DISCLAIMER is missing (I don't see in readme or release notes either): >>> http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer >>> here's an example: >>> http://svn.apache.org/viewvc/incubator/whirr/trunk/DISCLAIMER.txt?revision=991399&view=markup >>> >>> I see that the section "Verify distribution rights" in >>> http://incubator.apache.org/projects/hcatalog.html >>> is not filled in. >>> >>> The notice file says that javaewah is included, but I can't find it. >>> Should slf4j be included? (there are a number of jars included in the >>> release, you might review this) >>> >>> bin/umaskcheck.sh is missing a license header >>> >>> note: the archive's lib directory contain 3 versions of hcatalog jar >>> -rw-r--r-- 1 phunt phunt 139184 2011-07-12 03:19 >>> hcatalog-0.1.0-incubating.jar >>> -rw-r--r-- 1 phunt phunt 139184 2011-07-12 04:18 hcatalog-0.1.0.jar >>> -rw-r--r-- 1 phunt phunt 139184 2011-07-12 03:19 hcatalog-0.1.1.jar >>> >>> Patrick >>> >>> On Tue, Jul 26, 2011 at 9:20 AM, Ashutosh Chauhan >>> wrote: We need one more +1 to release HCatalog 0.1-incubating. Please give it a try and vote. Ashutosh On Fri, Jul 22, 2011 at 12:02, Alan Gates wrote: > +1 > > Built and tested on Mac and RHEL. Reviewed docs. Ch
Re: Karma to asf-authorization-template
Perfect. Thanks, Craig On Aug 1, 2011, at 11:13 AM, Daniel Shahaf wrote: % $svn info | grep URL URL: https://svn.apache.org/repos/infra/infrastructure/trunk/tools % $svn di Index: account-pmc.ezt === --- account-pmc.ezt (revision 793364) +++ account-pmc.ezt (working copy) @@ -13,5 +13,10 @@ Please grant additional karma to the projects in your domain you wish the user to have commit to. +Only PMC chairs (and, for podlings, also Infrastructure volunteers) can +grant karma. If needed, please post to the general@/dev@/private@ list +of your project asking for someone with sufficient karma to grant access +to '[username]'. + The Apache Infrastructure Team % $svn ci -m "clarify at clr's suggestion" Sendingaccount-pmc.ezt Transmitting file data . Committed revision 793571. Obviously if general@ doesn't respond after three days then escalate to infra@, but I'd like projects to manage access themselves when possible. Craig L Russell wrote on Mon, Aug 01, 2011 at 11:03:51 -0700: Hi Daniel, On Aug 1, 2011, at 10:52 AM, Daniel Shahaf wrote: There are 30 PMC chairs on the Incubator PMC, which is more than enough to sort its own authz needs without bugging infra every time. It would be nice if this fact were better known, so mentors-who-are- not-pmc-chairs would know what to do when the accounts for the podlings that they are mentoring are created. Maybe a better wording of this message sent to private@incubator might help: Please grant additional karma to the projects in your domain you wish the user to have commit to. The Apache Infrastructure Team Since most of the new account requests are for incubator projects, perhaps add this to the message: If you are mentoring an incubator podling and are not a pmc chair, please send a request to infrastructure@ with the name of the podling and the new committer and we'll be happy to add the necessary karma for your new committer. Craig Craig L Russell wrote on Mon, Aug 01, 2011 at 10:44:55 -0700: This appears to be by design. The only folks who have rw access to the file are: [/infrastructure/trunk/subversion/authorization] @pmc-chairs = rw @svnadmins = rw @board = rw @secretary = rw svn = r # apsite needs access to asf-authorization-template apsiteread = r So at the moment, it appears that karma is only for PMC chairs and a few select others. I'd agree that incubator pmc members should be able to rw the file or we have a choke point (incubator pmc chair). Maybe I'm reading this wrong... Craig On Aug 1, 2011, at 9:50 AM, Emmanuel Lecharny wrote: Same request that Alan : I'm part of the IPMC, and I don't have access to this file. Could someone grant me the needed karma ? Thanks ! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! Craig L Russell Secretary, Apache Software Foundation c...@apache.org http://db.apache.org/jdo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE][RESULT] Accept Giraph for Incubation
> [ ] +1 Accept Giraph for incubation > [ ] +0 Indifferent to Giraph incubation > [ ] -1 Reject Giraph for incubation > > This vote will close 72 hours from now. > > Thanks! > > Avery Voting is now closed. The vote passes with the following details: +1 binding votes (4) +1 non-binding votes (3) +0 votes (0) -1 votes (0) --- Details --- Binding: +1 Alan Cabrera +1 Mohammad Nour El-Din +1 Alex Karasulu +1 Owen O'Malley Non-binding: +1 Ashish Paliwal +1 Phillip Rhodes +1 Bill Graham The binding votes were counted based on the Incubator PMC membership list located at: http://people.apache.org/committers-by-project.html#incubator-pmc - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling accounts created
On Aug 1, 2011, at 11:01 AM, Nick Burch wrote: > On Mon, 1 Aug 2011, Alan D. Cabrera wrote: >> Sendingasf-authorization-template >> svn: Commit failed (details follow): >> svn: access to >> '/repos/infra/!svn/ver/793489/infrastructure/trunk/subversion/authorization/asf-authorization-template' >> forbidden > > If you could post the diff, then one of us who are also a PMC chair can apply > the change for you Already created. Thanks Daniel! Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][RESULT] Accept ODF Toolkit for Incubation
On Mon, Aug 1, 2011 at 7:05 AM, Nick Burch wrote: > On Sun, 31 Jul 2011, Sam Ruby wrote: >> >> On Thu, Jul 28, 2011 at 3:53 PM, Sam Ruby wrote: >>> >>> As the discussions on the ODF Toolkit threads seem to be winding down, >>> I would like to initiate the vote to accept the ODF Toolkit as an >>> Apache Incubator project. >>> >>> This vote will close 72 hours from now. >> >> Voting is now closed. Quorum was achieved, and the vote passes. > > Great. I've gone ahead and added the podling status page: > http://incubator.apache.org/projects/odftoolkit.html > (may take an hour or two for the site publish to go live though) > Thanks! > > Next step is probably to get the lists setup, so we can use them to discuss > importing the code, website etc. > > Can I have a couple of volunteers to be moderators for the lists? (List > moderators review emails from non members, and approve if appropriate or > discard if spam). Once we've a few volunteers, I can ask infra to create the > lists > I can moderate as well. > > I'll contact people needing iCLAs shortly > > Nick > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Karma to asf-authorization-template
% $svn info | grep URL URL: https://svn.apache.org/repos/infra/infrastructure/trunk/tools % $svn di Index: account-pmc.ezt === --- account-pmc.ezt (revision 793364) +++ account-pmc.ezt (working copy) @@ -13,5 +13,10 @@ Please grant additional karma to the projects in your domain you wish the user to have commit to. +Only PMC chairs (and, for podlings, also Infrastructure volunteers) can +grant karma. If needed, please post to the general@/dev@/private@ list +of your project asking for someone with sufficient karma to grant access +to '[username]'. + The Apache Infrastructure Team % $svn ci -m "clarify at clr's suggestion" Sendingaccount-pmc.ezt Transmitting file data . Committed revision 793571. Obviously if general@ doesn't respond after three days then escalate to infra@, but I'd like projects to manage access themselves when possible. Craig L Russell wrote on Mon, Aug 01, 2011 at 11:03:51 -0700: > Hi Daniel, > > On Aug 1, 2011, at 10:52 AM, Daniel Shahaf wrote: > > >There are 30 PMC chairs on the Incubator PMC, which is more than > >enough > >to sort its own authz needs without bugging infra every time. > > It would be nice if this fact were better known, so mentors-who-are- > not-pmc-chairs would know what to do when the accounts for the > podlings that they are mentoring are created. > > Maybe a better wording of this message sent to private@incubator > might help: > > >Please grant additional karma to the projects in your domain > >you wish the user to have commit to. > > > > > >The Apache Infrastructure Team > > Since most of the new account requests are for incubator projects, > perhaps add this to the message: > > >If you are mentoring an incubator podling and are not a pmc chair, > >please send a request to infrastructure@ with the name of the > >podling and the new committer and we'll be happy to add the > >necessary karma for your new committer. > > Craig > > > >Craig L Russell wrote on Mon, Aug 01, 2011 at 10:44:55 -0700: > >>This appears to be by design. The only folks who have rw access to > >>the file are: > >>[/infrastructure/trunk/subversion/authorization] > >>@pmc-chairs = rw > >>@svnadmins = rw > >>@board = rw > >>@secretary = rw > >>svn = r > >># apsite needs access to asf-authorization-template > >>apsiteread = r > >> > >>So at the moment, it appears that karma is only for PMC chairs and a > >>few select others. > >> > >>I'd agree that incubator pmc members should be able to rw the file > >>or we have a choke point (incubator pmc chair). > >> > >>Maybe I'm reading this wrong... > >> > >>Craig > >> > >>On Aug 1, 2011, at 9:50 AM, Emmanuel Lecharny wrote: > >> > >>>Same request that Alan : I'm part of the IPMC, and I don't have > >>>access to this file. > >>> > >>>Could someone grant me the needed karma ? Thanks ! > >>> > >>> > >>>- > >>>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >>> > >>> > >>>- > >>>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >> > >>Craig L Russell > >>Architect, Oracle > >>http://db.apache.org/jdo > >>408 276-5638 mailto:craig.russ...@oracle.com > >>P.S. A good JDO? O, Gasp! > >> > > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:craig.russ...@oracle.com > P.S. A good JDO? O, Gasp! > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Karma to asf-authorization-template
On Mon, 1 Aug 2011, Craig L Russell wrote: On Aug 1, 2011, at 10:52 AM, Daniel Shahaf wrote: There are 30 PMC chairs on the Incubator PMC, which is more than enough to sort its own authz needs without bugging infra every time. It would be nice if this fact were better known, so mentors-who-are-not-pmc-chairs would know what to do when the accounts for the podlings that they are mentoring are created. I think the correct process is someone who knows about the podling produces the diff, and if they can't apply it they should just email private@incubator to ask someone else to. This is actually already documented on our own site: http://incubator.apache.org/guides/mentor.html#who-auth-karma "If no mentor has karma then an email should be posted to the IPMC private list requesting that the grant is performed. One of the IPMCers with karma will authorize the committer. " If you are mentoring an incubator podling and are not a pmc chair, please send a request to infrastructure@ with the name of the podling and the new committer and we'll be happy to add the necessary karma for your new committer. We don't need to bug infra though, we have enough people in the incubator who can do it. We just need to bug the right people here if needed. Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Karma to asf-authorization-template
Hi Daniel, On Aug 1, 2011, at 10:52 AM, Daniel Shahaf wrote: There are 30 PMC chairs on the Incubator PMC, which is more than enough to sort its own authz needs without bugging infra every time. It would be nice if this fact were better known, so mentors-who-are- not-pmc-chairs would know what to do when the accounts for the podlings that they are mentoring are created. Maybe a better wording of this message sent to private@incubator might help: Please grant additional karma to the projects in your domain you wish the user to have commit to. The Apache Infrastructure Team Since most of the new account requests are for incubator projects, perhaps add this to the message: If you are mentoring an incubator podling and are not a pmc chair, please send a request to infrastructure@ with the name of the podling and the new committer and we'll be happy to add the necessary karma for your new committer. Craig Craig L Russell wrote on Mon, Aug 01, 2011 at 10:44:55 -0700: This appears to be by design. The only folks who have rw access to the file are: [/infrastructure/trunk/subversion/authorization] @pmc-chairs = rw @svnadmins = rw @board = rw @secretary = rw svn = r # apsite needs access to asf-authorization-template apsiteread = r So at the moment, it appears that karma is only for PMC chairs and a few select others. I'd agree that incubator pmc members should be able to rw the file or we have a choke point (incubator pmc chair). Maybe I'm reading this wrong... Craig On Aug 1, 2011, at 9:50 AM, Emmanuel Lecharny wrote: Same request that Alan : I'm part of the IPMC, and I don't have access to this file. Could someone grant me the needed karma ? Thanks ! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling accounts created
On Mon, 1 Aug 2011, Alan D. Cabrera wrote: Sendingasf-authorization-template svn: Commit failed (details follow): svn: access to '/repos/infra/!svn/ver/793489/infrastructure/trunk/subversion/authorization/asf-authorization-template' forbidden If you could post the diff, then one of us who are also a PMC chair can apply the change for you Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Karma to asf-authorization-template
There are 30 PMC chairs on the Incubator PMC, which is more than enough to sort its own authz needs without bugging infra every time. Craig L Russell wrote on Mon, Aug 01, 2011 at 10:44:55 -0700: > This appears to be by design. The only folks who have rw access to > the file are: > [/infrastructure/trunk/subversion/authorization] > @pmc-chairs = rw > @svnadmins = rw > @board = rw > @secretary = rw > svn = r > # apsite needs access to asf-authorization-template > apsiteread = r > > So at the moment, it appears that karma is only for PMC chairs and a > few select others. > > I'd agree that incubator pmc members should be able to rw the file > or we have a choke point (incubator pmc chair). > > Maybe I'm reading this wrong... > > Craig > > On Aug 1, 2011, at 9:50 AM, Emmanuel Lecharny wrote: > > >Same request that Alan : I'm part of the IPMC, and I don't have > >access to this file. > > > >Could someone grant me the needed karma ? Thanks ! > > > > > >- > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > >- > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >For additional commands, e-mail: general-h...@incubator.apache.org > > > > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:craig.russ...@oracle.com > P.S. A good JDO? O, Gasp! > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Karma to asf-authorization-template
This appears to be by design. The only folks who have rw access to the file are: [/infrastructure/trunk/subversion/authorization] @pmc-chairs = rw @svnadmins = rw @board = rw @secretary = rw svn = r # apsite needs access to asf-authorization-template apsiteread = r So at the moment, it appears that karma is only for PMC chairs and a few select others. I'd agree that incubator pmc members should be able to rw the file or we have a choke point (incubator pmc chair). Maybe I'm reading this wrong... Craig On Aug 1, 2011, at 9:50 AM, Emmanuel Lecharny wrote: Same request that Alan : I'm part of the IPMC, and I don't have access to this file. Could someone grant me the needed karma ? Thanks ! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Karma to asf-authorization-template
Same request that Alan : I'm part of the IPMC, and I don't have access to this file. Could someone grant me the needed karma ? Thanks ! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Karma to asf-authorization-template
As an Incubator PMC member and an mentor for a fair number of podlings I think I should have karma to this file. Is that possible? How do I get it? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling accounts created
Sendingasf-authorization-template svn: Commit failed (details follow): svn: access to '/repos/infra/!svn/ver/793489/infrastructure/trunk/subversion/authorization/asf-authorization-template' forbidden On Aug 1, 2011, at 9:18 AM, Mattmann, Chris A (388J) wrote: > Hi Alan, > > You add them to this file: > > https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template > > Cheers, > Chris > > On Aug 1, 2011, at 9:16 AM, Alan D. Cabrera wrote: > >> My podling's svn accounts have been created. How do I give them access to >> their svn project? >> >> >> Regards, >> Alan >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > ++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling accounts created
Hi Alan, You add them to this file: https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template Cheers, Chris On Aug 1, 2011, at 9:16 AM, Alan D. Cabrera wrote: > My podling's svn accounts have been created. How do I give them access to > their svn project? > > > Regards, > Alan > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Podling accounts created
My podling's svn accounts have been created. How do I give them access to their svn project? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: ODF Toolkit
On Mon, 2011-08-01 at 15:16 +0100, Nick Burch wrote: > On Mon, 1 Aug 2011, drew wrote: > > Wondering if it is still appropriate, acceptable, to add myself to the > > list of initial Committers > > Alas not, Not a problem. > now the proposal has been accepted, that initial list is final > > The good news is that as soon as the lists are set up, the podling would > be able to vote you in. If you've been involved in the project before, > that should be very quick, though for future new contributors it would > normally wait until after they've submitted patches that everyone is happy > with. > > If you were involved in the project before, I'd suggest you join the dev > list once it's created, and remind people that you're interested in > joining. OK - thanks, Drew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: ODF Toolkit
On Mon, 1 Aug 2011, drew wrote: Wondering if it is still appropriate, acceptable, to add myself to the list of initial Committers Alas not, now the proposal has been accepted, that initial list is final The good news is that as soon as the lists are set up, the podling would be able to vote you in. If you've been involved in the project before, that should be very quick, though for future new contributors it would normally wait until after they've submitted patches that everyone is happy with. If you were involved in the project before, I'd suggest you join the dev list once it's created, and remind people that you're interested in joining. Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
ODF Toolkit
Hi, Wondering if it is still appropriate, acceptable, to add myself to the list of initial Committers at: http://wiki.apache.org/incubator/ODFToolkitProposal Thanks much, Drew Jensen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for August 2011 (general@incubator.apache.org)
Dear ODFToolkit Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 August 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/August2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for August 2011 (general@incubator.apache.org)
Dear Libcloud Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 August 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/August2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
On 1 August 2011 11:18, seba.wag...@gmail.com wrote: > the Serlvet Container is Red5 (which is a modified Tomcat Servlet > Container), you cannot run OpenMeetings without it. > > For building the software, OpenMeetings implements some of the API > Interfaces of the Red5-Server. So you need at least the red5.jar available > at build time in order to produce a release... or you create some > Mock-Objects to simulate the API of the Servlet Container. I suggest this is going to be your biggest impediment to graduation. Red5 is LGPL and thus incompatibly licensed. Ross > > > Sebastian > > > 2011/8/1 Ross Gardler > >> Great to see this proposal coming back again. If I remember correctly >> there was some concern about whether the application could reasonably >> expect to be made to tun without (L)GPL dependencies. >> >> It's clear that you've already done a fair amount of work to remove >> these dependencies, but the main sticking point was the servlet >> container you were using. My recollection is that this is a runtime >> dependency, not a build time one. However, if that is the case then >> surely it could be run in any container. Is that the case? >> >> If not then this dependency needs to be identified in the "External >> Dependencies" section. >> >> Please note, having a runtime dependency on incompatibly licensed code >> does not prevent you from making releases, it just makes it harder for >> people to install and also limits the range of people who are able to >> install it. >> >> Can you please clarify whether the application can run in any servlet >> container or not. >> >> Thanks. >> Ross >> >> 2011/7/21 seba.wag...@gmail.com : >> > We would like to propose Openmeetings project to join the incubator. >> > >> > Full Proposal: >> > http://wiki.apache.org/incubator/OpenmeetingsProposal >> > >> > Quick summary: >> > OpenMeetings is Web Conferencing application that fits into >> > educational or business sector. You can make conference sessions in >> > different room-types with up to 100 peoples in a Room. It contains all >> > main features of Web Conferencing: Audio/Video, Whiteboard, Screen >> > Sharing, Chat and Moderation System. It is translated into more then >> > 30 languages and its a basic goal of OpenMeetings to be easy to embed >> > into existing environments. It already uses many of Apache >> > Technologies like Tomcat, Mina, Velocity, Commons, ... >> > >> > As you can see below the last time we did the proposal we had >> > Hibernate in our software stack, we did refactor the hole project and >> > use openJPA now. >> > So that one should be no more blocker to it. >> > Red5 is used like a Servlet container and licensed under the LGPL, >> > Red5 can be obtained for example from the Debian Repository: >> > http://packages.debian.org/wheezy/red5-server >> > >> > You may find all existing documents and further material on the >> > GoogleCode pages: http://code.google.com/p/openmeetings/ >> > >> > We appreciate any feedback and comments on the proposal. >> > >> > Sebastian Wagner >> > >> > 2009/11/9 Ross Gardler : >> >> Just as a point of interest, I just completed a test meeting using >> >> OpenMeetings across three sites using the demo server. >> >> >> >> I was suitably impressed by the project. It has a few annoying >> >> limitations, but as an online meeting tool it is very good. to the >> >> extent that I will almost certainly be installing a copy on our own >> >> servers. I would be very happy to see it coming into the incubator and >> >> would be willing to be a mentor, assuming the legal issues are not >> >> blockers. >> >> >> >> Ross >> >> >> >> 2009/11/3 Alexei Fedotov : >> >>> Noel, >> >>> Regarding Theora codec, I have checked the page [1]. Currently, there >> >>> are no products which successfully use the codec for video >> >>> communication. Video-phone encodes and decodes the stream in >> >>> real-time, adopts the quality with regard to network conditions (e.g. >> >>> lost packet rate) and tries to minimize subjective effects of network >> >>> errors - the list of requirements is broader than for media players >> >>> Theora is mostly used. The work [2] says suggests using hardware >> >>> implementations for Theora codec because, otherwise "a computational >> >>> performance too high to be implemented in the camera by the universal >> >>> processor". >> >>> >> >>> So at least it requires some time and testing before I can say that >> >>> Theora-based solution is feasible. Another ecosystem change, like >> >>> embedding video-codecs in browsers, may resolve our need in a >> >>> different way. >> >>> >> >>> [1] http://www.vorbis.com/software/ >> >>> [2] http://www3.elphel.com/linuxtag/talks_2005/paper-11081 >> >>> >> >>> 2009/11/3 Noel J. Bergman : >> Alexei Fedotov wrote: >> >> > I see two long-term possibilities for synergy. >> > 1. BlueSky can integrate browser pannel in their client to handle a >> > whiteboard. In this case the code for whiteboard can be r
Re: [VOTE][RESULT] Accept ODF Toolkit for Incubation
On Mon, 2011-08-01 at 12:05 +0100, Nick Burch wrote: > On Sun, 31 Jul 2011, Sam Ruby wrote: > > On Thu, Jul 28, 2011 at 3:53 PM, Sam Ruby wrote: > >> As the discussions on the ODF Toolkit threads seem to be winding down, > >> I would like to initiate the vote to accept the ODF Toolkit as an > >> Apache Incubator project. > >> > >> This vote will close 72 hours from now. > > > > Voting is now closed. Quorum was achieved, and the vote passes. > > Great. I've gone ahead and added the podling status page: > http://incubator.apache.org/projects/odftoolkit.html > (may take an hour or two for the site publish to go live though) > Hi Nick, > > Next step is probably to get the lists setup, so we can use them to > discuss importing the code, website etc. > > Can I have a couple of volunteers to be moderators for the lists? Raising hand. I'd be happy to help on that. Best wishes, //drew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][RESULT] Accept ODF Toolkit for Incubation
On Sun, 31 Jul 2011, Sam Ruby wrote: On Thu, Jul 28, 2011 at 3:53 PM, Sam Ruby wrote: As the discussions on the ODF Toolkit threads seem to be winding down, I would like to initiate the vote to accept the ODF Toolkit as an Apache Incubator project. This vote will close 72 hours from now. Voting is now closed. Quorum was achieved, and the vote passes. Great. I've gone ahead and added the podling status page: http://incubator.apache.org/projects/odftoolkit.html (may take an hour or two for the site publish to go live though) Next step is probably to get the lists setup, so we can use them to discuss importing the code, website etc. Can I have a couple of volunteers to be moderators for the lists? (List moderators review emails from non members, and approve if appropriate or discard if spam). Once we've a few volunteers, I can ask infra to create the lists I'll contact people needing iCLAs shortly Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hi Ross, the Serlvet Container is Red5 (which is a modified Tomcat Servlet Container), you cannot run OpenMeetings without it. For building the software, OpenMeetings implements some of the API Interfaces of the Red5-Server. So you need at least the red5.jar available at build time in order to produce a release... or you create some Mock-Objects to simulate the API of the Servlet Container. Sebastian 2011/8/1 Ross Gardler > Great to see this proposal coming back again. If I remember correctly > there was some concern about whether the application could reasonably > expect to be made to tun without (L)GPL dependencies. > > It's clear that you've already done a fair amount of work to remove > these dependencies, but the main sticking point was the servlet > container you were using. My recollection is that this is a runtime > dependency, not a build time one. However, if that is the case then > surely it could be run in any container. Is that the case? > > If not then this dependency needs to be identified in the "External > Dependencies" section. > > Please note, having a runtime dependency on incompatibly licensed code > does not prevent you from making releases, it just makes it harder for > people to install and also limits the range of people who are able to > install it. > > Can you please clarify whether the application can run in any servlet > container or not. > > Thanks. > Ross > > 2011/7/21 seba.wag...@gmail.com : > > We would like to propose Openmeetings project to join the incubator. > > > > Full Proposal: > > http://wiki.apache.org/incubator/OpenmeetingsProposal > > > > Quick summary: > > OpenMeetings is Web Conferencing application that fits into > > educational or business sector. You can make conference sessions in > > different room-types with up to 100 peoples in a Room. It contains all > > main features of Web Conferencing: Audio/Video, Whiteboard, Screen > > Sharing, Chat and Moderation System. It is translated into more then > > 30 languages and its a basic goal of OpenMeetings to be easy to embed > > into existing environments. It already uses many of Apache > > Technologies like Tomcat, Mina, Velocity, Commons, ... > > > > As you can see below the last time we did the proposal we had > > Hibernate in our software stack, we did refactor the hole project and > > use openJPA now. > > So that one should be no more blocker to it. > > Red5 is used like a Servlet container and licensed under the LGPL, > > Red5 can be obtained for example from the Debian Repository: > > http://packages.debian.org/wheezy/red5-server > > > > You may find all existing documents and further material on the > > GoogleCode pages: http://code.google.com/p/openmeetings/ > > > > We appreciate any feedback and comments on the proposal. > > > > Sebastian Wagner > > > > 2009/11/9 Ross Gardler : > >> Just as a point of interest, I just completed a test meeting using > >> OpenMeetings across three sites using the demo server. > >> > >> I was suitably impressed by the project. It has a few annoying > >> limitations, but as an online meeting tool it is very good. to the > >> extent that I will almost certainly be installing a copy on our own > >> servers. I would be very happy to see it coming into the incubator and > >> would be willing to be a mentor, assuming the legal issues are not > >> blockers. > >> > >> Ross > >> > >> 2009/11/3 Alexei Fedotov : > >>> Noel, > >>> Regarding Theora codec, I have checked the page [1]. Currently, there > >>> are no products which successfully use the codec for video > >>> communication. Video-phone encodes and decodes the stream in > >>> real-time, adopts the quality with regard to network conditions (e.g. > >>> lost packet rate) and tries to minimize subjective effects of network > >>> errors - the list of requirements is broader than for media players > >>> Theora is mostly used. The work [2] says suggests using hardware > >>> implementations for Theora codec because, otherwise "a computational > >>> performance too high to be implemented in the camera by the universal > >>> processor". > >>> > >>> So at least it requires some time and testing before I can say that > >>> Theora-based solution is feasible. Another ecosystem change, like > >>> embedding video-codecs in browsers, may resolve our need in a > >>> different way. > >>> > >>> [1] http://www.vorbis.com/software/ > >>> [2] http://www3.elphel.com/linuxtag/talks_2005/paper-11081 > >>> > >>> 2009/11/3 Noel J. Bergman : > Alexei Fedotov wrote: > > > I see two long-term possibilities for synergy. > > 1. BlueSky can integrate browser pannel in their client to handle a > > whiteboard. In this case the code for whiteboard can be re-used in > > both projects. > > > 2. They promise to get rid from mplayer and ffmpeg dependencies. If > > they get a working streaming video-client under APL, this would help > > us to remove the most imporant dependency from Flash. > > They are propo
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Great to see this proposal coming back again. If I remember correctly there was some concern about whether the application could reasonably expect to be made to tun without (L)GPL dependencies. It's clear that you've already done a fair amount of work to remove these dependencies, but the main sticking point was the servlet container you were using. My recollection is that this is a runtime dependency, not a build time one. However, if that is the case then surely it could be run in any container. Is that the case? If not then this dependency needs to be identified in the "External Dependencies" section. Please note, having a runtime dependency on incompatibly licensed code does not prevent you from making releases, it just makes it harder for people to install and also limits the range of people who are able to install it. Can you please clarify whether the application can run in any servlet container or not. Thanks. Ross 2011/7/21 seba.wag...@gmail.com : > We would like to propose Openmeetings project to join the incubator. > > Full Proposal: > http://wiki.apache.org/incubator/OpenmeetingsProposal > > Quick summary: > OpenMeetings is Web Conferencing application that fits into > educational or business sector. You can make conference sessions in > different room-types with up to 100 peoples in a Room. It contains all > main features of Web Conferencing: Audio/Video, Whiteboard, Screen > Sharing, Chat and Moderation System. It is translated into more then > 30 languages and its a basic goal of OpenMeetings to be easy to embed > into existing environments. It already uses many of Apache > Technologies like Tomcat, Mina, Velocity, Commons, ... > > As you can see below the last time we did the proposal we had > Hibernate in our software stack, we did refactor the hole project and > use openJPA now. > So that one should be no more blocker to it. > Red5 is used like a Servlet container and licensed under the LGPL, > Red5 can be obtained for example from the Debian Repository: > http://packages.debian.org/wheezy/red5-server > > You may find all existing documents and further material on the > GoogleCode pages: http://code.google.com/p/openmeetings/ > > We appreciate any feedback and comments on the proposal. > > Sebastian Wagner > > 2009/11/9 Ross Gardler : >> Just as a point of interest, I just completed a test meeting using >> OpenMeetings across three sites using the demo server. >> >> I was suitably impressed by the project. It has a few annoying >> limitations, but as an online meeting tool it is very good. to the >> extent that I will almost certainly be installing a copy on our own >> servers. I would be very happy to see it coming into the incubator and >> would be willing to be a mentor, assuming the legal issues are not >> blockers. >> >> Ross >> >> 2009/11/3 Alexei Fedotov : >>> Noel, >>> Regarding Theora codec, I have checked the page [1]. Currently, there >>> are no products which successfully use the codec for video >>> communication. Video-phone encodes and decodes the stream in >>> real-time, adopts the quality with regard to network conditions (e.g. >>> lost packet rate) and tries to minimize subjective effects of network >>> errors - the list of requirements is broader than for media players >>> Theora is mostly used. The work [2] says suggests using hardware >>> implementations for Theora codec because, otherwise "a computational >>> performance too high to be implemented in the camera by the universal >>> processor". >>> >>> So at least it requires some time and testing before I can say that >>> Theora-based solution is feasible. Another ecosystem change, like >>> embedding video-codecs in browsers, may resolve our need in a >>> different way. >>> >>> [1] http://www.vorbis.com/software/ >>> [2] http://www3.elphel.com/linuxtag/talks_2005/paper-11081 >>> >>> 2009/11/3 Noel J. Bergman : Alexei Fedotov wrote: > I see two long-term possibilities for synergy. > 1. BlueSky can integrate browser pannel in their client to handle a > whiteboard. In this case the code for whiteboard can be re-used in > both projects. > 2. They promise to get rid from mplayer and ffmpeg dependencies. If > they get a working streaming video-client under APL, this would help > us to remove the most imporant dependency from Flash. They are proposing to move to Theora/Vorbis, which is under a suitable license: http://www.vorbis.com/faq/#slic. Would that be suitable for your needs? > we [also] get more people on Apache who share the same task. Agreed. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >>> >>> -- >>> With best regards / с наилучшими пожеланиями, >>> Alexei Fedotov / Алексей Федотов, >>> http://www.tel
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
+1 from me too Mikhail Fursov gmail.com> writes: > > Used OpenMeetings yesterday for our local video web conference with 3 > sites online . It worked flawlessly. > > +1 from me! > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
