[Product-Developers] Moving collective.solr to the Github collective

[Jan-Carel Brand]

On Thu, 2012-09-06 at 09:08 +0200, Jens W. Klein wrote:
> On 2012-09-06 08:17, Jan-Carel Brand wrote:
> > On Wed, 2012-09-05 at 12:26 +0000, Hanno Schlichting wrote:
> >> Matthew Wilkes <matt at ...> writes:
> >>>> We're using collective.solr quite extensively at Syslab but we're now
> >>>> largely working on our own fork in the Syslab repo (which is becoming
> >>>> incompatible with the canonical).
> >>>>
> >>>> So, if there aren't any objections, I'd like to go ahead and create a
> >>>> collective.solr repo in the collective, where everybody who uses this
> >>>> add-on can contribute bugfixes and improvements.
> >>>
> >>> This sounds like the best thing to do.
> >>
> >> +1, the Solr instance recipe was already moved to the collective. Neither
> >> me nor any of the other ex-Jarnians seem to be maintaining these packages
> >> anymore.
> >
> > I finally got around to doing this:
> > https://github.com/collective/collective.solr
> >
> > Unfortunately due to the way we create new repos in the collective, this
> > repo is now not a fork of the original one in Jarn.
> 
> you did not use the fork option at
> https://github.com/collective/collective.github.com/blob/master/permissions.cfg#L1615 
> ?
> as described in the docs at
> http://collective.github.com/#instructions-on-editing-permissions-cfg

I'm pretty sure last time I looked at the instructions that part wasn't
there.

> to revert this I'd propose to remove the repo in permissions.cfg and add 
> a ticket at to ask for manual remove at
> https://github.com/collective/collective.github.com/issues/new
> 
> after complete removal re-add the entry in permissions.cfg and dont 
> forget about the fork line.

Thanks for the info! I'll do that.

JC