OzoneFarmCloudScape
Within the OzoneFarm workflow, plans to connect and empower urban gardeners, animal care specialists, rural farmers, chefs, cooks, food co-ops, CSAs, agritourism proponents, alternative energy collectives and many other active groups involve organization and funding strategies. The activity levels should be high enough to warrent inclusion into a matrix of funding sources such as grants, low-interest loans and subsidies for several specific types of work.
Membership and Participation
The core activity consists of modeling a system using the Wagn application to aggrigate planning schemes, research efforts, resource management, special and general project proposals and other consensus/participant-driven networks through a set of web-enabled nodes within a sustainable system of flows and processes. The process architecture constitutes extremely inclusive lists of existant web sites from which to draw knowledge-base elements and adaptive methods to get at things that align with the current common consensus about how to proceed if we really wish to "save the planet".
Building the Framework
The WikiProject_Keywords is the filesystem used for the three special user accounts:
*user:group the registration panel
'''How it Works:''' Keywords builds custom data types and query tables with definitions drawn from the WikiProject master template. :Category:User_groups register at the registration panel by simply dropping a WikiProjectNotice onto the queue. The client script reads Group keys from the queue, resets the queue and delivers a message to <font color="blue">#wikinode</font> where tractor's administrator(s) reside persistantly.
If the tractor drivers think the project is valid, they open Wikipedia:WikiProject_Keywords and build a custom Spreadsheet for the new project:
{| border= "1"
|+ scope & hierarchy
|-
| hash table {%hash} => spreadsheet
|}
The members of the new project can elect to be either '''''active''''' or '''passive''' in the process of configuring the hash table, which is essentially a little tiny database that belongs to each registered project. These become Attachments and are stored as PTOs.
That's the basic framework. Now the fun part...
=== IRC servers and channels ===
You have to be there:
*<font color="blue">irc.wikimedia.org</font>
**<font color="red">#en.wiktionary</font>
**<font color="red">#en.wikipedia</font>
**<font color="red">#meta.wikimedia</font>
*<font color="blue">irc.freenode.net</font>
**<font color="blue">#freenode</font> '' <-- just wait for +voice''
**<font color="red">#mediawiki</font>
**<font color="blue">#wikipedia</font>
**<font color="blue">#wiktionary</font>
**<font color="green">#wikipedia-bootcamp</font> ''<--This project enter''
** <font color="green">#wikiproject</font> ''<--This project participate''
**<font color="green">#wikinode</font>''<--This project administer''
Behavior codes:
*<font color="blue">open</font> You can type freely in these places
*<font color="red">touch</font> Ok to to watch - just don't touch anything
*<font color="green">play</font> People here ''may'' know about this project
=== Wikimedia Projects and Portals ===
The interaction between Wikimedia projects may need to increase its resolution to facilitate a more fine-grained approach. Local context encyclopedias and communities may need to create, sort and manage information that flows into larger contexts. This could solve or create several problems.
If you look at the Wikipedia:List of WikiProjects, you can see a natural relationship between ad hoc groups of users and a fairly orgainized topical outline of where their interests are. This phenomenon took place pretty much on its own and in many cases created high-quality, well-maintained portals with logically organized featured articles. With a Project namespace and good real-time collaboration, this trend could grow.
=== Lists for POE ===
Most tables are built from simple lists (arrays) with relevance to the protocols involved. These lists can grow into project timelines, activity percentiles, metadata charts, progress charts, and other dynamic records. Some of these functions exist in the Meta world and in individual WikiProjects, but with a bit more participation and a well designed POE-Component-MediaWiki they could go much further-faster.
'''IRC:'''
*@Users
*@Servers
*@Channels
'''MediaWiki'''
*@Users
*@Projects
*@Namespaces
*@Articles
=== Table definitions and the Heap ===
POE is really good at scheduling and tracking events.
MediaWiki users are really good at organizing objects.
IRC Users are really good at thinking on their feet.
There's your table.
=== Realtime control ===
sample-time has only two fields:
{| border=1
|+sample-time
| $timeIn
|-
| $timeOut
|}
group-thread has six:
{| border=1
|+group-thread
| #channel
|-
| <nowiki>~~~</nowiki> (User)
|-
| <nowiki>~~~~~</nowiki> <font color="green">start</font> sampling
|-
| <nowiki> nested table from the channel}}</nowiki>
|-
| <nowiki>~~~~~</nowiki> <font color="red">stop</font> sampling
|-
| <nowiki>~~~~~</nowiki> ''refresh time''
|}