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 aaaaanything 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 <aj...@virginia.edu> 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
