Dear all,
Please be careful of the exact wording of the motion:
I did not propose a move away from Trac, just a separation of Trac
instances/accounts from SAC.
In case most of us want to move to another system (Gitlab, Gogs, Github
etc), please raise a new motion to move to a new system instead
+1
I find the trac system confusing as well.
I agree with Cameron that we should make sure being able to exit the
"new" track system again (if needed in future).
Jakob
On 13.10.2017 09:42, Nicolas Roelandt wrote:
Hi all,
The actual trac system is confusing so +1 to move.
I join Astrid abo
Hi all,
The actual trac system is confusing so +1 to move.
I join Astrid about gog, since there is already an OSGeo-Lire repo there
and the platform is administrated OSGeo (presumably SAC).
And there is an issue system like github/gitlab [1]
My main concern is more about public access. Almost al
Hello,
+1 from me too.
I would suggest to move the tickets to a place like
https://git.osgeo.org/gogs/...
or
https://github.com/OSGeo/OSGeoLive
Astrid
Am 2017-10-12 22:43, schrieb Angelos Tzotsos:
Hi all,
Just attended a SAC meeting, and an old issue was brought up: our
issue tracker is i
On 10/12/2017 10:43 PM, Angelos Tzotsos wrote:
> Just attended a SAC meeting, and an old issue was brought up: our issue
> tracker is in OSGeo general instance, mixed with tickets from SAC and
> others.
> I would like to make a motion to move our tickets to another trac instance.
+1, the OSGeo-Liv
+1
On Thu, Oct 12, 2017 at 4:37 PM, Cameron Shorter
wrote:
> +0. I'm tentitively in favour of migrating to a better track system, but
> would fist like to be comfortable with:
>
> * What new tracker will we use and will it integrate with our current
> workflow?
>
> * Can we migrate old issues?
+0. I'm tentitively in favour of migrating to a better track system, but
would fist like to be comfortable with:
* What new tracker will we use and will it integrate with our current
workflow?
* Can we migrate old issues?
* Can we exit from the new system if we need to (as per Ben's comments
On vendredi 13 octobre 2017 10:02:29 CEST Ben Caradoc-Davies wrote:
> We control our trac instances. Even before comparing features, is there
> any mechanism for migrating issues from GitHub to another system should
> we need to do so? I am still smarting from the Codehaus shutdown and its
> impact
We control our trac instances. Even before comparing features, is there
any mechanism for migrating issues from GitHub to another system should
we need to do so? I am still smarting from the Codehaus shutdown and its
impact on GeoTools and GeoServer.
Kind regards,
Ben.
On 13/10/17 09:48, Joha
+1.
Kind regards,
Ben.
On 13/10/17 09:43, Angelos Tzotsos wrote:
Hi all,
Just attended a SAC meeting, and an old issue was brought up: our issue
tracker is in OSGeo general instance, mixed with tickets from SAC and
others.
I would like to make a motion to move our tickets to another trac in
I think we should really consider using a system integrated with our
version control, so gitlab or github issues.
If we don't reach consensus over that +1 on moving to a different trac
instance, it makes no sense to have the issues mixed.
On Thu, Oct 12, 2017 at 10:43 PM, Angelos Tzotsos
wrote:
11 matches
Mail list logo