[SAC] Access to GDAL Trac database

[Mateusz Loskot]

Frank,

First, I'd like to clarify the amusing part.

Six people responded so far and here are pro-GitHub counts:

+1   Dmitry, Even, Kurt, Tamas, Mateusz
  0   Daniel (not sure hot to interpret Daniel's voice though)

So, I assumed that those who did not respond are either
indifferent or will agree with any of the three proposed choices.
That is what I called silence == agreement.

Nobody has offered help in migration to any of the two other choices
proposed by Even.
If someone offers help to migrate to OSGeo gig/gogs, and if GDAL team
decides to go for it,
or if anyone from GDAL team asks me specifically to not to work on the
migration,
I'll be happy to fade away.

Even asked for help and, as incurable one who compulsively has to dunk
a hand in something, I thought I may **try** to help.

I don't advocate for GitHub.
I just like to use GitHub for pragmatic reasons.

I do not offer myself to help migrating to OSGeo git/gogs though.


Moving back to the topic:

The dump file will certainly work.
I can import it to local database and use for prototyping
Once the thing works, we can run it based on the original database, I guess.

I assume the attachment files are important part and have to be moved
along the tickets,
so yes, please pack it up all together.

Regards,
Mateusz



On 24 September 2017 at 22:43, Frank Warmerdam <warmerdam at pobox.com> wrote:
> Mateusz,
>
> I see that GDAL's trac is backed by a postgres database instance:
>
> database = postgres://postgres@/trac_gdal
>
> Would it be reasonable for me to prepare a database dump of that?  I'm
> not sure if it is open to direct connects from outside the machine.
>
> I can also tar up the "trac" tree which includes attachment files.
>
> I was amused by:
>
> "Although the feedback is modest so far and any silence means
> agreement, GitHub is the preferred choice now."
>
> While I'm not exactly a fan of GDAL tickets moving to github, I am
> ironically in the position of fighting to use github at my current
> employer (over some internally hosted git thingy) because "developers
> already know github".  So I suppose I can't really be hater. :-)
>
> Best regards,
> Frank
>
> On Sun, Sep 24, 2017 at 1:18 PM, Mateusz Loskot <mateusz at loskot.net> wrote:
>>
>>
>> On 24 Sep 2017 22:07, "Harrison Grundy" <harrison.grundy at astrodoggroup.com>
>> wrote:
>>
>> If it would help, I have the workflow we used for GeoServer to move to
>> Atlassian.
>>
>>
>> I don't know much about Atlassian or how it
>> Is different to GitHub, but any ideas that
>> worked for similar to the planned migration
>> may be useful.
>>
>> So please share.
>>
>> Thanks,
>> Mateusz
>>
>> _______________________________________________
>> Sac mailing list
>> Sac at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/sac
>
>
>
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
> light and sound - activate the windows |
> and watch the world go round - Rush    | Geospatial Software Developer
> _______________________________________________
> Sac mailing list
> Sac at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/sac



-- 
Mateusz Loskot, http://mateusz.loskot.net