Author: Ralph Ronnquist (rrq) Date: To: devuan developers internal list Subject: Re: [devuan-dev] Request for organization
Good thing. I believe I could adapt to using that. As a detail: it's
quite important that we have date stamps on the entries to mark when the
entry is made, then other date stamps (due date etc) as applicable.
Ivan J. wrote on 4/6/19 11:07 am: >
> Hello devs.
> I would like to propose an asynchronous task workflow that might benefit
> all of us. I'm saying asynchronous, because due to our timezone
> differences, and after all, general availability, we are not all able to
> be in the same place at the same time to discuss things.
> My idea is to have a central pad that we can always access and place
> tasks that need attendance in order of urgency on it. Something in
> this manner.
> Once the tasks are in place, anyone picking them up would mark that it
> has been picked up and possibly notify everyone else by sending an email
> to devuan-dev@ and update everyone about the task's progress. Each task
> would then have a thread of its own.
> Depending on whoever thinks a task should be done, and wherever they
> read it, they should put it up on the pad. Whether it's IRC, or a
> Wednesday meeting, or a mailinglist, or d1g, it doesn't matter. What
> matters is that there is a central place. I am not mentioning bugs.do
> here because to me it seems that it might not work well for this issue.
> Please give me feedback on this so we can see if we can get things
> moving again.
> Thank you.
> I am not going to reply to any emails dealing with personal issues.
>  https://pad.dyne.org/code/#/2/code/edit/dsFabYd7GS165eXdcCb90CSW/ >
> devuan-dev internal mailing list
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev >
This message was posted to the following mailing lists: