Difference between revisions of "put-it-on-the-wiki"

From Microformats Wiki
put-it-on-the-wiki
Jump to navigation Jump to search
(related wiki-better-than-email)
(add short video explaining wikis better than email, simplify language a bit)
Line 1: Line 1:
<h1>Put it on the wiki</h1>
+
<entry-title>Put it on the wiki</entry-title>
  
As stated in the [[mailing-lists]] general guidelines, maximizing the signal-to-noise ratio (S/N) on the email lists is important.  In addition, we don't want to lose good content in the pile of emails that goes across the lists. Thus here are some concrete examples, learned from experience with the lists, for when it is better to add information to the wiki directly rather than send email.
+
As stated in the [[mailing-lists]] general guidelines, maximizing the signal-to-noise ratio (S/N) on the email lists is important.  In addition, we don't want to lose good content in the pile of emails that goes across the lists. We've learned from experience that it's better to add information to the wiki directly rather than send email.
  
In general, use the wiki to capture state, and email lists only for notification when possible.
+
== wikis in plain english ==
 +
Here is a short video explaining how wikis work much better than email for collaboration, even for something as simple as planning a camping trip.
  
By creating more content on the wiki rather than the mailing lists we grow our community memory and knowledge in a way that can be much more easily searched, referenced, and discovered, as mailing list archives are quite impenetrable and make it difficult to determine what the current "state" is of any particular discussion.
+
[http://www.youtube.com/watch?v=-dnL00TdmLY YouTube: Wikis in Plain English]
 +
 
 +
== content belongs on the wiki ==
 +
Please add any substantial content to the wiki and use email only for referring to the URLs on the wiki accordingly.  If you're not sure where to add something, ask in IRC or email.
 +
 
 +
By creating more content on the wiki rather than the mailing lists we grow our community memory and knowledge in a way that can be much more easily searched, referenced, linked, and discovered, as mailing list archives are quite impenetrable and make it difficult to determine what the current "state" is of any particular discussion.
  
 
== Examples of microformats usage ==
 
== Examples of microformats usage ==
 
 
If you have examples of microformats usage, please go ahead and add them to the respective [[examples-in-the-wild]] page or section. E.g.
 
If you have examples of microformats usage, please go ahead and add them to the respective [[examples-in-the-wild]] page or section. E.g.
 
* [[geo-examples-in-wild|geo examples in the wild]]
 
* [[geo-examples-in-wild|geo examples in the wild]]
Line 18: Line 23:
  
 
Since new examples are often useful for others' understanding, and for developers' parser testing, if you like you are also encouraged to send email to the [mailto:microformats-discuss@microformats.org microformats-discuss] mailing list announcing your support of specific microformats, with URLs to the respective examples in the wild pages/sections on the wiki and noting that you have added your site and the specific URLs with the microformats to those examples in the wild pages/sections.
 
Since new examples are often useful for others' understanding, and for developers' parser testing, if you like you are also encouraged to send email to the [mailto:microformats-discuss@microformats.org microformats-discuss] mailing list announcing your support of specific microformats, with URLs to the respective examples in the wild pages/sections on the wiki and noting that you have added your site and the specific URLs with the microformats to those examples in the wild pages/sections.
 
Better than emailing, blog about it!
 
  
 
== related ==
 
== related ==

Revision as of 19:59, 15 June 2009

<entry-title>Put it on the wiki</entry-title>

As stated in the Mailing Lists general guidelines, maximizing the signal-to-noise ratio (S/N) on the email lists is important. In addition, we don't want to lose good content in the pile of emails that goes across the lists. We've learned from experience that it's better to add information to the wiki directly rather than send email.

wikis in plain english

Here is a short video explaining how wikis work much better than email for collaboration, even for something as simple as planning a camping trip.

YouTube: Wikis in Plain English

content belongs on the wiki

Please add any substantial content to the wiki and use email only for referring to the URLs on the wiki accordingly. If you're not sure where to add something, ask in IRC or email.

By creating more content on the wiki rather than the mailing lists we grow our community memory and knowledge in a way that can be much more easily searched, referenced, linked, and discovered, as mailing list archives are quite impenetrable and make it difficult to determine what the current "state" is of any particular discussion.

Examples of microformats usage

If you have examples of microformats usage, please go ahead and add them to the respective examples-in-the-wild page or section. E.g.

Since new examples are often useful for others' understanding, and for developers' parser testing, if you like you are also encouraged to send email to the microformats-discuss mailing list announcing your support of specific microformats, with URLs to the respective examples in the wild pages/sections on the wiki and noting that you have added your site and the specific URLs with the microformats to those examples in the wild pages/sections.

related