[Owncloud] Fwd: Re: ownCloud and KDE

[Jan-Christoph Borchardt]

Since contributions are better measured in quality rather than quantity,
we’ll just decide the old fashioned way on a case by case basis.

If a person is active & committed to the project + delivers good code –
they are likely to get direct commit access.


On Fri, August 19, 2011 00:16, Matthew Dawson wrote:
> Oops ... Accidentally replied to author, not list.
>
> Matthew
>
> Matthew Dawson <matthew at mjdsystems.ca> wrote:
>
>>Jan-Christoph Borchardt <JanCBorchardt at fsfe.org> wrote:
>>
>>>For that reason I just created 2 teams on Gitorious:
>>>https://gitorious.org/+owncloud for the core team. Should be set as
>>>owner
>>>of the owncloud project to enable flexibility when needing to edit
>>>things.
>>>Should also be owners and committers of the main owncloud repository.
>>>Also
>>>committers to every repository created in the project (maybe that’s
>>>already automatic because they are owners.)
>>>https://gitorious.org/+owncloud-contributors people who are granted
>>>commit
>>>access to the repository without needing to file merge requests. If
>>>that’s
>>>possible, people in this group should also be able to create new
>>>repositories in the project (for new apps etc.)
>>>
>>>The core team is Frank, Robin, Jakob and me, since we are the
>>>most+longest
>>>active / contributing. Is that ok? I think it makes sense to appoint
>>>that
>>>team for administration instead of only Frank because it will not
>>>create a
>>>bottleneck when quick changes are needed.
>>>
>>>What do you think?
>>>
>>>
>>>On Wed, August 17, 2011 17:06, Frank Karlitschek wrote:
>>>> Hi Matthew,
>>>>
>>>>
>>>> thats a valid question which still has to be discussed.
>>>> But even if a new contributor doesn´t have direct write access at
>>day
>>>one,
>>>> creating a clone and a merge request is very easy.
>>>>
>>>>
>>>> Cheers
>>>> Frank
>>>>
>>>>
>>>> On 17.08.2011, at 16:20, Matthew Dawson wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> My only questions is, how are you going to administer write access
>>>to
>>>>> the repository? Are you only going to allow a few trusted people,
>>>then
>>>>> work through merge requests? As I understood it, the kde-developers
>>>>> group is no longer supported, or is at least deprecated.
>>>>>
>>>>> To be clear, I'm not objecting, I just want to make sure the move
>>>has a
>>>>> well defined plan behind it.
>>>>>
>>>>> Matthew
>>>>>
>>
>>
>>That sounds great!  What are the policies for deciding who is allowed
>>into owncloud-contributers?  A few ground rules would probably be good,
>>like:
>> - After x successful merge requests in y time.
>>- Anyone with a 50% working prototype project to be developed under the
>>owncloud umbrella.
>>etc.
>>
>>Otherwise, I think its good to seperate owners vs contributers.  And
>>having multiple owners, allowing for division of responsibility and a
>>higher bus number.
>>
>>Matthew
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>