[Arm-netbook] Standards Organization as a Potentially Universal Free/Libre Software Developement Sustenance Model

[Pablo Rath]

On Tue, Jun 06, 2017 at 05:51:33AM +0100, Luke Kenneth Casson Leighton wrote:
...

>  the first step *really is* to quite literally copy - verbatim - the
> gnu devel.html page and "generify" it.
> 
>  where it says "we recommend savannah" put instead "we recommend the
> use of a Libre Hosting Service which has a minimum criteria of an A,
> as defined by the FSF's Hosting Criteria".
> 
>  where it says "we recommend mailing lists on gnu.org" put instead "we
> recommend the use of software libre hosted mailing lists".  a later
> revision should go into further detail as to *why* "announce",
> "users", "dev" etc. is recommended.
> 
>  etc. etc.
> 

As it seems to me the above points are done. Thank you Luke for
fixing my mishappened sentence. 
There is now a point for version control, mailing lists and web pages at
the wiki (http://rhombus-tech.net/proposed_best_practices/). 
Regarding the goal of a general standard for libre projects I don't
think it is necessary to cover the quite specific further points of the
gnu devel.html page: "FTP", "Login accounts", "Hydra: Continuous builds and portability
testing" and "platform-testers: Manual portability testing". 

I have read a good part of the Maintainer's Guide:
https://www.gnu.org/prep/maintain/maintain.txt
and wonder how to best incorporate it into the draft for best practices.
For example from gnu devel.html page we took the point about web pages
and generalised it: "we recommend to
host the webpages for the project using resources that meet the FSF's
Hosting Criteria"
Chapter 12 Web Pages of the Maintainer's Guide covers a lot of details. 

Some questions:
Has anyone else started to work on it (offline)?
How long shall the first draft of the standard be (e.g. 10 pages, 100 pages, as long as
necessary)?

As you can see I am looking for guidance and some kind of roadmap to
prevent working in the wrong direction.

kind regards
Pablo