Just checking: I'm guessing the plan is to stick with (at least for now) the tickets tracker at sourceforge, or move to the issue tracker at github?
And, less relevant to the GitHub Migration topic but still useful to know: is the best way to drum up interest in fixing a bug to post to this mailing list? (We have found a memory leak we can't track down that is blocking our progress on a separate project. Any advice? http://sourceforge.net/p/openbabel/bugs/867/ ) Thanks, Richard On Mar 4, 2013, at 3:49 PM, Geoffrey Hutchison <geoff.hutchi...@gmail.com> wrote: >> Someone (Geoff, I assume) will need to give you permissions to use that URL, >> which is read/write. The read only URL should still work if you just want to >> check a copy of the sources out: > > Right. Anyone who wants write access, please let me know. > > As far as a workflow, let's go with "pull requests" for now. When you've got > a change you want to integrate, please submit a "pull request" through > GitHub. This will let some level of review occur before things get merged. > > If this gets backed up, we can look for alternate approaches. > > -Geoff > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > OpenBabel-Devel mailing list > OpenBabel-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbabel-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
