Re: Git write access for podlings
On 02/01/15 16:40, David Nalley wrote: On Fri, Jan 2, 2015 at 5:36 AM, Stian Soiland-Reyes st...@apache.org wrote: Git allows you to commit as whoever you want - e.g. like in SMTP email, the headers are decided by the sender. SVN on the other hand will show the authenticated user in the commit log. So - speaking as a former sysadmin - it sounds a bit daring to let anyone new to Apache from a fresh Incubator proposal to also get instant write access to all Incubator projects, including those that are just about to graduate. From a git commit log perspective, this is true, but we also retain push records that show us the user authenticated as, as well as the IP Address they are pushing commits from. In example: https://git-wip-us.apache.org/logs/asf/incubator-nifi.git I looked at Jena's log and until Dec 2 this year, the IP address was always @http.192.168.0.58 and since 2014-12-03 there are likely looking true IP addresses but of the NAT gateway used. Andy That said - assuming there has not been any reported abuse of this global write access - then it is a very good sign of all the new committers being responsible people - or perhaps they just didn't know they had that write access to begin with :). It's a trust-thing - I remember when I started my first proper sysadmin job, and on day one received the root passwords for systems running web and email for 30.000 students. Don't mess it up was implicit. Apache Commons has already given write access to *all* ASF committers [1] - which would presumably include any incubator committers. If it's good enough for for Commons, it should be good enough for Incubator. Part of moving to Apache is also to trust all your committers. [1] https://mail-archives.apache.org/mod_mbox/commons-dev/201412.mbox/%3ccab917rjy57z-4pnwthvr9tuq7y3td8usg8jcmhvdthalwho...@mail.gmail.com%3E Even with the danger of introducing a bigger temptation by explicitly documenting the incubator-wide write policy - I would still +1 to document this so you are aware and don't accidentally push back (as git workflow is to commit locally and it is a bit easy to accidentally do git push) - with a clause that this does not mean you have formally become a committer on the other incubator projects. I would propose to also improve documentation at http://wiki.apache.org/general/GitAtApache http://www.apache.org/dev/git.html http://www.apache.org/dev/writable-git so it does not give impression you have to use SVN-with-git-mriroring or that writeable GIT is experimental. I don't know enough about the particular setup at git.apache.org yet to do it myself. sigh I thought we had removed all of the experimental labels. Thanks for finding these. --David - 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: Git write access for podlings
On Fri, Jan 2, 2015 at 5:36 AM, Stian Soiland-Reyes st...@apache.org wrote: Git allows you to commit as whoever you want - e.g. like in SMTP email, the headers are decided by the sender. SVN on the other hand will show the authenticated user in the commit log. So - speaking as a former sysadmin - it sounds a bit daring to let anyone new to Apache from a fresh Incubator proposal to also get instant write access to all Incubator projects, including those that are just about to graduate. From a git commit log perspective, this is true, but we also retain push records that show us the user authenticated as, as well as the IP Address they are pushing commits from. In example: https://git-wip-us.apache.org/logs/asf/incubator-nifi.git That said - assuming there has not been any reported abuse of this global write access - then it is a very good sign of all the new committers being responsible people - or perhaps they just didn't know they had that write access to begin with :). It's a trust-thing - I remember when I started my first proper sysadmin job, and on day one received the root passwords for systems running web and email for 30.000 students. Don't mess it up was implicit. Apache Commons has already given write access to *all* ASF committers [1] - which would presumably include any incubator committers. If it's good enough for for Commons, it should be good enough for Incubator. Part of moving to Apache is also to trust all your committers. [1] https://mail-archives.apache.org/mod_mbox/commons-dev/201412.mbox/%3ccab917rjy57z-4pnwthvr9tuq7y3td8usg8jcmhvdthalwho...@mail.gmail.com%3E Even with the danger of introducing a bigger temptation by explicitly documenting the incubator-wide write policy - I would still +1 to document this so you are aware and don't accidentally push back (as git workflow is to commit locally and it is a bit easy to accidentally do git push) - with a clause that this does not mean you have formally become a committer on the other incubator projects. I would propose to also improve documentation at http://wiki.apache.org/general/GitAtApache http://www.apache.org/dev/git.html http://www.apache.org/dev/writable-git so it does not give impression you have to use SVN-with-git-mriroring or that writeable GIT is experimental. I don't know enough about the particular setup at git.apache.org yet to do it myself. sigh I thought we had removed all of the experimental labels. Thanks for finding these. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Reflections from the outgoing Chair
The problem I am concerned with is the lack of mentoring support in a small number of projects and the fact the IPMC doesn't handle those situations well. Other than that I agree with Marvin - the IPMC usually does a fantastic job Sent from my Windows Phone From: Marvin Humphreymailto:mar...@rectangular.com Sent: 1/1/2015 7:51 PM To: general@incubator.apache.orgmailto:general@incubator.apache.org Subject: Re: Reflections from the outgoing Chair On Thu, Jan 1, 2015 at 5:32 PM, Benson Margulies bimargul...@gmail.com wrote: three cheers for Roman for all his hard work! +1! +1! +1! For all other projects in the Foundation, we say, 'The chair is just a clerk who facilitates communications with the board.' Here at the IPMC, we expect the chair to be moderator of a very fractious set of arguments about how to incubate (or whether to even have an incubator). A leader, even. For this reason, no one who runs for IPMC Chair will receive my support unless they pledge to serve for a limited duration. It is my impression that no one is very happy with the current state of the incubation process. I dissent. The Incubator is functioning about as well as it could under difficult circumstances, and I am extremely proud of our ongoing work. Including all that you do, Benson! The problems faced by the Incubator are the inevitable consequence of flaws in the Apache Software Foundation and The Apache Way. * We are expected to teach The Apache Way, but The Apache Way has no authoritative definition. * We are expected to enforce Apache policy, but the the documentation of Apache policy is a sprawling, incoherent mess. Yes, incubator.apache.org is awful, but so is www.apache.org/devhttp://www.apache.org/dev and community.apache.org. Why can't Apache produce decent policy? For the same reason that projects under Apache governance produce notoriously bloated APIs. * Consensus requirements make it all but impossible to remove complexity. * Openness requirements bias the system towards adding complexity. People should leave the Incubator alone and go work on more pressing problems. Come back once the ASF has policies normal people can understand. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Git write access for podlings
On Fri, Jan 2, 2015 at 11:52 AM, Andy Seaborne a...@apache.org wrote: On 02/01/15 16:40, David Nalley wrote: On Fri, Jan 2, 2015 at 5:36 AM, Stian Soiland-Reyes st...@apache.org wrote: Git allows you to commit as whoever you want - e.g. like in SMTP email, the headers are decided by the sender. SVN on the other hand will show the authenticated user in the commit log. So - speaking as a former sysadmin - it sounds a bit daring to let anyone new to Apache from a fresh Incubator proposal to also get instant write access to all Incubator projects, including those that are just about to graduate. From a git commit log perspective, this is true, but we also retain push records that show us the user authenticated as, as well as the IP Address they are pushing commits from. In example: https://git-wip-us.apache.org/logs/asf/incubator-nifi.git I looked at Jena's log and until Dec 2 this year, the IP address was always @http.192.168.0.58 and since 2014-12-03 there are likely looking true IP addresses but of the NAT gateway used. Indeed - originally git-wip-us was directly exposed to the internet. That changed a couple of years back and we had a SSL terminator host (which had the internal address of 192.168.0.58, because we failed to enable the forwarded IP address.) That's since been dealt with, but history is what it is. The generally, more useful item is that someone authenticated (successfully) as $user and pushed a commit. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reflections from the outgoing Chair
Marvin, I did go away. I came back to help with a podling, and fell into a conversation started by discontented board members. You might push back on the board, formally, and challenge them to either officially be discontented or leave the iPMC alone. Me, I have an idea for a proposal that might make everyone equally unhappy and improve some things. --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Git write access for podlings
Git allows you to commit as whoever you want - e.g. like in SMTP email, the headers are decided by the sender. SVN on the other hand will show the authenticated user in the commit log. So - speaking as a former sysadmin - it sounds a bit daring to let anyone new to Apache from a fresh Incubator proposal to also get instant write access to all Incubator projects, including those that are just about to graduate. That said - assuming there has not been any reported abuse of this global write access - then it is a very good sign of all the new committers being responsible people - or perhaps they just didn't know they had that write access to begin with :). It's a trust-thing - I remember when I started my first proper sysadmin job, and on day one received the root passwords for systems running web and email for 30.000 students. Don't mess it up was implicit. Apache Commons has already given write access to *all* ASF committers [1] - which would presumably include any incubator committers. If it's good enough for for Commons, it should be good enough for Incubator. Part of moving to Apache is also to trust all your committers. [1] https://mail-archives.apache.org/mod_mbox/commons-dev/201412.mbox/%3ccab917rjy57z-4pnwthvr9tuq7y3td8usg8jcmhvdthalwho...@mail.gmail.com%3E Even with the danger of introducing a bigger temptation by explicitly documenting the incubator-wide write policy - I would still +1 to document this so you are aware and don't accidentally push back (as git workflow is to commit locally and it is a bit easy to accidentally do git push) - with a clause that this does not mean you have formally become a committer on the other incubator projects. I would propose to also improve documentation at http://wiki.apache.org/general/GitAtApache http://www.apache.org/dev/git.html http://www.apache.org/dev/writable-git so it does not give impression you have to use SVN-with-git-mriroring or that writeable GIT is experimental. I don't know enough about the particular setup at git.apache.org yet to do it myself. On 31 December 2014 at 14:56, Ted Dunning ted.dunn...@gmail.com wrote: On Wed, Dec 31, 2014 at 12:27 PM, John D. Ament johndam...@apache.org wrote: On Wed Dec 31 2014 at 2:45:48 PM David Nalley da...@gnsa.us wrote: On Wed, Dec 31, 2014 at 2:40 PM, John D. Ament johndam...@apache.org wrote: On Wed Dec 31 2014 at 2:24:36 PM David Nalley da...@gnsa.us wrote: On Wed, Dec 31, 2014 at 11:59 AM, John D. Ament johndam...@apache.org wrote: Hi, So something Jan and I ran into on the infra list, does anyone know definitively what the access rights given to a podling's git repo are, if they request one (instead of a svn directory)? If nothing else we should document it somewhere on the incubator site indicating the permission sets for both svn and git. My current understanding is that svn sites are typically incubator wide, svn repos are confined to a specific list, and git repos are incubator wide. The git one in particular because we don't create ldap groups for podlings and I've heard that we only do groups in git (not individual lists). git is tied to LDAP, and all podling repos are writable by anyone in the incubator LDAP group. (there are no podling LDAP groups) Got it thanks. I'll update the docs to reflect this as the permission scheme. And here I think will come in Jan's bigger question - do we really want all podling committers to be able to commit to all other podlings? My question is: What problem are you trying to solve? And has it really proven to be a problem? I don't think anyone has abused their ability to commit to all projects, and it's been this way as long as git has been available. I'm not sure that there will be an issue. It could just be a couple of IPMC members being a little more cautious that needed. It's more than likely no one's going to care. To date, we have always told podlings that the initial committers and your mentors are the ones who have write access. Now we're saying if you're using git, it's any of the 1k + (i might be way off) members of the incubator group. Would it be much harder to create the ldap group up front when the podling's created, and shuffle people in/out at graduation? If it ain't broke ... Is there even a problem? I haven't ever heard of it. If there isn't a problem, why are you worried about it? -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Incubator Wiki] Update of January2015 by JosephWitt
Hi Joe, I see you updated your mentor sign off list. This list now does not match what is in podlings.xml. Please update podlings.xml to match this list, if these three were in fact added as mentors to your project. John On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Incubator Wiki for change notification. The January2015 page has been changed by JosephWitt: https://wiki.apache.org/incubator/January2015?action=diffrev1=6rev2=7 Three most important issues to address in the move towards graduation: - 1. - 2. - 3. + 1. Produce an initial release. + 2. Grow our community beyond the initial set of committers. + 3. Establish rhythm for releases, review processes, and document how to most effectively bring on new committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? + Nothing we wish to raise at this time. - - How has the community developed since the last report? - - - - How has the project developed since the last report? + How has the community developed since the last report? + The dev mailing list has picked up 20 new e-mails since the last report and is now at 62 (commits has grown to 25). + At the suggestion of the community we've adopted a review-then-commit strategy which is designed to among other things help with community development. + We've received several patches from members outside the initial committer list including changes which dramatically improved our build process and provide new extensions. + How has the project developed since the last report? - Date of last release: + All of our current infrastructure needs are setup and things are working really well. Our focus now is on working towards our first release which is 0.0.1 and presently + comprised of 85 JIRA issues the vast majority of which are resolved. We've conducted a thorough review of all source files to ensure proper license headers/notices/disclaimers + are present. We've completed a thorough review and modification of the overall LICENSE and NOTICE files in preparation for release. We've conducted the initial podling name search + and submitted the ticket for that analysis to be verified and confirmed. Our main focus now is getting past the first release so we can do a better job of building the community. - -XX-XX - When were the last committers or PMC members elected? + Date of last release: + N/A + When were the last committers or PMC members elected? + + We have not grown the official committer list beyond the initial committer list. Though there are a couple of folks who are committing fairly consistently now and a new member to join the dev mailing list that is very promising. Signed-off-by: @@ -731, +737 @@ [ ](nifi) Arvind Prabhakar [ ](nifi) Sergio Fernandez [ ](nifi) Benson Margulies + [ ](nifi) Brock Noland + [ ](nifi) Drew Farris + [ ](nifi) Andrew Purtell Shepherd/Mentor notes: - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org
Re: [Incubator Wiki] Update of January2015 by JosephWitt
John, I am not quite sure how to do that. Where can I find that? The mentor list we have is from here: http://incubator.apache.org/projects/nifi.html Thanks Joe On Fri, Jan 2, 2015 at 3:09 PM, John D. Ament johndam...@apache.org wrote: Hi Joe, I see you updated your mentor sign off list. This list now does not match what is in podlings.xml. Please update podlings.xml to match this list, if these three were in fact added as mentors to your project. John On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Incubator Wiki for change notification. The January2015 page has been changed by JosephWitt: https://wiki.apache.org/incubator/January2015?action=diffrev1=6rev2=7 Three most important issues to address in the move towards graduation: - 1. - 2. - 3. + 1. Produce an initial release. + 2. Grow our community beyond the initial set of committers. + 3. Establish rhythm for releases, review processes, and document how to most effectively bring on new committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? + Nothing we wish to raise at this time. - - How has the community developed since the last report? - - - - How has the project developed since the last report? + How has the community developed since the last report? + The dev mailing list has picked up 20 new e-mails since the last report and is now at 62 (commits has grown to 25). + At the suggestion of the community we've adopted a review-then-commit strategy which is designed to among other things help with community development. + We've received several patches from members outside the initial committer list including changes which dramatically improved our build process and provide new extensions. + How has the project developed since the last report? - Date of last release: + All of our current infrastructure needs are setup and things are working really well. Our focus now is on working towards our first release which is 0.0.1 and presently + comprised of 85 JIRA issues the vast majority of which are resolved. We've conducted a thorough review of all source files to ensure proper license headers/notices/disclaimers + are present. We've completed a thorough review and modification of the overall LICENSE and NOTICE files in preparation for release. We've conducted the initial podling name search + and submitted the ticket for that analysis to be verified and confirmed. Our main focus now is getting past the first release so we can do a better job of building the community. - -XX-XX - When were the last committers or PMC members elected? + Date of last release: + N/A + When were the last committers or PMC members elected? + + We have not grown the official committer list beyond the initial committer list. Though there are a couple of folks who are committing fairly consistently now and a new member to join the dev mailing list that is very promising. Signed-off-by: @@ -731, +737 @@ [ ](nifi) Arvind Prabhakar [ ](nifi) Sergio Fernandez [ ](nifi) Benson Margulies + [ ](nifi) Brock Noland + [ ](nifi) Drew Farris + [ ](nifi) Andrew Purtell Shepherd/Mentor notes: - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org
Re: [Incubator Wiki] Update of January2015 by JosephWitt
Funny, because I had just started working on those instructions.
http://incubator.apache.org/guides/ppmc.html
The files mentioned under adding mentors, it looks like someone already
updated projects/{podling}.xml (nifi.xml, to generate nifi.html). The
other file is this:
http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
On Fri Jan 02 2015 at 3:12:00 PM Joe Witt joe.w...@gmail.com wrote:
John,
I am not quite sure how to do that. Where can I find that?
The mentor list we have is from here:
http://incubator.apache.org/projects/nifi.html
Thanks
Joe
On Fri, Jan 2, 2015 at 3:09 PM, John D. Ament johndam...@apache.org
wrote:
Hi Joe,
I see you updated your mentor sign off list. This list now does not
match
what is in podlings.xml. Please update podlings.xml to match this list,
if
these three were in fact added as mentors to your project.
John
On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org
wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Incubator Wiki
for change notification.
The January2015 page has been changed by JosephWitt:
https://wiki.apache.org/incubator/January2015?action=
diffrev1=6rev2=7
Three most important issues to address in the move towards
graduation:
- 1.
- 2.
- 3.
+ 1. Produce an initial release.
+ 2. Grow our community beyond the initial set of committers.
+ 3. Establish rhythm for releases, review processes, and document
how
to most effectively bring on new committers.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
+ Nothing we wish to raise at this time.
-
- How has the community developed since the last report?
-
-
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
+ The dev mailing list has picked up 20 new e-mails since the last
report
and is now at 62 (commits has grown to 25).
+ At the suggestion of the community we've adopted a review-then-commit
strategy which is designed to among other things help with community
development.
+ We've received several patches from members outside the initial
committer list including changes which dramatically improved our build
process and provide new extensions.
+ How has the project developed since the last report?
- Date of last release:
+ All of our current infrastructure needs are setup and things are
working
really well. Our focus now is on working towards our first release
which
is 0.0.1 and presently
+ comprised of 85 JIRA issues the vast majority of which are resolved.
We've conducted a thorough review of all source files to ensure proper
license headers/notices/disclaimers
+ are present. We've completed a thorough review and modification of
the
overall LICENSE and NOTICE files in preparation for release. We've
conducted the initial podling name search
+ and submitted the ticket for that analysis to be verified and
confirmed. Our main focus now is getting past the first release so we
can
do a better job of building the community.
- -XX-XX
- When were the last committers or PMC members elected?
+ Date of last release:
+ N/A
+ When were the last committers or PMC members elected?
+
+ We have not grown the official committer list beyond the initial
committer list. Though there are a couple of folks who are committing
fairly consistently now and a new member to join the dev mailing list
that
is very promising.
Signed-off-by:
@@ -731, +737 @@
[ ](nifi) Arvind Prabhakar
[ ](nifi) Sergio Fernandez
[ ](nifi) Benson Margulies
+ [ ](nifi) Brock Noland
+ [ ](nifi) Drew Farris
+ [ ](nifi) Andrew Purtell
Shepherd/Mentor notes:
-
To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
For additional commands, e-mail: cvs-h...@incubator.apache.org
Re: [Incubator Wiki] Update of January2015 by JosephWitt
John,
Cool no problem. I couldn't do it through raw svn for some reason i'll
look into. But just did it via CMS. So I think it is all good.
If not please advise.
Thanks
Joe
On Fri, Jan 2, 2015 at 3:21 PM, John D. Ament johndam...@apache.org wrote:
Funny, because I had just started working on those instructions.
http://incubator.apache.org/guides/ppmc.html
The files mentioned under adding mentors, it looks like someone already
updated projects/{podling}.xml (nifi.xml, to generate nifi.html). The
other file is this:
http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
On Fri Jan 02 2015 at 3:12:00 PM Joe Witt joe.w...@gmail.com wrote:
John,
I am not quite sure how to do that. Where can I find that?
The mentor list we have is from here:
http://incubator.apache.org/projects/nifi.html
Thanks
Joe
On Fri, Jan 2, 2015 at 3:09 PM, John D. Ament johndam...@apache.org
wrote:
Hi Joe,
I see you updated your mentor sign off list. This list now does not
match
what is in podlings.xml. Please update podlings.xml to match this
list,
if
these three were in fact added as mentors to your project.
John
On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org
wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Incubator
Wiki
for change notification.
The January2015 page has been changed by JosephWitt:
https://wiki.apache.org/incubator/January2015?action=
diffrev1=6rev2=7
Three most important issues to address in the move towards
graduation:
- 1.
- 2.
- 3.
+ 1. Produce an initial release.
+ 2. Grow our community beyond the initial set of committers.
+ 3. Establish rhythm for releases, review processes, and document
how
to most effectively bring on new committers.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
be
aware of?
+ Nothing we wish to raise at this time.
-
- How has the community developed since the last report?
-
-
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
+ The dev mailing list has picked up 20 new e-mails since the last
report
and is now at 62 (commits has grown to 25).
+ At the suggestion of the community we've adopted a
review-then-commit
strategy which is designed to among other things help with community
development.
+ We've received several patches from members outside the initial
committer list including changes which dramatically improved our
build
process and provide new extensions.
+ How has the project developed since the last report?
- Date of last release:
+ All of our current infrastructure needs are setup and things are
working
really well. Our focus now is on working towards our first release
which
is 0.0.1 and presently
+ comprised of 85 JIRA issues the vast majority of which are
resolved.
We've conducted a thorough review of all source files to ensure
proper
license headers/notices/disclaimers
+ are present. We've completed a thorough review and modification of
the
overall LICENSE and NOTICE files in preparation for release. We've
conducted the initial podling name search
+ and submitted the ticket for that analysis to be verified and
confirmed. Our main focus now is getting past the first release so
we
can
do a better job of building the community.
- -XX-XX
- When were the last committers or PMC members elected?
+ Date of last release:
+ N/A
+ When were the last committers or PMC members elected?
+
+ We have not grown the official committer list beyond the initial
committer list. Though there are a couple of folks who are
committing
fairly consistently now and a new member to join the dev mailing list
that
is very promising.
Signed-off-by:
@@ -731, +737 @@
[ ](nifi) Arvind Prabhakar
[ ](nifi) Sergio Fernandez
[ ](nifi) Benson Margulies
+ [ ](nifi) Brock Noland
+ [ ](nifi) Drew Farris
+ [ ](nifi) Andrew Purtell
Shepherd/Mentor notes:
-
To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
For additional commands, e-mail: cvs-h...@incubator.apache.org
Re: [DISCUSS] Rolling shepherds?
Hi - I was off of the mailing lists for sometime. Work has been taking most all of my time for most of 2014 and I am catching up today. Please remove me from the shepherd list for a few months. I'll let the list know if I find enough bandwidth later in the new year. Regards, Dave On Dec 10, 2014, at 11:26 PM, Roman Shaposhnik wrote: Thanks for running the report, John! Not sure what the next step should be, but perhaps reaching out to these folks directly and asking whether they still want to be listed as shepherds? Thanks, Roman. On Tue, Dec 9, 2014 at 6:30 PM, John D. Ament johndam...@apache.org wrote: At least for this go around, I did the work manually (basically, scan the report, see who had some problem that a shepherd could have helped with and did the shepherd provide a comment). Comparing podlings that weren't quite perfect to shepherds that made notes of it. I would say the following shepherds did not provide due diligence during this month's report: - Andrei Savu * - Dave Fisher - Matthew Franklin - Raphael Bircher The following shepherds either did not provide, or did provide but saw no issues to comment on within their podlings: - Alan Cabrera - Ross Gardler - Suresh Marru Basically, this means that more than 50% of the shepherds are seemingly idle on the report perspective. John * = I was split on Andrei's placing, as Drill should have fallen off but they have not properly graduated from podlings.xml stand point. On Tue Nov 25 2014 at 4:33:06 PM Roman Shaposhnik ro...@shaposhnik.org wrote: On Tue, Nov 25, 2014 at 1:25 PM, jan i j...@apache.org wrote: Seen from the POW of one who is new around here, it seems a bit like having a title for the sake of a title. I mean, we have to call that function *something* I understand and value the functions of both champion and mentor and of course also the iPMC. But I fail to see the big difference between being an official shepherd, and just helping a project. The only difference here is that we have to track shepherd so that our script knows the pool of folks to assign. Also, being on that list is a really good karma booster for non-ASF members interested in helping around Incubator in a more formal capacity. Thanks, Roman. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reflections from the outgoing Chair
On 01/01/2015 08:32 PM, Benson Margulies wrote: I'd like to raise a topic directly related to the succession. To start, three cheers for Roman for all his hard work! cheers += 3; - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Reflections from the outgoing Chair
On Fri, Jan 2, 2015 at 6:53 AM, Benson Margulies bimargul...@gmail.com wrote: You might push back on the board, formally, and challenge them to either officially be discontented or leave the iPMC alone. I've been defending the Incubator before the Board for some time. I actually called in to the December Board meeting and was granted a request to speak during the Incubator segment; that's only the second time I've had something I thought was important enough to take the floor during a Board meeting. The critiques I've heard from the Board of late fall into roughly two categories. 1. The Incubator is not providing certain podlings with enough Mentoring. 2. The Incubator is graduating podlings who do not understand The Apache Way. I agree with Roman that the first problem arises due to fundamental flaws in the incentive structure of the Incubator. We have made some progress mitigating the consequences of this problem, but we have not addressed the underlying cause. To make further progress, I support a variety of approaches including controlled experiments (e.g. NiFi as pTLP) and incremental, reversible changes (such as requiring Mentor checkoff). The second critique is the one I take issue with. When TLPs transgress against some aspect of The Apache Way -- classically release policy, though most recently the issue has been PMC stratification -- some fraction of the Board seems to find fault with the Incubator for providing insufficient training. In my view, if the Board wants TLPs to follow Apache's rules better, it makes more sense to focus on making the rules coherent than giving the Incubator flak for failing to teach incoherent rules. I'd like to help -- I've got release policy clarifications in the can[1]. But in order to drive them through to final consensus I figure I have to set aside 2-4 weeks where reacting to developments on legal-discuss@apache must be my top priority at all times -- and since I got busy last fall I haven't been able to make such a commitment. Pruning complexity from Apache's policy documentation is hard. Marvin Humphrey [1] https://github.com/rectang/asfrelease - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
