On Thu, Apr 11, 2019 at 4:40 PM Markus Neteler wrote:
> On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras
> wrote:
> > On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler wrote:
> >>
> >>
> >> RFC 6: Migration from SVN to GitHub
> >> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
> >
> > Looks g
On Wed, Apr 17, 2019 at 7:53 PM Martin Landa wrote:
> st 17. 4. 2019 v 16:29 odesílatel Markus Neteler napsal:
> > Please check our work already done:
> > I have reconstructed the releases back to 3.2 including time stamps at file
> > level.
> >
> >
> > https://github.com/grass-svn2git/grass-leg
Hi,
st 17. 4. 2019 v 16:29 odesílatel Markus Neteler napsal:
> Please check our work already done:
> I have reconstructed the releases back to 3.2 including time stamps at file
> level.
>
>
> https://github.com/grass-svn2git/grass-legacy
note that this repo lack releases [0] (=git tags). This n
Hi Peter,
"Peter Löwe" schrieb am Mi., 17. Apr. 2019, 12:15:
> Hi Markus, hi PSC,
>
> the reason why I believe we should consider the Zenodo option (for long
> term archiving and DOI-based scientific recognition/citation) before making
> the switch to GitHub is the DOI versioning capability of
On Mon, Apr 1, 2019 at 11:13 AM Markus Neteler wrote:
>
> Hi Peter,
>
> On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" wrote:
> >
> > Hello PSC,
> >
> > before we actually venture into GitHub, I propose we should consider
> > beforehand how the GRASS repo(s) *could* make use of the Zenodo archive
On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras wrote:
> On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler wrote:
>>
>>
>> RFC 6: Migration from SVN to GitHub
>> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Looks great. Thanks!
>
> One thing it lacks are best practices for using Git. Git
On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler wrote:
>
> RFC 6: Migration from SVN to GitHub
> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
Looks great. Thanks!
One thing it lacks are best practices for using Git. Git is not Subversion
and we just can't use it as Subversion. Specif
Hi,
st 10. 4. 2019 v 9:29 odesílatel Michael Barton napsal:
> Just want to show my support
sure, thanks! Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-psc mailing list
grass-psc@lists.osgeo.org
ht
Just want to show my support
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC
Hi,
please be aware, this is not an official (clearly defined) vote thread.
Ma
út 9. 4. 2019 v 22:09 odesílatel Michael Barton napsal:
>
> 1+ since we have an exit strategy if GitHub becomes too commercial.
>
> Michael
>
> C. Michael Barton
> Director, Center for Social Dyn
1+ since we have an exit strategy if GitHub becomes too commercial.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizo
Hi Markus, all,
> Gesendet: Sonntag, 07. April 2019 um 22:02 Uhr
> Von: "Markus Neteler"
> An: "GRASS PSC list"
> Betreff: Re: [GRASS-PSC] git migration
>
> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration
+1
On Mon, Apr 8, 2019 at 4:49 AM Moritz Lennert
wrote:
> On 7/04/19 22:02, Markus Neteler wrote:
> > Hi PSC,
> >
> > a months has passed since the publication of the draft
> >
> > RFC 6: Migration from SVN to GitHub
> > https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
> >
> > Since then
On 7/04/19 22:02, Markus Neteler wrote:
Hi PSC,
a months has passed since the publication of the draft
RFC 6: Migration from SVN to GitHub
https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
Since then comments have been received and integrated into the document.
Let me suggest to come to
Dear PSC,
ne 7. 4. 2019 v 22:02 odesílatel Markus Neteler napsal:
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.
agreed. We need to come with decision. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/l
Hi PSC,
a months has passed since the publication of the draft
RFC 6: Migration from SVN to GitHub
https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
Since then comments have been received and integrated into the document.
Let me suggest to come to a vote in the next days in order to move
Hi,
st 27. 3. 2019 v 14:30 odesílatel Anna Petrášová napsal:
>>> I opened a thread for discussion about labels and priorities for issues in
>>> the RFC, but there was not so much interest apparently [1]. I still believe
>>> that we should keep
>>> raster(3d), vector, temporal and so on as compo
Hi Peter,
On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" wrote:
>
> Hello PSC,
>
> before we actually venture into GitHub, I propose we should consider
> beforehand how the GRASS repo(s) *could* make use of the Zenodo archive in
> the future, so we can set up things in a way that this option can
On 1/04/19 09:35, "Peter Löwe" wrote:
Hello PSC,
before we actually venture into GitHub, I propose we should
consider beforehand how the GRASS repo(s) *could* make use of the
Zenodo archive in the future, so we can set up things in a way that this
option can be used (setting up of credentials
servation for the old stable releases GRASS 4.x, 5.x and 6.x.
best,
peter
mailto:peter.lo...@gmx.de>>
Gesendet: Dienstag, 26. März 2019 um 12:28 Uhr
Von: "Markus Neteler" mailto:nete...@osgeo.org>>
An: GRASS-PSC mailto:grass-psc@lists.osg
On Wed, Mar 27, 2019 at 4:48 AM Margherita Di Leo
wrote:
> Hi,
>
> On Tue, Mar 26, 2019 at 10:59 PM Veronica Andreo
> wrote:
>
>> Hi,
>>
>> I opened a thread for discussion about labels and priorities for issues
>> in the RFC, but there was not so much interest apparently [1]. I still
>> believe
Hi,
On Tue, Mar 26, 2019 at 10:59 PM Veronica Andreo
wrote:
> Hi,
>
> I opened a thread for discussion about labels and priorities for issues in
> the RFC, but there was not so much interest apparently [1]. I still believe
> that we should keep
> raster(3d), vector, temporal and so on as compone
Hi,
I opened a thread for discussion about labels and priorities for issues in
the RFC, but there was not so much interest apparently [1]. I still believe
that we should keep
raster(3d), vector, temporal and so on as components. I think those are
useful and make search easier. Modules is maybe too
Hi,
út 26. 3. 2019 v 11:28 odesílatel Markus Neteler napsal:
> where do we stand here at time?
RFC document is OK for me. I am ready to vote about that. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
gras
Hi all,
where do we stand here at time?
Markus
___
grass-psc mailing list
grass-psc@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-psc
Markus Neteler wrote
> PS: Did I mention that Martin Landa did an outstanding hard job with
> developing the svn2git converter scripts for code and issues? Weeks of
> work... thanks Martin!!
big kudos to Martin!
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GRASS-
Hi Luís,
On Wed, Mar 6, 2019 at 2:51 PM Luís Moreira de Sousa
wrote:
>
> Hi Martin,
>
> the survey enquired which platforms people currently have access to, no which
> they would like GRASS migrate to. Personally, I would answer differently to
> each of these questions. I have an account on G
Hi,
On Wed, Mar 6, 2019 at 11:41 AM Stefan Blumentrath
wrote:
> Two minor non-PSC comment on RFC 6, which generally looks very good to me:
>
> 1) One thing I probably would word a bit differently, is the comment on the
> addon repository, that currently says:
> " repository grass-addons
> reposi
Hi,
st 6. 3. 2019 v 14:42 odesílatel Luís Moreira de Sousa
napsal:
> the survey enquired which platforms people currently have access to, no which
> they would like GRASS migrate to.
see question: "What would be your preferred git platform?"
> Personally, I would answer differently to each of
Hi Martin,
the survey enquired which platforms people currently have access to, no which
they would like GRASS migrate to. Personally, I would answer differently to
each of these questions. I have an account on GitHub, but I no longer use it
for personal projects and am trying to move collabora
Hi all, a quick voice as non-core dev,
1. there should be one official GRASS GIS Add-Ons repository
2. there should be a set of minimal requirements to accept requests to
include add-ons in the official repository
3. `g.extension` deserves some love and improvements and it should issue
a Warnin
Hi,
st 6. 3. 2019 v 11:41 odesílatel Stefan Blumentrath
napsal:
> That said, it would be nice if we could try to avoid making a later move away
> from github too painful (no lock in). In other words, lets try (as far as
> possible) to stay away from github-specific features[1] that will be hard
S PSC list
Subject: Re: [GRASS-PSC] git migration
On Tue, Mar 5, 2019 at 8:24 PM Martin Landa wrote:
> Hi,
>
> as you probably know there some attempts to move GRASS source code to
> git, see also related survey
> https://docs.google.com/forms/d/1BoTFyZRNebqVX98A3rh5GpUS2gKFfmui
On Tue, Mar 5, 2019 at 8:24 PM Martin Landa wrote:
> Hi,
>
> as you probably know there some attempts to move GRASS source code to
> git, see also related survey
> https://docs.google.com/forms/d/1BoTFyZRNebqVX98A3rh5GpUS2gKFfmuim78gbradDjc/viewanalytics.
>
> From my POV, GRASS PSC should decide w
34 matches
Mail list logo
