+1 to Peter!

I've read through this thread, though I, too, did not track the process around updating the compliance suite.

My observation:
* The Council (or members thereof) think that they are absolutely right and their actions lie within the boundaries of XSF regulations. * Sam I frustrated, because the 2018 compliance suite still is not finished and change requests are still coming in. This is not his fault, but resulted in (in-)actions by the Council. As a result he is demotivated and wants to drop the task.

Formally the Council may be right. They did not violate any established process.

But I see a more strategic question: Does losing Sam as editor and maintainer for the compliance suite justify the current course of action? Is the persistence on adding the feedback worth it?

If your answer is yes, what's your argument regarding this:

On 2018-01-19 03:38, Peter Saint-Andre wrote:
As Sam says, this means we need someone to put forward a revised suite
every year and shepherd it through the process. In olden days I did
this, and more recently Sam volunteered. IMHO treating the intrepid
volunteer well is especially important in this case, because it's a
thankless task and any oversights can be easily fixed the next year.

If the answer is still Yes, then who is going to maintain the suite from now on?

I'm not saying we should override any processes defined in XEP-0001, but I
sense that handing of this relatively unimportant XEP has resulted in
hard feelings all around, which is unfortunate and was probably avoidable.

+1

This is not about which process or person is right. This is an emotional problem and to solve it, an act of leadership from the Council is needed.

Please get Sam back on board!


Have a nice day and be excellent to each other,
Stefan


--
Netz39 e.V. - Real World Virtuality                http://www.netz39.de
Stefan Haun                                               [email protected]


E-Mail: [email protected]

Vertretungsberechtigter Vorstand: Benjamin Hatscher, Franz Kuntke
Inhaltlich verantwortlich gemäß §55 (2) RStV: Benjamin Hatscher

Registergericht: Amtsgericht Stendal
Registernummer:  VR 3169
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to