89
edits
Let.sysops.be: Difference between revisions
Jump to navigation
Jump to search
Fix links
GreenReaper (talk | contribs) (→License: Remove spam) |
GreenReaper (talk | contribs) (Fix links) |
||
| Line 2: | Line 2: | ||
wiki_logo = [[Image:lsb_logo.JPG]] | wiki_logo = [[Image:lsb_logo.JPG]] | ||
| wiki_URL = http://let.sysops.be | | wiki_URL = http://let.sysops.be | ||
| wiki_recentchanges_URL = http://let.sysops.be/ | | wiki_recentchanges_URL = http://let.sysops.be/wiki/Special:Recent_changes | ||
| wiki_wikinode_URL = No | | wiki_wikinode_URL = No | ||
| wiki_status = Active | | wiki_status = Active | ||
| Line 12: | Line 12: | ||
'''let.sysops.be''' deals with the professional issues of the shift to P2P and to user-authored content (so-called [[web 2.0]], [[wiki]]-centric). Major assumptions include the [[right to leave]] hosts without losing data or [[technical barrier]]s (including the ability to [[fork wiki]]s very easily as guaranteed by [[open content]] and [[open configuration]]), democratization of naming, flattening of namespaces, and [[trolls]]. | '''let.sysops.be''' deals with the professional issues of the shift to P2P and to user-authored content (so-called [[web 2.0]], [[wiki]]-centric). Major assumptions include the [[right to leave]] hosts without losing data or [[technical barrier]]s (including the ability to [[fork wiki]]s very easily as guaranteed by [[open content]] and [[open configuration]]), democratization of naming, flattening of namespaces, and [[trolls]]. | ||
*the essay on [http://let.sysops.be/ | *the essay on [http://let.sysops.be/wiki/The_real_web_3.0 the real web 3.0] provides a good starting point to understand the scope of coverage | ||
== Not for beginners == | == Not for beginners == | ||
The target audience appears to be software and service architects and perhaps academics and students. It maintains a [http://let.sysops.be/ | The target audience appears to be software and service architects and perhaps academics and students. It maintains a [http://let.sysops.be/wiki/Category:Defensible list of articles on topics that are considered defensible], though the references on many articles are weak. It also maintains a [http://let.sysops.be/wiki/Categpory:Praxis list of practices actually used]. These seem to take some pressure off to allow more speculative or opinionated statements on pages without these tags. This is one of many good practices followed in this wiki. | ||
=== Design economics === | === Design economics === | ||
| Line 23: | Line 23: | ||
Among the most immediately useful articles on design economics and metaphors include: | Among the most immediately useful articles on design economics and metaphors include: | ||
*[http://let.sysops.be/ | *[http://let.sysops.be/wiki/Mediawiki_gronks a sadly long list of ways mediawiki confuses users] | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Category:capital_asset categorization of capital assets] and the explanation of the [http://let.sysops.be/wiki/Capital_asset_model way they combine to create value] | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Twelve_levers definition of the twelve levers] and Forrester's Law | ||
*definition of the [http://let.sysops.be/ | *definition of the [http://let.sysops.be/wiki/Five_levels_of_intranet five levels of intranet] | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Reactive_process definition of a reactive process] | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Category:Reflective catalogue of reflective methods], or "heuristics", that improve aspects of a system while ultimate guidance remains external | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Category:Wiki many many articles on organizing aspects of wiki] | ||
*the state of the art [http://let.sysops.be/ | *the state of the art [http://let.sysops.be/wiki/Wiki_best_practice wiki best practice] list | ||
For the more political aspects it often defers to definitions at [[openpolitics.ca]], [[SourceWatch]], [[embodimentwiki.org]] (an even more sophisticated psychology/biology wiki). A central political question is who controls the editorial and governance path on a shared web service like a wiki. The [http://let.sysops.be/ | For the more political aspects it often defers to definitions at [[openpolitics.ca]], [[SourceWatch]], [[embodimentwiki.org]] (an even more sophisticated psychology/biology wiki). A central political question is who controls the editorial and governance path on a shared web service like a wiki. The [http://let.sysops.be/wiki/Category:Trolling many articles dealing with trolls and trolling] making the assumption appropriate to P2P, that they must be dealt with as equals. ''This is why P2P best describes this wiki's purpose.'' | ||
=== Technical coverage === | === Technical coverage === | ||
Technical coverage is no less sophisticated. The level of discourse is high and includes most or all of the very hardest problems in security, hardware, software and online service design. Some of the interesting technical material for wikiindex users includes: | Technical coverage is no less sophisticated. The level of discourse is high and includes most or all of the very hardest problems in security, hardware, software and online service design. Some of the interesting technical material for wikiindex users includes: | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Open_configuration definition of open configuration] which lays out the terms of reference to integrate P2P with conventional/mainframish [[web host]] | ||
*the [http://let.sysops.be/ | *the [http://let.sysops.be/wiki/Open_host more detailed definition of an open host] which would make it possible to move all services (email, web hosting, wikis) around like P2P services | ||
*explanation of the [http://let.sysops.be/ | *explanation of the [http://let.sysops.be/wiki/Verb/noun/type verb/noun/type] API design theory | ||
*explanation of the [http://let.sysops.be/ | *explanation of the [http://let.sysops.be/wiki/Key_trade responsibilities of security personnel] | ||
*explanation of the [http://let.sysops.be/ | *explanation of the [http://let.sysops.be/wiki/Net_trade responsibilities of network operators] | ||
*a preliminary [http://let.sysops.be/ | *a preliminary [http://let.sysops.be/wiki/Infra_trade stack description of the various trades] that are emerging given the responsibilities in a mixed P2P/web universe | ||
== Teaching wiki == | == Teaching wiki == | ||
| Line 50: | Line 50: | ||
=== Good examples === | === Good examples === | ||
This category scheme seems to be the major feature of this wiki. To put it simply, every infrastructural aspect of hardware and connectivity to get to the first wiki edit is defined as part of infrastructure and [http://let.sysops.be/ | This category scheme seems to be the major feature of this wiki. To put it simply, every infrastructural aspect of hardware and connectivity to get to the first wiki edit is defined as part of infrastructure and [http://let.sysops.be/wiki/Category:Infra goes in one category 'infra'], as everything social and financial (like selling and training) that happens after that [http://let.sysops.be/wiki/Category:Ultra goes in another category 'ultra']. The [[first wiki edit]] is treated as the most important distinction of all! | ||
Other good examples of best practice include: | Other good examples of best practice include: | ||
*[http://let.sysops.be/category_as_tag redirecting names of categories to the category] and treating them as just another tag, and always using singular not plural forms (as tags do) | *[http://let.sysops.be/wiki/category_as_tag redirecting names of categories to the category] and treating them as just another tag, and always using singular not plural forms (as tags do) | ||
*as mentioned above, dealing with precedent and credibility with separate "[http://let.sysops.be/ | *as mentioned above, dealing with precedent and credibility with separate "[http://let.sysops.be/wiki/Category:Defensible defensible]" and "[http://category:praxis empirical practice]" tags | ||
*keeping controversial terms in their own "[http://let.sysops.be/ | *keeping controversial terms in their own "[http://let.sysops.be/wiki/Term:Namespace term namespace]" so that the wiki won't be seen to be sanctioning any deprecated terminology | ||
*keeping command terms that have specific meanings in REST protocols (like "get") in a "[http://let.sysops.be/ | *keeping command terms that have specific meanings in REST protocols (like "get") in a "[http://let.sysops.be/wiki/Verb:Namespace verb namespace]" to keep the strict technological meaning separate from the ordinary conversation meaning | ||
*keeping good documentation of internal practices such as [http://let.sysops.be/ | *keeping good documentation of internal practices such as [http://let.sysops.be/wiki/Edit_summary_tag edit summary tag]s and [http://let.sysops.be/wiki/page_name_prefix page name prefix]es | ||
*insisting articles [http://let.sysops.be/ | *insisting articles [http://let.sysops.be/wiki/Adopt_Wikipedia_names adopt Wikipedia names] when talking about roughly the same topic, and further adopting their naming conventions | ||
The entire wiki, which is named '''eg''', is designed to make it easy to copy and cut out all content not relevant to a specific purpose, while keeping as many pages as possible. | The entire wiki, which is named '''eg''', is designed to make it easy to copy and cut out all content not relevant to a specific purpose, while keeping as many pages as possible. | ||