On Fri, 18 Aug 2017, KatolaZ wrote:

> The only way to let Devuan proceed more swiftly is to avoid single
> points of failure, and to allow other developers to help Devuan.

this goal, generic enough when applied to various roles and
specialisations, is of high priority for Devuan right now. the time
and energy to go this route is demanding and doubts and resistance is
legitimate to the decision process, so please everyone be patient and
at all costs lets all avoid personalisation.

We all want clear distribution of responsibilities that is redundant
enough to not have blockers, but also allows review and avoids quick
changes that are not well understood and debated.

Based on the activity and investments done during the past years, we
have informally accepted the ultimate presence of a "triumvirate" for
final decisions and also blockers to be composed by me, Daniel and
Nextime and I really believe this network of trust should not be
forced, but respected, until we reach consensus and/or we enlarge (and
not shrink!) the decision making group. The current empasse related to
to the DIP-1 proposal by Katolaz, backed by me and Parazyd, is not the
only signal we can observe of a conservative behaviour, which can be
annoying at times but also healthy to the project and as such should
be observed and debated.

There isn't yet a well researched alternative to the DIP-1, but
meanwhile the debate has triggered some heat and also appropriate
mediation by Evilham leading to the good documentation effort he is
curating, another much needed contribution for the project in this
phase. If we manage to continue the debate in a constructive way, I
propose then we interact focusing on DIP-1 and documentation of the
infrastructure until the end of this month, leaving aside any general
consideration about decision making and personal involvement or other
para-political issues.

Thanks everyone for signaling here or privately your intention to add
your help. After the dust settles on a final setup of the build
infrastructure, we'll have a clear developer's manual on how to use
it, which is already at a very good point and will be shared for
comments in the coming weeks. Also soon enough we'll debate the
opportunity to extend the leadership role to more developers: speaking
for myself, in case it wasn't clear enough already, I believe it is
not sustainable to have only three people developing and deciding on
all issues for a project like Devuan, that is evidently growing much
in importance and achievements and also infrastructure.

ciao