[GRASS-dev] communication of community sprint decisions

Markus Neteler neteler at osgeo.org
Mon Jan 13 12:00:44 PST 2020


On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras <wenzeslaus at gmail.com> wrote:
> On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler <neteler at osgeo.org> wrote:
>> Hi Prague-2019 sprinters, all,
>>
>> On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras <wenzeslaus at gmail.com> wrote:
>> > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo <veroandreo at gmail.com> wrote:
>> >>
>> >>
>> >> I've been reading the discussion page at: https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 and I see that we should open new bug reports or feature requests directly in GitHub. When does this decision start to take effect?
>> >>
>> >> I think it is important to communicate this broadly to the user community through grass-user list
>> >
>> >
>> > Yes. I wrote it there and what I meant by putting this into "Decisions made" section is that we made that decision, but it won't happen until the steps are done, i.e. until we allow opening issues on GitHub, disallow opening new issues on Trac, and announce this on mailing lists.
>>
>> Shall we go for this? What do you think?
>> I would like to see GH issues enabled now.
>
>
> The plan assumes that Trac allows removing the privilege to create tickets for all users, but leaving tickets editable. Can you please check that?

We could change it to this:

[X] TICKET_VIEW
[  ] TICKET_CREATE
[X] TICKET_MODIFY

> Perhaps even the New Ticket in top menu bar could be replaced by link to GitHub for those used to Trac, but that's a low priority.

That seems to be easy:
https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries

Let's go for it!

Markus


More information about the grass-dev mailing list