On the June Status report thread, Ross raises this concern: "The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad."
Good point. As Dave Fisher and others have remarked, the desire is for a work flow that facilitate/expedites attributable contributions from non-committers that matters. It appears that the list is coming up with useful ideas for the case of Pootle and translators. - Dennis PS: I am not so certain that "Hierarchy in an open development project is bad" is a universal truth. I do appreciate that The Apache Way toward sustainable projects demands a non-hierarchical approach. That is not without its own challenges [;<). -----Original Message----- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Thursday, June 07, 2012 23:58 To: ooo-dev@incubator.apache.org Subject: Re: *DRAFT FINAL* June board report I'm a little concerned about this idea of AOO being somehow different from other Apache projects. Its not, its just software. In Apache projects everyone is equal. If someone earns merit they earn merit, it makes no difference how that merit is earned. The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad. Note we have a VP who has never written a line of code in their life. As far as I'm aware they have never written a translation string or any documentation. Despite this there was no need to create a new class of community member to bring them into the ASF. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. Ross Sent from my mobile device, please forgive errors and brevity. On Jun 7, 2012 11:30 PM, "Kay Schenk" <kay.sch...@gmail.com> wrote:
