[GRASS-dev] First steps to switch the bug tracker

GRASS GIS GRASS GIS developer
1

Hi,

as a follow up of the bug tracker discussions,
I just created a project "GRASS" on our GForge platform:
http://wald.intevation.org/projects/grass/

First, we need someone to be the project manager.
Probably Markus or a steering commitee should decide
who. However, it is good to have two.

The managers and anyone submitting or working on
bug entries should create a user account.

Also, you will currently see quite a number of tabs for
the project (forums, mailing lists, tasks, etc).
Actually, we only need the bug tracker (so far).
All others can be switched off. I will do so unless
you want a specific feature to remain.

Next, there are curently some default trackers configured.
These could be deleted, or additionally be created and of course
configured to some extend.

The managers will have the power to do the configurations (as they
can configure everything).
However, they could also create new roles, e.g. for just Managers
of specific parts. And assign users to roles.

Have fun :slight_smile:

Best

  Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de

2

Hi!

CCing GRASS PSC.

Jan-Oliver Wagner wrote:

as a follow up of the bug tracker discussions,
I just created a project "GRASS" on our GForge platform:
http://wald.intevation.org/projects/grass/

First, we need someone to be the project manager.
Probably Markus or a steering commitee should decide
who. However, it is good to have two.

I volunteer.

The managers and anyone submitting or working on
bug entries should create a user account.

Done. Sent you a request to add me to GRASS project.

Also, you will currently see quite a number of tabs for
the project (forums, mailing lists, tasks, etc).
Actually, we only need the bug tracker (so far).
All others can be switched off. I will do so unless
you want a specific feature to remain.

Next, there are curently some default trackers configured.
These could be deleted, or additionally be created and of course
configured to some extend.

You mean Bugs, Support, Patches, Feature Request? I think we could drop
Support. It will be better to keep all tech-support traffic on
the lists as we used to, so more people would participate in discussion
and more could benefit of it.

I also would prefer to close the Forums and Lists - for the same
reason. We have too little recources to take care of all the eventuall
discussions spreaded here and there.

Regarding Tasks, Docs, Surveys, News and Files there are dedicated
facilities on grass.itc.it and on GRASS WIKI. So I would prefer to
remove them too.

What about the SCM? Is moving to SVN planned? If not, could we close
that as well?

In general, GRASS is missing a good BT. I think we don't need any other
GForge features in the moment.

Opinions?

Regarding the trackers:

@ Oliver:

1. Can I use more than 1 email for "Send email on new submission to
address:"?

2. Is it posible to customize what columns will be displayed in
http://wald.intevation.org/tracker/?atid=167&group_id=21&func=browse
? I'd like to add Version there.

The managers will have the power to do the configurations (as they
can configure everything).
However, they could also create new roles, e.g. for just Managers
of specific parts. And assign users to roles.

I can take care of bugs (in terms of further testing and communication
with the reporter until a reproducable test case is ready for a
developer to jump in). It is necessary to have someone focused on
revising patches submitted though - a programmer with experience in
GRASS. That's not me :). Candidates?

Have fun :slight_smile:

Thanks a tone!

Best,
Maciek

3

On Sun, 8 Oct 2006, Maciej Sieczka wrote:

Hi!

CCing GRASS PSC.

Jan-Oliver Wagner wrote:

as a follow up of the bug tracker discussions,
I just created a project "GRASS" on our GForge platform:
http://wald.intevation.org/projects/grass/

First, we need someone to be the project manager.
Probably Markus or a steering commitee should decide
who. However, it is good to have two.

I volunteer.

+1 from me for Maciek to manage the GForge bug tracker.

4

On Sun, 2006-10-08 at 17:28 +0100, Paul Kelly wrote:

On Sun, 8 Oct 2006, Maciej Sieczka wrote:

> Hi!
>
> CCing GRASS PSC.
>
> Jan-Oliver Wagner wrote:
>> as a follow up of the bug tracker discussions,
>> I just created a project "GRASS" on our GForge platform:
>> http://wald.intevation.org/projects/grass/
>>
>> First, we need someone to be the project manager.
>> Probably Markus or a steering commitee should decide
>> who. However, it is good to have two.
>
> I volunteer.

+1 from me for Maciek to manage the GForge bug tracker.

Ditto. +1.

--
Brad Douglas <rez touchofmadness com> KB8UYR
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785

5

On Sunday 08 October 2006 17:14, Maciej Sieczka wrote:

Jan-Oliver Wagner wrote:
> The managers and anyone submitting or working on
> bug entries should create a user account.

Done. Sent you a request to add me to GRASS project.

You are added.

> Also, you will currently see quite a number of tabs for
> the project (forums, mailing lists, tasks, etc).
> Actually, we only need the bug tracker (so far).
> All others can be switched off. I will do so unless
> you want a specific feature to remain.
>
> Next, there are curently some default trackers configured.
> These could be deleted, or additionally be created and of course
> configured to some extend.

You mean Bugs, Support, Patches, Feature Request? I think we could drop
Support. It will be better to keep all tech-support traffic on
the lists as we used to, so more people would participate in discussion
and more could benefit of it.

sounds reasonable.

I also would prefer to close the Forums and Lists - for the same
reason. We have too little recources to take care of all the eventuall
discussions spreaded here and there.

Regarding Tasks, Docs, Surveys, News and Files there are dedicated
facilities on grass.itc.it and on GRASS WIKI. So I would prefer to
remove them too.

make sense.

What about the SCM? Is moving to SVN planned? If not, could we close
that as well?

well, it is on the roadmap to move on to a better SCM. Whether it should
be SVN or even something more advanced like Mercurial is still to be
discussed.

Regarding the trackers:

@ Oliver:

1. Can I use more than 1 email for "Send email on new submission to
address:"?

don't know. Should be tested.

2. Is it posible to customize what columns will be displayed in
http://wald.intevation.org/tracker/?atid=167&group_id=21&func=browse
? I'd like to add Version there.

not in the admin interface. But maybe at some deeper point.

Best

  Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de

6

Have fun :slight_smile:

Hi,

Just for kicks I was looking to add GRASS 6.2.0RC2 to the "Files"
release section.

I encounter this: (Maximum upload file size: 6M)

the source .tar.gz is 12M.

Hamish

7

Hamish wrote:

Have fun :slight_smile:

Hi,

Just for kicks

OK, but we *won't* be putting here anything for *real*, will we?

Cheers,
Maciek

8

On Monday 09 October 2006 02:27, Hamish wrote:

> Have fun :slight_smile:
Just for kicks I was looking to add GRASS 6.2.0RC2 to the "Files"
release section.

I encounter this: (Maximum upload file size: 6M)

the source .tar.gz is 12M.

the maximum size could be configured. However, as Maciej indicates -
is this an issue?

Best

  Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de

9

Jan-Oliver Wagner wrote:

> Just for kicks I was looking to add GRASS 6.2.0RC2 to the "Files"
> release section.
>
> I encounter this: (Maximum upload file size: 6M)
>
> the source .tar.gz is 12M.

the maximum size could be configured. However, as Maciej indicates -
is this an issue?

why not distribute the souce there? (as a secondary site)

Hamish

10

Hamish wrote:

Jan-Oliver Wagner wrote:

Just for kicks I was looking to add GRASS 6.2.0RC2 to the "Files"
release section.

I encounter this: (Maximum upload file size: 6M)

the source .tar.gz is 12M.

the maximum size could be configured. However, as Maciej indicates -
is this an issue?

why not distribute the souce there? (as a secondary site)

What for? Who will keep 2 sources in sync?

Maciek

11

On Sunday 08 October 2006 17:14, Maciej Sieczka wrote:

CCing GRASS PSC.

Jan-Oliver Wagner wrote:
> as a follow up of the bug tracker discussions,
> I just created a project "GRASS" on our GForge platform:
> http://wald.intevation.org/projects/grass/
>
> First, we need someone to be the project manager.
> Probably Markus or a steering commitee should decide
> who. However, it is good to have two.

I volunteer.

as far as I understand the voting process, you made it :wink:
(PSC: please correct me if I am wrong)

I made Maciej Admin at Wald for GRASS and removed myself
and Bernhard Reiter as Admins.

Maciej: If you now go to the admin tab you should see quite
some management opportunities.
Especially note that there is a pending request to join GRASS.

Best

  Jan

--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de