My first thought is that the maintainer should keep the repository in there own github account which is the whole point of contrib. However, I think this does break down a little with some existing contrib projects (i.e. view components) where we don't really have a maintainer and may never have one, however people still submit patches to fix things. The other concern is that contrib projects don't get a lot of love, so keeping a main repository somewhere grouped with other contrib projects would entice people to push their changes back to one main repository.
I would vote for option 2. On Tue, Jun 1, 2010 at 7:22 AM, John Simons <[email protected]>wrote: > Hi guys, > > I'm sure everyone saw the work Nicholas put to migrate ActiveWriter to > vs2010 - > http://groups.google.com/group/castle-project-users/browse_thread/thread/a13c39b21ca722ad?hl=en_US. > My question is should we ask Nicholas to host the source and d/l package in > github? > > If yes, where exactly? > - Our own repository - http://github.com/castleproject > - The castlecontrib one - http://github.com/castleprojectcontrib > - Nicholas own repository > - A standalone repository eg http://github.com/castleactivewriter > or > - leave it in svn > > Thoughts? > > > > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > -- Jono -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
