Apologies for dropping off the radar for the past few weeks, but things at work got busier rather than slacking off after the semester started (I got assigned several new high-priority projects - such is life when working in an understaffed IT shop) and I vastly underestimated how busy things would be in the evenings and weekends shuttling my kids back and forth to various activities. Anyway, things still are very busy with non-Fedora related stuff, but I thought that I owed it to the community to post this and get the discussion started again. It was my impression that there was very little consensus on what (if anything) should be done. There seemed to be three camps: 1) Stick with CVS as is. 2) Switch to another VCS, but the data in the repository would remain similar to what we currently use (RPM spec plus patches). 3) Switch to another VCS, but the data in the repository would radically change to an "expanded source" style repository. All three camps have vocal proponents as well as vocal opponents. My suspicion is that the "silent majority" is in the "stick with CVS" camp. My personal choice would be to switch to Git for the VCS but keep the repository data the same (spec file plus patches). I feel that switching to expanded source-style repositories is too radical of a change - we give up the notion of pristine source plus patches. Also, using an expanded source-style repository would mean that packagers would have to become much more familiar with the VCS since they would need to maintain various branches (vendor branch, branches for various patches). In any case, it's unlikely that I'll have significant amounts of time to work on a VCS conversion anyway so until someone else steps up to take charge of this project we'll have to live with what we have. Jeff P.S. I'll be in Chicago next week for a training class so if anyone in the Chicagoland area would like to get together some evening for drinks ping me on IRC or off-list. There's probably a couple of you out there that I should probably buy a beer so this could be your chance to collect!
Attachment:
signature.asc
Description: This is a digitally signed message part
