|
|
| Line 1: |
Line 1: |
| __NOTOC__
| | 45, Paris, France, fan of wikis. |
|
| |
|
| = Overview =
| | [[Image:Image:Cyclope.jpg]] |
|
| |
|
| <div style="float: right; margin: 15px">
| | Co-founder of [http://km2.net/aplush A+H Cultural Lab] / [[Km2Wiki]] (ProjectWiki of A+H) |
| http://farm3.static.flickr.com/2666/4027443168_879c7b7ccf.jpg | |
| </div>
| |
|
| |
|
| Prepared for http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon
| | Co-founder of [http://navidis.com Navidis] (interactive maps) |
|
| |
|
| == Who is a non-technical person ==
| | Co-founder of [[NotreConstitutionPointNet]] |
|
| |
|
| * Their focus is not technology, but they can contribute
| | Contributor of [[CraoWiki]], [[WikiArtLibre]]... |
| * Never learned programming concepts
| |
| * Didn't realize Wikipedia can be edited
| |
| * Maybe used a web content management system, blog, Facebook
| |
| * Busy with their own concerns
| |
|
| |
|
| == Types and motivations of participants==
| | Currently working on: |
|
| |
|
| * Traditional '''executive''' — "everyone else is doing it," inexpensive solution | | * [[Poietic Aggregator]] |
| ** Ideally they will participate but getting them to can be difficult | | * [[PoieticGenerator]] |
| ** May be more cautious about full commitment - license, security, who can access and edit | | * [[@rbre]] |
| * '''Creative group''' or '''individual''' — may be inspired but needs constant guidance
| |
| * '''Worker bee''' — tasked to use the wiki
| |
| ** May be less receptive to wiki ideals, make it straightforward
| |
| * '''Outside contributors''' - often a stated goal of projects, have their own objectives
| |
| ** Flexible to meet random demands
| |
| ** Fair re-use terms
| |
|
| |
|
| <br class="cleared" />
| |
|
| |
|
| = Goals =
| | [[User_talk:OlivierAuber|leave me a message !]] |
| | | ---- |
| == What do they want ==
| | [[Category:Wiki People]] |
| | |
| # To solve their problem, often a "one of those" web site with some special requirements
| |
| # Something that looks good - '''design is still paramount'''
| |
| # To learn about the participatory web
| |
| # To have more control over their own site but keep things simple
| |
| ## Usually they don't want to 'innovate,' just do what everyone else is doing
| |
| # To work with someone they trust
| |
| # Don't really seem concerned about "silo" and re-use aspects
| |
| | |
| == What do I want ==
| |
| | |
| # Avoid per client custom code, fit things into the developing picture
| |
| # '''Promote digital literacy — filling out forms isn't it, stop treating computers as a typewriter'''
| |
| ## Reference-able statements, reusable data under fair terms of re-use
| |
| # Get people to consider issues of site design and how to organize information without overburdening
| |
| # '''Promote transparency and co-development'''
| |
| ## Help flatten organizations and their external relationships
| |
| ## Don't be fearful and build hidden compromises, open it up
| |
| # Grow my own skills based on relevant requirements
| |
| ## Focused on small groups
| |
| | |
| Shirky:
| |
| <bockquote>
| |
| ...where the student population is about evenly divided between technologists who care about aesthetics and artists who aren't afraid of machines, [http://www.shirky.com/writings/situated_software.html which makes it a pretty good place to see the future].
| |
| </blockquote>
| |
| | |
| | |
| = Success=
| |
| | |
| In order:
| |
| | |
| # Useful one-off resource with lots of development input from stakeholders, possible to build on in future
| |
| # Contributions by many types of people
| |
| # Basic editing using forms
| |
| # Wiki markup, categories
| |
| # Sharing knowledge, creating more converts
| |
| # Creating templates/queries/classes
| |
| # Understanding of good class design, distributed data, licensing
| |
| # Reuse ontologies and web-based content
| |
| # Distributed applications, creating standards
| |
| | |
| = Failure =
| |
| | |
| <div style="background: black; padding: 50px">
| |
| <center>
| |
| http://wiki.zooid.org/images/no-edits.png
| |
| </center>
| |
| </div>
| |
| | |
| * Commitment vs follow through
| |
| ** Constant attention, guidance
| |
| * Tangly mess
| |
| ** Better use of SMW features, more forms, patience for gardening
| |
| * Misunderstood requirements, not really listening to what they want
| |
| ** Learning experience
| |
| | |
| = How =
| |
| | |
| <div style="float: right; margin: 15px">
| |
| http://zooid.org/~vid/pics/ced/marchwikiparty/small_03072009374.jpg
| |
| </div>
| |
| | |
| Lots and lots of guiding
| |
| | |
| Inspire - self empowerment, learning culture, creating, leading, "coolness" (graphs), "where the web is going," open source and transparency, participatory web
| |
| | |
| Reassure - built on Mediawiki, always exportable
| |
| | |
| Threaten - others are doing it, loss of leadership
| |
| | |
| Blow past increasing complexity of security to simpler wiki model (all private or all public)
| |
| | |
| Really enforce importance of discussion tab, history, diff, learning from others ('''view source''').. site evolution as an interest
| |
| | |
| Appoint leads based on interests, give them responsibilities
| |
| | |
| Peer helpers — spread the virus
| |
| | |
| Translators for those who can't directly contribute
| |
| | |
| Profiles of uses
| |
| | |
| Magic — Exhibit example of copying filtered data and pasting to spreadsheet
| |
| | |
| The importance of design
| |
| * promote the cues of Wikipedia but provide something original
| |
| | |
| <div style="magin: 15px">
| |
| http://wiki.zooid.org/images/innocell-wp.png
| |
| </div>
| |
| | |
| <br class="cleared" />
| |
| | |
| = SMW vs Wordpress =
| |
| | |
| Compare Wordpress vs SMW — "Raskin vs Englebart," specialized appliance model vs learning to use a computer
| |
| | |
| http://www.retrofacto.com/wp-content/uploads/2009/06/wordpress.jpg
| |
| | |
| * '''Wordpress''' is task driven software. Forms for every day tasks. SMW is building blocks, play-doh. Helpful to map MW, SMW, extensions but it still won't be the same.
| |
| | |
| Every day tasks —
| |
| * Everything oriented towards content management around blogging
| |
| * SEO, user management
| |
| * "Delete" content, one click
| |
| * SMW site will need a UI (immediate functions) inside a UI (MW)
| |
| * Learning curve is constant on wordpress, gets steep fast using SMW
| |
| | |
| = Summary=
| |
| | |
| * Some successes with non technical users, usually individuals within orgs
| |
| * Patience, constant guidance, listening to requirements are most important
| |
| * Build up big expectations but focus on immediate goals
| |
| * Some SMW facilities such as task oriented guides would help a lot
| |
| ** Slick rich page editors - links and annotations - would help a lot
| |
| ** 'Class' editors work with existing elements
| |
| ** Visual form editor
| |
| * People like visualizations and they can help with shaping and debugging data
| |
| * Always focus on their goals rather than ideals, but try to explain the vision, the two should come together
| |
| * Use lots of meaningful examples
| |
| ** Placeography, DiscourseDB, sites related to organization
| |
| ** Good distributed examples would help too
| |
| | |
| == Questions ==
| |
| | |
| * What are the best extensions to make the site easy to use?
| |
| ** Do people use the rich text editor?
| |
| * Is SMW a good "universal platform?"
| |
| | |
| = Notes =
| |
| | |
| ==Notes from conference==
| |
| | |
| * Business people love reports
| |
| * Authoring tools - ease of tagging
| |
| ** Problems with easy to use rich text editors mangling output
| |
| * Stop saying "semantic" — "knowledge engineering"
| |
| ** Bad perceptions about 'wiki,' they get messy - call it "knowledge management"
| |
| * Need more white papers instead of mountain of data
| |
| * Find meaningful ways to connect to well known solutions (SQL, etc), use it as an integration platform
| |
| | |
| <headertabs />
| |
