[lime-users] To continue the conversation about the wiki

Hi guys, apologize for reorganizing this conversation again. I think it is better for it to have its own thread. So, to recap, the conversation comes from the thread "Recommended devices?": Patricio Gibbs on 07/27/2017 The conversation in this thread has documented some useful knowledge. Is  there a place to compile this information in a list of compatible  devices? I see the mostly empty list at: http://libremesh.org/docs/hardware/ Such a list could be part of a guide about how to choose a device, or  how to guess whether a device might work or is definitely unsupported. Bruno Vianna on 07/29/2017 I like the idea too, but it would be much easier if it were a wiki or some kind of editable page. I contribute to openwrt's wiki every time when I find out info on a new device. I understand the content from libremesh is in github, but it is a lot more bureaucratic to edit the html, push it, wait for merge... So, dear libremesh site managers, do you think we can have a wiki or some open content solution? We talked with Gui/Gio/Pau/NicoE about this and think that would like to make a decision that reinforces the community, so instead of pushing a specific implementation, it is better to share our perspectives on the subject and consider experimenting something a bit in the way to the "advice process" http://www.reinventingorganizationswiki.com/Decisi on_Making, which we are implementing as:  someone who is in a good/the best place to make this decision (can mean many things but let's consider responsible for implementing and maintaining, and accountable for the results... who would be me so far) will lead an "advice process" which means receiving advice from all those who can have relevant contributions and/on will be affected by it, meaning you. So this is a brief of the points of that group, which I'll share since I consider valuable for all to know them: Pro "current state" We left RedMine because it was not working, people was not contributing and the info was not being updated. Now that it is more code-related the info is kept in a more coherent way. On GitHub there is the "Edit" button. It is not necessarilly bad to have to wait for a Pull Request to be accepted. Pro "Wiki" Now we are a bigger communitty, how do we enhance involvement? We can make a monthly test with the GitHub wiki with the unnoficial info like "experiences with hw", "specific tutorials", "cases" and so. The downside of the github wiki is that it can only be editted by collaborators of the repository. So based on this information, which key points would be relevant to consider to move forwards? Please share your points of view so we move on to have a definition. As said, it is an experiment of using a decision making method which seemed to us can be a good one for the kind of community we work to build. Please then shared also your feedback about this. Part of this process has been promoted by a relative new member of the community (5 months or so), Rodrigo Monelos, who has been mainly acting as facilitator and Agile coach on the LibreRouter project, so he will be helping also with the coordination of it. I hope he can introduce himself to come out of the shadows :) Regards,