I'm also strongly in support of a community-oriented hosting solution
such as GitHub, BitBucket, or Google Code. Having a centralized list
of forks is quite useful when one is looking to figure out what's
really going on with the source code and community contributions.
While manually submitting and updating patches is workable, why not
move to a solution that allows for fluid flow of code between authors?
DVCS systems and open source are seemingly made for each other. I
have a minor preference for Mercurial, but quite frankly, any one of
the three hosting solutions would be fantastic! Just converting the
SVN repository to GIT/HG once isn't a great solution since it makes
merging from/to the trunk and sharing changes with each other
significantly more difficult than need be. SVN, being a less capable
system, makes a poor back-end to GIT and HG. One has to constantly
fiddle (rebase) the changesets instead of following a natural
workflow. Once rebased, this causes problems for other users sharing
the code. Basically, using a DVCS as a front-end to SVN gives up too
many important benefits in terms of code sharing and ease of use.
Consider also the benefits of shared code reviews using the
community-oriented sites. Patches can be analyzed, improved, and
commented on in place. Even different people can contribute to the
same significant feature without having to put the code on the trunk
before it's ready.
I'm getting all excited talking about this stuff. I'm very much
looking forward to the conversion and hope we can take action on this
in short order. Thanks for your continued consideration.
Patrick Earl
On Fri, Jun 4, 2010 at 11:38 PM, Fabio Maulo <[email protected]> wrote:
> Man,
> RSS feeds... puf...http://sourceforge.net/projects/nhibernate/ It is there
> since long time.
> GitHub, as GoogleCode, as bitbucket, may show clones hosted in the same
> place but the idea behind DVCS does not mean "distributed but hosted all in
> the same place".
> btw... and again... you have 90% work done. Download the mirror, convert it
> to Git, put it wherever you want and start patching it.
> Somebody will follow your activity, will clone your fork and everybody
> happy.
> If you need it, just do it.
> On Fri, Jun 4, 2010 at 7:44 PM, Mauricio Scheffer
> <[email protected]> wrote:
>>
>> Yes, GoogleCode *did* implement this properly with their Mercurial
>> support. There's a "create a clone" button and a clones tab which
>> lists all clones of the original repository. But the discussion was
>> about sourceforge, and I don't see these things on sourceforge.
>> This "project network" I was talking about is not just hope, on github
>> for example I can see all forks (e.g.
>> http://github.com/jagregory/fluent-nhibernate/network/members
>> ) and see what people are doing on those forks (e.g.
>> http://github.com/jagregory/fluent-nhibernate/network ). You can also
>> get an RSS feed of all activity within a project network. I believe
>> bitbucket implements similar features.
>> That's what makes github a "hub", it concentrates all forks in one
>> place, making managing the project easier .
>>
>> --
>> Mauricio
>>
>> On Jun 4, 7:24 pm, Fabio Maulo <[email protected]> wrote:
>> > but you can see it in GoogleCode and btw we can require it to
>> > sourceforge...
>> > at the end a fork/clone is a fork/clone in my PC, in your PC, in
>> > GoogleCode,
>> > in CodePlex, or whatever you want host it.
>> >
>> > About "project network being able to see what everyone else is working
>> > on"
>> > IMO is a merely hope....
>> > or you have proposed something in our JIRA ?
>> >
>> > On Fri, Jun 4, 2010 at 7:06 PM, Mauricio Scheffer <
>> >
>> >
>> >
>> >
>> >
>> > [email protected]> wrote:
>> > > If I may chip in, moving to a DVCS is not just about moving the code
>> > > to another repository.
>> > > It's also about people being able to fork easily and everyone on the
>> > > project network being able to see what everyone else is working on.
>> > > Github and Bitbucket were built from the ground up around these
>> > > concepts. I might be wrong but I don't see any fork button or fork
>> > > list on Sourceforge projects using git (e.g.
>> > >https://sourceforge.net/projects/gitextensions/
>> > > ). I couldn't find any projects using a mercurial repository on
>> > > sourceforge. It looks as if DVCS was bolted on as an afterthought.
>> > > Without this fork management thing, a huge part of DVCS is lost.
>> >
>> > > --
>> > > Mauricio
>> >
>> > > On Jun 4, 11:14 am, Fabio Maulo <[email protected]> wrote:
>> > > > SourceForge gives support to any thing we want and, over all,
>> > > > SourceForge
>> > > is
>> > > > one of the most important and historical piece of OSS world.
>> > > > We have no strong reason to move NH sources somewhere else (at least
>> > > > so
>> > > > far).
>> >
>> > > > On Fri, Jun 4, 2010 at 10:44 AM, Lorenzo Melato <
>> > > [email protected]>wrote:
>> >
>> > > > > Have you evaluated bitbucket.org as Mercurial hosting ?
>> >
>> > > > > --
>> > > > > Lorenzo Melato
>> > > > >http://blogs.ynnova.it/lorenzomelato
>> >
>> > > > --
>> > > > Fabio Maulo
>> >
>> > --
>> > Fabio Maulo
>
>
> --
> Fabio Maulo
>
>
