I'm glad that DVCS is back on the table - I was going to write something about it to the list to encourage a move away from svn (most of the other projects I follow have either already moved, and a few are about to move out of sourceforge because of svn limitations).
With that said, I'm not thrilled about git, with its umpteen hundred commands and a whole other philosophy/approach to how to think about version control. [yes, this is probably because i don't understand it - but i prefer not to HAVE to grok something from the moment i start using it]. So if everyone else is already comfortable with git, then it makes sense, but I found that mercurial has an almost 1-1 command mapping with svn - it's the most svn-like DVCS, As far as bazaar, I'm not fond of Launchpad's weird folding-in of merges (you have click through 3 pages in order to see what the second parent branch). then again, maybe this is a moot point - I can totally learn git. The few patches I've already contributed I developed using a parallel mercurial repo (adding files as I started to change them). It just didn't seem worth it at the time to use git for my personal projects when i was switching away from svn two years ago. I'm just glad we're moving away from a single point of failure - so at least for the source code - at any point, any one of the developers could temporarily host a full source mirror. And most of these have quite decent two-way bridges, we can always switch the VCS later. As far as the issue tracking - let's also look at how easy / if it's possible to get issues OUT of whatever system we go with - to gauge what that commitment will be. Incidentally, this is one place where I really want to spend time this summer improving in Sycamore: I think we would get a lot more users (and with them, developers) if we had both a way to import e.g. MediaWiki into Sycamore, as well as export out to MediaWiki, etc. This way, people can feel comfortable with trying out Syc without having to fully commit to using it. As far as I understand it, there isn't currently even a way to export from Sycamore using one back end and into a Sycamore using another one, so that would at least be a first step. Paul Philip Neustrom, on 2009-05-27 01:11, wrote: > Anyone have objections to git / github? It's the new hotness. > > On Tue, May 26, 2009 at 8:40 PM, Alex Mandel <tech_...@wildintellect.com> > wrote: > > I think we'd need to file a ticket in order for our trac database to be > > imported. They do not provide direct disk access to hosted app > > databases, only direct access to version control. > > They do however offer backup tools for trac to dump the site out when we > > want. > > > > Alex > > > > Alex Mandel wrote: > >>>From what I can tell it's a case of uploading the dumpfile and then running > >> svnadmin load /svnroot/andsoft < dumpfile > >> > >> Not sure about importing trac information though, still looking. > >> > >> I did find that we can shorten the urls to the SVN browse and the trac > >> site with our own domain via the sourceforge settings. > >> > >> Alex > >> > >> Philip Neustrom wrote: > >>> That sourceforge setup looks good, actually. Do you know if importing > >>> an existing project's SVN data is a pain? > >>> > >>> Hosting the SVN install on the current wikispot.org machine isn't the > >>> best because we want to be able to always have the code available > >>> independently of the site being up. Also, I think that giving SVN > >>> auth access may be a security risk, but I'd guess it depends on the > >>> authentication mechanism. > >>> > >>> -p > >>> > >>> On Tue, May 26, 2009 at 7:14 PM, Alex Mandel <tech_...@wildintellect.com> > >>> wrote: > >>>> What are the hesitations about hosting it ourselves? > >>>> > >>>> I've used the sourceforge system and basically only for SVN/Trac, didn't > >>>> bother to turn on anything else. In the long run this would make the > >>>> project more discoverable. Looking around at other options, few if any > >>>> services offer SVN/Trac. > >>>> Here's what a SF trac site looks like > >>>> http://apps.sourceforge.net/trac/qgismetaedit/ > >>>> > >>>> Berlios, Tigris(Where SVN is) and Google Code all offer SVN but with > >>>> their own Bug Tracking systems. We could also move to Git, Mercurial or > >>>> Bazaar and use Github, Launchpad, or Berlios for any of those too. > >>>> > >>>> I would hesitate to use any but the largest hosts, since smaller ones > >>>> may take the same route as our current provider. I also think regardless > >>>> of who we pick we should consider url redirecting via a wikispot > >>>> subdomain. > >>>> > >>>> Alex > >>>> > >>>> > >>>> > >>>> Philip Neustrom wrote: > >>>>> I downloaded a copy of the svn and trac environment. Threw both up on > >>>>> the wikispot.org server. > >>>>> > >>>>> Not sure where would be best to host this stuff now. I tend to think > >>>>> sourceforge is too spammy / indirect. > >>>>> > >>>>> -p > >>>>> > >>>>> On Mon, May 25, 2009 at 7:10 PM, Alex Mandel > >>>>> <tech_...@wildintellect.com> wrote: > >>>>>> Have you done the dump? > >>>>>> I'm about to export to bzr or git just in case but that won't copy the > >>>>>> trac site at all. Not that there's anything on that of any importance. > >>>>>> But it would be better to get svn via svnadmin dump, especially if we > >>>>>> plan to continue using svn. > >>>>>> > >>>>>> > >>>>>> Like I said before, I know how to setup Trac/SVN, it's not all that > >>>>>> hard > >>>>>> and I offer to assist. > >>>>>> > >>>>>> Alex > >>>>>> > >>>>>> > >>>>>> Philip Neustrom wrote: > >>>>>>> We'll have to set up Trac / SVN soon > >>>>>>> > >>>>>>> ---------- Forwarded message ---------- > >>>>>>> From: "DevjaVu Team" <j...@devjavu.com> > >>>>>>> Date: May 2, 2009 6:09 PM > >>>>>>> Subject: Important Notice: DevjaVu is going to be shutting down > >>>>>>> To: "phil...@gmail.com" <phil...@gmail.com> > >>>>>>> > >>>>>>> Hello everyone, > >>>>>>> > >>>>>>> You're getting this message because you have a project at > >>>>>>> DevjaVu and we have a very important notice about the service. > >>>>>>> > >>>>>>> Over the next few months, DevjaVu will be winding down and > >>>>>>> eventually shutting down. We'll try to hold on as long as > >>>>>>> possible, but we don't have the money to run more than a few > >>>>>>> months unless we work something out with Engine Yard (perhaps > >>>>>>> go down to one slice). We highly recommend you start migrating > >>>>>>> off as soon as possible. A more concrete end of service date > >>>>>>> will be announced soon on our blog: http://blog.devjavu.com > >>>>>>> > >>>>>>> You have full access to your SVN repo and Trac instance in the > >>>>>>> Admin under Export. If your repository is too big to export, we > >>>>>>> can do the export for you and give you a link to download. Just > >>>>>>> contact supp...@devjavu.com if that's the case. If worse comes > >>>>>>> to worse and we do have to shut down before everybody is off, > >>>>>>> we'll give plenty of warning and then provide downloadable > >>>>>>> exports of everybody's projects linked in an email to the > >>>>>>> project owner once the service is off. > >>>>>>> > >>>>>>> This is the first time I've had to do anything like this, so > >>>>>>> if you have any feedback on handling this in a better way, let > >>>>>>> me know. I'd love to give a detailed explanation of what's > >>>>>>> going on, but I think I'm going to hold off until the final day. > >>>>>>> In short: the business never got the momentum I wanted to > >>>>>>> sustain my personal interest, so while running at break-even > >>>>>>> worked so-so for so long, it finally started dying and has been > >>>>>>> losing money for a while. I started an effort to save it, but > >>>>>>> I decided I did not want to continue supporting this type of > >>>>>>> service, especially by myself. > >>>>>>> > >>>>>>> So, sorry everybody! I would have liked this to be less of a > >>>>>>> surprise than I'm sure it is for some of you. Yes, it certainly > >>>>>>> could have been avoided if I better communicated with you guys > >>>>>>> up to this point. But I want to thank you for using DevjaVu > >>>>>>> while you did. > >>>>>>> > >>>>>>> If you have questions or concerns, email me at j...@devjavu.com > >>>>>>> > >>>>>>> Jeff Lindsay > >>>>>>> DevjaVu > >>>>>>> > >>>>>>> This email was sent to phil...@gmail.com. > >>>>>>> You can instantly unsubscribe from these emails by clicking the link > >>>>>>> below: > >>>>>>> http://devjavu.cmail4.com/t/y/u/htdttt/dtdkjruhu/ > >> > >> > >> _______________________________________________ > >> Sycamore-Dev mailing list > >> sycamore-...@wikispot.org > >> http://www.projectsycamore.org/ > >> https://tools.cernio.com/pipermail/sycamore-dev/ > >> https://tools.cernio.com/mailman/listinfo/sycamore-dev > > > > _______________________________________________ > > Sycamore-Dev mailing list > > sycamore-...@wikispot.org > > http://www.projectsycamore.org/ > > https://tools.cernio.com/pipermail/sycamore-dev/ > > https://tools.cernio.com/mailman/listinfo/sycamore-dev > > > > _______________________________________________ > Sycamore-Dev mailing list > sycamore-...@wikispot.org > http://www.projectsycamore.org/ > https://tools.cernio.com/pipermail/sycamore-dev/ > https://tools.cernio.com/mailman/listinfo/sycamore-dev _______________________________________________ Sycamore-Dev mailing list sycamore-...@wikispot.org http://www.projectsycamore.org/ https://tools.cernio.com/pipermail/sycamore-dev/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
