put-it-on-the-wiki: Difference between revisions
LicodEldar (talk | contribs) (zelmonela) |
WebOrganics (talk | contribs) (Undo revision 36112 by LicodEldar (Talk)(vandalism)) |
||
Line 1: | Line 1: | ||
<h1>Put it on the wiki</h1> | <h1>Put it on the wiki</h1> | ||
Revision as of 17:16, 20 December 2008
Put it on the wiki
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.
In general, use the wiki to capture state, and email lists only for notification when possible.
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.
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.
- geo examples in the wild
- hCalendar examples in the wild
- hCard examples in the wild
- hReview examples in the wild
- Include-Pattern examples in the wild (various types of microformat, using the include-pattern)
- ... please add more links to "Examples in the Wild" pages and sections of specs.
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.
Better than emailing, blog about it!