[postgis-devel] repository hosting (was: is PostGIS ready for git ?) NO?

[Paragon Corporation]

One could argue similarly people who put in documentation typo fixes may not want to create a github account just to do so and a lot of those folks aren't necessarily developers.

 

Interesting idea about bot auto-create though I could see that going haywire.  So would only do it if we have a mass number of developers pushing git pulls having issue with putting in trac tickets.

Maybe we can have a survey sometime about that to get a sense of how much contribution we are losing by forcing people to put in trac tickets.

 

Thanks,

Regina

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Daniel Baston
Sent: Monday, October 19, 2015 8:33 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] repository hosting (was: is PostGIS ready for git ?) NO?

 

Setting up Trac tickets for me has been no problem, though I wouldn't want to do it to fix documentation typos.

 

Where I imagine a barrier is for a developer that is among the ~9 million people with GitHub accounts, and who interacts only occasionally with PostGIS as part of their work. These users may not want to register w/OSGeo and figure out Trac just to make a small fix, but they would be quite capable and willing if they didn't have to navigate a somewhat project-specific process.

 

Complete speculation on my part, of course, but a scenario that I hadn't seen didn't see in the discussion so far.

 

An interesting solution, if this is even a problem, may be to have a bot auto-create Trac tickets from GitHub PRs.

 

Thanks,

Dan

 

 

On Fri, Oct 16, 2015 at 5:56 PM, Paragon Corporation <lr at pcorp.us <mailto:lr at pcorp.us> > wrote:

>> On Fri, Oct 16, 2015 at 07:41:38AM -0400, Daniel Baston wrote:
>>  If PostGIS were to accept contributions only through patches posted to
>> Trac, I think it would bring about two barriers to contributions:

> Agreed. But if we want to keep some consistency between commit logs and trac tickets / NEWS items we'd then have the barriers on ourselves, having to create a ticket ourselves.

> Or, we can use a looser protocol and just apply patches straight away, reference revisions in the NEWS and rely on the commit log for getting to the origin of that change... (more likely to happen).

> --strk;

My thinking is that people would put in a ticket in trac about a feature request, and either provide a link to the git/pull where they patched it or the patch itself.
Dan as I recall, I think you've been pretty good about that.  Has it been a big burden?

I'm not so against people having code conversations in github/gitlab or whatever about a patch, as that's all noise anyway when you are trying to figure out what new features we've got going.

In the end we just need a centralized location to query what's new, in queue for new, and what commit it happened in (or patch it is in).

Getting back to Greg's point - related to his point,
A lot of people who report issues are not developers.  They have crash reports and how to reproduce which I think are often more important than new development.
Many of them do not have github accounts. If they are going to have to register as a user in some organization, Selfishly I'd prefer that organization to be OSGEO than github, if nothing more than for marketing :)

Thanks,
Regina



_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
http://lists.osgeo.org/mailman/listinfo/postgis-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20151019/309abd1d/attachment.html>