Smalltalk › Pharo › Pharo Smalltalk Developers

Issue Tracker: enabled Projects (Boards)

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

Marcus Denker-4

Issue Tracker: enabled Projects (Boards)

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Ben Coman

Re: Issue Tracker: enabled Projects (Boards)

How are issue priorities being assigned? Perhaps there could be a High Priority board?

cheers -ben

On Mon, 18 Mar 2019 at 15:28, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Ben Coman

Re: Issue Tracker: enabled Projects (Boards)

Poking around the web bumped into a recommendation for this...

https://www.zenhub.com/blog/open-source/

cheers -ben

On Mon, 18 Mar 2019 at 20:08, Ben Coman <[hidden email]> wrote:

How are issue priorities being assigned? Perhaps there could be a High Priority board?
cheers -ben

On Mon, 18 Mar 2019 at 15:28, Marcus Denker <[hidden email]> wrote:
Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

In reply to this post by Ben Coman

On 18 Mar 2019, at 13:08, Ben Coman <[hidden email]> wrote:

How are issue priorities being assigned? Perhaps there could be a High Priority board?
cheers -ben

Yes, that might be a good idea.

We did not use priorities that much in the old issue tracker which means that

a very simple scheme (like a board) should work, I think.

Poking around the web bumped into a recommendation for this...
https://www.zenhub.com/blog/open-source/

We tried to use Trello in the past… with mixed success. What I like with

the GitHub board is that they are right there, no need to have yet another

system, yet another account…

But it would be definitely interesting to play with it.

Marcus

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

In reply to this post by Marcus Denker-4

Hi,

it seems that the account / access model of GitHub forces us to move the boards to the organisation level

(where we can have a user group with write access for the boards).

This means I will move them slowly to

https://github.com/orgs/pharo-project/projects

So lets treat all this as a test… as soon as it is really working I will send another mail.

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

SergeStinckwich

Re: Issue Tracker: enabled Projects (Boards)

but you need to be on the Pharo organization to be able to add/modify card on the board ?

A+

On Tue, Mar 19, 2019 at 11:07 AM Marcus Denker <[hidden email]> wrote:

Hi,

it seems that the account / access model of GitHub forces us to move the boards to the organisation level
(where we can have a user group with write access for the boards).

This means I will move them slowly to

https://github.com/orgs/pharo-project/projects

So lets treat all this as a test… as soon as it is really working I will send another mail.

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Serge Stinckwic

Int. Research Unit

on Modelling/Simulation of Complex Systems (UMMISCO)

Sorbonne University

(SU)

French National Research Institute for Sustainable Development (IRD)

niversity of Yaoundé I, Cameroun

"Programs must be written for people to read, and only incidentally for machines to execute."
https://twitter.com/SergeStinckwich

EstebanLM

Re: Issue Tracker: enabled Projects (Boards)

In reply to this post by Marcus Denker-4

The GitHub criteria is that issue reporters are not the ones that can distribute/label/recognise the areas of the reported issue, and that should be done by “admins”.

I wonder if instead trying to fix the issue, we couldn’t first check if that’s an actual issue? I mean: maybe they have a point and we shouldn’t ask people to know what area of effect is the problem they are reporting.

Esteban

On 19 Mar 2019, at 11:06, Marcus Denker <[hidden email]> wrote:

Hi,

it seems that the account / access model of GitHub forces us to move the boards to the organisation level
(where we can have a user group with write access for the boards).

This means I will move them slowly to

https://github.com/orgs/pharo-project/projects

So lets treat all this as a test… as soon as it is really working I will send another mail.

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

In reply to this post by SergeStinckwich

Yes, it can not be completely public or it will be vandalised.

On 19 Mar 2019, at 12:17, Serge Stinckwich <[hidden email]> wrote:

but you need to be on the Pharo organization to be able to add/modify card on the board ?
A+

On Tue, Mar 19, 2019 at 11:07 AM Marcus Denker <[hidden email]> wrote:
Hi,

it seems that the account / access model of GitHub forces us to move the boards to the organisation level
(where we can have a user group with write access for the boards).

This means I will move them slowly to

https://github.com/orgs/pharo-project/projects

So lets treat all this as a test… as soon as it is really working I will send another mail.

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

--
Serge Stinckwic
h

Int. Research Unit
on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
(SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for machines to execute."
https://twitter.com/SergeStinckwich

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

In reply to this post by EstebanLM

On 19 Mar 2019, at 12:22, Esteban Lorenzano <[hidden email]> wrote:

The GitHub criteria is that issue reporters are not the ones that can distribute/label/recognise the areas of the reported issue, and that should be done by “admins”.

I wonder if instead trying to fix the issue, we couldn’t first check if that’s an actual issue? I mean: maybe they have a point and we shouldn’t ask people to know what area of effect is the problem they are reporting.

Does it make sense to have boards if only I use them? For sure not…

e.g. Steven wants to use the Reflectivity board. I now added to to the organisation instead, created a Team for Kanban boards, added him there and now he can edit

https://github.com/orgs/pharo-project/projects/7

Esteban

On 19 Mar 2019, at 11:06, Marcus Denker <[hidden email]> wrote:

Hi,

it seems that the account / access model of GitHub forces us to move the boards to the organisation level
(where we can have a user group with write access for the boards).

This means I will move them slowly to

https://github.com/orgs/pharo-project/projects

So lets treat all this as a test… as soon as it is really working I will send another mail.

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

I moved them all to the Project level

https://github.com/orgs/pharo-project/projects

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus

Marcus Denker-4

Re: Issue Tracker: enabled Projects (Boards)

I added a description to the GitHub wiki: https://github.com/pharo-project/pharo/wiki/GitHub-Project-Boards

On 29 Mar 2019, at 09:52, Marcus Denker <[hidden email]> wrote:

I moved them all to the Project level

https://github.com/orgs/pharo-project/projects

On 18 Mar 2019, at 08:27, Marcus Denker <[hidden email]> wrote:

Hi,

We enabled the GitHub “Projects” feature for the pharo repo:

https://github.com/pharo-project/pharo/projects

The idea is that one can add as many “Kanban” style boards as one wants.
issues and pull requests can be added, as well as simple cards that are not yet issues.

This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there
are >500 issues.

With these boards, we can create “views” on this sea of issues.

I created for now:

-> some board related to specific parts of the system (e.g. Traits or Reflectivity)
example: https://github.com/pharo-project/pharo/projects/11
-> "Pharo7 Backporting”
https://github.com/pharo-project/pharo/projects/12
-> "Simple Issues for Beginners”
https://github.com/pharo-project/pharo/projects/14
Here the feature to be able to put things that are not yet issue tracker entries seems very useful

I think this can be quite nice… we should add more Projects as soon as we find that they make sense
and should move issues there.

Marcus