Re: recognizing valuable non-code contributions
Many more than one, in fact one of the early members fits this category. --- Twitter: @rgardler From: hedh...@gmail.com <hedh...@gmail.com> on behalf of Niclas Hedhman <nic...@hedhman.org> Sent: Friday, October 14, 2016 4:11:59 PM To: dev@community.apache.org Subject: Re: recognizing valuable non-code contributions Reminder, ASF has at least one *Member* who doesn't (didn't?) know how to operate source control. But very valuable to the foundation in other ways. Cheers On Fri, Oct 14, 2016 at 11:04 PM, sebb <seb...@gmail.com> wrote: > On 14 October 2016 at 15:13, A. Soroka <aj...@virginia.edu> wrote: > > I was responding to a previous message from Greg Chase: > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F34f2f4859aac61141cfe903a692c58=01%7C01%7CRoss.Gardler%40microsoft.com%7C71298d6b19d14078a42f08d3f487914d%7C72f988bf86f141af91ab2d7cd011db47%7C1=snrwvush6yedeeYJJFAgKSxlx7GCT4%2FOHFiZdhP3jnQ%3D=0 > 06e50282eb6ca388a7f8959d35@%3Cdev.community.apache.org%3E > > > > but perhaps I read too much into his remark "As a frequent non-code > contributor to several projects, having people like us as PMC (or PPMC) > members seems to do the trick." > > I see. > > In order to commit, one must be a committer, but the reverse is not true. > People with committer status don't have to commit code. > They may commit docn or not commit at all. > > > --- > > A. Soroka > > The University of Virginia Library > > > >> On Oct 14, 2016, at 10:08 AM, sebb <seb...@gmail.com> wrote: > >> > >> On 14 October 2016 at 12:16, A. Soroka <aj...@virginia.edu> wrote: > >>> Thanks, community thinkers! > >>> > >>> The consensus is overwhelming for being generous with committer status. > >>> > >>> (Additionally, just as a point of record, it seems that at least some > projects are indeed giving PMC membership without committer status, so that > does seem to be reasonable Apache-fu, when appropriate.) > >> > >> I'm not sure what you mean by "committer status" here. > >> > >> To become a PMC member currently requires an ASF login and this > >> automatically gives committer karma on many projects. > >> To get an ASF login requires an ICLA. > >> > >> AIUI there are no plans to relax these requirements. > >> > >>> --- > >>> A. Soroka > >>> The University of Virginia Library > >>> > >>>> On Oct 13, 2016, at 9:30 PM, Shane Curcuru <a...@shanecurcuru.org> > wrote: > >>>> > >>>> Luciano Resende wrote on 10/13/16 9:20 PM: > >>>>> On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen <rbo...@rcbowen.com> > wrote: > >>>>> > >>>>>> On Oct 13, 2016 12:26, "Daniel Gruno" <humbed...@apache.org> wrote: > >>>>>>> > >>>>>>> Top-posting because yay ponies! > >>>>>>> We've elected people committers in HTTPd solely due to them > helping out > >>>>>>> on IRC. There is no rule that says you must write anything > down in a > >>>>>>> file (code or documentation or otherwise) to become a committer :) > >>>>>>> > >>>>>>> Any contribution can count towards merit. > >>>>>> > >>>>>> Also, more than one person who was made a docs committer on httpd > went on > >>>>>> to make small code contributions. And some not so small. Point > being, when > >>>>>> you extend trust, most people will rise to that level. > >>>>>> > >>>>>> I'm a strong believer in handing out commit early and easy. If > someone > >>>>>> breaks something, revert it. No harm done. > >>>>>> > >>>>>> > >>>>> +1, I just wished some of the existing projects are watching this > thread. > >>>>> > >>>> This is exactly the kind of helpful guidance that folks should feel > free > >>>> to write content for the ComDev website. Much easier to share when > it's > >>>> at a permanent URL. > >>>> > >>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.apache.org%2Fnewbiefaq.html%23websitecms=01%7C01%7CRoss.Gardler%40microsoft.com%7C71298d6b19d14078a42f08d3f487914d%7C72f988bf86f141af91ab2d7cd011db47%7C1=y1bNNtOLtvtkL0NK7b8OGwQ
Re: recognizing valuable non-code contributions
Reminder, ASF has at least one *Member* who doesn't (didn't?) know how to operate source control. But very valuable to the foundation in other ways. Cheers On Fri, Oct 14, 2016 at 11:04 PM, sebbwrote: > On 14 October 2016 at 15:13, A. Soroka wrote: > > I was responding to a previous message from Greg Chase: > > > > https://lists.apache.org/thread.html/34f2f4859aac61141cfe903a692c58 > 06e50282eb6ca388a7f8959d35@%3Cdev.community.apache.org%3E > > > > but perhaps I read too much into his remark "As a frequent non-code > contributor to several projects, having people like us as PMC (or PPMC) > members seems to do the trick." > > I see. > > In order to commit, one must be a committer, but the reverse is not true. > People with committer status don't have to commit code. > They may commit docn or not commit at all. > > > --- > > A. Soroka > > The University of Virginia Library > > > >> On Oct 14, 2016, at 10:08 AM, sebb wrote: > >> > >> On 14 October 2016 at 12:16, A. Soroka wrote: > >>> Thanks, community thinkers! > >>> > >>> The consensus is overwhelming for being generous with committer status. > >>> > >>> (Additionally, just as a point of record, it seems that at least some > projects are indeed giving PMC membership without committer status, so that > does seem to be reasonable Apache-fu, when appropriate.) > >> > >> I'm not sure what you mean by "committer status" here. > >> > >> To become a PMC member currently requires an ASF login and this > >> automatically gives committer karma on many projects. > >> To get an ASF login requires an ICLA. > >> > >> AIUI there are no plans to relax these requirements. > >> > >>> --- > >>> A. Soroka > >>> The University of Virginia Library > >>> > On Oct 13, 2016, at 9:30 PM, Shane Curcuru > wrote: > > Luciano Resende wrote on 10/13/16 9:20 PM: > > On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen > wrote: > > > >> On Oct 13, 2016 12:26, "Daniel Gruno" wrote: > >>> > >>> Top-posting because yay ponies! > >>> We've elected people committers in HTTPd solely due to them > helping out > >>> on IRC. There is no rule that says you must write anything > down in a > >>> file (code or documentation or otherwise) to become a committer :) > >>> > >>> Any contribution can count towards merit. > >> > >> Also, more than one person who was made a docs committer on httpd > went on > >> to make small code contributions. And some not so small. Point > being, when > >> you extend trust, most people will rise to that level. > >> > >> I'm a strong believer in handing out commit early and easy. If > someone > >> breaks something, revert it. No harm done. > >> > >> > > +1, I just wished some of the existing projects are watching this > thread. > > > This is exactly the kind of helpful guidance that folks should feel > free > to write content for the ComDev website. Much easier to share when > it's > at a permanent URL. > > https://community.apache.org/newbiefaq.html#websitecms > > And using the CMS, anyone can make suggested changes just from a web > browser - even non-committers! > > - Shane > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >>> For additional commands, e-mail: dev-h...@community.apache.org > >>> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
Re: recognizing valuable non-code contributions
On 14 October 2016 at 15:13, A. Sorokawrote: > I was responding to a previous message from Greg Chase: > > https://lists.apache.org/thread.html/34f2f4859aac61141cfe903a692c5806e50282eb6ca388a7f8959d35@%3Cdev.community.apache.org%3E > > but perhaps I read too much into his remark "As a frequent non-code > contributor to several projects, having people like us as PMC (or PPMC) > members seems to do the trick." I see. In order to commit, one must be a committer, but the reverse is not true. People with committer status don't have to commit code. They may commit docn or not commit at all. > --- > A. Soroka > The University of Virginia Library > >> On Oct 14, 2016, at 10:08 AM, sebb wrote: >> >> On 14 October 2016 at 12:16, A. Soroka wrote: >>> Thanks, community thinkers! >>> >>> The consensus is overwhelming for being generous with committer status. >>> >>> (Additionally, just as a point of record, it seems that at least some >>> projects are indeed giving PMC membership without committer status, so that >>> does seem to be reasonable Apache-fu, when appropriate.) >> >> I'm not sure what you mean by "committer status" here. >> >> To become a PMC member currently requires an ASF login and this >> automatically gives committer karma on many projects. >> To get an ASF login requires an ICLA. >> >> AIUI there are no plans to relax these requirements. >> >>> --- >>> A. Soroka >>> The University of Virginia Library >>> On Oct 13, 2016, at 9:30 PM, Shane Curcuru wrote: Luciano Resende wrote on 10/13/16 9:20 PM: > On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen wrote: > >> On Oct 13, 2016 12:26, "Daniel Gruno" wrote: >>> >>> Top-posting because yay ponies! >>> We've elected people committers in HTTPd solely due to them helping out >>> on IRC. There is no rule that says you must write anything down in a >>> file (code or documentation or otherwise) to become a committer :) >>> >>> Any contribution can count towards merit. >> >> Also, more than one person who was made a docs committer on httpd went on >> to make small code contributions. And some not so small. Point being, >> when >> you extend trust, most people will rise to that level. >> >> I'm a strong believer in handing out commit early and easy. If someone >> breaks something, revert it. No harm done. >> >> > +1, I just wished some of the existing projects are watching this thread. > This is exactly the kind of helpful guidance that folks should feel free to write content for the ComDev website. Much easier to share when it's at a permanent URL. https://community.apache.org/newbiefaq.html#websitecms And using the CMS, anyone can make suggested changes just from a web browser - even non-committers! - Shane - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
I was responding to a previous message from Greg Chase: https://lists.apache.org/thread.html/34f2f4859aac61141cfe903a692c5806e50282eb6ca388a7f8959d35@%3Cdev.community.apache.org%3E but perhaps I read too much into his remark "As a frequent non-code contributor to several projects, having people like us as PMC (or PPMC) members seems to do the trick." --- A. Soroka The University of Virginia Library > On Oct 14, 2016, at 10:08 AM, sebbwrote: > > On 14 October 2016 at 12:16, A. Soroka wrote: >> Thanks, community thinkers! >> >> The consensus is overwhelming for being generous with committer status. >> >> (Additionally, just as a point of record, it seems that at least some >> projects are indeed giving PMC membership without committer status, so that >> does seem to be reasonable Apache-fu, when appropriate.) > > I'm not sure what you mean by "committer status" here. > > To become a PMC member currently requires an ASF login and this > automatically gives committer karma on many projects. > To get an ASF login requires an ICLA. > > AIUI there are no plans to relax these requirements. > >> --- >> A. Soroka >> The University of Virginia Library >> >>> On Oct 13, 2016, at 9:30 PM, Shane Curcuru wrote: >>> >>> Luciano Resende wrote on 10/13/16 9:20 PM: On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen wrote: > On Oct 13, 2016 12:26, "Daniel Gruno" wrote: >> >> Top-posting because yay ponies! >> We've elected people committers in HTTPd solely due to them helping out >> on IRC. There is no rule that says you must write anything down in a >> file (code or documentation or otherwise) to become a committer :) >> >> Any contribution can count towards merit. > > Also, more than one person who was made a docs committer on httpd went on > to make small code contributions. And some not so small. Point being, when > you extend trust, most people will rise to that level. > > I'm a strong believer in handing out commit early and easy. If someone > breaks something, revert it. No harm done. > > +1, I just wished some of the existing projects are watching this thread. >>> This is exactly the kind of helpful guidance that folks should feel free >>> to write content for the ComDev website. Much easier to share when it's >>> at a permanent URL. >>> >>> https://community.apache.org/newbiefaq.html#websitecms >>> >>> And using the CMS, anyone can make suggested changes just from a web >>> browser - even non-committers! >>> >>> - Shane >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
On 14 October 2016 at 12:16, A. Sorokawrote: > Thanks, community thinkers! > > The consensus is overwhelming for being generous with committer status. > > (Additionally, just as a point of record, it seems that at least some > projects are indeed giving PMC membership without committer status, so that > does seem to be reasonable Apache-fu, when appropriate.) I'm not sure what you mean by "committer status" here. To become a PMC member currently requires an ASF login and this automatically gives committer karma on many projects. To get an ASF login requires an ICLA. AIUI there are no plans to relax these requirements. > --- > A. Soroka > The University of Virginia Library > >> On Oct 13, 2016, at 9:30 PM, Shane Curcuru wrote: >> >> Luciano Resende wrote on 10/13/16 9:20 PM: >>> On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen wrote: >>> On Oct 13, 2016 12:26, "Daniel Gruno" wrote: > > Top-posting because yay ponies! > We've elected people committers in HTTPd solely due to them helping out > on IRC. There is no rule that says you must write anything down in a > file (code or documentation or otherwise) to become a committer :) > > Any contribution can count towards merit. Also, more than one person who was made a docs committer on httpd went on to make small code contributions. And some not so small. Point being, when you extend trust, most people will rise to that level. I'm a strong believer in handing out commit early and easy. If someone breaks something, revert it. No harm done. >>> +1, I just wished some of the existing projects are watching this thread. >>> >> This is exactly the kind of helpful guidance that folks should feel free >> to write content for the ComDev website. Much easier to share when it's >> at a permanent URL. >> >> https://community.apache.org/newbiefaq.html#websitecms >> >> And using the CMS, anyone can make suggested changes just from a web >> browser - even non-committers! >> >> - Shane >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
Thanks, community thinkers! The consensus is overwhelming for being generous with committer status. (Additionally, just as a point of record, it seems that at least some projects are indeed giving PMC membership without committer status, so that does seem to be reasonable Apache-fu, when appropriate.) --- A. Soroka The University of Virginia Library > On Oct 13, 2016, at 9:30 PM, Shane Curcuruwrote: > > Luciano Resende wrote on 10/13/16 9:20 PM: >> On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowen wrote: >> >>> On Oct 13, 2016 12:26, "Daniel Gruno" wrote: Top-posting because yay ponies! We've elected people committers in HTTPd solely due to them helping out on IRC. There is no rule that says you must write anything down in a file (code or documentation or otherwise) to become a committer :) Any contribution can count towards merit. >>> >>> Also, more than one person who was made a docs committer on httpd went on >>> to make small code contributions. And some not so small. Point being, when >>> you extend trust, most people will rise to that level. >>> >>> I'm a strong believer in handing out commit early and easy. If someone >>> breaks something, revert it. No harm done. >>> >>> >> +1, I just wished some of the existing projects are watching this thread. >> > This is exactly the kind of helpful guidance that folks should feel free > to write content for the ComDev website. Much easier to share when it's > at a permanent URL. > > https://community.apache.org/newbiefaq.html#websitecms > > And using the CMS, anyone can make suggested changes just from a web > browser - even non-committers! > > - Shane > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
Luciano Resende wrote on 10/13/16 9:20 PM: > On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowenwrote: > >> On Oct 13, 2016 12:26, "Daniel Gruno" wrote: >>> >>> Top-posting because yay ponies! >>> We've elected people committers in HTTPd solely due to them helping out >>> on IRC. There is no rule that says you must write anything down in a >>> file (code or documentation or otherwise) to become a committer :) >>> >>> Any contribution can count towards merit. >> >> Also, more than one person who was made a docs committer on httpd went on >> to make small code contributions. And some not so small. Point being, when >> you extend trust, most people will rise to that level. >> >> I'm a strong believer in handing out commit early and easy. If someone >> breaks something, revert it. No harm done. >> >> > +1, I just wished some of the existing projects are watching this thread. > This is exactly the kind of helpful guidance that folks should feel free to write content for the ComDev website. Much easier to share when it's at a permanent URL. https://community.apache.org/newbiefaq.html#websitecms And using the CMS, anyone can make suggested changes just from a web browser - even non-committers! - Shane - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
On Thu, Oct 13, 2016 at 6:06 PM, Rich Bowenwrote: > On Oct 13, 2016 12:26, "Daniel Gruno" wrote: > > > > Top-posting because yay ponies! > > We've elected people committers in HTTPd solely due to them helping out > > on IRC. There is no rule that says you must write anything down in a > > file (code or documentation or otherwise) to become a committer :) > > > > Any contribution can count towards merit. > > Also, more than one person who was made a docs committer on httpd went on > to make small code contributions. And some not so small. Point being, when > you extend trust, most people will rise to that level. > > I'm a strong believer in handing out commit early and easy. If someone > breaks something, revert it. No harm done. > > +1, I just wished some of the existing projects are watching this thread. -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: recognizing valuable non-code contributions
On Oct 13, 2016 12:26, "Daniel Gruno"wrote: > > Top-posting because yay ponies! > We've elected people committers in HTTPd solely due to them helping out > on IRC. There is no rule that says you must write anything down in a > file (code or documentation or otherwise) to become a committer :) > > Any contribution can count towards merit. Also, more than one person who was made a docs committer on httpd went on to make small code contributions. And some not so small. Point being, when you extend trust, most people will rise to that level. I'm a strong believer in handing out commit early and easy. If someone breaks something, revert it. No harm done. > > With regards, > Daniel. > On 10/13/2016 06:24 PM, Ian Dunlop wrote: > > Hello, > > > > I second Bertrand. Just elect them as committers. Whether it is code, > > documentation or answering questions, everything is a "commitment" and > > of equal value. That's the way we see it in Apache Taverna. > > > > Cheers, > > > > Ian > > > > On 13/10/16 15:48, Bertrand Delacretaz wrote: > >> Hi, > >> > >> On Thu, Oct 13, 2016 at 3:50 PM, A. Soroka wrote: > >>> ...1) Just elect these folks as committers with the understanding that anyone responsible enough > >>> to be at the heart of the community will presumably not do anything rash with committer privileges, > >>> and anyway, version control is there for a reason... > >> That's how all projects that I've been active in do it. > >> > >> The idea is that those folks become committers not because they are > >> committing code to the project, but because they are committed to it. > >> > >> And it's also fine to have such people on your PMC of course. > >> > >> -Bertrand > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org >
Re: recognizing valuable non-code contributions
As a frequent non-code contributor to several projects, having people like us as PMC (or PPMC) members seems to do the trick. That being said, there can be ways we can contribute in a binary form, such as adding to HTML, blogs, and updating calendars. -Greg On Thu, Oct 13, 2016 at 9:26 AM, Daniel Grunowrote: > Top-posting because yay ponies! > We've elected people committers in HTTPd solely due to them helping out > on IRC. There is no rule that says you must write anything down in a > file (code or documentation or otherwise) to become a committer :) > > Any contribution can count towards merit. > > With regards, > Daniel. > On 10/13/2016 06:24 PM, Ian Dunlop wrote: > > Hello, > > > > I second Bertrand. Just elect them as committers. Whether it is code, > > documentation or answering questions, everything is a "commitment" and > > of equal value. That's the way we see it in Apache Taverna. > > > > Cheers, > > > > Ian > > > > On 13/10/16 15:48, Bertrand Delacretaz wrote: > >> Hi, > >> > >> On Thu, Oct 13, 2016 at 3:50 PM, A. Soroka wrote: > >>> ...1) Just elect these folks as committers with the understanding that > anyone responsible enough > >>> to be at the heart of the community will presumably not do anything > rash with committer privileges, > >>> and anyway, version control is there for a reason... > >> That's how all projects that I've been active in do it. > >> > >> The idea is that those folks become committers not because they are > >> committing code to the project, but because they are committed to it. > >> > >> And it's also fine to have such people on your PMC of course. > >> > >> -Bertrand > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: recognizing valuable non-code contributions
Top-posting because yay ponies! We've elected people committers in HTTPd solely due to them helping out on IRC. There is no rule that says you must write anything down in a file (code or documentation or otherwise) to become a committer :) Any contribution can count towards merit. With regards, Daniel. On 10/13/2016 06:24 PM, Ian Dunlop wrote: > Hello, > > I second Bertrand. Just elect them as committers. Whether it is code, > documentation or answering questions, everything is a "commitment" and > of equal value. That's the way we see it in Apache Taverna. > > Cheers, > > Ian > > On 13/10/16 15:48, Bertrand Delacretaz wrote: >> Hi, >> >> On Thu, Oct 13, 2016 at 3:50 PM, A. Sorokawrote: >>> ...1) Just elect these folks as committers with the understanding that >>> anyone responsible enough >>> to be at the heart of the community will presumably not do anything rash >>> with committer privileges, >>> and anyway, version control is there for a reason... >> That's how all projects that I've been active in do it. >> >> The idea is that those folks become committers not because they are >> committing code to the project, but because they are committed to it. >> >> And it's also fine to have such people on your PMC of course. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
Hello, I second Bertrand. Just elect them as committers. Whether it is code, documentation or answering questions, everything is a "commitment" and of equal value. That's the way we see it in Apache Taverna. Cheers, Ian On 13/10/16 15:48, Bertrand Delacretaz wrote: > Hi, > > On Thu, Oct 13, 2016 at 3:50 PM, A. Sorokawrote: >> ...1) Just elect these folks as committers with the understanding that >> anyone responsible enough >> to be at the heart of the community will presumably not do anything rash >> with committer privileges, >> and anyway, version control is there for a reason... > That's how all projects that I've been active in do it. > > The idea is that those folks become committers not because they are > committing code to the project, but because they are committed to it. > > And it's also fine to have such people on your PMC of course. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > 0xDAEA877B.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: recognizing valuable non-code contributions
Hi, On Thu, Oct 13, 2016 at 3:50 PM, A. Sorokawrote: > ...1) Just elect these folks as committers with the understanding that anyone > responsible enough > to be at the heart of the community will presumably not do anything rash with > committer privileges, > and anyway, version control is there for a reason... That's how all projects that I've been active in do it. The idea is that those folks become committers not because they are committing code to the project, but because they are committed to it. And it's also fine to have such people on your PMC of course. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: recognizing valuable non-code contributions
My preferred approach is option 1. If you document the role of "committee" as "someone who is committed to the project" then this works well. --- Twitter: @rgardler From: A. Soroka <aj...@virginia.edu> Sent: Thursday, October 13, 2016 6:50:50 AM To: dev@community.apache.org Subject: recognizing valuable non-code contributions Hello, community-builders! I (ajs6f) am writing from Apache Jena. We've been tossing around a question that would certainly benefit from the wisdom and experience on this list. We have inside the community around Jena persons who have done really good work for the project in such ways as answering questions, providing helpful examples, suggesting useful improvements and documentation, and so forth, but who have not made code contributions. We'd very much like to recognize and reward these people for their excellent efforts, but the particular role of "committer" doesn't seem obviously appropriate to all of us. We were wondering how other projects have dealt with similar circumstances. We've come up with a couple of possibilities: 1) Just elect these folks as committers with the understanding that anyone responsible enough to be at the heart of the community will presumably not do anything rash with committer privileges, and anyway, version control is there for a reason. 2) Create some kind of new non-committer role within the project (e.g. "Community Expert") for these folks that might provide some privileges (e.g. special rights/permissions in Jira or to the documentation base) without full committer rights to the code base. 3) Elect these people to membership in the PMC _without_ electing them committers. We're not totally sure whether this is actually possible within the Apache framework, so one question of fact we have is whether this is in fact a possibility. Any thoughts, advice, experience very welcome! --- A. Soroka ; Apache Jena - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
recognizing valuable non-code contributions
Hello, community-builders! I (ajs6f) am writing from Apache Jena. We've been tossing around a question that would certainly benefit from the wisdom and experience on this list. We have inside the community around Jena persons who have done really good work for the project in such ways as answering questions, providing helpful examples, suggesting useful improvements and documentation, and so forth, but who have not made code contributions. We'd very much like to recognize and reward these people for their excellent efforts, but the particular role of "committer" doesn't seem obviously appropriate to all of us. We were wondering how other projects have dealt with similar circumstances. We've come up with a couple of possibilities: 1) Just elect these folks as committers with the understanding that anyone responsible enough to be at the heart of the community will presumably not do anything rash with committer privileges, and anyway, version control is there for a reason. 2) Create some kind of new non-committer role within the project (e.g. "Community Expert") for these folks that might provide some privileges (e.g. special rights/permissions in Jira or to the documentation base) without full committer rights to the code base. 3) Elect these people to membership in the PMC _without_ electing them committers. We're not totally sure whether this is actually possible within the Apache framework, so one question of fact we have is whether this is in fact a possibility. Any thoughts, advice, experience very welcome! --- A. Soroka ; Apache Jena - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org