[GRASS-PSC] next PSC task
Dear PSC, after the election of the new PSC, before defining the new chair, may I (as a community member) ask you what will be the next task of the PSC? when will be the new chair announced? I think an important first/next step to broaden the dev community may be to investigate how new source code management technologies like GIT could be implemented beside/instead of svn. There are ongoing some OSGeo initiatives to provide GIT infrastructure for OSGeo projects? Will be the GRASS GIS project will use such new technologies? Python 3 is heavily knocking on the door. Will there be some lead of the new PSC regarding these challenges? Thanks for clarifications! - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/next-PSC-task-tp5286412.html Sent from the GRASS-PSC mailing list archive at Nabble.com. ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
On Fri, Sep 16, 2016 at 11:47 PM, Helmut Kudrnovsky wrote: > Dear PSC, > > after the election of the new PSC, before defining the new chair, may I (as > a community member) ask you what will be the next task of the PSC? > > when will be the new chair announced? IMHO we need to have someone besides the current candidate(s) to organize the election of the chair. I hoped for some faster pace here :-) > I think an important first/next step to broaden the dev community may be to > investigate how new source code management technologies like GIT could be > implemented beside/instead of svn. It was on the recent community sprint agenda, with no real outcome. We do need a git *expert* for this. Anyone? However, I believe that this topic is more a technical rather than a political one which belongs to grass-dev. > There are ongoing some OSGeo initiatives to provide GIT infrastructure for > OSGeo projects? Will be the GRASS GIS project will use such new > technologies? At time there is some experimental setup: GRASS GIS is obviously already registered there but a git *expert* is needed. In addition we have to understand how to use git and svn together (like GDAL appears to do) and when the experimental stage will be turned into production mode. > Python 3 is heavily knocking on the door. IMHO also the Python 3 is a grass-dev topic. > Will there be some lead of the new PSC regarding these challenges? For sure the new PSC will do related house keeping but the technical part should remain in the grass-dev discussion space unless there is a strong motivation to make it a PSC task. > Thanks for clarifications! Urgent is the election of the chair. Best Markus ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
>IMHO we need to have someone besides the current candidate(s) to >organize the election of the chair. >I hoped for some faster pace here :-) is there a similar system /infrastructure needed as for the PSC voting? - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/next-PSC-task-tp5286412p5286532.html Sent from the GRASS-PSC mailing list archive at Nabble.com. ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
Hi, 2016-09-18 18:51 GMT+02:00 Markus Neteler : > It was on the recent community sprint agenda, with no real outcome. > We do need a git *expert* for this. Anyone? > However, I believe that this topic is more a technical rather than a > political one which belongs to grass-dev. I am willing to help with this issue. Probably others will be interested too, Vaclav? Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
On Sun, Sep 18, 2016 at 2:04 PM, Martin Landa wrote: > 2016-09-18 18:51 GMT+02:00 Markus Neteler : > > It was on the recent community sprint agenda, with no real outcome. > > We do need a git *expert* for this. Anyone? > > However, I believe that this topic is more a technical rather than a > > political one which belongs to grass-dev. > > I am willing to help with this issue. Probably others will be > interested too, Vaclav? Ma Yes, to certain extent. However, I think it is not purely technical and it is coupled with OSGeo and other OSGeo projects. ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
On Sun, Sep 18, 2016 at 8:42 PM, Vaclav Petras wrote: > On Sun, Sep 18, 2016 at 2:04 PM, Martin Landa > wrote: >> >> 2016-09-18 18:51 GMT+02:00 Markus Neteler : >> > It was on the recent community sprint agenda, with no real outcome. >> > We do need a git *expert* for this. Anyone? >> > However, I believe that this topic is more a technical rather than a >> > political one which belongs to grass-dev. >> >> I am willing to help with this issue. Probably others will be >> interested too, Vaclav? Ma > > > Yes, to certain extent. However, I think it is not purely technical and it > is coupled with OSGeo and other OSGeo projects. Right- But the PSC is only involved once the technical aspects are clear. E.g., we (at grass-dev) may check first how it works for GDAL. Markus ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
On 18/09/16 20:50, Markus Neteler wrote: On Sun, Sep 18, 2016 at 8:42 PM, Vaclav Petras wrote: On Sun, Sep 18, 2016 at 2:04 PM, Martin Landa wrote: 2016-09-18 18:51 GMT+02:00 Markus Neteler : It was on the recent community sprint agenda, with no real outcome. We do need a git *expert* for this. Anyone? However, I believe that this topic is more a technical rather than a political one which belongs to grass-dev. I am willing to help with this issue. Probably others will be interested too, Vaclav? Ma Yes, to certain extent. However, I think it is not purely technical and it is coupled with OSGeo and other OSGeo projects. Right- But the PSC is only involved once the technical aspects are clear. One of the questions I would think we should think about from the beginning is whether we really want to run with a double system (svn and git) or whether it might be easier in the long run, to completely switch over to git... Moritz ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] next PSC task
* Moritz Lennert [2016-09-19 11:12:09 +0200]: On 18/09/16 20:50, Markus Neteler wrote: On Sun, Sep 18, 2016 at 8:42 PM, Vaclav Petras wrote: On Sun, Sep 18, 2016 at 2:04 PM, Martin Landa wrote: 2016-09-18 18:51 GMT+02:00 Markus Neteler : It was on the recent community sprint agenda, with no real outcome. We do need a git *expert* for this. Anyone? However, I believe that this topic is more a technical rather than a political one which belongs to grass-dev. I am willing to help with this issue. Probably others will be interested too, Vaclav? Ma Yes, to certain extent. However, I think it is not purely technical and it is coupled with OSGeo and other OSGeo projects. Right- But the PSC is only involved once the technical aspects are clear. One of the questions I would think we should think about from the beginning is whether we really want to run with a double system (svn and git) or whether it might be easier in the long run, to completely switch over to git... From my point of view, git is easier. I have experiences now, like many in the GRASS community, controlling almost everything ascii using git (not only code). My experiences in resolving conflicts, though, when it comes to merge branches, are, indeed, limited. I did a few stuff, but not enough. But we should just go for it, in the beginning, at least, experimental and playing around in a sandbox-like repository. Cheers, Nikos ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
