One meta-issue is that some issues might be raised in Pharo, but should be raised in some sub-project (Spec, Iceberg, Microdown, …).
I for one has been working mostly in Microdown, and would not obviously discover an issue regarding Microdown raised in the Pharo project. Perhaps it is just I who is sluppy. Best, Kasper > On 18 May 2022, at 08.50, Marcus Denker <marcus.den...@inria.fr> wrote: > > Hi, > > One problem with a public issue tracker: it accumulates lots of issues… > > This sadly means that issues will not be looked at one by one… there are > just too many. > > One thing that is interesting to do is to check the issue that *you* > submitted. > > - Is the issue still relevant? > - is the title good and in sync with the issue? > - Has it been fixed already ? (it happens!) > > Then, for every issue there is a “next step”. It can be a good thing to spell > out > very explicitly what the next step is “We need to create a Pull Request for > the > suggested fix”. > > Or maybe what is needed is a summary of the huge discussion in the > issue tracker entry. > > Another idea: try to find others to help. E.g. > > - send a mail to the mailinglist. > - ask on discord. > > Maybe you can find a small group that works on this issue together. > > > > Marcus > > >
