On 15/12/18 17:28, Markus Neteler wrote:
On Mon, Jun 4, 2018 at 11:00 PM Markus Neteler wrote:
On Mon, Jun 4, 2018 at 10:50 PM, Martin Landa wrote:
[...]
Migration to *git* is planned in any
case :-) A host platform is not decided yet.
We simply need to decide between own hosting (incl.
Hi,
so 29. 12. 2018 v 3:05 odesílatel Martin Landa napsal:
> and tags.
>
> $ git tag
a little issue found: all tags has been marked with same date [1]. I
will fix it ASAP. Ma
[1] http://geo102.fsv.cvut.cz:8090/grass/grass/tags
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
Hi,
so 15. 12. 2018 v 17:29 odesílatel Markus Neteler napsal:
> ... a friendly ping...
>
> What are the remaining open problems with
> https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git
based on migrate.sh [0] I have created testing a git repo running
local gitlab instance at [1].
On Mon, Jun 4, 2018 at 11:00 PM Markus Neteler wrote:
> On Mon, Jun 4, 2018 at 10:50 PM, Martin Landa wrote:
> [...]
> > Migration to *git* is planned in any
> > case :-) A host platform is not decided yet.
>
> We simply need to decide between own hosting (incl. git repo by OSGeo)
> and
On Thu, Jun 14, 2018 at 6:44 PM, Markus Neteler wrote:
> Luca Delucchi schrieb am Do., 14. Juni 2018, 01:16:
>>
>> On 13 June 2018 at 22:07, Markus Neteler wrote:
>> >
>> > As I said: the OSGeo git services are IMHO under-staffed and would
>> > require a dedicated budget. Could be a nice idea
Luca Delucchi schrieb am Do., 14. Juni 2018, 01:16:
> On 13 June 2018 at 22:07, Markus Neteler wrote:
> >
> > As I said: the OSGeo git services are IMHO under-staffed and would
> > require a dedicated budget. Could be a nice idea but the board needs
> > to support that.
> >
>
> I don't think
On Wed, Jun 13, 2018 at 7:16 PM, Luca Delucchi wrote:
> On 13 June 2018 at 22:07, Markus Neteler wrote:
> >
> > As I said: the OSGeo git services are IMHO under-staffed and would
> > require a dedicated budget. Could be a nice idea but the board needs
> > to support that.
> >
>
> I don't think
On 13 June 2018 at 22:07, Markus Neteler wrote:
>
> As I said: the OSGeo git services are IMHO under-staffed and would
> require a dedicated budget. Could be a nice idea but the board needs
> to support that.
>
I don't think so, git on OSGeo server is working [0], and the board
also use it [1].
On Wed, Jun 13, 2018 at 12:21 PM, Luca Delucchi wrote:
> Il mer 13 giu 2018, 04:13 Vaclav Petras ha scritto:
>>
>> > gitea, gitlab is not working for me
>>
>> Luca, I think you need to be more specific.
>
> I was speaking about the gitlab instance on OSGeo server [0], it is not
> working for
Il mer 13 giu 2018, 04:13 Vaclav Petras ha scritto:
>
> > gitea, gitlab is not working for me
>
>
> Luca, I think you need to be more specific.
>
I was speaking about the gitlab instance on OSGeo server [0], it is not
working for me... Otherwise I like gitlab it self and I'm already using it.
On Tue, Jun 12, 2018 at 5:19 PM, Luca Delucchi wrote:
>
> On 6 June 2018 at 07:23, Markus Neteler wrote:
> >
> > Which of the two? Gitea or gitlab?
> >
>
> gitea, gitlab is not working for me
Luca, I think you need to be more specific.
...and this discussion should probably go to new thread.
On 6 June 2018 at 07:23, Markus Neteler wrote:
>
> Which of the two? Gitea or gitlab?
>
gitea, gitlab is not working for me
> Will they be stable and maintained installations with backup strategy for
> the years to come?
>
I think like svn and trac. However the backup for the git repository
is
Hi,
2018-06-06 0:26 GMT+02:00 Luca Delucchi :
>> Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?
>
> This is my favourite choice
in this case we can always do GitHub/Gitlab mirrors for PRs. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
Luca Delucchi schrieb am Mi., 6. Juni 2018, 00:26:
> On 5 June 2018 at 01:21, Huidae Cho wrote:
> > Yeah, that acquisition is bad news. Why can we just not use the OSGeo
> one?
>
> This is my favourite choice
>
Which of the two? Gitea or gitlab?
Will they be stable and maintained
On 5 June 2018 at 01:21, Huidae Cho wrote:
> Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?
This is my favourite choice
> Just curious.
>
> Huidae
>
--
ciao
Luca
www.lucadelu.org
___
grass-dev mailing list
On Tue, Jun 5, 2018 at 1:21 AM, Huidae Cho wrote:
> Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?
> Just curious.
... of course that's open to be discussed.
So far/at time there is more or less a single person behind it to
maintain that repo. At least for me too
Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?
Just curious.
Huidae
On Mon, Jun 4, 2018 at 5:00 PM, Markus Neteler wrote:
> On Mon, Jun 4, 2018 at 10:50 PM, Martin Landa
> wrote:
> [...]
> > Migration to *git* is planned in any
> > case :-) A host platform is not
On Mon, Jun 4, 2018 at 10:50 PM, Martin Landa wrote:
[...]
> Migration to *git* is planned in any
> case :-) A host platform is not decided yet.
We simply need to decide between own hosting (incl. git repo by OSGeo)
and effectively commercial providers (github, gitlab, bitbucket, ...).
As long
Hi,
2018-06-04 22:47 GMT+02:00 Martin Landa :
> btw, there is a new fact which makes migration to git less convenient [1].
sorry, I meant GitHub not git! Migration to *git* is planned in any
case :-) A host platform is not decided yet.
Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
Hi,
2018-04-12 22:58 GMT+02:00 Huidae Cho :
btw, there is a new fact which makes migration to git less convenient [1].
Ma
[1]
https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
Great! Thanks, Markus!
--
Huidae Cho, Ph.D., P.E., M.ASCE, CFM, GISP
Sent from my phone
On Thu, Apr 12, 2018, 4:51 PM Markus Neteler wrote:
> Huidae,
>
> On Wed, Mar 28, 2018 at 2:57 PM, Huidae Cho wrote:
> > Markus,
> >
> > You can add me:
Huidae,
On Wed, Mar 28, 2018 at 2:57 PM, Huidae Cho wrote:
> Markus,
>
> You can add me: https://github.com/HuidaeCho
Happily done. Sorry for the delay due to travelling and inbox overflow :)
Markus
> On Mon, Mar 19, 2018 at 10:48 AM, Markus Neteler
Markus,
You can add me: https://github.com/HuidaeCho
Thanks.
Huidae
On Mon, Mar 19, 2018 at 10:48 AM, Markus Neteler wrote:
> On Mon, Mar 19, 2018 at 11:01 AM, Pietro wrote:
> > On Sat, Mar 17, 2018 at 6:27 PM, Markus Neteler
>
On Mon, Mar 19, 2018 at 11:01 AM, Pietro wrote:
> On Sat, Mar 17, 2018 at 6:27 PM, Markus Neteler wrote:
>>
>> Hi,
>>
>> as per
>>
>> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>>
>> I have created a "GRASS GIS dev"
Dear Markus,
On Sat, Mar 17, 2018 at 6:27 PM, Markus Neteler wrote:
> Hi,
>
> as per
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_
> Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
On Sat, Mar 17, 2018 at 6:27 PM, Markus Neteler wrote:
>
> Hi,
>
> as per
>
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
> ... who
Hi,
Il giorno sab 17 mar 2018 alle 18:27 Markus Neteler ha
scritto:
> Hi,
>
> as per
>
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
Hi,
2018-03-18 10:37 GMT+01:00 Luca Delucchi :
> why also in github? We already did in OSGeo infrastructure
> https://git.osgeo.org/gitea/grass_gis
there is misunderstanding. It was not decided yet that main git repo
will be hosted by GitHub. Markus just created GRASS GIS
On 17 March 2018 at 18:27, Markus Neteler wrote:
> Hi,
>
Hi,
> as per
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
why also in
Le Sat, 17 Mar 2018 18:27:25 +0100,
Markus Neteler a écrit :
> Hi,
>
> as per
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
> ...
* Nikos Alexandris [2018-03-17 20:14:16 +]:
If this is open for non-core devs, I'd love to join. If it is, I can still fork
and submit merge requests.
Sorry, second sentence: if it is not open to non-core dev community
members, I can still submit merge requests
If this is open for non-core devs, I'd love to join. If it is, I can still fork
and submit merge requests.
Things will be so much easier!
Hard work will be to unmess complicated multiple stuff to-merge situations.
Nikos
Le Samedi 17 mars 2018, Markus Neteler a écrit :
> On Sat, Mar 17, 2018
On Sat, Mar 17, 2018 at 7:04 PM, Helmut Kudrnovsky wrote:
> Markus Neteler wrote
>> Hi,
>>
>> as per
>> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>>
>> I have created a "GRASS GIS dev" team here:
>>
Markus Neteler wrote
> Hi,
>
> as per
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Move_to_Git
>
> I have created a "GRASS GIS dev" team here:
> https://github.com/orgs/OSGeo/teams/grass-gis/members
>
> ... who wants to join, please speak up (and send your account
34 matches
Mail list logo