Open Source Ecology - User contributions [en]

Core message

2009-07-28T02:58:07Z

Dan: /* About OSE in general */

{{HdrMarketing}}
A 'core' message is a condensed message that helps explain what your goals are in an easy to remember phrase.

= Possible core messages =

== About OSE in general ==
* "Creating tools for building modern off-grid resilient communities that can be reproduced by anyone at low cost."
* "Building the world's first replicable, open source, modern off-grid global village - to transcend survival and evolve to freedom."
* "Our aim is the full integration of flexible small-scale manufacturing with sustainable agriculture."
* [[Evolve to freedom|"Evolve to freedom"]]
* [[Inventing a New Civilization on a Shoestring Budget|"Inventing a new civilization on a shoestring budget"]]
* Messages from [http://factorefarm.org/content/what-do-people-think-idea-ose discussion in Forum]
** "Building the world's first replicable, open source, off-grid Global Village"
** "Social transformation through off-grid villages"
** "Developing technology to enable easily copied high-tech resilient communities"
** "Open Source Ecology is a movement dedicated to the collaborative development of the world's first replicable, open source, modern off-grid global village"
** "The goal of Open Source Ecology is to develop an ecology of appropriate technology products and services that promote right livelihoods"

== About the GVCS ==
* "Just tools for living"

== Some notes on core messages in general ==
* To be effective, a core message must be short, simple and clear.
** Messages are shortened by leaving something out; there's no other way to do it.
** To say that one thing is "core" is to imply that other things are "not core".
* To be effective, a core message must be consistent.
** Inconsistency (using different core messages in different parts of the web site, for example) communicates indecisiveness.

== See also: ==

[[Category:Marketing]]

Core message

2009-07-28T02:57:38Z

Dan:

{{HdrMarketing}}
A 'core' message is a condensed message that helps explain what your goals are in an easy to remember phrase.

= Possible core messages =

== About OSE in general ==
* "Creating tools for building modern off-grid resilient communities that can be reproduced by anyone at low cost."
* "Building the world's first replicable, open source, modern off-grid global village - to transcend survival and evolve to freedom."
* "Our aim is the full integration of flexible small-scale manufacturing with sustainable agriculture."
* [[Evolve to freedom|"Evolve to freedom"]]
* [[Inventing a New Civilization on a Shoestring Budget|"Inventing a new civilization on a shoestring budget"]]
* Messages from [http://factorefarm.org/content/what-do-people-think-idea-ose|discussion in Forum]
** "Building the world's first replicable, open source, off-grid Global Village"
** "Social transformation through off-grid villages"
** "Developing technology to enable easily copied high-tech resilient communities"
** "Open Source Ecology is a movement dedicated to the collaborative development of the world's first replicable, open source, modern off-grid global village"
** "The goal of Open Source Ecology is to develop an ecology of appropriate technology products and services that promote right livelihoods"

== About the GVCS ==
* "Just tools for living"

== Some notes on core messages in general ==
* To be effective, a core message must be short, simple and clear.
** Messages are shortened by leaving something out; there's no other way to do it.
** To say that one thing is "core" is to imply that other things are "not core".
* To be effective, a core message must be consistent.
** Inconsistency (using different core messages in different parts of the web site, for example) communicates indecisiveness.

== See also: ==

[[Category:Marketing]]

Evolve to freedom

2009-07-28T02:28:22Z

Dan:

{{HdrMarketing}}
==So, you want more freedom?==

Does a 2 hour work day sound good to you? Are you tired of pushing paper all day, making money for somebody else, only to have precious rare moments and weekends to spare?
What if you could eliminate all bureaucracy in your life, plus your housing costs, your food costs, and your personal financial contribution to war? Here's the formula: be self-sufficient. Produce enough to provide yourself a quality life.

==How?!==
Gather a few of your friends, get yourself a 10 acre plot of land, install your [[Open_Source_Fab_Lab|Personal Fabrication Lab (Fab Lab)]], [[OSA|plant an orchard]], and [[Modular Housing Units|build a house with a greenhouse]].

With a [[Modular Greenhouse Units|greenhouse]], [[OSA|orchard]], a couple lactating animals, fishpond, and chickens, you've got 100% of your food needs covered. Add a [[Agricultural Microcombine|microcombine]], and you've got some grains.

With a personal Fab Lab and computer, with open source software and blueprints, you can fabricate your own [[Open_Source_Car|car]], [[LifeTrac]] tractor, and any other tech toys you like with the click of a mouse and some wrench turning.

A [[solar turbine]] feeds energy to your new stronghold of peace, with a few days storage in case the sun doesn't shine. The sun sends you no bills. But you might have to plant a fuel crop, or go to a local restaurant for waste oil, to make biodiesel on extremely cold days.

Go down to your local junkyard, get scrap metal, [[Foundry|cast it]], and you have your feedstocks for the Fab Lab, at the cost of materials.

Don't have enough money for an advanced Fab Lab? A 3D printer ([[RepRap]]) can be made for under $400, and requires nothing more powerful than an [[OLPC]] computer. A [[Multimachine]] open source drill-mill-lathe costs a few hundred in parts. Come to us and propagate for yourself a 300 tree [[orchard]] in a weekend workshop, free to friends.

Need a place to live? A high production [[CEB_press|compressed earth block press]] yields basic shelter from on-site dirt – or a legacy mansion if you like. It's the most advanced building method known to humankind, if ecology is considered.

Your junkyard closed out of metal because society eliminated all waste by lifetime design techniques? Then you need to extract aluminum from your onsite clays, in a furnace fueled by compressed gas produced from waste wood chips. Forget about conflicts for once rare resources.

==Dreamy but doable==
Well, it's not really as easy as that. You will need a team of 10 or
more skilled people who want to live right, visionary mindset
included.

For the rest of your life, do what you really want. Perhaps pressing
world issues are a concern of yours? Go ahead, work them. Or just a
little more attention to your personal evolution, so that all of
society can benefit? When you control your destiny, everyone benefits.

Now show me the money. Your three acres of orchard give $5k per
season, just by passive U-pick in the local area. People are attracted
to your showcase, and begin asking questions. That is valuable
conversation, and at the end you return to your Fab Lab, as you got an
order for an open source car – that's $1k dollar value earned for 20
hours of your time. Or, your tree propagation workshop brought in $1k
for the day, as your plant stock is abundant. A few small organic
farmers in your area are waiting for you to fill their microcombine
order. Or, the training workshop for earth block building. You can
roll in extra cash if you like, but your expenses are low, and you may
have more important things to do. Perhaps providing clean water or
gasifier stoves to the rest of the world, at a ridiculously affordable
cost?

We like to help others. Low on money and high on vision? Come to our
workshops, build yourself an infrastructure so you could live like
this, if you have lifetime durable equipment. Start with basics: car
at $2k; not bad for a high performance, low maintenance lifetime vehicle;
tractor at $2k, brick machine at $1k, greenhouse another
$1k; flex fab outfit, a large price item, $5k for all you need in
machine work and cutting jobs. Orchard literally free, and all of our
gene pool too, if you do the propagation work. And the glazing
comes from bioplastics onsite, or extruded waste plastic. Then you may need some immediate cash after you start up, because you wanted to buy some more books or other exotic merchandise. Maybe marketing products of other farmer scientist friends of yours will do the job as you get on your feet.

As your operations get off the ground, you cannot help but notice that everyone around you is going off-grid, starting to produce other open source items of Fab Lab industry, and those government workers are leaving town as they have no more problems left to solve or create.

[[Main Page|Evolve to freedom.]]
== See also: ==
[[Category:Marketing]]

Template:HdrOther

2009-07-28T02:26:45Z

Dan:

'''[[Main Page|Main]] => [[:Category:Other|Other]] ([[:Category:Marketing|Marketing]], [[:Category:Wiki|Wiki]])'''
----

Category:Marketing

2009-07-28T02:25:55Z

Dan:

{{HdrMarketing}}
* Category for everything related to marketing.
* [[:Template:HdrMarketing|Header template]]
=List of Blogs Contacted=
*Tiny Farm Blog - Mike is savvy in organizational work and social technology
*http://www.gonefarming.com/the-problem/comment-page-1/#comment-3 - IT and white collar people going organic
*Emailed Steven from Reality Sandwich
*https://www.blogger.com/comment.g?blogID=36903664&postID=3424874846085557874&pli=1 - invited author to the Factor e pow-wow.
== See also ==

[[Category:Emails Sent]]
[[Category:Other]]

Template:HdrMarketing

2009-07-28T02:24:11Z

Dan: Created page with ''''Main => Other => Marketing''' ----'

'''[[Main Page|Main]] => [[:Category:Other|Other]] => [[:Category:Marketing|Marketing]]'''
----

Core message

2009-07-28T02:22:59Z

Dan:

Talk:Wiki wish list

2009-07-28T02:03:20Z

Dan:

Created a draft of a new site header, along with subheaders for each package. I've implemented them in the energy category page so you can get a feel for them and discuss before refactoring through other packages.
----
* I figured how do the tooltips and made a few changes to Site Header 2 and ProjectHdr Habitat templates to illustrate.
* Style notes (IMHO)
** Never use CAPS FOR EMPHASIS (= SHOUTING)
** Never use <u>underlines for emphasis (= link)</u>
** No need to repeat the word "package" in every link, just put "Packages:" before the list
----
Agreed. The particular styles were in place to try and distinguish the packages from the whole array of projects in the original header. By breaking it down into a clean package only header and then subheaders for the projects the styling can be cleaned up and it should be easier to see what's going on.

* I've modified the project header for habitat to include the site header directly, that way people only need to include the project header and the other one is included by default. Also removed the seemingly redundant "Packages" from the beginning of the package only content, as the site header above seems to qualify that enough. Check out [[:Category:Habitat]] to see if it's headed in an acceptable direction.
----
# I see where you're going and I think it's a big improvement over what is presently in the wiki.
# We've been talking about "site header" but it really isn't. A page like [[Evolve to freedom]] doesn't fit into any of the packages or projects. It really needs a header like: '''Main -> Vision -> Freedom'''. We might want a Sawmill category with a header like: '''Main -> Packages -> Habitat -> Sawmill'''.
# I think your latest example works well for a 2-level hierarchy, but not so well for 3 or 4 levels.
# I personally (and this is a matter of style, not acceptable vs. unacceptable) favor extreme minimalism as to headers. People come to a page to read the contents, not the header. I'd rather hide the information for other levels inside tooltips than make it visible all the time.
# Think about what I've said here. If you're happy with your current example, go ahead and implement it. If I've convinced you of the value of minimalism, let's see if we can simplify it first.
----
* I agree that there is a lot that doesn't fit under the current package arrangement. There certainly needs to be a way of tying those things back into the overall navigation scheme. I'm not attached to anything I've presented, I was just aware that change was required, and usually the best way to decide how that change should progress is to get in there and start changing things, or presenting examples of what change might look like. That way we get an idea of what will and wont work, and what other things need to be considering within the changes.
* Where to from this point?
** How can the whole be divided up into segments that will make sense to visitors, and keep the information arranged logically?
** Would it make sense to have two (or more) top level domains, e.g. Philosophy and Practicality, or something along those lines?
** There will be generic information (refer current [[:Category:Materials]] category) that is generically useful across different packages, and currently doesn't seem to placed firmly within a package. I think there are a few like this where they need to be drawn into one of the existing packages (flex industry for materials for e.g.) or consider creating new sections. Most of materials could go under a resource extraction and recycling project/package within flex industry.
** I like the idea of breadcrumb style headers. Are you also thinking we would be better doing away with any forward links?
*** '''Main -> Packages -> Habitat'''
*** rather than:
*** '''Main -> Packages -> Habitat: CEB, Living Machines, Modular Housing, Sawmill'''
** It would make sense to go with the former, as you'd only be seeing that header on the habitat category page anyway, but it will require some method of highlighting the main packages within the category page so they stand out from the crowd. Perhaps every package category page has an introduction that bullet points the primary projects and gives an idea of progress/state for each?
----
# At some point we will run out of ideas, and it will be time to start editing. I don't think we're there yet (we're still coming up with better and better ideas).
# I think there should be several top level categories, at least these
#* Factor e (the physical location)
#* Packages (I don't like the word, but I'm not sure what would be better)
#* Vision (I like this better than Philosophy, which suggests the academic discipline)
# It will be impossible to come up with a hierarchy of categories, in advance, which will work perfectly for all the current pages and whatever pages will be added in the future. Materials is a good example of this. We just have to make a good effort and expect to refactor it now and again.
#* Pages can have more than one category
#* There can be more than one way to navigate to a particular page (although the breadcrumb menu will show the one, "official" path)
# I'm OK with breadcrumbs only, and no forward links, on most pages, but I think that the category pages, Habitat for example, have to have the forward links somewhere on the page, and it might as well be in the header. The forward links need to be set off visually from the breadcrumbs, maybe on a second line.
----
* Packages is a difficult one to escape. They are also "domains" in a sense, but that loses the implication of being packages of tech solutions fitting within the particular domain. They are also "sub-systems" within the larger system of a community. I'm sure something will be suggested or come up along the way.
* Your vision vs philosophy argument makes sense. I guess all philosophical references can be tied back to the original vision, so the category wouldn't be exclusive of such things (eg an entry discussing the ethical treatment of animals and arguments for free-range would fit under OSA, but also ties back to the vision for the whole operation, so would appear in both categories.)
* I think the main thing to come up with at this stage is the skeleton of the category structure and general principles to guide a common theme for laying out the entries within categories. Enough to provide consistency across the pre-existing work as it's refactored, and to guide any new additions in future. If we say that all project specific documents should be tied back to the project category, rather than the package category for instance, then in addition to making navigation easier and reducing orphaned pages we also make any future refactoring easier. For example:
** Do we want documents about steam engines tied back to the Energy package category? If we went that way we would have an energy package category page with potentially thousands of disparate entries without any organisation. If on the other hand it was determined that project-specific pages tied directly to their project category only, as much as possible, then it keeps the package category clean with mostly project category links and the few documents directly pertaining to the package category itself. So documents about energy in general might link directly to the energy package category.
* Are the following examples on the right track for the different levels of organisation? The bit in parenths are forward links.
*# At top level: '''Main (Factor e | Packages | Vision | etc )'''
*# At second level on packages category page: '''Main -> Packages (Habitat | Agroecology | Energy | Flexible Industry | Transport | Other | etc )'''
*# At third/package level on habitat package category page: '''Main -> Packages -> Habitat (CEB Press | Sawmill | etc )'''
*# At fourth/project level on CEB Press category page: '''Main -> Packages -> Habitat -> CEB Press'''
*# For all documents under the CEB press category this last header would be used, obviously not meaning to be exclusive of subcategories.
----
# This is very good! Time to make some changes and see how it looks.
# I started to make some header templates for the Wiki category pages.
#* The first thing I noticed was that Wiki needs a top-level supercategory Other. Something like this has to be done.
#* I've added a [[Using header templates|page describing the header templates]].
# If you'd like to put together a top-down skeleton category structure, go ahead. I tend to think this needs to be approached from the bottom up.
----
* Going top down in that way would leave us in a world of pain I think. If we produce draft headers to allow anyone playing with refactoring to work through things, and just include the sections that are done from the bottom up into the existing headers when they are ready then there shouldn't be any issues with existing stuff becoming inaccessible.
* I'll go through one of the smaller packages and do some refactoring according to the new scheme later in the week. There are sure to be other issues picked up as the system is actually implemented.
----
* I've been playing with this scheme in another wiki, and I've reached a few conclusions:
** '''=>''' looks better than '''->'''
** '''(Subcategory 1, Subcategory 2)''' looks better than '''(Subcategory 1 | Subcategory 2)'''
*** The commas are closer to English, which the vertical bar is used for wiki markup. Commas are less confusing all around.
* Bottom-up refactoring works pretty well
** There is a certain amount of overhead per category
** I don't get everything right the first time
** Refactoring a category is fairly easy, at least easier than setting up the category in the first place

Template:HdrOther

2009-07-28T01:55:39Z

Dan:

'''[[Main Page|Main]] => [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----

Using header templates

2009-07-28T01:55:04Z

Dan: /* Examples */

{{HdrWiki}}
= Overview =
* The wiki category system allows authors to group related pages together.
* The header templates build on the category system to provide a means for the reader to navigate to pages of interest.
* The category system is an ongoing process; as content is added, the category system will be refactored.
* The category system can be refactored by making changes only to the category pages and category header templates. The navigation headers for individual pages will automatically change along with the categories.
= Design principles =
# Every page has a "primary" category
#* This page has the primary category '''Wiki'''
# Every page has a navigation header based on its primary category
#* This page has the header '''HdrWiki'''
#* Pages may have multiple categories, but only one header
# Every category has a header
#* The Wiki category has a header named '''HdrWiki'''
#* The header template lists the supercategories '''Main => Major category => Minor category => This category'''
#* Followed by the subcategories, if any, in parentheses: '''(Subcategory 1, Subcategory 2)'''
#* Every category has a link to its header template

= Examples =
* Markup for this page's header
<pre>
{{HdrWiki}}
</pre>
* [[Template:HdrOther]]
<pre>
'''[[Main Page|Main]] => [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----
</pre>

= See also: =
* [[Using Categories]]
[[Category:Wiki]]

Using header templates

2009-07-28T01:54:31Z

Dan: /* Design principles */

{{HdrWiki}}
= Overview =
* The wiki category system allows authors to group related pages together.
* The header templates build on the category system to provide a means for the reader to navigate to pages of interest.
* The category system is an ongoing process; as content is added, the category system will be refactored.
* The category system can be refactored by making changes only to the category pages and category header templates. The navigation headers for individual pages will automatically change along with the categories.
= Design principles =
# Every page has a "primary" category
#* This page has the primary category '''Wiki'''
# Every page has a navigation header based on its primary category
#* This page has the header '''HdrWiki'''
#* Pages may have multiple categories, but only one header
# Every category has a header
#* The Wiki category has a header named '''HdrWiki'''
#* The header template lists the supercategories '''Main => Major category => Minor category => This category'''
#* Followed by the subcategories, if any, in parentheses: '''(Subcategory 1, Subcategory 2)'''
#* Every category has a link to its header template

= Examples =
* Markup for this page's header
<pre>
{{HdrWiki}}
</pre>
* [[Template:HdrOther]]
<pre>
'''[[Main Page|Main]] -> [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----
</pre>
= See also: =
* [[Using Categories]]
[[Category:Wiki]]

Template:HdrWiki

2009-07-28T01:52:31Z

Dan:

'''[[Main Page|Main]] => [[:Category:Other|Other]] => [[:Category:Wiki|Wiki]]'''
----

User talk:199.67.236.234

2009-07-22T04:12:10Z

Dan:

Tried to fix a type-o "reserach" -> "research." However, now the embedded google map is showing up as a link and not being interpreted correctly. Tried undo-ing my change, to no effect. Hoping this some strange problem with my browser . . .
----
* Not a browser problem. MediaWiki helpfully changes
<pre>
<ehtml> to <eehtml>, <eehtml> to <eeehtml>, etc. when you save the page.
</pre>
* The only quick workaround I see (other than an extension) is to set $wgRawHtml='true' in LocalSettings.php for a few minutes, make the edits, then set it back to false.
* Alternatively, you can set $wgRawHtml to true all the time, and restrict editing to approved users.
* Leaving $wgRawHtml set to true all the time and allowing just anyone to edit is asking for trouble.

Factor e Farm

2009-07-22T03:55:22Z

Dan:

[[Factor e Farm]] is the land-based facility where we put the ''theory'' of Open Source Ecology '''''into practice'''''. Factor e Farm is not a [http://www.sustainabletable.org/issues/factoryfarming/ factory farm]. Why [http://en.wikipedia.org/wiki/E_(mathematical_constant) e]? It is a transcendental number. We aim to transcend. We push towards open source. Factor 10 reduction in price. Or at least e. Ten times cheaper means ten times the freedom. It is Factor e improvement in quality of life. It is technology for ecology.

We started with 30 acres of raw land in rural Missouri - a former soybean field. We paid our last electricity bill three years ago. We are getting our power from waste vegetable oil and the sun. We drink pure free rain water. We grow most of our food. We are free. Welcome to our life. We want to help others do the same. Decentralization. Regain control of your life. Be your own boss. [[Evolve_to_freedom|Evolve to freedom.]]

<ehtml><center><object width="480" height="385"><param name="movie" value="http://www.youtube.com/p/FF0B396794CE6CDE&hl=en" /><embed src="http://www.youtube.com/p/FF0B396794CE6CDE&hl=en" type="application/x-shockwave-flash" width="480" height="385"></embed></object><br>Click the arrows to see another video.</center></ehtml>

The Factor e [[Distillations]] are a review of Factor e Farm in 2008.

<eehtml><center><object width="480" height="385"><param name="movie" value="http://www.youtube.com/p/8222E33C29B683CE&hl=en" /><embed src="http://www.youtube.com/p/8222E33C29B683CE&hl=en" type="application/x-shockwave-flash" width="480" height="385"></embed></object></center></eehtml>

See a slide show presentation about the [[First Year at Factor e Farm]], 2007.

<eehtml><center><embed id="VideoPlayback" src="http://video.google.com/googleplayer.swf?docid=-710075551990473235&hl=en&fs=true" style="width:400px;height:326px" allowFullScreen="true" allowScriptAccess="always" type="application/x-shockwave-flash"> </embed>
</center></eehtml>

[[Image:oekonuxtalk.jpg]]

[http://openfarmtech.org/weblog/?p=611 See the latest presentation from 2009, given at the Oekonux 4 Conference in Manchester, UK.]
=More Information=

See the [http://openfarmtech.org/weblog/ weblog] for the latest updates.

You can view videos from Factor e Farm on our [http://www.youtube.com/user/marcinose Youtube Channel.]

[http://www.flickr.com/photos/11113094@N03/ Pictures] from Factor e Farm.

See [http://factorefarm.org/ Factor e Farm.org] for discussion forums.

The core team members are the people at Factor e Farm who are engaged actively in the reserach and development program for the Resilient Community Construction Set (formerly called the Global Village Construction Set).

<eehtml>
<iframe width="425" height="350" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105613177309411485244.00046566d85d9fb56693f&ll=39.865297,-94.374259&spn=0.00722,0.005482&t=h&output=embed"></iframe><br /><small>View <a href="http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105613177309411485244.00046566d85d9fb56693f&ll=39.865297,-94.374259&spn=0.00722,0.005482&t=h&source=embed" style="color:#0000FF;text-align:left">Factor e Farm</a> in a larger map</small>
</eehtml>

=What it's like at Factor e Farm=

Definitions: ''Core Team'' or ''Factor e Farm Core Team'' or ''Factor e Core Team'' refers to the full time people at Factor e Farm, who are also involved in the research and development program.

Learn about what it's like at [[Factor e Farm]] before you come.

Current as of April 25, 2009.

We are on 30 acres in rural Missouri.

Shelter
[[image:Solar_cell.jpg|thumb]]
[[Image:Cordwood_Structure.jpg|thumb|Cordwood structure]]
[[image:Outside_Hexayurt.JPG|thumb|Hexayurt]]
[[image:Hexacube1.jpg|thumb|Hexacube]]

*[[Solar_Panels_at_Factor_e_Farm|We are totally off grid with solar panels]] that charge a forklift battery. Buildings are wired, including the new CEB workshop addition. We need to wire the two workshop silos, and install an electric fence charger for the goat pen.
*We have wood stoves in the cordwood, earthbag, and CEB workshop buildings. We have 4 acres of wooded area, but this is not sufficient to sustain all stoves without upgrading to efficient stoves, proper solar design, Babington burner option, and central hydronic heating. We aim to address these points by end of 2009.
*[[Solar Cubicle]]s are insulated, the CEB workshop is partly insulated, while earthbag and cordwood structures feature only thermal mass.
*Buildings:
**[[Earthbag hut]]
**[[Cordwood hut]] - Usual visitor area.
**[[Hexayurt]] - uninsulated
**2 [[Solar Cubicle]]s - $380 insulated housing unit built in one day
**[[CEB building]] and [[greenhouse]] - thermal mass retains heat
**Army tent
**[http://openfarmtech.org/weblog/?p=632 Solar Village] planned for 2009.

Water
*Hand pumped water well
*Roof rain water catchment system on greenhouse, with about 1000 gallon storage capacity. Pressure tank provides water to sink in earthbag structure, CEB addition sink and shower, plus greenhouse irrigation. Hose can be extended to water the garden. Well pumping can be automated via 3" submersible pump (not available) or a manual-to-motorized handpump converter (available). On-demand electric heater is installed for kitchen sink and shower.
*Next improvement will be a deep well - beneath bedrock at 100 feet - after we build an open source [[Well Rig]]

Electricity, Internet, and Fuel
*We presently have 1.4 kW of solar panels installed. This is sufficient to run lights, internet, appliances, and workshop tools without problems. It is ''not'' sufficient for extensive electricity usage, such as electric heaters, welders, or items left on when not needed. As such, people need to be conscious of energy usage. Battery voltage should be checked regularly (readout on inverter) to make sure there is no unaccounted energy usage or leakage. As a general rule, voltage should not go below 12.0 volts, and charging should not exceed 14.0 volts. The inverter shuts off automatically below 11 volts and above 15 volts. The overcharge condition can degrade the battery rapidly from its 20 year rated life.
*Higher power items, such as welder, are run off the tractor generator, which can produce 20 kW of electric power.
*Internet is provided. It can be supported easily all day by our available power, but it should be turned off whenever not in use.
*We make our own biodiesel for the [[LifeTrac]] tractor and Suburban farm truck.

Food
*400 tree fruit, nut, and berry orchard
*Garden with many raised beds planted out in 2009
*Asparagus and raspberries are presently available in abundance
*Orchard was planted 2 years ago from small trees.
*Chickens - eggs; [[Incubator]] recently open-sourced, and in testing. Abundant eggs and chicken meat expected later in 2009.
*Goats - milk; meat reserve if needed; present population of 7, with 2 males.
*We buy food that we don't grow on the farm
*Agricultural Permaculture tasks, landscaping, taking care of plants
*We try to eat together

Waste
*2 composting toilets as described at [[Composting Toilet]].
*3 compost bins
*Need to reestablish redworm population for vermiposting, as these have died out over winter.

Sanitation
[[Image:molly_sink.jpg|thumb]]
*Installed hot water, dish washing sink, and shower in CEB addition
*We have an indoors sink in the earthbag structure; pressure tank froze last winter, and this winter we aim to have the pressure tank in a heated space.

Finances
*Finances are handled individually. Factor e Farm provides electricity, internet, and Core Team members are responsible for their foo. Project See [[Transparency]]
*[[1000 True Fans]] campaign provides ongoing funding. Currently 38 subscribers.
*Project-based crowd funding is deployed via ChipIn and PayPal.
*Need to set up donation handling via Revolution Money Exchange.
*We (by Core Team principled consensus) will negotiate the level of financial responsibility and joining costs for prospective Core Team members based on the interests and resources of the applicant

Governance
*Priorities of the Resilient Community Construction Set (formerly called [[Global Village Construction Set]]) determine direction and funding allocation. Director of Research and Development is responsible for setting research and development priorities, as well as for determining necessary infrastructure improvements.
*Council of Elders settles disputes by mediation. Council of Elders is presently being recruited. Core Team selects Councils of Elders by ''principled consensus''. Anyone may bring up a topic for mediation, and in case of any objections, the decision to enter mediation will be determined by 'principled consensus' of all core team members.
*Board of Academic Advisors is currently being recruited.
*[[Rules of Conduct]]
*Core Team members are required to study consensus techniques and conflict resolution techniques. We expect all participants to accept the responsibility for effective conflict resolution.

Legal
*Legal structure and land tenure is discussed at [[Transparency]]

Learning
*DSL internet connection
*Wireless router
*We are not set up well for training Core Team members in various skills for living, research, and development work. We typically require prospective members to come with skills, and this point is negotiable.
*We are a learning community, and we are all expected to help each other grow in practical, mental, emotional, and spiritual techniques.

Tool Use
*People may use tools either:
**by bringing their own
**demonstrating proficiency in using and maintaining Factor e Farm tools
*We are also building various tools, and whoever builds one may also use it and teach others to use it

Build technology for ecology to easily provide the above and replicate it at low cost for others
*The [[Global Village Construction Set]]

We are seeking interns for our research and development program to help develop open source technology for building resilient communities. This includes designing and building "permanent agriculture," agricultural machines, infrastructure buildings, and metalworking products. We don't just make diagrams or theory, we make machines that help people achieve their dreams. Please consider [[Volunteer|volunteering]] at Factor e Farm.

[[Category:Factor e Farm]]

Talk:Wiki wish list

2009-07-22T02:36:17Z

Dan:

Using header templates

2009-07-22T02:30:16Z

Dan:

{{HdrWiki}}
= Overview =
* The wiki category system allows authors to group related pages together.
* The header templates build on the category system to provide a means for the reader to navigate to pages of interest.
* The category system is an ongoing process; as content is added, the category system will be refactored.
* The category system can be refactored by making changes only to the category pages and category header templates. The navigation headers for individual pages will automatically change along with the categories.
= Design principles =
# Every page has a "primary" category
#* This page has the primary category '''Wiki'''
# Every page has a navigation header based on its primary category
#* This page has the header '''HdrWiki'''
#* Pages may have multiple categories, but only one header
# Every category has a header
#* The Wiki category has a header named '''HdrWiki'''
#* The header template lists the supercategories '''Main -> Major category -> Minor category -> This category'''
#* Followed by the subcategories, if any, in parentheses: '''(Subcategory 1 | Subcategory 2)'''
#* Every category has a link to its header template
= Examples =
* Markup for this page's header
<pre>
{{HdrWiki}}
</pre>
* [[Template:HdrOther]]
<pre>
'''[[Main Page|Main]] -> [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----
</pre>
= See also: =
* [[Using Categories]]
[[Category:Wiki]]

Using header templates

2009-07-22T02:26:45Z

Dan: Created page with '{{HdrWiki}} = Overview = * The wiki category system allows authors to group related pages together. * The header templates build on the category system to provide a means for the...'

{{HdrWiki}}
= Overview =
* The wiki category system allows authors to group related pages together.
* The header templates build on the category system to provide a means for the reader to navigate to pages of interest.
* The category system is an ongoing process; as content is added, the category system will be refactored.
* The category system can be refactored by making changes only to the category pages and category header templates. The navigation headers for individual pages will automatically change along with the categories.
= Design principles =
# Every page has a "primary" category
#* This page has the primary category '''Wiki'''
# Every page has a navigation header based on its primary category
#* This page has the header '''HdrWiki'''
#* Pages may have multiple categories, but only one header
# Every category has a header
#* The Wiki category has a header named '''HdrWiki'''
#* The header template lists the supercategories '''Main -> Major category -> Minor category -> This category'''
#* Followed by the subcategories, if any, in parentheses: '''(Subcategory 1, Subcategory 2)'''
#* Every category has a link to its header template
= Examples =
* Markup for this page's header
<pre>
{{HdrWiki}}
</pre>
* [[Template:HdrOther]]
<pre>
'''[[Main Page|Main]] -> [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----
</pre>
= See also: =
* [[Using Categories]]
[[Category:Wiki]]

Wiki Documentation Standards

2009-07-22T02:05:56Z

Dan:

{{HdrWiki}}
=Introduction=

As the number of contributors to the OSE Wiki is growing, it is time to begin defining standards for content. Wikipedia is a good example of clear formatting and standards. Our standards are by nature more demanding, since we are not only re-presenting knowledge as Wikipedia does, but also developing/inegrating designs at the same time. A collaborative multimedia strategy for accomplishing this task successfully is yet to be defined and perfected. Our aim is to start this process, and make significant contibutions thereto.

=On OSE Wiki=

Todo items for wiki development:

* We need some kind of template flag to place at the top of each page, to show where it lives in [[Development Work Template]] process. (a couple of days work).

* We need to install semantic media wiki extensions, and refactor pages to include semantic links, which will help us bridge our work with the work of others in an open way(and allow a bridge between OSE Drupal and OSE Media Wiki, and other projects. (probably a 1 to 2 month project, if 4-5 people help). Also, within the wiki, this would allow us to flag dependencies in logical ways. We would need to analyze and create a realistic workflow for this. We can also help other wikis participate in [http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData LinkingOpenData] in this way (like appropedia). Then, we can start to build open source web applications that can let you logically combine data from multiple locations, and output a unique collection as pdf, a repository, a new wiki, etc.

* We may need to create templates for steps in the [[Development Work Template]] process.

* Invite some volunteers to help with the above.

==Using Category==

Media wiki offers an affordance that allows exporting whole collections of pages by category. Pages in media wiki may have multiple categories. So, we should use category both in the way that it is being used now, plus

==Workflow==

One mistake that Wikipedia makes is to make ambiguous rules that people then use as a foundation for different agendas.

Therefore, we need a *fair*, objective criteria for quality of articles:

1: No deletion (unless page is total spam). Space on OSE wiki is cheap. It is better to keep a page, and edit it, than to delete. Category system can be used to map pages that are considered to be part of specific collections (like actual projects in progress vs an idea).

2: We should use a system of flags at the top of pages that let people know what needs to be done.

Criteria could be:

* Content should follow [[OSE Specifications]] for replicability and ecological design
* There is a clear statement of purpose
* There are verifiable references to any claims made
* Templates are used where applicable
* pages maintain higher quality when they have maintainers. So, a page should list declared maintainer(s). These are the people who are responsible for creating, and upkeep of the page.

* please list anything I may be missing here...

=Exporting from wiki=

(draft in progress...not complete)

Structure your work stages according to [[Development Work Template]].

For each stage, first document text on wiki, as described above. This will allow others to work with you on text as project develops.

Click on Printable Version in left sidebar, right cick on page and save as "pagename.html" where pagename = the name of the wiki page.

Download Python http://www.python.org/download/releases/2.5/

Download Mercurial http://www.selenic.com/mercurial/wiki/

Place all of your files into a folder

navigate to that folder in your terminal (or Putty terminal in windows).

type "hg init"

This is will initiate the files into a repostiory of their own

Type "hg add", which will add your files to the repository.

Type "hg ci -m 'you notes and messages here'

Also usable: http://www.selenic.com/mercurial/wiki/index.cgi/OtherTools GUI clients for mercurial.

..more to come

[[Category:Status]]
[[Category:Software]]
[[Category:Documentation]]
[[Category:Wiki]]

Using Categories

2009-07-22T02:05:26Z

Dan:

{{HdrWiki}}
= Overview =
* Categories allow related pages to be grouped together easily.
* For example, if you have pages A, B, C and D, you could link A to B, C and D, and link B to A, C and D, and link C to A, B and D, and link D to A, B and C... or you could link A to category X, B to category X, C to category X and D to category X. You've created 4 links instead of 12. Category X will automatically link to A, B, C and D.
* The more related pages in a category, the better this works.

= Categorizing a new page =
* First, see if there is an [[:Special:Categories|existing category]] for the page.
* If so, create a link to the category at the bottom of the page. For example, this page is about using the wiki, so it belongs in the Wiki category:
<pre>
[[Category:Wiki]]
</pre>
* If a category belongs in more than one category, create a link for each category.

= Creating a new category =
* If no existing category really fits, make up a new category and create the link:
<pre>
[[Category:Cetaceans]]
</pre>
* Click on the category link and edit the category page.
** Describe what belongs in the category. Example:
<pre>
Whales, dolphins and related mammals.
</pre>
** If there's something similar that really belongs in a different but related category, point that out and link to the related category. Example:
<pre>
Seals and walruses are listed under [[:Category:Pinnipeds|Pinnipeds]].
</pre>
** If the category belongs to a larger category (for example, Cetaceans are aquatic mammals), create a link to the larger category:
<pre>
[[Category:Aquatic mammals]]
</pre>
= Linking to a category page =
* To link to the Wiki category page, prepend a colon so that the parser sees a link ([[:Category:Wiki]]) instead of a categorization:
<pre>
[[:Category:Wiki]]
</pre>
* To change the appearance of a category link, append a vertical bar and the desired text to display ([[:Category:Wiki|Style guide]]):
<pre>
[[:Category:Wiki|Style guide]]
</pre>
= Refactoring categories =
* These pages will assist:
** [[:Special:Categories|List of all categories]]
** [[:Special:UncategorizedPages|Pages without categories]]
** [[:Special:UnusedCategories|Categories without pages]]
** [[:Special:UncategorizedCategories|Categories without categories]]

= See also: =
* [http://www.mediawiki.org/wiki/Help:Categories MediaWiki help on Categories]
[[Category:Wiki]]

Template:HdrOther

2009-07-22T02:03:32Z

Dan:

'''[[Main Page|Main]] -> [[:Category:Other|Other]] ([[:Category:Wiki|Wiki]])'''
----

Template:HdrWiki

2009-07-22T02:01:27Z

Dan:

'''[[Main Page|Main]] -> [[:Category:Other|Other]] -> [[:Category:Wiki|Wiki]]'''
----

Wiki wish list

2009-07-22T02:00:35Z

Dan:

{{HdrWiki}}
= Categories needed =
= Pages needed =
* Using Templates
**Very important. Please document at [[Instructions]]
* Available Templates

= Refactoring needed =
= MediaWiki extensions needed =
* [http://www.mediawiki.org/wiki/Extension:CategoryTree CategoryTree] allows the category structure to be seen in outline form

= Clean-up needed =
* various spam pages need to be removed: "buy Cialis..." etc.
* There are also MANY pages in Chinese characters, probably spam also.

= Templates needed =
* A more compact Site header template, showing just the packages, with a tooltip for each package showing the projects within the package
** Not sure if this can be done without [http://www.mediawiki.org/wiki/Extension:Tooltip an extension]
** But the [http://en.wikipedia.org/wiki/Help:Pipe_trick Pipe trick] might help
** July 16: Pipe trick plus redirection will work, no need for tooltip extension
*** See [[Template:Site Header 2]] and [[Template:ProjectHdr Habitat]] for examples

= See also: =
[[Category:Wiki]]
*[[Template:Site Header 2]]
*[[Template:ProjectHdr Habitat]] - Header for use within Habitat package pages
*[[Template:ProjectHdr OSA]] - Header for use within OSA package pages
*[[Template:ProjectHdr Energy]] - Header for use within Energy package pages
*[[Template:ProjectHdr FIP]] - Header for use within Flexible Industry package pages
*[[Template:ProjectHdr Transport]] - Header for use within Transport package pages

Template:HdrWiki

2009-07-22T01:59:44Z

Dan:

'''[[Main Page|Main]] -> [[:Category:Other|Other]] -> Wiki'''
----

Category:Wiki

2009-07-22T01:59:16Z

Dan:

{{HdrWiki}}
* Pages to help authors use the wiki
** Syntax
** Style guide
= See also: =
* [[:Template:HdrWiki|Header template for Wiki]]
* [[:Category:Documentation|Documentation]] (focused on projects, and including but not limited to wiki pages)
[[Category:Other]]

Category:Wiki

2009-07-22T01:58:34Z

Dan:

Category:Wiki

2009-07-22T01:58:19Z

Dan:

{{HdrWiki}}
* Pages to help authors use the wiki
** Syntax
** Style guide
= See also: =
* [[:Template:Wiki|Header template for Wiki]]
* [[:Category:Documentation|Documentation]] (focused on projects, and including but not limited to wiki pages)

Category:Wiki

2009-07-22T01:57:27Z

Dan:

{{HdrWiki}}
* Pages to help authors use the wiki
** Syntax
** Style guide
= See also: =
* [[:Category:Documentation|Documentation]] (focused on projects, and including but not limited to wiki pages)

Template:HdrOther

2009-07-22T01:56:39Z

Dan:

'''[[Main Page|Main]] -> Other ([[:Category:Wiki|Wiki]])'''
----

Template:HdrOther

2009-07-22T01:56:23Z

Dan:

'''[[Main Page|Page]] -> Other ([[:Category:Wiki|Wiki]])'''
----

Template:HdrOther

2009-07-22T01:55:57Z

Dan: Created page with ''''Main Page -> Other (Wiki) ----'

'''[[Main|Main Page]] -> Other ([[:Category:Wiki|Wiki]])
----

Template:HdrWiki

2009-07-22T01:52:44Z

Dan: Created page with ''''Main -> Other -> Wiki''''

'''[[Main Page|Main]] -> [[:Category:Other|Other]] -> Wiki'''

Talk:Wiki wish list

2009-07-21T04:35:52Z

Dan:

Category:Agriculture

2009-07-21T04:10:06Z

Dan:

Agriculture is the process of producing food, feed, fiber and other desired products by cultivation of certain plants and the raising of domesticated animals. Agriculture is also known as farming.
= See also: =
* [[:Category:OSA|OSA (Open Source Agroecology category)]] (need to refactor)

Talk:Wiki wish list

2009-07-20T05:36:35Z

Dan:

Technological and Humanitarian Evolution

2009-07-17T22:40:59Z

Dan:

In a nutshell, strategically speaking - I think there is much more to be gained via open source agroecology (permaculture replicator + equipment pool + fabrication + ecoindustry) than by DIY Bio, unless your definition of DIY bio reaches beyond lab technique/equipment to permaculture replicator + ecoindustry of process design + materials handling equipment + fabrication thereof.

I believe that our main point of difference is the assumption on population. You imply that population will keep growing to about 100 times the present value, I imply that it will stabilize to approximately the same number of people as today up to 10 times that. I favor agroecological integration (natural limits of population determined by local resource use). It appears that you assuming that people will not ever stop and say 'enough is enough' on the human population issue. I think that they will, as they notice that production of everything in 'vats' just causes to much trouble by the pressures of human density. I am hoping that we never get to the point of finding this out first hand - as we retain a more ecologically integrated way of life.

You seemed to imply that DIY Bio will relieve the human density pressures. Not with so many selfish people out there. History is not showing signs of wisdom. So we might as well wisen up right now, because I smell trouble with the 'growing everything in test tubes' route. This route eliminates natural constraints on human greed and population.

Well, this all above is speculation...RE:

>I also follow the open farm tech group.
Intriguing. Not many people make this connection. My problem with OSE (as detailed in many email
conversations with Marcin) is that some crucial pieces of technology are missing.

The point to keep in mind is to demonstrate the synergies of an integrated ecology of technologies - and if this fails to produce hands-down unprecedented quality of life, then we will be moving forward to more 'exotic' technologies. Integration is our first avenue to unprecedented productivity, not point technologies. Essentially, we want to avoid the 'myth of technology' - the critique of technology that shows that further-evolved technology causes deepening problems - largely because humans and their organizational systems are incapable of managing the technology properly.

Therefore, our general approach is to optimize the simplest technology set - so that humans and their organizational systems are capable of managing them properly. To do this, one must begin with the simplest technology set.

This is all too heavy on the machinery and engineering side. If they really want "high-tech
neo-subsistence", as claimed, then synthetic biology or at least more biochemistry is in order.
I doubt that OSE will go there but I support them (I am a "true fan") because it's a useful set
of technologies. What your group is doing is producing another useful set. Putting them both
together eventually will create true neo-subsistence.

The priorities of OSE are chosen from a strategic perspective. If one is pursuing a boot-strapping approach, one moves from basic necessities to more exotic technologies. Therefore, one would pursue DIY Bio first under two major assumptions:
(1) assumption of external dependence on electromechanical infrastructure, (2) assumption that DIY Bio precedes integrated ecological design (permaculture and agroecology)

We are pursuing this program instead:

1. Mastery of all electromechanical infrastructure for all surviving, thriving, and neosubsistence tasks. This includes self-replicating fabrication capacity.
2. Use the above to master the built environment, direct solar energy provision, biofuel provision, food provision, and transportation needs. It should be noted that our goal on food provision is utilizing an integrated gene pool, which is in istelf self-replicating - together with productive machinere - to master food provision at any scale at the cost of 15 minutes per person per day.
3. From the standpoint of comfortable lifestyle resulting from achieving step 2 , develop import substitution - from the global to on-site resources - primarily for metals, semiconductors, rubber, plastic, and glass. This means technologies such as sand and clay converted to aluminum, silicon, glass, and ceramics; biomass to bioplastic; and dandelion latex to rubber.

Above all, it must be kept in mind that the program above is 'machinery and engineering' on the surface only. It is actually a humanitarian program of evolving beyond materials scarcity, so that this aspect can be eliminated as the driving force of civilization. I'm really interested in post-scarcity practice leading to more highly-evolved human beings.

One cannot forget that any other higher tech begins with the mundane materials handling, biofuel generation, direct solar conversion, fabrication, integrated gene pool - or many other horsepower-to-service conversion of energy to human service. This is what our 'machinery and engineering' is about. Materials provision (DIY Bio or agroecology or pyrolysis oil, etc) all rely on this electromechanical infrastructure. Hence, anyone interested in a better world should take this as the first priority for opensourcing - as mundane as it is.

Personally, I never thought I'd be getting into building tractors or machining equipment. It's just what needs to be done (opensourced) right now.

Thoughts?

Marcin
= See also: =
[[Category:Strategy]]

Using Categories

2009-07-17T05:43:38Z

Dan: /* See also: */

= Overview =
* Categories allow related pages to be grouped together easily.
* For example, if you have pages A, B, C and D, you could link A to B, C and D, and link B to A, C and D, and link C to A, B and D, and link D to A, B and C... or you could link A to category X, B to category X, C to category X and D to category X. You've created 4 links instead of 12. Category X will automatically link to A, B, C and D.
* The more related pages in a category, the better this works.

= Categorizing a new page =
* First, see if there is an [[:Special:Categories|existing category]] for the page.
* If so, create a link to the category at the bottom of the page. For example, this page is about using the wiki, so it belongs in the Wiki category:
<pre>
[[Category:Wiki]]
</pre>
* If a category belongs in more than one category, create a link for each category.

= Creating a new category =
* If no existing category really fits, make up a new category and create the link:
<pre>
[[Category:Cetaceans]]
</pre>
* Click on the category link and edit the category page.
** Describe what belongs in the category. Example:
<pre>
Whales, dolphins and related mammals.
</pre>
** If there's something similar that really belongs in a different but related category, point that out and link to the related category. Example:
<pre>
Seals and walruses are listed under [[:Category:Pinnipeds|Pinnipeds]].
</pre>
** If the category belongs to a larger category (for example, Cetaceans are aquatic mammals), create a link to the larger category:
<pre>
[[Category:Aquatic mammals]]
</pre>
= Linking to a category page =
* To link to the Wiki category page, prepend a colon so that the parser sees a link ([[:Category:Wiki]]) instead of a categorization:
<pre>
[[:Category:Wiki]]
</pre>
* To change the appearance of a category link, append a vertical bar and the desired text to display ([[:Category:Wiki|Style guide]]):
<pre>
[[:Category:Wiki|Style guide]]
</pre>
= Refactoring categories =
* These pages will assist:
** [[:Special:Categories|List of all categories]]
** [[:Special:UncategorizedPages|Pages without categories]]
** [[:Special:UnusedCategories|Categories without pages]]
** [[:Special:UncategorizedCategories|Categories without categories]]

= See also: =
* [http://www.mediawiki.org/wiki/Help:Categories MediaWiki help on Categories]
[[Category:Wiki]]

Template:ProjectHdr Habitat

2009-07-17T02:35:44Z

Dan:

'''[[Packages overview|Packages]]''' -> '''[[:Category:Habitat|Habitat]]''' -> '''[[CEB Press]]''' - '''[[Living Machines]]''' - '''[[Modular Housing Units]]''' - '''[[Sawmill]]'''
----

Category:Habitat

2009-07-17T02:35:05Z

Dan:

{{ProjectHdr Habitat}}
{{Site header}}

Things that help you live, like housing and sanitation.

[[Category:Global Village Construction Set]]

Template:Site Header 2

2009-07-17T02:34:20Z

Dan:

[[Packages overview|Packages]] -> [[:Category:Habitat (CEB Press - Living Machines - Modular Housing Units - Sawmill)|Habitat]],
[[:Category:OSA|Agroecology]],
[[:Category:Energy|Energy]],
[[:Category:Flexible_Industry|Flexible Industry]],
[[:Category:Transportation|Transportation]],
[[:Category:Materials|Materials]]
----------------

Talk:Wiki wish list

2009-07-17T02:33:17Z

Dan:

Talk:Wiki wish list

2009-07-17T02:31:33Z

Dan:

Template:ProjectHdr Habitat

2009-07-17T02:25:51Z

Dan:

'''[[Packages overview|Packages]]''' -> '''[[:Category:Habitat|Habitat]]''' -> '''[[CEB Press]]''' - '''[[Living Machines]]''' - '''[[Modular Housing Units]]''' - '''[[Sawmill]]'''

Template:ProjectHdr Habitat

2009-07-17T02:24:46Z

Dan:

[[Packages overview|Packages]] -> [[:Category:Habitat|Habitat]] -> '''[[CEB Press]]''' - [[Living Machines]] - [[Modular Housing Units]] - '''[[Sawmill]]'''

Template:Site Header 2

2009-07-17T02:22:30Z

Dan:

[[Packages overview]] -> [[:Category:Habitat (CEB Press - Living Machines - Modular Housing Units - Sawmill)|Habitat]],
[[:Category:OSA|Agroecology]],
[[:Category:Energy|Energy]],
[[:Category:Flexible_Industry|Flexible Industry]],
[[:Category:Transportation|Transportation]],
[[:Category:Materials|Materials]]
----------------

Wiki wish list

2009-07-17T02:20:55Z

Dan: /* Templates needed */

= Categories needed =
= Pages needed =
* Using Templates
* Available Templates

= Refactoring needed =
= MediaWiki extensions needed =
* [http://www.mediawiki.org/wiki/Extension:CategoryTree CategoryTree] allows the category structure to be seen in outline form

= Clean-up needed =
* various spam pages need to be removed: "buy Cialis..." etc.
* There are also MANY pages in Chinese characters, probably spam also.

= Templates needed =
* A more compact Site header template, showing just the packages, with a tooltip for each package showing the projects within the package
** Not sure if this can be done without [http://www.mediawiki.org/wiki/Extension:Tooltip an extension]
** But the [http://en.wikipedia.org/wiki/Help:Pipe_trick Pipe trick] might help
** July 16: Pipe trick plus redirection will work, no need for tooltip extension
*** See [[Template:Site Header 2]] and [[Template:ProjectHdr Habitat]] for examples

= See also: =
[[Category:Wiki]]
*[[Template:Site Header 2]]
*[[Template:ProjectHdr Habitat]] - Header for use within Habitat package pages
*[[Template:ProjectHdr OSA]] - Header for use within OSA package pages
*[[Template:ProjectHdr Energy]] - Header for use within Energy package pages
*[[Template:ProjectHdr FIP]] - Header for use within Flexible Industry package pages
*[[Template:ProjectHdr Transport]] - Header for use within Transport package pages

Wiki wish list

2009-07-17T02:20:28Z

Dan: /* Templates needed */

= Categories needed =
= Pages needed =
* Using Templates
* Available Templates

= Refactoring needed =
= MediaWiki extensions needed =
* [http://www.mediawiki.org/wiki/Extension:CategoryTree CategoryTree] allows the category structure to be seen in outline form

= Clean-up needed =
* various spam pages need to be removed: "buy Cialis..." etc.
* There are also MANY pages in Chinese characters, probably spam also.

= Templates needed =
* A more compact Site header template, showing just the packages, with a tooltip for each package showing the projects within the package
** Not sure if this can be done without [http://www.mediawiki.org/wiki/Extension:Tooltip an extension]
** But the [http://en.wikipedia.org/wiki/Help:Pipe_trick Pipe trick] might help
** July 16: Pipe trick plus redirection will work, no need for tooltip extension
*** See [[Template:Site header 2]] and [[Template:ProjectHdrHabitat]] for examples

= See also: =
[[Category:Wiki]]
*[[Template:Site Header 2]]
*[[Template:ProjectHdr Habitat]] - Header for use within Habitat package pages
*[[Template:ProjectHdr OSA]] - Header for use within OSA package pages
*[[Template:ProjectHdr Energy]] - Header for use within Energy package pages
*[[Template:ProjectHdr FIP]] - Header for use within Flexible Industry package pages
*[[Template:ProjectHdr Transport]] - Header for use within Transport package pages

Template:ProjectHdr Habitat

2009-07-17T02:18:26Z

Dan:

[[Packages overview|Packages]] -> [[:Category:Habitat|Habitat]] -> '''[[CEB Press]]''' - '''[[Sawmill]]''' - [[Living Machines]] - [[Modular Housing Units]]

Category:Habitat (CEB Press - Living Machines - Modular Housing Units - Sawmill)

2009-07-17T02:13:35Z

Dan: Redirected page to Category:Habitat

#Redirect [[:Category:Habitat]]

Template:Site Header 2

2009-07-17T02:12:28Z

Dan:

Packages: [[:Category:Habitat (CEB Press - Living Machines - Modular Housing Units - Sawmill)|Habitat]],
[[:Category:OSA|Agroecology]],
[[:Category:Energy|Energy]],
[[:Category:Flexible_Industry|Flexible Industry]],
[[:Category:Transportation|Transportation]],
[[:Category:Materials|Materials]]
----------------

Wiki wish list

2009-07-16T05:01:51Z

Dan: /* Templates needed */