OASIS Member Discuss

 View Only

  • 1.  distributed VCS (DVCS) platform rollout at W3C

    Posted 04-29-2010 14:48 
    On April 08 2010, Farrukh Najmi introduced the topic of
distributed VCS at OASIS, mentioning specifically Mercurial
and git/github:

   "svn was great several years back but today it is quite limiting a
   choice now that distributed VCS such as Mercurial (aka hg) and git
   (used by the Linux project) are mature and stable. The benefits of mercurial
   or git are huge over svn..."  See:

http://lists.oasis-open.org/archives/oasis-member-discuss/201004/msg00004.html

Just FYI: today Alexandre Bertails of W3C announced the availability of a new
Distributed Version Control System, based on Mercurial.

See the blog article on "Decentralized versioning system at W3C" and references:

http://www.w3.org/blog/systeam/2009/12/09/decentralized_versioning_system_at_w3c

All resources in W3C Mercurial will be World readable.  See e.g.,

http://dvcs.w3.org/hg

- rcc

Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783


  • 2.  RE: [oasis-member-discuss] distributed VCS (DVCS) platform rollout at W3C

    Posted 04-29-2010 17:26 
    Robin, I see the blog discussion from last year, but I don't see anything
about the announcement of availability.  Where is that announcement?

The discussion on the blog is the usual developer-centric view of the
universe and the World readability of what I see at dvcs.w3.org/hg doesn't
strike me as much of an accomplishment.

Where is the announcement of its availability.  Where are whatever
procedures put in place to have it fit into W3C policies there are for
maintenance of materials, their custody and their provenance?

 - Dennis

PS: I am a little puzzled about "patch" in this statement on the blog:
" The goal of such a repository would be to host the reference versions of
these items, while allowing as many people as possible to modify, branch,
patch the content of the repository, without the hurdles that CVS creates
for this kind of cooperation."

I assume they do not mean open patching of the reference version (there
would need to be something more disciplined for that, I would think).  I
maintain that I (and any unindicted collaborators) can do all of those
things without requiring OASIS to provide anything on my/our behalf other
than a way to get and synchronize from a "reference version" on the current
SVN, something that is remarkably easy to do.

Of course my experience with the OASIS SVN is on a small TC where only two
of us have ever done commits and we can easily avoid trampling on the work
of each other.  So we are probably not representative of those who crave
something new and maybe shinier.  We also haven't dealt with the
preservation of the "reference version" of the work and are not certain how
that can be done in the current arrangement.  It looks like reference
versions would need to be segregated in some way to prevent their alteration
and the rewriting of history, just as that is done for documents beyond TC
internal working drafts.



    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


Related Content