code for FLUID-2925

[Colin Clark]

Laurel,

On 12-Jun-09, at 11:58 AM, Laurel A. Williams wrote:
> Basically my question boils down to: Can the new code be committed  
> to an SVN somewhere as is or with the corrections noted by you and  
> Jacob? How does this work for non-committing project members?

Generally speaking, contributors who don't have commit access are  
paired up with a committer. In your case you're paired up with both  
Jacob and Justin, so you've got lots of help available.

I think we're ready to get this code into the repository. Your work is  
shaping up nicely. Jacob, if you agree, can you commit Laurel's code  
today?

> I read your email about the proposed "new code committing policy",  
> including a main repository, and two other levels of commits. I like  
> the idea, since it would be very useful to have svn access even  
> though the code isn't "functional" or final. I'd like somewhere to  
> keep these first few rounds of code edits, other than attached to a  
> JIRA. Tools such as svn diff and revert would be very helpful, as  
> well as having access to the code from multiple locations (instead  
> of emailing it to myself at the end of the day). I could set up a  
> personal SVN somewhere, and there are other solutions out there, but  
> perhaps it would be just as well to store these publicly if the  
> community agrees.

Governance changes require a formal vote by the whole community, so  
I'll be proposing the new approach to our repository formally soon. In  
general, you should always have access to the benefits that SVN  
provide--that's where your committer mentors come in.

Colin

---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org