To be filed / built out
 To be filed & filed :)
- Secret sharing (for registrar/DNS, etc.)
 Duly Noted
 WON Notes
 March 29, 2012
Meeting Notes - March 29, 2012 - wiki.occupy.net (WON)
Attending: Amgine, Lippe
 Breadcrumb structure and "/" pages
Should we clean up and standardize to the templates + sub-page system as used on:
Though it should be noted these use two different templates, though they're both listed under "projects." Are there any slashed paged left around?
There are a number of pages with poor namespaces, sloppy structure, or could be considered dodgy style:
WON could adopt a stylebook/styleguide: Wikipedia: http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style
With current usage it might be more appropriate to:
Patrollers are being added by Amgine, to distribute the first level of cleaning and abuse reverting: http://wiki.occupy.net/index.php?title=Special%3AListUsers&username=&group=patrollers&limit=50
 Article issue tagging
To allow for queues of work, and quick marking of pages for future review or need for improvment.
 Using multimedia
Media can be uploaded and inserted from these sites:
 Dynamic Page List with abstract/summary
Revisiting notion of using DPL extension to create lists of category intersections with summaries pulled from page text.
Need OO PHP coding to make this happen. :)
 New Skin
Demo of skin: http://devteam.arxnet.org/mediawiki/mediawiki-1.18.0/index.php/Main_Page?useskin=won
Many "share" widgets are running .js which fingerprints visitors browsers. Agreement that holding up release of skin till noninvasive widgets are found is not necessary, we can add share features iteratively as they are found/made/modified.
- Amgine: look into adding a gadget which has 1-click adding of issue templates to articles.
- Lippe: look for straggler breadcrumb pages
- Lippe: Poke around Template framework, make suggestions.
- Lippe: Suggest edit page header & footer text, "no article" text.
- Information in templates is less available/intuitive to edit.
 Consensus process
 Consensus as Concept and as Formal Model
 Why to Use Consensus
Both as a term and as a formal decision model, consensus represents cultural and political values. As such, use of consensus may represent either a manifestation, aspiration, or via implementation, a clarification of those values.
- Open & participatory
- Group cohesion & cooperation
- Trust & good faith.
- Creative process
(+ how to represent approach to disruptive elements)
 Why to Not Use Consensus
- Consensus is a process for adopting proposals.
- No decision is made until concerns are heard and discussed.
- Any concerns that remain after discussion are acknowledged.
- The group may go ahead with a consensus decision without complete agreement. (specify model)
 Basic Procedure
(Is it possible to outline basic procedure without specifying model?)
Elements occurring before meeting
- Bring materials/supplies needed
Elements generally occurring prior to meeting
- Choose facilitator(s)
- Gather agenda items
- Determine agenda items
- Determine presenter/initiator for each item
- Determine item type: announcement, report, discussion, decision
Elements of meeting
- Informal Opening
- Connect (game, song, ritual, etc.)
- Agenda review: agree on order and time
- Choose roles
- Step through the agenda (big or little first?)
- Set next meeting