Loading...
 

Green web

''The Green web standards are one of several concerns that must be addressed in an IT centre. Genuine green web (and email) service:

A green web applies these web best practices, listed in order of importance (0 being beyond dispute and 10 being the least important:)

technical problem spotters


0. actually meeting RFC 2142 IETF standards for email role address, e.g. postmaster, hostmaster, webmaster, "must all be live and attended to properly whether or not actual role accounts exist. Traffic to those addresses must be logged centrally for *any* net domain hosted. Other addresses relevant to services, e.g. wikimaster, critmaster, SMSmaster, ircmaster, newsmaster, as required in same format. No one must be forced to look up service role addresses, or guess their internal routing, and extensions must be obvious.

10. network security at least intelligent enough to *notice* a Satan (software) attack.

party officers


1. Email forwarding - all mail can be forwarded from any account to anywhere, can be received as a forward from anywhere, without limitations; webmail forwarded to another account with one button; future web-based email to that account can be forwarded with auto-notification of change of email address with no bounces and no losses for at least one full year after service contract ceases;temporary and permanent 'away' and 'vacation' type notices; easy forwarding to pagers/worn devices, and simple email aliasing; easy to track what aliases are in effect, and to compile mail to each alias in different folders; role accounts are controlled by the organization that assigns them, not the individual

1a. Organizational control of any and all accounts that may be reasonably interpreted to being role accounts, e.g. "policy@"; As per wiki best practice, such names must be discouraged in favour of real names and obvious troll names including IP numbers.

2. archived backups of all mail sent to officers in a web-based account, and all contents of web site can be one-click downloaded as sit/hqx (Mac), zip (PC), tar/gzip (Unix) archive; (webmail account limits are immaterial if this is in effect).

3. means to authenticate users for sensitive access control - ideally, web of trust and PKI certificate control, with quorum keying (i.e. 2 of 3 trusted parties must authorize any release of the trusting party's key, with statements like "yes he is dead, I saw the body, release the info to his successor XX at XX.org)."; archives encoded using public key so that only the receiver can decode them; SSL access to web based email and forward confirmation; longer term, a credential and sovereign identity model

policy publicists (including candidates)


4. resilient web streamlining - mis-spelt, mis-capitalized, and outright WRONG URLs go to a list of reasonable equivalents, for any publicity-based site (i.e. those that don't exploit security by obscurity and unadvertised URLs, thus would not want those to be visible in any automatic search).

For instance openpolitics.ca/forest resolves to a reasonable list of pages. Eventually greenparty.on.ca/forest must resolve to a list of possible references to "forest", "forestry", "wood products" and "silviculture", as established by a thesaurus and a search engine. See permalink and green URIs.

4a. Also any other HTTP-redirects required after services cease must be supported for at least six months after termination of any contracts. It must be possible to have the same URLs supported at another provider of web services, and give substantially simlar results, e.g. not the same search engine necessarily, but an equivalent good list of 'hits'. This is particularly hard to do if nonsensical technology dependent strings such as "/tiki-index.php?" show up in bookmarks, as they presently do unwisely at openpolitics.ca itself. Removing this is one of the most important OP upgrades

5. web indexing - it must be very easy for any official communications director to know what areas of the web service are indexed by streamlining searches, and by general searches by search engines such as google or yahoo, and in what categories the site is listed in directories and other major index sources.Ideally visibility will be compiled using a multi-search engine and some utilities to make it easy (a bunch of web forms all linked to a single page) to change classification, alter XML/HTML meta tags, or other activities that change the way web materials appear in index and search engine. It must be particularly easy to *remove* an area from search engine scrutiny, so that it doesn't show up in any queries by the public (e.g. of members' web content which may contain statements the party doesn't want identified with itself but stores for discussion purposes). For example, the distinction between Living Agenda and Living Platform pages in the Green Party of Canada Living Platform.

8. easy subhosting, e.g. niagara.greenparty.on.ca or other regional or factional sub-sites ought to be easy to set up without waiting for permission, and should be handled using the same systems as are used to set up new email addresses and such. Hostmaster notification and 48 hour approval ought to be automatic.

9. easy secure means to transfer roles and their function, i.e. not only is it possible to change roles and account names, it is easy for a non-technophile to do, like a secretary of a political party, who might have no expertise in the technologies used.

content editors and contributors


6. one-page management of all external links from a given domain/website; easy to see what is out-linked to, and if it has changed recently, and ideally if it *should* change, i.e.someone suggests a better link with annotation-ware, an attached comment, crit.org, thirdvoice, or some other utility.

Good link ethics and management of out-links in general, tracking of this and responses to statements made there about the site (i.e. technorati tags on a page count the same as an 'external link from' the site rather than as a 'link to' as would be assumed by those who don't think much about annotation mechanics).

7. Support for managing pages using wikitext or some other format that is provably learnable by novices and very widely supported. At present, only mediawiki and getwiki support any such standard. The use of textile is not recommended as drupal has serious deficiencies in its model and management. See wiki best practice for more.

The green business web, open politics web, and Genuine Green Web recommendations extend the above.

This page is CC-by-nc-sa by Efficient Civics Guild.