Le 11 juin 2011 à 22:41, Michael A. Smith a écrit : > Hi, I have a couple of quick patches I was thinking about submitting to a > collective project that is not my own, and I wanted to get your thoughts on > the etiquette of the collective. > > 1. I've already committed some whitespace-consistency, spelling, and > syntax-error fixes that were preventing the HEAD revision from running on a > couple of projects. No-one has complained, but did I cross a line? (I hope > not, but it only occurred to me that that might not be appreciated after the > fact.) > > 2. What constitutes an abandoned/languishing project? Take > collective.ckeditor, which hasn't been touched in 9 mo. Its listed owner is > Ingeniweb, which seems to have been replaced by Alter Way, which in turn > doesn't seem to do Zope afaict. Is this project "fair game"? (I'm not saying > I want to take it over, necessarily, but talking in generalities.) Hi,
The author of collective.ckeditor has left Alter Way but still maintains this component and associated friends (collective.plonefinder and collective.quickupload). You can contact Jean-Mathieu Grimaldi from here http://plone.org/author/macadames or at his new mail address [email protected] He welcomes contributions. Keep Plone 4.0 compatibility unless it is not possible. > > 3. For our own projects, is there some standard way we (as collective.X > product "owners") can signal to other collective contributors whether or not > we would welcome commits to trunk? (As opposed to branching and forking, > which are protected rights in free software) > > Please share your thoughts, > -Michael > _______________________________________________ > Product-Developers mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-product-developers _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
