admin-to-do

From Microformats Wiki
admin-to-do /
Revision as of 23:47, 1 April 2011 by Tantek (talk | contribs) (→‎ongoing: expand a bit with known areas that have needed work)
Jump to navigation Jump to search

<entry-title>admin to-do</entry-title> Filtered and processed To Do items specifically for microformats admins.

Only microformats admins should edit this page with non-minor edits.

Please add to-do suggestions for admins to the general to-do page's Admins section. Thanks!

Items here may list who originally suggested the item on the To Do page.


inbox

Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the to-do page's Admins section.

  • ...


next actions and projects

Per GTD, here are processed next-actions for admins, grouped by area/project

irc

  • Pibb integration for the #microformats IRC channel. It is relatively simple to embed the Pibb chat widget into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. User:Chris_Messina 16:50, 31 Aug 2007 (PDT)
  • maintainer for mfbot. Ryan King has indicated that he no longer has time to maintain mfbot and would like another admin to pick up the maintenance and running of mfbot.

wiki

  • Set up a cron job to export the wiki database (without user details), and make it available in a public location.
  • Add Extensions - especially those that help implement more microformats on the wiki itself!
    • Evaluate against Wikipedia's Version Page for a list of currently installed extensions on the English Wikipedia.
    • I'd personally advise getting Cite, ParserFunctions --JimboJW 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)
    • HTML Profiles - allows people editing the wiki to add URIs to <head profile> TobyInk 16:52, 9 March 2009 (UTC)
      • +1 Tantek 09:58, 25 June 2009 (UTC)
    • Link Attributes - allows easy-ish setting of rel/rev/class attributes on links. TobyInk 16:52, 9 March 2009 (UTC)
      • +1 Tantek 09:58, 25 June 2009 (UTC)
  • Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) User:RobManson 14:00, 20 Jul 2007 (AEST)
  • add a class, noprint to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.
    • ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.
  • Add admins sidebar (quick ban list access)
  • Allow webcal://, javascript: (for posting bookmarklets/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified
    • +1 Tantek 09:58, 25 June 2009 (UTC)
  • Would be great to have a video template that embeds an object. Tantek 09:58, 25 June 2009 (UTC)
  • Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse input element
  • Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content should not be sub-optimally edited according to the requirements of the CMS.
  • Can we imply entry-title from h1? Tantek


ongoing

Ongoing and as neeeded duties/tasks:

  • Delete spam and block spammers from the wiki.
  • Send emails to the microformats list(s) guiding the community per our Mailing Lists guidelines.
  • Helped out with questions on #microformats chat
  • Accepted / filtered comments on the blog (or posted!)
  • Help with web server matintenence:
    • Apache (reboot Apache if it hangs, debug Apache server problems)
    • WordPress (including upgrading installs as needed)
    • Mailman (clearing of internal spam queues)
    • MediaWiki (upgrades, help package mods for resubmission back to core)
  • Provide guidance to other admins
  • Remove pages awaiting deletion

waiting for

Per GTD, here are next-actions for admins that are awaiting some external dependency.

Waiting-for: a decent OpenID user experience for the OpenID MediaWiki plugin, in order to:

  • install and make available OpenID login, on behalf of a requests a while ago from User:DanC and User:Chris_Messina (especially for comments in WordPress). User:Chris_Messina 16:50, 31 Aug 2007 (PDT)
    • The plug-in is installed, but the user experience of exposing it to commenting visitors is poor. There's no other registration function, so it's not being pushed for the time being.
      • Regarding OpenID Log-in. Needs lightweight extension. Current extension turns the wiki into an OpenID *provider*. DO NOT WANT. Anyone want to write a simple OpenID login extension for MediaWiki?
        • You could always install the OpenID extension and then use Apache to block access to Special:OpenIDServer.


someday maybe

Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.

someday actions

  • Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)

someday maybe projects

improved issue tracking

Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.

  • I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. Tantek 02:38, 10 September 2009 (UTC)
  • Investigate possibility/santity of using Launchpad/Github/Google Code for spec issue tracking
  • Wiki is excellent documentation tool. Terrible issue tracking tool.
  • External services avoid large maintenance burden
  • Could better handle this todo list
  • Better handle issue resolutions
  • Better handle issue discussions
  • Evaluate options
    • Consider integration points with µf.org
    • Consider open standards a plus (OpenID)
    • Consider effort in porting existing content
  • Copy over issues from each wiki page as standalone bugs
  • Ensure that each spec editor is added with suitable authorities to manage issues
Custom Install of Trac
  • + Reliable
  • + Well Established
  • + Can customise to look like µf.org
  • + Flexible milestones etc.
  • + Hook into source repository of our choosing
  • + OpenID support
  • + Support whatever licensing we like
  • - Administration overhead

Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?

Google Code

Chris Messina has ‘microformats’ on Google Code

  • + Reliably Hosted, minimal admin overhead
  • + Very flexible milestones/tagging
  • + SVN repository for test cases, libraries
  • - Can't be styled to µf.org
  • - No OpenID
  • - Ugly as sin
  • - No Public Domain license support
Launchpad

Ben Ward has ‘microformats’ on Launchpad

  • + BZR repository for test cases, libraries
  • + Public Domain License Support
  • - Not instantly intuitive
  • - Seems better suited to software than specifications
  • - Can't style like µf.org, but, quite pretty
  • - No OpenID
Github
  • + Git repository for test cases, libraries
  • - Issue tracking is external (Lighthouse)
  • - No OpenID


related