Hi,
disregard parts of this. I understand why this happened again (better visibility
of tasks for the meeting in switzerland). What still applies is in general
thinking in general more about if a certain task can be finished by a certain
date. For website and documentation this is often inappropriate unless it is
very important.
I think we all can estimate how long a task can take. This message was sent
only because I lacked context for why this was assigned again to the roadmap.
n...@n0.is transcribed 1.3K bytes:
> Hi,
>
> I appreciate the attention to documentation and website bugs,
> and I would like to hand off some responsibilities for an ease of mind.
>
> The current team size + current
> interest team group + availability of time for gnunet of those people
> does mean that medium or big documentation tasks can not be part of
> a roadmap goal.
> Even smaller tasks. If you think it should be part of the roadmap,
> please consult with me about this (I might know people who already
> are working on what you want to propose or can give you feedback about
> if your guess about time required for this is right. I'm growing tired of
> un-assigning
> roadmap goals from tasks we got no one working on ( Create a quick reference
> sheet ("cheat sheet") for GNUnet)
> or which are simply too abstract ( improving the installation
> guide/handbook), etc.
>
>
> Thanks.
>
> _______________________________________________
> GNUnet-developers mailing list
> GNUnet-developers@gnu.org
> https://lists.gnu.org/mailman/listinfo/gnunet-developers
_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers
