Workflow
The general idea is that role's workspace articles link to categories and queries which contain the kind of work which that role performs. But to implement and use this idea in practice requires more specific detail, for example:
- Workflow templates/conventions (e.g. DPL based category queries rather than slashes in cat names)
- How is hierarchy implemented (workflows which contain other workflows)
- Tying in schedule
- Job classes/templates
- Workflow package
- Specialpage (should be report on workflow tree, not old selection-operations idea)
- Email notification
- Job creation (& job guid-names)
Workflow categories
- Time
- Digit
- Enabled (yes,no)
- version
- OS (Linux, OSX, Windows)
- Apptype? (Source/Binary/deb,exe etc)
- Mediatype (Text,Application,XML...)
- Storage type (CD,DVD,Memory stick,RAM,Hard drive,floppy)
- Order (lead,quote,started,invoiced,paid)
- State (Open, filed...)
- Priority (High, meduim, low)
- Entity (machine,org,human)
Image sources
- SVG Category
- Vote symbols
- Arrows
- Icons
- AIGA symbol signs
- Indication icons
- Crystal Clear icons
- Category:Mascots
- icons Category:Film icons
- Adobe Illustrator and other propriatary softare contain directories of symbols, but most likely under license.
Tasks and roles
The category articles contain information about the tasks and policies, and these can also evolve through discussion of the perceived problems and needs as they arise. They also contain links to other information frequently needed in that context. Categories must also be defined for the roles and the workflow categories are subcategories of the roles.
Migration
If we start organising our various development and work using common categories and conventions, then it can be migrated into the new interface more effectively. Also, since we are already teaching the wiki workflow principles independently of the project's education or XmlWiki, we should try and maintain a good clear working example of those methods ourselves.
- Organic Design Conventions has been started to help standardise various aspects of our content
We don't have Nodal Organisation in a functional state yet, but the current wiki paradigm uses categorisation very effectively as a means of workflow management. Here are some names of workflow categories from wikipedia to give some examples:
- Articles actively undergoing construction
- Articles copied to Wikibooks in need of cleanup
- Articles for speedy deletion
- Articles needing Chinese script
- Articles that are way too long
- Articles with confusing statements
- Articles with broken links
Obviously these are all oriented toward presentation and publication due to the nature of the Wikipedia project's work, but the general idea can apply easily to any manner of organisation. Its the general concept of creating an idea or collection of goals as an article and categorising it based on the roles and processes which are currently required to act on it. Each role which acts on it can then remove it from their category and add it to the next roles category who needs to work on it.
Its a lot like a Human-Tuple space where no communication is necessary between the processors of the work, and the items of work can be selected by roles randomly from the categories of work they feel like doing with no timing coordination needed.
