PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2
Here is my understanding of situation

Everyone wants GIT of some sort (Sandro, Mateusz, Dan Baston etc.)
Most people want Github (Mateusz, Paul Ramsey, Dan Baston etc.)
Some people want Github as the official repo to simplify the process
(Mateusz and Paul Ramsey)

We've already got postgis website, buidbot repo on OSGeo git.

I want my tickets and comments preserved cause I still remember the mess
getting off of google code.

I like svn more than git just cause git provides me nothing of value I can
appreciate at the moment, but I'm willing to let go of that in spirit of
doing what's best for all.

Github has a community so we'll always need at least a mirror there.

Having github as anything but a mirror seems pretty pointless (aside from
Gitea upkeep) to me unless the tickets are there as well which brings up the
question of how to push our existing tickets there,
How to export our tickets and comments should github decide to become evil
or we just want to get off for some other reason.

Some staunch Free Software advocates - Sandro, Sebastien, Linus, and I think
a lot of PostgreSQL devs don't like their primary source control being a
proprietary thing.
I feel somewhat in that camp but feel it might be an illogical / emotional
gut feeling drive thing that I might need to learn to let go.

That said my vote is for:

Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

Reason being is if for some reason Gitea doesn't work out, I think it's far
easier to move from Gitea to GitHub
It also means tickets don't need moving (though having the seamless patch
view would be gone and I'd have to settle for a link to a git pull).
Until we get tracgit working.

It also means I don't have to worry about exporting tickets and comments out
of github should something go wrong with github or we decide github is no
longer the solution for us.

If we decide to change, I was thinking we can do it after PostGIS 2.4
release and start with PostGIS 2.5.

Other people feel free to chime in with your thoughts.


Thanks,
Regina






_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Paul Ramsey-3
The practical aspects of "going where the people are" leads me to advocate for going all over to github. Code, tickets, etc. Mapserver managed to go there with all their history, so there's prior art and folks we can talk to about it. 


P.


On Tue, Aug 8, 2017 at 1:56 PM, Regina Obe <[hidden email]> wrote:
Here is my understanding of situation

Everyone wants GIT of some sort (Sandro, Mateusz, Dan Baston etc.)
Most people want Github (Mateusz, Paul Ramsey, Dan Baston etc.)
Some people want Github as the official repo to simplify the process
(Mateusz and Paul Ramsey)

We've already got postgis website, buidbot repo on OSGeo git.

I want my tickets and comments preserved cause I still remember the mess
getting off of google code.

I like svn more than git just cause git provides me nothing of value I can
appreciate at the moment, but I'm willing to let go of that in spirit of
doing what's best for all.

Github has a community so we'll always need at least a mirror there.

Having github as anything but a mirror seems pretty pointless (aside from
Gitea upkeep) to me unless the tickets are there as well which brings up the
question of how to push our existing tickets there,
How to export our tickets and comments should github decide to become evil
or we just want to get off for some other reason.

Some staunch Free Software advocates - Sandro, Sebastien, Linus, and I think
a lot of PostgreSQL devs don't like their primary source control being a
proprietary thing.
I feel somewhat in that camp but feel it might be an illogical / emotional
gut feeling drive thing that I might need to learn to let go.

That said my vote is for:

Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

Reason being is if for some reason Gitea doesn't work out, I think it's far
easier to move from Gitea to GitHub
It also means tickets don't need moving (though having the seamless patch
view would be gone and I'd have to settle for a link to a git pull).
Until we get tracgit working.

It also means I don't have to worry about exporting tickets and comments out
of github should something go wrong with github or we decide github is no
longer the solution for us.

If we decide to change, I was thinking we can do it after PostGIS 2.4
release and start with PostGIS 2.5.

Other people feel free to chime in with your thoughts.


Thanks,
Regina






_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Sandro Santilli-3
In reply to this post by Regina Obe-2
On Tue, Aug 08, 2017 at 04:56:47PM -0400, Regina Obe wrote:

> That said my vote is for:
>
> Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

This motion is a bit confusing, but assuming it is about
moving the code repository from OSGeo/SVN to OSGeo/GIT my
vote is a +1

> It also means tickets don't need moving (though having the seamless patch
> view would be gone and I'd have to settle for a link to a git pull).
> Until we get tracgit working.

I don't understand this statement: "patch view would be gone".
If we keep using trac for tickets why would you loose "patch view" ?

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Paul Ramsey-3
In reply to this post by Paul Ramsey-3
The mapserver github migration seems to have also retained "patch view" which I assume Regina means the r999 notation links to diffs.




On Tue, Aug 8, 2017 at 2:07 PM, Paul Ramsey <[hidden email]> wrote:
The practical aspects of "going where the people are" leads me to advocate for going all over to github. Code, tickets, etc. Mapserver managed to go there with all their history, so there's prior art and folks we can talk to about it. 


P.


On Tue, Aug 8, 2017 at 1:56 PM, Regina Obe <[hidden email]> wrote:
Here is my understanding of situation

Everyone wants GIT of some sort (Sandro, Mateusz, Dan Baston etc.)
Most people want Github (Mateusz, Paul Ramsey, Dan Baston etc.)
Some people want Github as the official repo to simplify the process
(Mateusz and Paul Ramsey)

We've already got postgis website, buidbot repo on OSGeo git.

I want my tickets and comments preserved cause I still remember the mess
getting off of google code.

I like svn more than git just cause git provides me nothing of value I can
appreciate at the moment, but I'm willing to let go of that in spirit of
doing what's best for all.

Github has a community so we'll always need at least a mirror there.

Having github as anything but a mirror seems pretty pointless (aside from
Gitea upkeep) to me unless the tickets are there as well which brings up the
question of how to push our existing tickets there,
How to export our tickets and comments should github decide to become evil
or we just want to get off for some other reason.

Some staunch Free Software advocates - Sandro, Sebastien, Linus, and I think
a lot of PostgreSQL devs don't like their primary source control being a
proprietary thing.
I feel somewhat in that camp but feel it might be an illogical / emotional
gut feeling drive thing that I might need to learn to let go.

That said my vote is for:

Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

Reason being is if for some reason Gitea doesn't work out, I think it's far
easier to move from Gitea to GitHub
It also means tickets don't need moving (though having the seamless patch
view would be gone and I'd have to settle for a link to a git pull).
Until we get tracgit working.

It also means I don't have to worry about exporting tickets and comments out
of github should something go wrong with github or we decide github is no
longer the solution for us.

If we decide to change, I was thinking we can do it after PostGIS 2.4
release and start with PostGIS 2.5.

Other people feel free to chime in with your thoughts.


Thanks,
Regina






_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel



_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2
In reply to this post by Sandro Santilli-3

But OSGEo trac is on postgresql now J

I'm sure if I am given a postgresql backup I can figure out how to get data out of it much easier than using a github api J

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 5:40 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

Getting issues out of github is pretty straightforward, particularly compared to trac, 

 

 

 

 

P.

 

On Tue, Aug 8, 2017 at 2:34 PM, Regina Obe <[hidden email]> wrote:

Because there is no point of moving to github unless we move the whole thing that means trac too.
The main benefit of moving to GitHub would be lower maintenance which means getting rid of trac and any need for any other git mirror.

To Paul's point I'm more concerned about getting out of github than getting into it.
Though would be interesting to know how much effort they put into the migration of all their tickets to github.

Maintaining an OSGeo git and trac does take some maintenance.
 Is it worth keeping or not is the question in my mind absence of any emotional argument.

I would say probably still, but strk you are the one doing most of the work keeping things running so I don't know.





-----Original Message-----
From: postgis-devel [mailto:[hidden email]] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 5:13 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

On Tue, Aug 08, 2017 at 04:56:47PM -0400, Regina Obe wrote:

> That said my vote is for:
>
> Gitea (OSGeo Git) / OSGeo Trac / mirror GitHub - ditch SVN

This motion is a bit confusing, but assuming it is about moving the code repository from OSGeo/SVN to OSGeo/GIT my vote is a +1

> It also means tickets don't need moving (though having the seamless
> patch view would be gone and I'd have to settle for a link to a git pull).
> Until we get tracgit working.

I don't understand this statement: "patch view would be gone".
If we keep using trac for tickets why would you loose "patch view" ?

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2

I think you are overrating the discomfort of having to handle pull requests from github (as a mirror vs. being our official) if everything isn't there and forgetting that you are forcing people who don't have github accounts to create one.

 

There are 3 kinds of contributors I think are important

 

1)      End users reporting bugs – many of these don't have github accounts so forcing them to create an osgeo instead of github sounds better. You can argue creating a github account is easier these days.

2)      Developers who are on github – we take pull requests from them whether I do it from github/gogs/svn doesn't matter to me.  The conversation if changes need to be made is better on github or gogs.

To me after it's committed that's all noise I don't really need in final commit or on ticket.

 

If a dev becomes a serious contributor e.g. Dan Baston or Björn Harrtell then I'd really like them to have an OSGeo account.

From what I presume from both, they just want to work with a git repo and less sensitive to where the official is.

Sandro is already struggling with svn so I know he prefers git.

 

So my reason for wanting the git move is to make it easier for those with commit access already and future.

 

3)      Developers/users who don't have a github account or don't like committing to github for political reasons.  We lose all these people if they are forced to create a github accounts before they can exchange with us.

 

So I'm still +1 for GIT OSGeo and okay with tickets moving from trac to gogs.

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 7:46 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

The point isn't features, it's developer density. I don't see any great advantage to gogs if we still have PRs and work managing the github mirror. Might as well continue on w/ trac/svn, since gogs shares the main drawback; forcing folks to get new accounts / logins before they can start engaging.

 

I'm sure gogs is technically wunderbar, but it's not where the persons are.


P.

 

On Tue, Aug 8, 2017 at 4:38 PM, Regina Obe <[hidden email]> wrote:

Nice.

1) So gogs with the pull and the lazy editing feature (I can edit via the web interface which I have done) has everything github has and appeases my emotional side too
2) appeases my need to be able to know I can access via SQLif I really really wanted to which I got from this:
https://git.osgeo.org/gogs/postgis/postgis/pulls/9#issuecomment-3040

 :)

3) I'm okay with trac eventually moving to gogs.  It would be sweet if we change the r... to the actual git hash.  That seems like a simple r.. map to git hash UPDATE  statement if we have a table that maps svn revision numbers to git which I assume we might be able to generate via the mirror.

That's a minor thing for me though.

Thanks,
Regina




-----Original Message-----
From: postgis-devel [mailto:[hidden email]] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 6:34 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

On Tue, Aug 08, 2017 at 06:22:35PM -0400, Regina Obe wrote:
> But OSGEo trac is on postgresql now :) I'm sure if I am given a
> postgresql backup I can figure out how to get data out of it much
> easier than using a github api :)

An XSLT recipe ? :P

I'm speaking as the one who made `Trac -> Gogs` tool based on PostgreSQL queries.
See example results: https://git.osgeo.org/gogs/strk/geos-migration-test/issues
Code: http://strk.kbt.io/projects/go/trac2gogs/

--strk;

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Paul Ramsey-3
On Tue, Aug 8, 2017 at 5:38 PM, Regina Obe <[hidden email]> wrote:

I think you are overrating the discomfort of having to handle pull requests from github (as a mirror vs. being our official) if everything isn't there and forgetting that you are forcing people who don't have github accounts to create one.

 

There are 3 kinds of contributors I think are important

 

1)      End users reporting bugs – many of these don't have github accounts so forcing them to create an osgeo instead of github sounds better. You can argue creating a github account is easier these days.

Yes, I can.
 

2)      Developers who are on github – we take pull requests from them whether I do it from github/gogs/svn doesn't matter to me.  The conversation if changes need to be made is better on github or gogs.

This is almost all of them.

3)      Developers/users who don't have a github account or don't like committing to github for political reasons.  We lose all these people if they are forced to create a github accounts before they can exchange with us.


Who? Even this guy <https://github.com/strk> has a github account and it's active.



P.



 

So I'm still +1 for GIT OSGeo and okay with tickets moving from trac to gogs.

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 7:46 PM


To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

The point isn't features, it's developer density. I don't see any great advantage to gogs if we still have PRs and work managing the github mirror. Might as well continue on w/ trac/svn, since gogs shares the main drawback; forcing folks to get new accounts / logins before they can start engaging.

 

I'm sure gogs is technically wunderbar, but it's not where the persons are.


P.

 

On Tue, Aug 8, 2017 at 4:38 PM, Regina Obe <[hidden email]> wrote:

Nice.

1) So gogs with the pull and the lazy editing feature (I can edit via the web interface which I have done) has everything github has and appeases my emotional side too
2) appeases my need to be able to know I can access via SQLif I really really wanted to which I got from this:
https://git.osgeo.org/gogs/postgis/postgis/pulls/9#issuecomment-3040

 :)

3) I'm okay with trac eventually moving to gogs.  It would be sweet if we change the r... to the actual git hash.  That seems like a simple r.. map to git hash UPDATE  statement if we have a table that maps svn revision numbers to git which I assume we might be able to generate via the mirror.

That's a minor thing for me though.

Thanks,
Regina




-----Original Message-----
From: postgis-devel [mailto:[hidden email]] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 6:34 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

On Tue, Aug 08, 2017 at 06:22:35PM -0400, Regina Obe wrote:
> But OSGEo trac is on postgresql now :) I'm sure if I am given a
> postgresql backup I can figure out how to get data out of it much
> easier than using a github api :)

An XSLT recipe ? :P

I'm speaking as the one who made `Trac -> Gogs` tool based on PostgreSQL queries.
See example results: https://git.osgeo.org/gogs/strk/geos-migration-test/issues
Code: http://strk.kbt.io/projects/go/trac2gogs/

--strk;

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Mateusz Loskot
In reply to this post by Paul Ramsey-3
On 8 August 2017 at 23:07, Paul Ramsey <[hidden email]> wrote:
> The practical aspects of "going where the people are" leads me to advocate
> for going all over to github. Code, tickets, etc.

I second Paul's vote,

Although, I'm just an ad-hoc contributor, so I don't aim to interfere
with PSC decision.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Mateusz Loskot
In reply to this post by Regina Obe-2
On 9 August 2017 at 01:46, Paul Ramsey <[hidden email]> wrote:
> The point isn't features, it's developer density.

Indeed.

> I'm sure gogs is technically wunderbar...

feature-wise, it's long development months behind GitHub.
It's worth to be aware, before getting too excited about gogs/gitea thing.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2
In reply to this post by Mateusz Loskot

> On 8 August 2017 at 23:07, Paul Ramsey <[hidden email]> wrote:
>> The practical aspects of "going where the people are" leads me to
>>  advocate for going all over to github. Code, tickets, etc.

> I second Paul's vote,

Paul has not voted.  He has advocated.  Advocation is NOT a vote.  
It's a way of saying I'm encouraging other people to move in the direction I feel is right. :)  

He has to say +1, -1, 0 for it to be considered a vote.

I suspect Sandro is conveniently not voting either.

> Although, I'm just an ad-hoc contributor, so I don't aim to interfere with PSC decision.

> Best regards,
--
> Mateusz Loskot

Mat,

If you had a choice between doing noting (e.g. keep svn, trac)

Or moving to

Gogs (git.osgeo.org, gogs ticket system)

Which would you choose?

I would choose the second, because even if git.osgeo.org isn't stable it's more trivial to go to github.
Nothing lost - we get to experiment, developers get to use git instead of svn while we do so.
We've already started the experiment.


Thanks,
Regina


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Daniel Baston
In reply to this post by Regina Obe-2
End users reporting bugs – many of these don't have github accounts so forcing them to create an osgeo instead of github sounds better. You can argue creating a github account is easier these days.

I'm not sure about this.  Remember that the OSGeo account creation process, if you can find it, requires that you send an email or go on IRC and explain why you need to have an account, the null hypothesis being that you want to spam people or perform other mischief**.  If you decide to write a request, you may hear back after a few days, or it may fall through the cracks.  Meanwhile, you have moved on to other work and the information you wanted to paste into the ticket is no longer in front of you.  This is a pretty unwelcoming system, and one that I suspect most people never bother to deal with.

If GitHub is not an option, I'd prefer to stick with SVN and Trac.  At least they're stable, and the pull request process doesn't have do diverge into troubleshooting the hosting platform.

Dan

**Interestingly, when writing this request, users are advised to provide a link to a public profile such as GitHub to verify their identity.

On Tue, Aug 8, 2017 at 8:38 PM, Regina Obe <[hidden email]> wrote:

I think you are overrating the discomfort of having to handle pull requests from github (as a mirror vs. being our official) if everything isn't there and forgetting that you are forcing people who don't have github accounts to create one.

 

There are 3 kinds of contributors I think are important

 

1)      End users reporting bugs – many of these don't have github accounts so forcing them to create an osgeo instead of github sounds better. You can argue creating a github account is easier these days.

2)      Developers who are on github – we take pull requests from them whether I do it from github/gogs/svn doesn't matter to me.  The conversation if changes need to be made is better on github or gogs.

To me after it's committed that's all noise I don't really need in final commit or on ticket.

 

If a dev becomes a serious contributor e.g. Dan Baston or Björn Harrtell then I'd really like them to have an OSGeo account.

From what I presume from both, they just want to work with a git repo and less sensitive to where the official is.

Sandro is already struggling with svn so I know he prefers git.

 

So my reason for wanting the git move is to make it easier for those with commit access already and future.

 

3)      Developers/users who don't have a github account or don't like committing to github for political reasons.  We lose all these people if they are forced to create a github accounts before they can exchange with us.

 

So I'm still +1 for GIT OSGeo and okay with tickets moving from trac to gogs.

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Paul Ramsey
Sent: Tuesday, August 08, 2017 7:46 PM


To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

The point isn't features, it's developer density. I don't see any great advantage to gogs if we still have PRs and work managing the github mirror. Might as well continue on w/ trac/svn, since gogs shares the main drawback; forcing folks to get new accounts / logins before they can start engaging.

 

I'm sure gogs is technically wunderbar, but it's not where the persons are.


P.

 

On Tue, Aug 8, 2017 at 4:38 PM, Regina Obe <[hidden email]> wrote:

Nice.

1) So gogs with the pull and the lazy editing feature (I can edit via the web interface which I have done) has everything github has and appeases my emotional side too
2) appeases my need to be able to know I can access via SQLif I really really wanted to which I got from this:
https://git.osgeo.org/gogs/postgis/postgis/pulls/9#issuecomment-3040

 :)

3) I'm okay with trac eventually moving to gogs.  It would be sweet if we change the r... to the actual git hash.  That seems like a simple r.. map to git hash UPDATE  statement if we have a table that maps svn revision numbers to git which I assume we might be able to generate via the mirror.

That's a minor thing for me though.

Thanks,
Regina




-----Original Message-----
From: postgis-devel [mailto:[hidden email]] On Behalf Of Sandro Santilli
Sent: Tuesday, August 08, 2017 6:34 PM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

On Tue, Aug 08, 2017 at 06:22:35PM -0400, Regina Obe wrote:
> But OSGEo trac is on postgresql now :) I'm sure if I am given a
> postgresql backup I can figure out how to get data out of it much
> easier than using a github api :)

An XSLT recipe ? :P

I'm speaking as the one who made `Trac -> Gogs` tool based on PostgreSQL queries.
See example results: https://git.osgeo.org/gogs/strk/geos-migration-test/issues
Code: http://strk.kbt.io/projects/go/trac2gogs/

--strk;

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Darafei "Komяpa" Praliaskouski
In reply to this post by Regina Obe-2
I'm not that frequent PostGIS contributor or a maintainer.

Most time I'm interacting with its code is when something is not covered in docs (like O() of the functions to get idea of how long the query will be running, or details of estimator, etc.).
I just read it on Github repo, as search and code highlighting are good enough there.
Sometimes I see a logical error and fix it right away in the github web editor, making a PR and looking at tests passing or not.

I think process of moving from git to svn let half of our parallel aggregates patch fall through the cracks, and I'm not even sure if it's completely there, as it's not a "merged PR", but a diff applied by maintainer. I also had issues creating OSGeo account, so a couple of tickets were created on trac by my IRC reports by other good people.

Github as a main home for postgis would be much easier for me, as postgis is not the only piece of software I'm looking into.

ср, 9 авг. 2017 г. в 16:10, Regina Obe <[hidden email]>:

> On 8 August 2017 at 23:07, Paul Ramsey <[hidden email]> wrote:
>> The practical aspects of "going where the people are" leads me to
>>  advocate for going all over to github. Code, tickets, etc.

> I second Paul's vote,

Paul has not voted.  He has advocated.  Advocation is NOT a vote.
It's a way of saying I'm encouraging other people to move in the direction I feel is right. :)

He has to say +1, -1, 0 for it to be considered a vote.

I suspect Sandro is conveniently not voting either.

> Although, I'm just an ad-hoc contributor, so I don't aim to interfere with PSC decision.

> Best regards,
--
> Mateusz Loskot

Mat,

If you had a choice between doing noting (e.g. keep svn, trac)

Or moving to

Gogs (git.osgeo.org, gogs ticket system)

Which would you choose?

I would choose the second, because even if git.osgeo.org isn't stable it's more trivial to go to github.
Nothing lost - we get to experiment, developers get to use git instead of svn while we do so.
We've already started the experiment.


Thanks,
Regina


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2

Darafei,

 

I think the issues you faced wouldn't matter if we were on github, gogs, or svn and we'll still have at the very least a Github mirror for the very reasons you mentioned.

 

The reason half your PR for parallelization did not go thru is because I intentionally deleted them.  I did not want them in 2.3 and wanted to think about them for 2.4.

So that has nothing to do with github/svn

 

The travis issue with not being able to test was because our travis was broken.  I think regardless which we choose, our laziness about fixing bots is not going to change.

 

The other patch about the points index optimizations that was then again me deliberating.  There is  some stuff there I have not committed and some I might revert because I wanted to do more tests on real data and some tests I did I did not see much of an improvement and in some cases slower.

 

So as far as your commits it shouldn't matter whether github, git whatever.  I’d still want to study and cut things out I don't think should be in there.

 

Thanks,

Regina

 

 

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Darafei "Kom?pa" Praliaskouski
Sent: Wednesday, August 09, 2017 9:25 AM
To: PostGIS Development Discussion <[hidden email]>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

I'm not that frequent PostGIS contributor or a maintainer.


Most time I'm interacting with its code is when something is not covered in docs (like O() of the functions to get idea of how long the query will be running, or details of estimator, etc.).
I just read it on Github repo, as search and code highlighting are good enough there.
Sometimes I see a logical error and fix it right away in the github web editor, making a PR and looking at tests passing or not.

I think process of moving from git to svn let half of our parallel aggregates patch fall through the cracks, and I'm not even sure if it's completely there, as it's not a "merged PR", but a diff applied by maintainer. I also had issues creating OSGeo account, so a couple of tickets were created on trac by my IRC reports by other good people.

Github as a main home for postgis would be much easier for me, as postgis is not the only piece of software I'm looking into.

 

ср, 9 авг. 2017 г. в 16:10, Regina Obe <[hidden email]>:


> On 8 August 2017 at 23:07, Paul Ramsey <[hidden email]> wrote:
>> The practical aspects of "going where the people are" leads me to
>>  advocate for going all over to github. Code, tickets, etc.

> I second Paul's vote,

Paul has not voted.  He has advocated.  Advocation is NOT a vote.
It's a way of saying I'm encouraging other people to move in the direction I feel is right. :)

He has to say +1, -1, 0 for it to be considered a vote.

I suspect Sandro is conveniently not voting either.

> Although, I'm just an ad-hoc contributor, so I don't aim to interfere with PSC decision.

> Best regards,
--
> Mateusz Loskot

Mat,

If you had a choice between doing noting (e.g. keep svn, trac)

Or moving to

Gogs (git.osgeo.org, gogs ticket system)

Which would you choose?

I would choose the second, because even if git.osgeo.org isn't stable it's more trivial to go to github.
Nothing lost - we get to experiment, developers get to use git instead of svn while we do so.
We've already started the experiment.


Thanks,
Regina


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Even Rouault-2
In reply to this post by Regina Obe-2

On mardi 8 août 2017 14:39:44 CEST Paul Ramsey wrote:

> Getting issues out of github is pretty straightforward, particularly

> compared to trac,

>

> https://api.github.com/repos/mapserver/mapserver/issues?page=1&per_page=10

>

>

 

 

Linked to that, I found

https://github.com/josegonzalez/python-github-backup

 

which can backup code, issues, pull requests, etc.. using the github API

 

Quickly tested it on their own repo. Seems to work (although a bit slow: requires 2 GET per issue / pull request to retrieve extra details that are not retrieved by the global request you showed above)

 

Even

 

--

Spatialys - Geospatial professional services

http://www.spatialys.com


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Sandro Santilli-3
In reply to this post by Darafei "Komяpa" Praliaskouski
On Wed, Aug 09, 2017 at 01:24:55PM +0000, Darafei "Komяpa" Praliaskouski wrote:

> I think process of moving from git to svn let half of our parallel
> aggregates patch fall through the cracks

I can apply GitHub pull requests to PostGIS SVN with these
commands (in case others have problems doing it):

 curl -L https://github.com/postgis/postgis/pull/23.patch | git am
 git svn dcommit

No visible cracks from here. Other than keeping track of the need
to apply or not a change, which is currently done using Trac (not GitHub).

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Sandro Santilli-3
In reply to this post by Daniel Baston
On Wed, Aug 09, 2017 at 09:12:27AM -0400, Daniel Baston wrote:

> **Interestingly, when writing this request, users are advised to provide a
> link to a public profile such as GitHub to verify their identity.

Every "mantra whisperer" (do you want to become one?) decides how to
determine trustwortship of requestors.

I personally don't ask for a GitHub account, but do accept anything
that can prove reputation (ie: a just-created github account gives no
credit).

Just a note: Gitea development has recently been targetted by vandals
using GitHub accounts (spam tickets).

Yes, it takes some work to register an OSGeo account.
Can that be of a value in this world of high noise/signal ratio ?

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Regina Obe-2
In reply to this post by Even Rouault-2

Okay sound like it's doable but not trivial.

 

I imagine going to github is also doable but not trivial.

 

So I'm beginning to lean on the side of do nothing since so many people are against switching to just git.

And I see my life harder dealing with github tickets.

 

 

 

From: postgis-devel [mailto:[hidden email]] On Behalf Of Even Rouault
Sent: Wednesday, August 09, 2017 10:19 AM
To: [hidden email]
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

On mardi 8 août 2017 14:39:44 CEST Paul Ramsey wrote:

> Getting issues out of github is pretty straightforward, particularly

> compared to trac,

>

> https://api.github.com/repos/mapserver/mapserver/issues?page=1&per_page=10

>

>

 

 

Linked to that, I found

https://github.com/josegonzalez/python-github-backup

 

which can backup code, issues, pull requests, etc.. using the github API

 

Quickly tested it on their own repo. Seems to work (although a bit slow: requires 2 GET per issue / pull request to retrieve extra details that are not retrieved by the global request you showed above)

 

Even

 

--

Spatialys - Geospatial professional services

http://www.spatialys.com


_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

Angelos Tzotsos
In reply to this post by Sandro Santilli-3


On Wed, Aug 9, 2017 at 6:05 PM, Sandro Santilli <[hidden email]> wrote:
On Wed, Aug 09, 2017 at 09:12:27AM -0400, Daniel Baston wrote:

> **Interestingly, when writing this request, users are advised to provide a
> link to a public profile such as GitHub to verify their identity.

Every "mantra whisperer" (do you want to become one?) decides how to
determine trustwortship of requestors.

I personally don't ask for a GitHub account, but do accept anything
that can prove reputation (ie: a just-created github account gives no
credit).


As a "mantra whisperer" myself I agree with Sandro about this.
 
Angelos

--
Angelos Tzotsos, PhD
OSGeo Charter Member

_______________________________________________
postgis-devel mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/postgis-devel
Loading...