[RFC] Rethink the voting / decision making process
john at phrozen.org
Tue May 31 05:22:33 EDT 2016
On 31/05/2016 11:09, Conor O'Gorman wrote:
> On 30/05/16 17:06, Jo-Philipp Wich wrote:
>> Hi Conor,
>> I am still looking around...
>> The first candidate I looked at was Debian but its project policy
>> documents read like German tax law, not exactly the simple, yet
>> democratic project rules I had in mind ;(
>> ~ Jo
> Some googling yesterday suggested the idea of sub-committees.
> I suggest a possible arrangement:
> Build system (stuff in include/)
> Management/Config (procd,netifd,ubus,uci,luci)
> Repo, Build and Test Infrastructure
> Community/Corporate interaction
> There may not be formal sub-committees, but I think it is useful to
> consider some sub-divisions of the project.
i think you are running down the wrong road here. if you start voting on
implementation details then this will kill the operational ability of
the project. the areas of voting should be
* design (website, logo, ...)
* infrastructure (server locations, services, ....)
* release (timing, naming, ...)
* industrial relations (conferences, funding, ...)
* governance (NGO governance, trademark, rules, ...)
these are the areas that require voting.
> lede-adm mailing list
> lede-adm at lists.infradead.org
More information about the openwrt-adm