On 10/31/12 2:02 PM, Peter Hartmann wrote: >> Much thanks to Peter Hartmann for his work on >> #3883<https://sourceforge.net/p/allura/tickets/3883/>, >> his changes <https://sourceforge.net/p/allura/git/merge-requests/9/> have >> been merged. >> >> This gets us well on our way to being ready for an Incubator release, as >> the SCM tools are now decoupled and can be moved into separate projects to >> deal with the licensing issues they raised. >> >> Thanks again, and great work. >> >> >> - Cory >> > I'm flattered to see my humble doings being lauded in public like that. An > undeserved praise compared to all the work you guys are commiting every day, > but > nontheless nice. Thanks for offering me all the help I needed on my first > contribution and patiently answering my questions on irc. > > I will take this opportunity to write a bit on how I think we should handle > moving the SCM tool in question, ForgeHg, outside the scope of Allura > incubation > project. As https://sourceforge.net/p/allura/tickets/4655/ states, this will > technically go down the way of creating new project as a sort of distribution > channel - repository, possibly some tarball release etc. Registering a project > on SourceForge is something anyone can do, but I think this should be done by > someone from the core dev team, so that ForgeHg can be kept in line with any > future changes to Allura's core. As I understand that, ForgeHg won't be > distributed along Allura anymore and will not be distributed through Apache > Incubator, but it still remains somewhat of an "official" module, being used > on > SourceForge and all. > > The ticket specifically mentions optional installation, so in addition to > above, > I propose to make a pypi release of ForgeHg. Preparing such a release is a > task > when I can actually be useful. It's no rocket science, but it would involve > code > separation, preparing installation routine - with test data, possibly some > configuration - and testing how it would behave. This looks like nonexciting > task that I can handle ;) Once finished, I'll push a branch with this tool > alone, prepared for distribution, and then someone competent would register a > project and use this branch as repo's basis. >
That sounds like a good plan, matches how I had been envisioning it. I've created https://sourceforge.net/p/forgehg/ with you and some of the other active developers as admins. Feel free to use it whenever. You or any dev here can set up the pypi package too and add the other devs. The code separation might be the trickiest part here. Since we are regularly updating ForgeHg code, we'll want to avoid having a period of time where the code lives in two places and is confusing. One idea might be that after the process and any changes are all figured out, then redo the code copy. That way we'll have a quick painless cutover. -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
