[LEDE-DEV] A Wiki for LEDE Documentation
Fernando Frediani
fhfrediani at gmail.com
Thu Sep 15 05:26:33 PDT 2016
That's why I am an adept of hierarchy or at least have well defined
who is responsible for what, otherwise when something is sent to all
nobody will care much to respond unless that affects him/her directly
in some way.
I'm not talking about someone giving orders and others following it,
but just having someone or a small group of people that answers
anything related to that topic. When you have something to say about
that subject you know exactly who are the people in charge of that.
Well, good this is going ahead finally.
On 14 September 2016 at 20:11, Alberto Bursi <alberto.bursi at outlook.it> wrote:
>
>
> On 09/14/2016 12:27 AM, Jo-Philipp Wich wrote:
>> Hi Alberto,
>>
>> don't hold back yourself waiting for a response from "the LEDE devs" -
>> those who care about a wiki will likely endorse whatever good solution
>> is proposed and the rest either has no opinion or time to participate in
>> the decision making processes
> Thanks for the heads up and confirmation. I was thinking along these
> lines too but I needed a more "official" statement to be sure it was ok
> for you. :)
>
> Just a quick reminder, you are the leaders of the LEDE project now, you
> cannot just ignore posts and say "it's not my thing" like when you were
> mostly developers.
> Someone from the core team (i.e. the ones with "voting power" according
> to your rules) has to at least come out with an "ack but you must do
> this yourself" or a "nack we don't like this" for proposals or important
> matters.
> Otherwise most people will default to "wait for leaders decision" as you
> saw in mails above, and that is not good for anyone.
>
> Now that you made it clear that we can arrange it ourselves we will (at
> least try to, anyway).
>
>
> -Alberto
>
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
More information about the Lede-dev
mailing list