On Wed, 2012-09-05 at 12:26 +0000, Hanno Schlichting wrote: > Matthew Wilkes <matt@...> 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. So people cannot make pull requests to it from forks they made of the Jarn repo. It is however relatively simple to move your fork of the Jarn repo to a branch in the collective (from which a pull request or merge could be made). I just did this with the Syslab "highlighting" branch: > git clone https://github.com/syslabcom/collective.solr.git > cd collective.solr/ > git checkout highlighting (Only if you're using a branch) > git remote add cltve https://github.com/collective/collective.solr.git > git push -u cltve highlighting Cheers JC _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
