[GRASS-PSC] PSC management

[Margherita Di Leo]

Hi,

On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler <neteler at osgeo.org> wrote:

> Dear PSC,
>
> I would like to restart the discussion on "PSC member roles" to be
> assigned:
>
> On Thu, May 21, 2015 at 2:39 PM, Moritz Lennert
> <mlennert at club.worldonline.be> wrote:
> > On 17/05/15 12:43, Markus Neteler wrote:
> >>
> >> Hi PSC,
> >>
> >> ... back to this topic of management, I have updated
> >>
> >> https://trac.osgeo.org/grass/wiki/PSC/Agenda#Openissues
> >>
> >> Important are
> >> 1) PSC: assign roles to the PSC members (see there)
> >
> >
> > Looking at the list, I have the feeling that the following are the most
> > important:
> >
> > - treasurer/financial manager: the issue of how to collect funds from
> > sponsors for code sprints comes up regularly
> >
> > - release manager: Markus shouldn't have to handle this on his own any
> > longer
> >
> > - documentation manager / education outreach: these can actually go
> > together. I think that the manual page system works relatively well (some
> > more detailed descriptions and notes and possibly some more examples
> might
> > be nice), but that we lack a coherent body of up-to-date tutorial-like
> > documentation. Such documentation could be very useful for educational
> > purposes as well
> >
> > - translation manager: although I think that the translations system
> seems
> > to work.
> >
> > But even if we designate documentation and translation managers we cannot
> > expect them to do all the work, so the real question is whether having
> such
> > managers will bring in more volunteers...
> >
> > For the first two roles (financial and release) one person to support
> Markus
> > in these tasks would already make a big difference.
> >
> > Markus, could you maybe list the different things that need to be done in
> > these roles ?
>
> Yes:
> https://trac.osgeo.org/grass/wiki/PSC/Roles
>
> Now I think that all new and confirmed members may contribute to this
> question and edit the trac page directly (and report here)
>  :-)
>

The first email in this thread dates back to 2014 and no action has been
taken, from my POV we would need to discuss this thread, as well as other
threads that were posed by members of the community, in a more interactive
way, perhaps via IRC. Regarding the roles, I am sure other important roles
can be individuated as well (e.g. GSoC coordinator/mentors). At the same
time, I'm not sure that these roles must be necessarily found withing the
PSC. Besides the activities that clearly fall currently on the shoulders of
Markus and few others, I don't understand why we need a coordinator at all,
since some activities seem to flow well without a designated coordinator,
as Moritz pointed out. But I'm sure that to propose this, Markus, you must
have your reasons. Could we make a quick check of the situation,
individuate the current issues and what are we trying to achieve (or which
problems are we trying to solve) with this proposal? Thanks

-- 
Margherita Di Leo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20161117/b8251422/attachment.html>