I don't think that we need anything else, to be truthful.
The way I usually seen it work, the project hosting site is merely about the
code / pull requests, not much else.

On Thu, Aug 18, 2011 at 6:56 PM, Stephen Bohlen <[email protected]> wrote:

> ** Agreed. I'd posited early on that along w a move to *some* VCS hosting
> provider we needed to consolidate the all else around NHForge so that all
> existing deprecated resources could simply point to NHForge as a hub from
> which links to all else (JIRA, downloads, whatever) could emanate.
>
> With JIRA remaining hosted by Atlassian, source somewhere (yet to be
> decided), what other than downloads still needs a 'home' at this point?
>
> -Steve B.
> ------------------------------
> *From: * Julian Maughan <[email protected]>
> *Sender: * [email protected]
> *Date: *Fri, 19 Aug 2011 06:48:15 +0800
> *To: *<[email protected]>
> *ReplyTo: * [email protected]
> *Subject: *Re: [nhibernate-development] VCS Vote
>
> I just think if the project infrastructure is too fragmented, it will
> become confusing. I think we can divide the infrastructure into two
> categories: front-of-shop and back-of-shop. I think it is important there is
> one place users go for downloads, doco, etc. (NHForge). The back-of-shop
> stuff - eg (VCS, bug-tracker) - it doesn't matter so much. That is the
> reason I raised the question about download hosting.
> On 19/08/2011 6:37 AM, "Stephen Bohlen" <[email protected]> wrote:
> > Yeah, some time ago (early on in this last attempt at this) I pointed out
> that there are indeed two distinct categories in which we're trying to make
> a decision: VCS specifically and project infrastructure more broadly (issue
> tracking, announcements, etc).
> >
> > Even if we go to github for VCS, I'm not sure this precludes our
> retaining sourceforge + nhforge in the other roles (e.g., as we were already
> discussing earlier today re: central hub for downloads, etc ).
> >
> > Couldn't a move to github for VCS leave all else exactly as-is and be a
> (relatively) non-invasive change (wondering....)?
> >
> > -Steve B.
> > -----Original Message-----
> > From: Julian Maughan <[email protected]>
> > Sender: [email protected]
> > Date: Fri, 19 Aug 2011 06:24:45
> > To: <[email protected]>
> > Reply-To: [email protected]
> > Subject: Re: [nhibernate-development] VCS Vote
> >
> > +1
> >
> > I don't have a problem with git or using GitHub as a source code host.
> > However, GitHub doesn't seem as good as Google Code or CodePlex in
> offering
> > a project 'home'. Larger projects like NServiceBus, that use GitHub for
> > their source, often have a strong alternative web presence with their
> > website. If we use GitHub, I believe NHForge will need to be improved to
> > become a better project home. Do we have the resources for this
> improvement?
> > Maybe not.
> > On 19/08/2011 3:28 AM, "Richard Brown" <[email protected]> wrote:
> >> Oops, sorry. I should have read more carefully.
> >> On 18 Aug 2011 20:25, "Fabio Maulo" <[email protected]> wrote:
> >>> The meaning is:
> >>> -1 = Do not use the github repository, find another alternative.
> >>>
> >>> On Thu, Aug 18, 2011 at 3:23 PM, Richard Brown <
> [email protected]
> >>>wrote:
> >>>
> >>>> Is that -1 for github? Or -1 for this specific branch?
> >>>>
> >>>> (just checking there isn't something wrong with the import I wasn't
> > aware
> >>>> of.)
> >>>> On 18 Aug 2011 19:11, "Fabio Maulo" <[email protected]> wrote:
> >>>> > -1
> >>>> >
> >>>> > On Thu, Aug 18, 2011 at 2:43 PM, Patrick Earl <[email protected]>
> > wrote:
> >>>> >
> >>>> >> So we need to ensure there has been a clear decision on the source
> >>>> >> control matter. Committers should indicate one of the following
> >>>> >> options.
> >>>> >>
> >>>> >> +1 = Use the github repository.
> >>>> >> -1 = Do not use the github repository, find another alternative.
> >>>> >>
> >>>> >> Please respond on this thread with your vote.
> >>>> >>
> >>>> >> Patrick Earl
> >>>> >>
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Fabio Maulo
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Fabio Maulo
> >
>

Reply via email to