Developers of Sympa

[Flack Maguire <address@concealed>]

Hi David/All,

 

We are going to be going through our initial learning on Git as well.  But, we will jump into working on getting the code in Git and working on GitHub.  Give us a little bit as we are deep in final rounds of demonstrations of the light integration of 4 open source platforms with one being Sympa.

 

I did see in one of the replies that it looked like my initial comments might have been misunderstood.  I was mainly focused on the migration to a DVCS and less so about moving to another platform for bug tracking, wiki, feature requests, etc.  Others may think differently, I personally go with good enough is simply good enough.  The existing tools around Sympa seem to be doing the job just fine.

 

I noticed your earlier posting about 6 SVN branches for the Sympa code.  We are just transitioning to Git ourselves, but one of those reasons is the ease of which distributed teams can independently add/test before the commit back to the core.  We will start by just setting up 1 interation on GitHub just as a test because I think, as you get exposed to DVCS, you thinking on how you have different branches of the code might change.

 

And, we have zero desire to hijack anything here.  If you like what you see after playing around with the GitHub load we do, just let us know and we can hand over sole admin authority over to the core Sympa team.

 

I will post back here when we have links to GitHub.  We will try to not screw up the first test load to GitHub too badly:)))

 

Cheers,

Flack

 

 

 

>>Hi Flack,
>>
>> Flack Maguire a crit :
>>Hi David,
>>  
>>I was just curious if there had been any talk on the core team of moving over to one of the
>> distributed version control systems (DVCS) like Git, Bazaar, or Mercurial.
>> Not yet. Actually, we are pretty happy with subversion so far. We know these new systems are
>> emerging now but didn't have the time to investigate what would be the benefits of migrating to
>> them.
>> Some readings ahead, I guess. Do you use them yourself or do you have any pointers that could
>> help us understanding these tools?
>>
>>  
>>  
>>Married up to these are code hosting services such as Launchpad and GitHub.  But, I think your
>> team has more than covered the issues such as a wiki, bug tracking, etc. so I wouldimagine they
>> would not be a substantial value add.
>> Actually, the CRU (the french organization which Serge, Olivier and I are working for) is
>> operating a development forge, sourcesup (http://sourcesup.cru.fr/) dedicated to public
>> developments done by French universities. It provides a set of tools for each project : tracker,
>> subversion repository, mailing lists, wiki and so on. We use them for Sympa.
>>
>>  
>>  
>>Still, the DVCS tools themselves are growing in popularity for the flexibility they provide to
>> global efforts and can be used completely outside of the hosting services. Indeed! And if a tool
>> is really useful, we will always find a way to adpat it to our framework. -)
>>
>>  
>>Do let me openly acknowledge that it is extremely easy for any of us to come up with ideas like
>> this when it is not us implementing the idea.  And, I will be the first to say that my particular
>> group has gained far more from Sympa than we have given at this date which is something we hope &
>> plan to change as we go farther with Sympa. Ideas are important. You never implement anything if
>> you don't have any idea... So feel free to keep on leaving suggestions through the Sympa mailing
>> lists. We are always interested by new ideas, even if we -sadly - don't always have the time to
>> implement them.
>> But it /you/ have the time to do so, you are even more welcome! )
>>
>> Best regards,
>>
>> David
>>
>>  
>>Cheers,
>>Flack
>>  
>>  
>>  
>>>>Hi Paul!
>> >>
>> >>Well that two files properties... That's a problem I want to fix very soon, but as it is not
>> that
>> >>big of a problem, I always had something more urgent to do until now.
>> >>Actually, the properties changes for these two files regards the svn:mergeinfo properties only.
>> >>
>> >>A little background can help you understand the situation: There are 6 active SVN branches (in
>> >>addition to the main development trunk) for now in the Sympa project. Two stabilization
>> branches
>> >>and four side projects. When we fix a bug, it is wise to transfer the bug fix to all the
>> branches
>> >>to avoid a too great divergence from the trunk. It helps the fusion once the work on a branch
>> is
>> >>over and needs to be transferred to the trunk. Until recently, we used manual patches. But the
>> >>merge option in SVN (> 1.5) is so easy to use that we changed our habits, and so far it works
>> >>great.
>> >>
>> >>Safe for those two...
>> >>
>> >>Since the first time we changed the way we handle the different development branches of the
>> Sympa
>> >>subversion repository, there has always been a discrepancy between a branch and another,
>> whatever
>> >>branch we work on, for these files only,on the svn:merge property only. This has no impact at
>> all
>> >>on the Sympa code or on the efficiency of the merges, but they keep appearing in the commit
>> >>summaries because of it, and it's becoming annoying.
>> >>
>> >>I'll fix that right as soon as possible, but that probably implies manually setting the
>> svn:merge
>> >>property for these files on all the Sympa branches.
>> >>
>> >>Life is pain... -)
>> >>
>> >>Regards,
>> >>
>> >>David
>> >>
>> >>Paul Menzel a crit : Dear David, Am Donnerstag, den 03.09.2009, 12:26 +0200 schrieb David
>> >>Verdin: [€] You're both right! We applied your patch to both 6.0 branch and the  development
>> >>trunk. Thanks for submitting it! Big thanks fromme too. David commited your patch in revision
>> >>6168. David, the commit changed also the properties of two files. Was that intentional? Bests,
>> >>Paul [1] http://sourcesup.cru.fr/cgi/viewvc.cgi?view=rev&revision=6168
>> >>--  David Verdin Comit rseau des universits
>>
>>
>> --  David Verdin Comit rseau des universits