Because of the messed up stuff on the Raspberry Pi wiki, I have found it necessary to create a governing council for the RPi wiki. Please edit the below section if you'd like to become a member (alderman) of the council.
Note: This is official and is ok with the administration of eLinux.
If anything is wrong with these guidelines please feel free to edit them. Thank you.
Guidelines are made from consensus
All supplemental guidelines and decisions will now be made by the RPWC and eLinux administration.
Current council aldermen
As he is not answering my requests for identity, he may be impersonating Mahjongg on the forums. I propose the account be blocked indefinitely because it clearly is copying the RPi forum mod's user name. --Jeff • (talk) RPWC President 12:26, 5 October 2012 (UTC)
I propose that since he ruined a lot of formatting that he is not to edit the Raspberry Pi Wiki's formatting for 1 month. You can see clearly here. He, in fact, misguided everyone in best practices! I want you to go to Wikipedia and take a hard stare and compare the articles! They are misleading! He clearly cannot go on with this! Anyone else agree? --Jeff 02:15, 2 October 2012 (UTC)
Edit: and also add a block of 1 month if he does not comply. --Jeff 22:39, 2 October 2012 (UTC)
(Note: This decision must be concluded by Wednesday, October 3, 2012.)
- Having compared Ghans' "Best Practice" with which, I believe, are the equivalent areas of Wikipedia and parts of the Help sections here I can see what you mean. However, using Wikipedia as a guide, one also has to assume that he was writing with the best of intentions. Unfortunately he does not reveal much about his background, experience etc. on his user page. However, having had the experience of encouraging "best practice" within a mixed group of programmer's of different backgrounds (scientific, computational) and training (formal, informal, none), I am well aware that when considering adopting such from a related area, one also has to consider the needs etc. of the intended users ie. adopt as much as is appropriate, adapt or reject the remainder. An analogy would be that when preparing a presentation one may end up with several versions depending upon the expected audience. Hence, whilst I am prepared to support your proposal, it is on the understanding that this is done so to allow us to begin to formulate more suitable guidelines, given that, eventually, hopefully, there will be younger, enthusiastic but less experienced contributers whom I would not wish to discourage. --TrevorGowen 14:40, 2 October 2012 (UTC)
- So you're a support? --Jeff 22:32, 2 October 2012 (UTC)
- Assuming I'm interpreting your update above correctly, to mean that he is requested to refrain from edits that change formatting aspects of the Raspbery Pi sections of the Wiki for one month and ignores that request, yes. Hopefully such a request will generate a response, therebye opening up a dialogue, which may resolve matters such that a formal block need not be imposed. --TrevorGowen 12:09, 3 October 2012 (UTC)
- So you're a support? --Jeff 22:32, 2 October 2012 (UTC)
Wiki Design principles
All good things require a good design. To improve this site, we should (re)define / clarify its purpose. The following principles are suggested:
Users of the Raspberry Pi will be of three types (or a mixture of these); (a) competent Linux user, (b) experienced hardware and/or software modifier / hobbyist (c) beginner
Each page should consider WHY a reader would be using that page.
A competent Linux user would only want to know how to get the Raspberry Pi working and set up, and any 'peculiarities' relating to the hardware or Linux distribution. The hobbyist would additionally want to know how to use the GPIO ports and associated software, or how to modify / build the distribution or packages not included in that distribution. There should be clear pointers on the first page for the sections relating to these groups.
The beginner will need careful guidance in their first steps. For this, instructions should be clear:
- they lead the user from what they know into what they don't, with each step being small and simple with the 'objective' clearly defined.
- they use simple steps, and should skip optional complications that are not relevant to the current 'lesson', e.g. half of the raspi-config settings are 'advanced'.
- they should include a link to complete documentation for the topic, with a warning that this may cover advanced material, e.g. full raspi-config instructions.
- the writer should take into account that the site, and users, will be global, with english as a second language.
- the writer should take into account the variations of hardware and distribution installed, e.g. the raspi-config utility is not available in many distributions.
- the instructions should clearly state if they are specific to a particular set up, or are 'date sensitive' to changes.
- pages should be separated into GUI and command line pages and flows.
- instructions should be free from point-of-view opinions.
- instructions should link to 'choice' pages that give pros and cons regarding that choice, e.g. which text editor should be used and if it is available / installable.
The beginner guidance should stop at the point where other sites can take over, e.g. once sufficient Linux has been covered, other Linux sites can provide more advanced or specific information. It should also be aligned to the objectives stated by the Raspberry Pi Foundation for why the Raspberry Pi exists.
Proposal, in absence of anything similar. SimonSmall 16:54, 4 October 2012 (UTC)
- I strongly oppose this. We should NEVER split users into "social classes" and English is our official language, just as English is the Raspberry Pi's preferred language. I think this overhaul is too much right now. Why don't we focus on something else first? Also, you can't make proposals unless you already are a council alderman, in which case, as of my posting time, you currently are not. --Jeff • (talk) RPWC President 01:40, 5 October 2012 (UTC)
If you are interested edit here
Please indicate your interest in joining the council below here, along with a link to your userpage.