the other matter is more than 5 years of people knowing SourceForge as the
site where find fresh trunk of NH...
but SF in not so cool as GitHub and I have part of white beard and hair.

Perhaps as ppl help us to improve NH we can help to improve SourceForge
http://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/708/
perhaps... perhaps... perhaps...

On Fri, Jun 11, 2010 at 9:47 PM, John Davidson <[email protected]> wrote:

> One thing that people should be aware of is the list of sponsors as shown
> on the NHibernate Home page at http://nhforge.org/
>
> <http://nhforge.org/>Moving the source repository is more than just
> migrating the source code. There is the problem of re-integrating a build
> server, including an automated unit test system into the new site.
>
> here are probably other considerations that I, and others are also
> forgetting. Just what is necessary to move to a new site, how much resource
> will it take and are resources available to do the actual work?
>
> John Davidson
>
>
> On Thu, Jun 10, 2010 at 12:42 PM, Chris Constantin 
> <[email protected]>wrote:
>
>> Why not run a poll to see what the community thinks?
>>
>> Cheers,
>> Chris
>>
>> On Thu, Jun 10, 2010 at 6:26 AM, Fabio Maulo <[email protected]>
>> wrote:
>> > You move from SVN to Git.
>> > You never check the result of Hg in GoogleCode.
>> >
>> > On Thu, Jun 10, 2010 at 5:00 AM, James Gregory <[email protected]
>> >
>> > wrote:
>> >>
>> >> What does public host availability mean?
>> >> Moving away from googlecode was the single best thing FNH did for
>> >> contributions. Just because lots of people have google accounts doesn't
>> make
>> >> it a good choice.
>> >> On Thu, Jun 10, 2010 at 5:28 AM, Fabio Maulo <[email protected]>
>> wrote:
>> >>>
>> >>> If the point is about "more chance" we should use the DVCS with more
>> >>> public host availability.
>> >>> Compare bitbucket with GitHub shouldn't be so hard.
>> >>> But what about clone/fork in the "evil" CodePlex
>> >>>
>> >>>
>> http://blogs.msdn.com/b/codeplex/archive/2010/03/05/codeplex-mercurial-support-for-forks.aspx
>> >>> Probably we will see the similar features soon in GoogleCode.
>> >>> Hopefully SourceForge will add clone/fork function to external hosts
>> for
>> >>> Git and for Mercurial since SF give support to both.
>> >>> The mayor part of NH users has a google account (all NH's forums in
>> >>> various languages are GoogleGroup). If you have a google account you
>> have a
>> >>> GoogleCode account.
>> >>> IMO "more chance" mean more public host availability.
>> >>>
>> >>> On Wed, Jun 9, 2010 at 9:42 AM, Paul Batum <[email protected]>
>> wrote:
>> >>>>
>> >>>> Using a DVCS gives you a more pleasant development experience, but
>> the
>> >>>> move to a community focused host makes your project more attractive
>> to
>> >>>> get involved with. GitHub's network graph, fork queue, pull request
>> >>>> system and the ability to watch people/projects are all valuable
>> >>>> features. As an existing github user I'm obviously biased, but at
>> >>>> least in my case there is more chance that NH will recieve a
>> >>>> submission from me at some point in the future if its hosted on
>> github
>> >>>> because
>> >>>>
>> >>>> a) I will have more visibility of the work being done on NH
>> >>>> b) Committing to my fork and sending a pull request is very low
>> >>>> friction.
>> >>>>
>> >>>> On Jun 8, 11:13 pm, Fabio Maulo <[email protected]> wrote:
>> >>>> > We can switch to DVCS but I don't think that we should change the
>> >>>> > host.
>> >>>> >
>> >>>> > On Tue, Jun 8, 2010 at 4:09 AM, Patrick Earl <[email protected]>
>> wrote:
>> >>>> > > Since Castle and Fluent NHibernate are both on github, I propose
>> >>>> > > that
>> >>>> > > NH be moved to github as well.  GIT has great mindshare and is
>> >>>> > > undoubtedly a very fast and capable system.  Being on the same
>> >>>> > > system
>> >>>> > > as other closely related community projects will make it easier
>> for
>> >>>> > > the developers in the related projects to build off of each
>> other's
>> >>>> > > skills and code.
>> >>>> >
>> >>>> > >        Patrick Earl
>> >>>> >
>> >>>> > --
>> >>>> > Fabio Maulo
>> >>>
>> >>>
>> >>> --
>> >>> Fabio Maulo
>> >>>
>> >>
>> >
>> >
>> >
>> > --
>> > Fabio Maulo
>> >
>> >
>>
>
>


-- 
Fabio Maulo

Reply via email to