On Mar 1, 2019, at 9:46 AM, Ivan Kanakarakis <ivan.kanak at gmail.com> wrote: On Fri, 1 Mar 2019 at 19:36, Heather Flanagan <hlflanagan at sphericalcowgroup.com <mailto:hlflanagan at sphericalcowgroup.com>> wrote: I think this is good as a basis to expand upon. We can certainly explain more what we mean by a community volunteer and how this will work (probably craft a sketch like the one we had on the whiteboard).

This will be common for all projects under IdPy. I think it is a bit cumbersome to have it replicated on all repositories. Maybe we can have it as part of the governance repo (and later on the website) and have any other projects point there. What do you think?

On Mar 2, 2019, at 12:15 AM, Rainer Hoerbe <rainer at hoerbe.at> wrote: Wouldn’t it be good enough to to have links to a common repo the wiki and README of each project? > Am 2019-03-01 um 19:05 schrieb Heather Flanagan <hlflanagan at sphericalcowgroup.com <mailto:hlflanagan at sphericalcowgroup.com>>: > > > >> On Mar 1, 2019, at 9:46 AM, Ivan Kanakarakis <ivan.kanak at gmail.com <mailto:ivan.kanak at gmail.com>> wrote: >> >> On Fri, 1 Mar 2019 at 19:36, Heather Flanagan >> <hlflanagan at sphericalcowgroup.com <mailto:hlflanagan at sphericalcowgroup.com>> wrote: >>> >>> Hola a todos! >>> >>> I’ve added a brief wiki page to the SATOSA, pySAML2, and pyXMLSecurity repositories about branching and versioning. The text for each is as follows: >>> >>> --- >>> >>> The idpy projects (including this one) are maintained by a few core maintainers and a larger number of community volunteers. The core maintainers focus entirely on the master branch, developing and evolving the code there. The community volunteers maintain the point-in-time minor and patch releases. >>> >>> For every major release, the core maintainers will create a branch. All work on that branch, including bug fixes and minor enhancements from both the volunteers and the core maintainers, will be coordinated and maintained by the community volunteers. >>> >>> If you would like to be a community volunteer with the appropriate permissions to control a branch, please contact us at discuss at idpy.org <mailto:discuss at idpy.org>. >>> >>> — >>> >> >> I think this is good as a basis to expand upon. We can certainly >> explain more what we mean by a community volunteer and how this will >> work (probably craft a sketch like the one we had on the whiteboard). > > I am happy to have someone to volunteer to create a diagram! :-) > >> >> >>> Should we add this to any other repository? pyFF? pyOP? >> >> This will be common for all projects under IdPy. I think it is a bit >> cumbersome to have it replicated on all repositories. Maybe we can >> have it as part of the governance repo (and later on the website) and >> have any other projects point there. What do you think? > > I’m not a fan of having it replicated in every repository, but I don’t see a better way to get it in front of the people that need to see it. There is no top level wiki for everything in that organizational repository. > > -hf > > _______________________________________________ > Idpy-discuss mailing list > Idpy-discuss at lists.sunet.se <mailto:Idpy-discuss at lists.sunet.se> > https://lists.sunet.se/listinfo/idpy-discuss <https://lists.sunet.se/listinfo/idpy-discuss>