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 <marcus.denker@inria.fr> 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 <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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
Hi,
We enabled the GitHub âProjectsâ feature for the pharo repo:
https://github.com/pharo-project/pharo/projects <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