:: Re: [devuan-dev] Devuan Meet Sept. …
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Evilham
日付:  
To: devuan-dev
題目: Re: [devuan-dev] Devuan Meet Sept. 13/14 2017
Am 10/09/2017 um 21:36 schrieb Svante Signell:
> The current absence of main developers for these meetings (as well as
> software/infrastructure upgrades/mail contributions) makes me _very_

worried
> about the future of Devuan. Anything (we who cares) can do?
>


On that note.

I was thinking a lot about this over the past few days, so I am very
glad to see you brought it up and feel like I have to state the
following:
* In spite of being mid-September already, lack of activity /
communication is very disappointing.
* Since there are tons of things requiring my attention this month
and trying to do sth on Devuan starts being frustrating, I'm
*somewhat* switching focus. To clarify, I am still:
- reading IRC periodically
- reading the -dev mailing list daily
- checking-in for the weekly meeting to see if anything changes
- sprint some Devuan work a couple times a week
- available if something lands on my inbox
However:
- I am keeping the time invested in Devuan low for the next couple
weeks
- not checking IRC as much as I'd like to
- limiting how often I check the devuan-dev ML since there's not much
going on there these days

Why? Devuan is having a Governance crisis. Surely, I am not the only
one noticing this.

I must admit, at first I thought this crisis was a technical one, and
my attempt at helping solve it may have made things worse. I apologise
for that. At least some documentation came out of it, which is in my
eyes sth positive.

I've only been around for about 3 months, that is 1/4th of a year and
in most of that time, Devuan (as a project) has been... let's call it
dysfunctional. Yes, some progress has been made, however the core
issues remain: there are tons of blockers, discussion either dies or
escalates quickly and then gets abandoned without reaching any
consensus so it all ends up being in vain, leaving questions
unanswered. The fact that it doesn't seem to be getting any better is
more than worrisome.

So, how can we get through this and keep it from happening again?
If the project is to move forward, the root issues leading to the
current state of affairs have to be resolved.

Thoughts?

--
Evilham