Proposal for change to repository governance - follow-on

[Michelle D'Souza]

Are we also voting on this? It sounds like a good idea to me.

Michelle

On 12-Jun-09, at 4:44 PM, Antranig Basman wrote:

> I also think this is a great proposal.
>
> As a follow-on proposal, I would like to talk about strategies for  
> working across our
> various projects. Those working on engage need also to work on  
> infusion - and also
> working with a trunk version, in case they need to make commits to  
> base functions.
>
> To be clearer - it would be great for the team that works across  
> multiple projects to
> be able to do this with a SINGLE checkout of each project. Our  
> traditional solution
> based on externals is asymmetric - and ends up with multiple images  
> of infusion.
>
> My proposal is to make an "externals-only" section which is intended  
> to be the root
> checkout for developers who work across multiple trunks. This  
> ensures that multiple
> projects can be checked out with consistent directory names and in a  
> consistent
> relative structure.
>
> I suggest making an area such as "fluid-checkout" or "fluid- 
> externals", which,
> for example, has an externals structure like this:
>
> fluid-checkout\
>   fluid-infusion -> https://source.fluidproject.org/svn/fluid/infusion/trunk
>   fluid-engage -> https://source.fluidproject.org/svn/fluid/engage/trunk
>
> and any other projects that we might work with.
>
>
>
> Jess Mitchell wrote:
>>
>> This looks really good to me.
>>
>> J
>> ~~~~~~~~~~~~~~~~~~~~~~
>> Jess Mitchell
>> Boston, MA, USA
>> Project Manager / Fluid Project
>> jess at jessmitchell.com
>> / w / 617.326.7753  / c / 919.599.5378
>> jabber: jessmitchell at gmail.com
>> http://www.fluidproject.org
>> ~~~~~~~~~~~~~~~~~~~~~~
>>
>> On Jun 5, 2009, at 3:38 PM, Colin Clark wrote:
>>
>>> Hi everyone,
>>>
>>> It's exciting to see the Fluid community growing, with a number of  
>>> new prospective
>>> committers getting involved. After talking with a number of  
>>> community members about
>>> how we organize and govern our source code repository, I'd like to  
>>> propose a change to
>>> our approach.
>>>
>>> New members of the community are starting to explore deliverables  
>>> that will be on the
>>> critical path for our Engage project as well as the Infusion  
>>> product. At the moment,
>>> prospective committers are not given any commit access to the  
>>> repository until they've
>>> gone through a process of submitting patches and earning the  
>>> respect of the community.
>>> Overall, this process works well to ensure the quality of our code.
>>>
>>> On the other hand, we want to foster increased collaboration and  
>>> make newcomers feel
>>> welcome, giving them space to play even before they've earned  
>>> committer status. To
>>> this end, I'd like to propose splitting our source code repository  
>>> into three separate
>>> areas:
>>>
>>> 1. A space for our current, shipping products. This area will be  
>>> fully governed by all
>>> the familiar coding and commit standards used so far to ensure  
>>> quality in Fluid
>>> releases. Prospective committers will be nominated and voted on  
>>> for access to this
>>> space as usual.
>>>
>>> http://wiki.fluidproject.org/display/fluid/Process+for+Granting+Commit+Access
>>> http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards
>>>
>>> 2. A space for incubated projects. This is a place for growing  
>>> code that we expect to
>>> some day include in our releases. Anyone can ask for commit access  
>>> to this space, and
>>> will be paired with a current committer as a mentor. Code reviews  
>>> will be a requisite
>>> part of the  incubation process, and we'll expect a growing  
>>> standard of quality over
>>> time.
>>>
>>> 3. A scratch pad space. This area will provide anyone with a space  
>>> to experiment and
>>> sketch in code. It is assumed that work here will either be  
>>> entirely experimental or
>>> will be promoted to another space as soon as it has taken  
>>> reasonable shape. No release
>>> deliverables should be worked on here.
>>>
>>> Comments, suggestions, and refinements are much appreciated. After  
>>> we've all had a
>>> chance to think about it and talk it through, I hope we can put it  
>>> to a formal vote
>>> sometime next week.
>>>
>>> Colin
>>>
>>> ---
>>> Colin Clark
>>> Technical Lead, Fluid Project
>>> Adaptive Technology Resource Centre, University of Toronto
>>> http://fluidproject.org
>>>
>>> _______________________________________________________
>>> fluid-work mailing list - fluid-work at fluidproject.org
>>> To unsubscribe, change settings or access archives,
>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>
>>     
>> --------------------------------------------------------------------------------
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work

------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto