Hi all On 7 December 2015 at 19:42, Ronny Pfannschmidt <opensou...@ronnypfannschmidt.de> wrote: > Hi everyone, > > given that pytest-dev is slowly growing, i'm feeling it is necessary to > have a transparent management channel to see > and communicate the details that span more than one project, and their > management > > that includes infrastructure, addition of projects, handling maintainer > management as well as simpy stuff like the planned/ongoing github > migration of further projects. > > an example of such a management channel that i liked was the meta-flask > organisation that the pocoo team created around flask.
For those wondering, the description of this is at https://github.com/pocoo/metaflask While what is described at metaflask sounds rather heavy and like it would easily be out of date I do thing it could be beneficial to spell out how pytest-dev repos operate, when you can "hijack" it from a maintainer and how you get commit access. This last one is probably the most important one, it's more inclusive to spell out clear rules on how to get commit access then on just leaving it "when the other core devs think appropriate". And giving people commit access is empowering them to contribute more. Personally I think this could easily be a page on pytest.org though. In fact I just searched pytest.org for "pytest-dev" and was surprised not to get any results. Regards, Floris _______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
