Re: [GRASS-PSC] PSC management
On Thu, Nov 17, 2016 at 10:54 AM, Markus Neteler wrote: > On Thu, Nov 17, 2016 at 2:53 PM, Margherita Di Leo wrote: >> On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler wrote: > ... >>> 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, > > Right. Howver, we have a new PSC in place now. > >> 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. > > Sounds good to me. > >> Regarding the roles, I am sure other important roles >> can be individuated as well (e.g. GSoC coordinator/mentors). > > It is a draft wiki page which could be extended. > Regarding the GSoC mentors, I think that this works ok. If we really > need a designated GRASS GIS GSoC coordinator, I don't know. > >> At the same >> time, I'm not sure that these roles must be necessarily found withing the >> PSC. > > As I wrote in the trac wiki page > > "Note: a PSC member with a certain role can also delegate another > community member to share the workload " > >> 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. > > Yes: I want a more active PSC. Not sporadically but constantly. > >> 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 > > Here you go - the current situation (of course my completely biased > private view): > > * treasurer: done by Martin Landa and Markus Neteler > * release manager: done by Markus Neteler > * translation manager: done by Markus Neteler > * education manager: vacant > * press and marketing manager: : done by Markus Neteler > * documentation manager: : mainly done by Markus Neteler, with > contributions by Vero, Vaclav and others > * designer: Vincent Bain for flyer, Web site mainly done by Markus > Neteler lacking the migration to a new CMS > * trac bug report manager: mainly done by Markus Neteler with major > support by core developers > * testing manager: vacant? major efforts done by Sören and Vaclav > * GUI design manager: vacant? major efforts done by Anna, Vaclav, Martin > > This and that name appears too often :-) We suggest 'working groups' instead of managers, for some tasks it fits better and might put the pressure off if people want to join. I also added additional groups, which would be focused on specific tasks, such as Python 3. A + V > > HTH, > Markus > ___ > grass-psc mailing list > grass-psc@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-psc ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] PSC management
On Thu, Nov 17, 2016 at 2:53 PM, Margherita Di Leo wrote: > On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler wrote: ... >> 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, Right. Howver, we have a new PSC in place now. > 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. Sounds good to me. > Regarding the roles, I am sure other important roles > can be individuated as well (e.g. GSoC coordinator/mentors). It is a draft wiki page which could be extended. Regarding the GSoC mentors, I think that this works ok. If we really need a designated GRASS GIS GSoC coordinator, I don't know. > At the same > time, I'm not sure that these roles must be necessarily found withing the > PSC. As I wrote in the trac wiki page "Note: a PSC member with a certain role can also delegate another community member to share the workload " > 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. Yes: I want a more active PSC. Not sporadically but constantly. > 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 Here you go - the current situation (of course my completely biased private view): * treasurer: done by Martin Landa and Markus Neteler * release manager: done by Markus Neteler * translation manager: done by Markus Neteler * education manager: vacant * press and marketing manager: : done by Markus Neteler * documentation manager: : mainly done by Markus Neteler, with contributions by Vero, Vaclav and others * designer: Vincent Bain for flyer, Web site mainly done by Markus Neteler lacking the migration to a new CMS * trac bug report manager: mainly done by Markus Neteler with major support by core developers * testing manager: vacant? major efforts done by Sören and Vaclav * GUI design manager: vacant? major efforts done by Anna, Vaclav, Martin This and that name appears too often :-) HTH, Markus ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] Introducing DOI for software, documentation and data in the GRASS project
On Thu, Nov 17, 2016 at 6:04 AM, Markus Neteler wrote: > The question for me is: what do we need to do for that? Since a DOI > refers to a state in time, GRASS GIS module DOIs might be attached to > releases since they evolve over time. How would that practically work? > There are some services which can give you DOI for SW. From what I understood, DOI for a specific version in version control is often encourage, but that wouldn't work if you want to add the DOI back to the source or documentation because you just advanced the version in version control. Associating DOI with release makes more sense but than what to do with addons which (at least usually) don't have releases? Also some modules don't change between releases of GRASS GIS. Does this mean same DOI or different one? Also, one module would accumulate different DOIs over time. Can we than accumulate number of citations for one module? Another idea (for core modules) is assigning DOI to GRASS GIS release and then use DOI with hash (...doi.../123456#r.slope.aspect) similarly to how the TBI AV-Portal references an exact time in a video. I hope Peter has a better idea if this makes at least some sense or it is completely off. Anyway, my current vision, partially related and partially unrelated, is to have a `Cite as` section in the manual unique for each module which would be generated from info stored in the parser information. Using parser is more flexible than putting it to the HTML directly and `Cite as` is more clear than including the info into `References` section. The info for `Cite as` can be DOI for the module or a paper associated with the module. ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] Introducing DOI for software, documentation and data in the GRASS project
On 2016-11-17 7:04 AM, Markus Neteler wrote:
Hi,
I take liberty to split Peter's email
(https://lists.osgeo.org/pipermail/grass-psc/2016-November/001606.html)
into two, separating out the DOI part for an "unmixed" discussion:
On Tue, Nov 1, 2016 at 7:41 PM, "Peter Löwe" wrote:
[...]
b) Option to use persistent identifiers (Digital Object Identifiers (DOI)) for software, documentation and
data in the GRASS project. DOI are currently mostly known to reference and cite scientific articles
("like a ISBN number for books"). DOI can also be assigned to scientific data, including software.
The benefit in doing this is providing scientific citability, which implies scientific credit and recognition
for the authors of the software or data. DOI for software/data are provided/minted by the DataCite non profit
organisation (https://www.datacite.org/ https://en.wikipedia.org/wiki/DataCite). OSGeo, being a non profit
organisation itself with significant IT infrastructure, could apply to DataCite to receive DOI (has already
been positively checked by the DataCite folks). However, this requires a need within the OSGeo projects to
use DOI. I believe this could be a great driver to foster the authoring and publication of add-on modules for
GRASS, for which the authors could be credited via a DOI upon "publication" within the GRASS
community. FWIW, DOI are already assigned to all OSGeo (and GRASS!)-related FOSS4G conference videos in the
TIB AV-Portal. Example: http://dx.doi.org/10.5446/20425 (DOI also serve as "unbreakable" weblinks.)
Like others I think that this proposal is very interesting.
The question for me is: what do we need to do for that? Since a DOI
refers to a state in time, GRASS GIS module DOIs might be attached to
releases since they evolve over time. How would that practically work?
I also see the huge value in this, for promoting the use of OSGeo
projects in research. Small world, yesterday I sat in a long meeting
with local researchers (Acadia University) and they spoke of the need
for DOI for data etc. So I know and value the use of this. I think
this could be an important addition to all OSGeo projects; but maybe the
GRASS PSC leads the way for others :)
So, I'm watching ;) But I also have the same questions.
-jeff
--
Jeff McKenna
President Emeritus, OSGeo Foundation
http://wiki.osgeo.org/wiki/Jeff_McKenna
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] PSC management
Hi, On Thu, Nov 17, 2016 at 12:15 PM, Markus Neteler 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 > 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 ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] PSC management
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 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) :-) Markus ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
[GRASS-PSC] Introducing DOI for software, documentation and data in the GRASS project
Hi,
I take liberty to split Peter's email
(https://lists.osgeo.org/pipermail/grass-psc/2016-November/001606.html)
into two, separating out the DOI part for an "unmixed" discussion:
On Tue, Nov 1, 2016 at 7:41 PM, "Peter Löwe" wrote:
[...]
> b) Option to use persistent identifiers (Digital Object Identifiers (DOI))
> for software, documentation and data in the GRASS project. DOI are currently
> mostly known to reference and cite scientific articles ("like a ISBN number
> for books"). DOI can also be assigned to scientific data, including software.
> The benefit in doing this is providing scientific citability, which implies
> scientific credit and recognition for the authors of the software or data.
> DOI for software/data are provided/minted by the DataCite non profit
> organisation (https://www.datacite.org/
> https://en.wikipedia.org/wiki/DataCite). OSGeo, being a non profit
> organisation itself with significant IT infrastructure, could apply to
> DataCite to receive DOI (has already been positively checked by the DataCite
> folks). However, this requires a need within the OSGeo projects to use DOI. I
> believe this could be a great driver to foster the authoring and publication
> of add-on modules for GRASS, for which the authors could be credited via a
> DOI upon "publication" within the GRASS community. FWIW, DOI are already
> assigned to all OSGeo (and GRASS!)-related FOSS4G conference videos in the
> TIB AV-Portal. Example: http://dx.doi.org/10.5446/20425 (DOI also serve as
> "unbreakable" weblinks.)
Like others I think that this proposal is very interesting.
The question for me is: what do we need to do for that? Since a DOI
refers to a state in time, GRASS GIS module DOIs might be attached to
releases since they evolve over time. How would that practically work?
thanks,
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc
