[VOTE][RESULT] Accept Pig graduation as a Hadoop subproject
On Fri, Oct 17, 2008 at 8:44 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > ...The Pig [1] and Hadoop [2] communities have voted to graduate Pig as a > Hadoop subproject. > > According to [3| the Incubator PMC needs to accept this graduation. > > Please cast your votes - as the weekend is starting, I'll tally the > vote open until Wednesday October 22n morning UTC The vote passes with +1s from the following 9 incubator PMC members, and no other votes: Yoav Shapira (mentor) Upayavira Doug Cutting (mentor) Craig L Russell Paul Fremantle Jukka Zitting Martijn Dashorst Matt Hogstrom Bertrand Delacretaz (mentor) Thanks everybody, and congratulations to the Pig team! I will update the incubator website info accordingly, in the next few days. -Bertrand > [1] > http://mail-archives.apache.org/mod_mbox/incubator-pig-dev/200810.mbox/[EMAIL > PROTECTED] > > [2] > http://mail-archives.apache.org/mod_mbox/hadoop-general/200810.mbox/[EMAIL > PROTECTED] > > [3] http://incubator.apache.org/guides/graduation.html#subproject > [4] http://en.wikipedia.org/wiki/Pig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool "clutch" assist oversight of all podlings
On Sun, Oct 19, 2008 at 12:37 PM, David Crossley <[EMAIL PROTECTED]> wrote: > ...I developed a tool called "clutch". Below are some notes > from its generated web page Just ran clutch to process the Pig graduation changes, inconsistencies between [1] and [2] were detected correctly, everything looks good. I just updated the pages on people.a.o, not synced to the website yet. Great stuff, David, thanks! -Bertrand [1] http://wiki.apache.org/incubator/ReportingSchedule [2] https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/index.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool "clutch" assist oversight of all podlings
Bertrand Delacretaz wrote: > David Crossley wrote: > > > ...I developed a tool called "clutch". Below are some notes > > from its generated web page > > Just ran clutch to process the Pig graduation changes, inconsistencies > between [1] and [2] were detected correctly, everything looks good. There is something wrong there. Clutch should not fail like this. The Pig entry should simply be removed from the table. I am now away to dinner. Will look later. -David > I just updated the pages on people.a.o, not synced to the website yet. > > Great stuff, David, thanks! > > -Bertrand > > [1] http://wiki.apache.org/incubator/ReportingSchedule > [2] > https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/index.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool "clutch" assist oversight of all podlings
On Wed, Oct 22, 2008 at 10:31 AM, David Crossley <[EMAIL PROTECTED]> wrote: > Bertrand Delacretaz wrote: >> ...Just ran clutch to process the Pig graduation changes, inconsistencies >> between [1] and [2] were detected correctly, everything looks good. > > There is something wrong there. Clutch should not > fail like this. The Pig entry should simply be > removed from the table I don't think Clutch failed - what I did is 1. Move pig from the "incubating" to "graduated" section of projects/index.html (or rather the xml source of that) 2. Run clutch before removing pig from the wiki ReportingSchedule page At that point clutch complained about pig missing from projects/index.html, as expected. 3. Remove pig from ReportingSchedule 4. Run clutch again, everything looks good to me, pig removed from the clutch.html page. BTW I don't think there's a link to clutch.html on the incubator website. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP CLEARANCE] Velocity-Tiles integration, need for someone to process the request
Dear all, I am Antonio Petrelli, PMC member of the Apache Tiles project. We would like to process the IP Clearance for the Velocity-Tiles integration, whose ZIP file containing the code and the IP clearance template are in this JIRA issue: https://issues.apache.org/struts/browse/TILES-170 We need someone that can process this IP clearance. Notice that Sergey Zolotaryov, the only original contributor, already sent a signed Software Grant and does not want to become a committer at the moment, but only donated the code. Thanks in advance Antonio Petrelli - 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-tabpanel&focusedCommentId=12641768#action_12641768 ] scott comer commented on INCUBATOR-86: -- hmmm. it appears someone is waiting on someone else who's waiting on them. but who? and why? > 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]
Re: new tool "clutch" assist oversight of all podlings
Bertrand Delacretaz wrote: > David Crossley wrote: > > Bertrand Delacretaz wrote: > >> ...Just ran clutch to process the Pig graduation changes, inconsistencies > >> between [1] and [2] were detected correctly, everything looks good. > > > > There is something wrong there. Clutch should not > > fail like this. The Pig entry should simply be > > removed from the table > > I don't think Clutch failed - what I did is Damnit, sorry to cause you effort. It was my side. I had neglected to do 'svn up' to pick up your changes to projects/index.xml file and clutch.py crashed for me. I read your message too quickly and thought you saw the same. Still, clutch.py needs to handle that. > 1. Move pig from the "incubating" to "graduated" section of > projects/index.html (or rather the xml source of that) > > 2. Run clutch before removing pig from the wiki ReportingSchedule page > > At that point clutch complained about pig missing from > projects/index.html, as expected. Ah, good test. Thanks. > 3. Remove pig from ReportingSchedule > > 4. Run clutch again, everything looks good to me, pig removed from the > clutch.html page. Fantastic. > BTW I don't think there's a link to clutch.html on the incubator website. Yeah, i haven't yet figured out which section of the left-hand menu to put it. I am inclined towards "Podling Guides" section just above the "Graduation" item, rather than the more official top-most section. I see this as serving many purposes. I will soon go ahead with that unless i hear otherwise, i.e. i presume that the IPMC is okay with this approach. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][RESULT] Accept Pig graduation as a Hadoop subproject
On Wed, Oct 22, 2008 at 9:52 AM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > ...I will update the incubator website info accordingly, in the next few > days... Done, the following pages reflect pig's new status: http://incubator.apache.org/projects/index.html http://incubator.apache.org/clutch.html http://incubator.apache.org/projects/pig.html And I have also removed pig from http://wiki.apache.org/incubator/ReportingSchedule -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What's up with WSRP4J?
Hi, According to clutch, WSRP4J has been incubating for 1876 days... Did not report at all this year AFAIK, and not much seems to be happening on the project lists [1] The code is in the portals svn space [3] with no disclaimer. About a year ago [2] Carsten mentioned a pending license issue that was blocking the project. I think it's time to do something with that podling - if the code is fine but not suitable for Apache licensing it's probably better to move it somewhere else. -Bertrand [1] http://portals.apache.org/wsrp4j/contributing/mail.html [2] http://markmail.org/message/weuvsdg5fxh62yw2 [3] http://svn.apache.org/repos/asf/portals/wsrp4j/trunk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Policy] clarify podling acceptance: INCUBATOR-93
David Crossley wrote: > See patch at > https://issues.apache.org/jira/browse/INCUBATOR-93 > to clarify the acceptance phase of new podlings > because the process depends on who is Sponsor. > > The gist of it is: > - > In Incubation_Policy.xml ... > * Add sentence to distinguish between IPMC being the sponsor or a TLP. > * Move the "Acceptance of Mentors" paragraph to its own sub-section. > > In Process_Description.xml ... > * Add an "Introduction" section at beginning to remind to read other > documents which also explain the process. > * Add words to distinguish between IPMC being the sponsor or a TLP. > - > > According to: > http://incubator.apache.org/incubation/Incubation_Policy.html#Changing+this+Document > "All changes must be authorised by the Incubator PMC." > > To me it seems to be straight-forward changes. > It is more than just tweaks, so it needs a vote. > > Please vote on accepting these documentation changes. > > This majority vote is open for one week. Votes from the > Incubator PMC members are binding. Three people voted (one inside the INCUBATOR-93) and those were all +1 and all binding votes. I read that as a successful majority vote and will proceed to make the changes. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-95) Release guidelines contain incorrect permissions, url for distributing release
[ https://issues.apache.org/jira/browse/INCUBATOR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642012#action_12642012 ] Aidan Skinner commented on INCUBATOR-95: Bueller? You can really hork things if you follow the instructions as is. Really, really hork things. In bad, annoying to recover from ways. > Release guidelines contain incorrect permissions, url for distributing release > -- > > Key: INCUBATOR-95 > URL: https://issues.apache.org/jira/browse/INCUBATOR-95 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Aidan Skinner > Attachments: INCUBATOR-95.patch, INCUBATOR-95.patch > > > The chmod command in the release pages is wrong and knackers stuff. The > directory in the checklist is also incorrect. > In addition, the suggested permission scheme leaves all incubator artifacts > writable by a group of around 500 people, which is unfortunate. -- 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-93) Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor
[ https://issues.apache.org/jira/browse/INCUBATOR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley closed INCUBATOR-93. --- Resolution: Fixed The Vote was a successful result. One person voted here, the others on general@ list. [Vote] [Policy] clarify podling acceptance: INCUBATOR-93Link to this message http://markmail.org/message/w5e2j6fyavwom7bm Patch is now applied. > Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process > depends on who is Sponsor > - > > Key: INCUBATOR-93 > URL: https://issues.apache.org/jira/browse/INCUBATOR-93 > Project: Incubator > Issue Type: Bug > Components: policy >Reporter: David Crossley > Attachments: INCUBATOR-93.txt > > > This section details the next step after a successful acceptance vote. It > involves a special message to general@ and acknowledgment from IPMC and 72 > hours wait. It seems that this is not being followed, rather just doing a > vote summary. Does this section need review, or is this a necessary > due-process type of thing? It should at least be clarified who can do this > step. > This arises because i am investigating why some projects are not commencing > properly, e.g. adding to reporting roster and getting their status document > started. -- 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-95) Release guidelines contain incorrect permissions, url for distributing release
[ https://issues.apache.org/jira/browse/INCUBATOR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley closed INCUBATOR-95. --- Resolution: Fixed I applied your patch, thanks. According to http://incubator.apache.org/guides/website.html the first paragraph of "Edit the content" explains that any podling committer can edit these documents. So no need to wait to fix any docs inaccuracies. The "policy" documents are review-then-commit, otherwise go ahead. > Release guidelines contain incorrect permissions, url for distributing release > -- > > Key: INCUBATOR-95 > URL: https://issues.apache.org/jira/browse/INCUBATOR-95 > Project: Incubator > Issue Type: Bug > Components: site >Reporter: Aidan Skinner > Attachments: INCUBATOR-95.patch, INCUBATOR-95.patch > > > The chmod command in the release pages is wrong and knackers stuff. The > directory in the checklist is also incorrect. > In addition, the suggested permission scheme leaves all incubator artifacts > writable by a group of around 500 people, which is unfortunate. -- 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: new tool "clutch" assist oversight of all podlings
David Crossley wrote: > Bertrand Delacretaz wrote: > > > > BTW I don't think there's a link to clutch.html on the incubator website. > > Yeah, i haven't yet figured out which section of the > left-hand menu to put it. > > I am inclined towards "Podling Guides" section just above > the "Graduation" item, rather than the more official > top-most section. I see this as serving many purposes. > > I will soon go ahead with that unless i hear otherwise, > i.e. i presume that the IPMC is okay with this approach. I decided that the "guides" all belong as as a group, so i put it at the top-level after them. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-91) Request User accounts from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642054#action_12642054 ] Niclas Hedhman commented on INCUBATOR-91: - Requests sent to root. This typically takes a couple of days, depending on how busy they are. > Request User accounts from INFRA > > > Key: INCUBATOR-91 > URL: https://issues.apache.org/jira/browse/INCUBATOR-91 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > Once the CLAs are submitted, for each initial committer request the user > account from INFRA. It should contain "preferred id", "alternate1 id", > "alternate2 id", "full name" and "valid email address". -- 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] Resolved: (INCUBATOR-91) Request User accounts from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved INCUBATOR-91. - Resolution: Fixed Marking this as Resolved. Close it when the Confirmations arrive from root@ > Request User accounts from INFRA > > > Key: INCUBATOR-91 > URL: https://issues.apache.org/jira/browse/INCUBATOR-91 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > Once the CLAs are submitted, for each initial committer request the user > account from INFRA. It should contain "preferred id", "alternate1 id", > "alternate2 id", "full name" and "valid email address". -- 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-87) Submission of ICLAs for initial committers
[ https://issues.apache.org/jira/browse/INCUBATOR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated INCUBATOR-87: Description: All committers must file ICLAs with the ASF Secretary. By snail mail, fax or Signed Email/ (was: All committers must file ICLAs and CCLAs with the ASF Secretary. By snail mail, fax or Signed Email/) Summary: Submission of ICLAs for initial committers (was: Submission of ICLAs and CCLAs for initial committers) > Submission of ICLAs for initial committers > -- > > Key: INCUBATOR-87 > URL: https://issues.apache.org/jira/browse/INCUBATOR-87 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > All committers must file ICLAs with the ASF Secretary. By snail mail, fax or > Signed Email/ -- 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-87) Submission of ICLAs for initial committers
[ https://issues.apache.org/jira/browse/INCUBATOR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-87. --- Resolution: Fixed All initial committers have their ICLAs on file. > Submission of ICLAs for initial committers > -- > > Key: INCUBATOR-87 > URL: https://issues.apache.org/jira/browse/INCUBATOR-87 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > All committers must file ICLAs with the ASF Secretary. By snail mail, fax or > Signed Email/ -- 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] Created: (INCUBATOR-97) Submission of CCLAs for initial committers
Submission of CCLAs for initial committers -- Key: INCUBATOR-97 URL: https://issues.apache.org/jira/browse/INCUBATOR-97 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman The company that a committer work for must acknowledge that the employee(s) in question are allowed to work on Apache projects. In this case, that is Cisco, and we have no CCLA at all on file from Cisco. -- 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: [jira] Created: (INCUBATOR-97) Submission of CCLAs for initial committers
> The company that a committer work for must acknowledge that the employee(s) > in question are allowed to work on Apache projects. > > In this case, that is Cisco, and we have no CCLA at all on file from Cisco. This is incorrect (unless you are speaking of you). CCLA's are a convenience for the benefit of ICLA signatories. It is not the incubator's responsibility to validate that ICLA signers are legally able to do so. Depending on their contractual relationship to their employer/contractor they may need this or they may not. Point ICLA signers at this document to reinforce the fact that they -might- not be able to sign the ICLA without it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (INCUBATOR-97) Submission of CCLAs for initial committers
On Thu, Oct 23, 2008 at 7:38 AM, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: >> The company that a committer work for must acknowledge that the employee(s) >> in question are allowed to work on Apache projects. >> >> In this case, that is Cisco, and we have no CCLA at all on file from Cisco. > > This is incorrect (unless you are speaking of you). > > CCLA's are a convenience for the benefit of ICLA signatories. It is not the > incubator's responsibility to validate that ICLA signers are legally able to > do so. Depending on their contractual relationship to their > employer/contractor > they may need this or they may not. > > Point ICLA signers at this document to reinforce the fact that they -might- > not > be able to sign the ICLA without it. Ook So, what you are saying is that we now asking the committers to become legally affluent? My point; What happens to average committer candidate when the employer says "No, you don't need us to sign this..."? Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (INCUBATOR-97) Submission of CCLAs for initial committers
Niclas Hedhman wrote: > > Ook So, what you are saying is that we now asking the > committers to become legally affluent? No, only to become aware of the fact that what they do is owned by their employer, or that it is not. In most cases in CA US for example, what you do on "your time" in the evening is yours, at least if it is not related to your work projects and doesn't borrow any code from the office. In other cases, it is not. And they are signing a document, I almost used the word fraud to describe signing this when, in fact, they are not authorized to commit under the AL to the ASF repositories due to their employers ownership of the code and lack of authorization. That is what it is. > My point; What happens to average committer candidate when the > employer says "No, you don't need us to sign this..."? My point; this has been asked and answered many times on board@, legal@ and other lists. Until they issue a different opinion, the foundation-wide policy is to accept CCLA's for clarification on the individual's behalf. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
