Take a look at 'kanboard', used (professionally) for exactly this purpose.
An incorrect description would be 'Post-it notes in User queues'
Works in a web browser of 'your' choice...
It's use really does improve workflow esp working across timezones.

It would be trivial for dev1 to set up an own-served kanboard instance,
and is very quick and easy to learn to drive as a User. Unlike other methods,
(that I have been forced to use in the past) you do not waste all your
development time managing the system.

Being naturally a rebel and non-conformist anything management\business
orientated I praise deserves it!

On 04/06/2019 13:13, KatolaZ wrote:
> On Tue, Jun 04, 2019 at 08:18:54PM +0900, Olaf Meeuwissen wrote:
>>
>> Devuan has a GitLab instance. Why not use its issues? With a suitable
>> set of priority labels and people assigning issues to themselves, the
>> workflow would be pretty much the same as below.
>>
>
> I probably shouldn't intervene on this, but I guess past experience is
> useful in making decisions: the usage of gitlab issues to signal bugs
> and things to do was what effectively stalled and delayed Devuan
> Jessie release by more than one year and a half. The few developers
> had to cope with issues scattared all around the place, with no idea
> of what needed to be done in order to have the release ready. The
> turning point there was to have all the issues manually collected from
> all the different gitlab projects and collated (and tagged) into
> bugs.devuan.org. At that point we knew what needed to be done and
> worked for it. Jessie was released three months after that collation
> work was completed.
>
> IMHO gitlab issues work well only if you have many developers, each of
> them supervising just a couple of projects, and only those. In that
> case it is clear who should take care of which issue. If you have only
> a handful of people who need to do whatever needs to be done, all over
> the place, then a pad would be much more efficient, IMHO.
>
> Sorry
>
> KatolaZ
>
>
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
>