On Wed, Mar 30, 2016 at 05:12:00PM -0500, Ian Cordasco wrote: > On Wed, Mar 30, 2016 at 5:02 PM, Laurent Peuch > <cor...@worlddomination.be> wrote: > > Hello, > > > > On Mon, Mar 28, 2016 at 11:15:59AM -0500, Ian Cordasco wrote: > >> On Mon, Mar 28, 2016 at 11:13 AM, Ian Cordasco > >> <graffatcolmin...@gmail.com> wrote: > >> > I'm really happy you sent this. I had forgotten about RedBaron and was > >> > going to start looking for a project exactly like it. Would you be > >> > interested in moving the project under the umbrella of the PyCQA? We > >> > could probably more easily integrate new contributors in an > >> > organization. I'll start taking a look at how I could help out with > >> > RedBaron since Flake8 will probably start depending on it or something > >> > like it. > >> > >> Of course Baron is also welcome in addition to RedBaron. In > >> particular, I'd love to firm up the Python 3 support (since Flake8 > >> would need that). > >> > >> If you need more PyCQA information, we have some documentation on > >> http://meta.pycqa.org > > > > Thanks a lot for this proposition :) > > > > After reading the documentation, I am very tempted to say yes, but I > > have one small hesitation (not about the CoC, I'm actually quite happy > > that you have one): PyCQA define itself as "a loose organization of > > people who maintain projects in roughly the same domain: automatic > > style and quality reporting" but that's not exactly (red)baron is > > doing. While it's not very far away (like a low level more general > > tool that can be used to build those kind of tools), it's still a bit > > different, won't that be a problem? > > Not really. That's a living document and we can amend it to use > language that would make (Red)Baron feel more comfortable joining. > When I wrote that, I was mostly describing the state of things rather > than the future which was a bit silly of me. I feel like RedBaron > would be a good fit, especially since I'm not exactly sure astroid on > its own can be squeezed into that statement. Maybe we should just > remove the "automatic style and reporting" bit to keep it a bit more > general?
Oh, I don't have strong feelings regarding a modification of this document, it was more about the existing group, but if you think it's ok then it's a "yes" from me :) I'll take a look tomorrow about migrating the repositories to the organisation. (ps: I won't be there at pyconUS, too far away, not enough money and time) -- Laurent Peuch -- Bram _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality