Re: SVG Book

Hi Doug,

I'm not sure if I need a CVS account, I might already have one.

Can you give us a walkthrough on how to check out the files and get started?

Thanks,
Jeff

On Wed, Oct 14, 2009 at 5:28 PM, Doug Schepers <schepers@w3.org> wrote:
> Hi, Folks-
>
> At the risk of being a bit of a killjoy... the only version control system
> supported by W3C's systems team (right now) is CVS, and while it's not
> ideal, I think it's more than ample for the simple needs of getting this
> book done.  Let's not bury the real task we're trying to accomplish
> --getting the book ready for publication-- under the means of doing so.
>
> If you need a CVS account, let me know.
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG and WebApps WGs
>
>
> Manuel Strehl wrote (on 10/14/09 6:05 PM):
>>
>> Hi,
>>
>> I'd go with GIT on github, but would also be happy with SVN or any other
>> VCS. A further use case for branching, by the way, would be translations.
>>
>> Another possibility (just to be mentioned) would be to transfer the book
>> to Wikibooks (http://en.wikibooks.org) and edit it there. Disadvantage:
>> Losing control. Advantage: Broader interest from potential co-authors.
>>
>> Cheers,
>> Manuel
>>
>>
>> Jeff Schiller schrieb:
>>>
>>>  On Mon, Oct 12, 2009 at 10:39 PM, Jon A. Cruz<jon@joncruz.org>  wrote:
>>>
>>>>  However... the main benefit can come from branches for development
>>>> tweaking.
>>>>  As each person/group/company/whatever works on refining a test or sets
>>>> of
>>>>  tests, they can be checking into a branch as they go along. This allows
>>>> for
>>>>  better collaboration, and avoids the problem of someone "breaking" the
>>>>  trunk. This also allows for easier experimentation and a "safer" way
>>>> for
>>>>  newer contributors to get involved with less risk. A DCVS such as git
>>>> or bzr
>>>>  can really help in such cases.
>>>>
>>>>
>>>
>>>  I agree that publishing in-progress branches is a BIG benefit of a
>>>  DVCS and I'm really in favor of this.
>>>
>>>  However, I was reminded this morning of another big benefit of
>>>  Subversion:  the ability to set MIME types.  This may not sound like
>>>  much, but for web apps (and for web documents) this can be a big
>>>  advantage as you can browse directly to the trunk and see the
>>>  progress.  This is what we do in SVG-edit:
>>>
>>>  http://svg-edit.googlecode.com/svn/trunk/editor/svg-editor.html
>>>
>>>  We also use branching in SVN:
>>>
>>>  http://svg-edit.googlecode.com/svn/branches/2.1/editor/svg-editor.html
>>>  http://svg-edit.googlecode.com/svn/branches/2.2/editor/svg-editor.html
>>>  http://svg-edit.googlecode.com/svn/branches/2.3/editor/svg-editor.html
>>>
>>>  We also use one tag to indicate the latest stable release (currently
>>> 2.3):
>>>
>>>  http://svg-edit.googlecode.com/svn/tags/stable/editor/svg-editor.html
>>>
>>>  When 2.4 is released, I will delete the 'stable' tag and re-create it
>>>  pointing to the 2.4 branch.
>>>
>>>  The fact that this is all accessible by a web browser without
>>>  requiring the user to check out any code is, I think, a big advantage.
>>>
>>>  Do any of the DVCS allow this?  I'm thinking of Mercurial since
>>>  GoogleCode supports that as well as SVN, but I'm not familiar enough
>>>  with it.  I admit that this may not be as big of a factor with the SVG
>>>  book or the Torture Tests since they will presumably be published
>>>  elsewhere when finished.
>>>
>>>  Though it may sound like it, I'm really not trying to push Subversion
>>>  and I'm willing to go with whatever system we all agree on.  Just
>>>  trying to gather facts.
>>>
>>>  Jon, do you want to take the lead on investigating the best option for
>>>  either of these projects in terms of where to host them and the DVCS
>>>  to go with?
>>>
>>>  Regards,
>>>  Jeff
>>>
>>>
>>
>
>

Received on Wednesday, 14 October 2009 22:30:43 UTC