admin-to-do: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(removing spam fighting requests - we seem to be okay on that front now)
(→‎wiki problems: possible special:version garbage culprit: mediawiki-entry-title-override)
Line 58: Line 58:


* http://microformats.org/wiki/Special:Version looks weird
* http://microformats.org/wiki/Special:Version looks weird
** suggested culprit from cweiske: https://github.com/microformats/mediawiki-entry-title-override (so maybe that needs debugging in this case?)
** suggested troubleshooting from Tom Morris:  
** suggested troubleshooting from Tom Morris:  
*** do a diff between microformats.org wiki and the old version of MW
*** do a diff between microformats.org wiki and the old version of MW

Revision as of 18:07, 27 February 2014

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

Only 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.

Related: admin-how-to.

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.

Main site home page:

  • The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.
    • +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. Tantek 13:32, 15 September 2013 (UTC)

ex: Homepage with the right box implemented .


Wiki area suggestion:

To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.

This implementation should be done on all other duplicate content pages of the website.

  • This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - Tantek 13:32, 15 September 2013 (UTC)


Mirror server requests:

  • Note that requests from 88.190.13.197 are for a mirror server run by neuro at 88.190.224.126.
  • ...

next actions and projects

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

web server

  • redirect www.microformats.* to canonical microformats.org URLs.
  • Investigate an upgrade of PHP from 5.2.

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

wiki problems

Problems with the microformats wiki that an admin needs to look at and resolve:

  • MediaWiki needs updating
    • Last time update attempt broke the theme, didn't have time time debug and fix. - User:BenWard

wiki documentation

Need more documentation about how we have the wiki setup, so more admins are able to fix/update it.

  • Update our mediawiki customization documentation with specifically:
    • What plug-ins/add-ons are installed?
    • What customizations / patches have been made to MediaWiki?
    • What special things does the microformats mediawiki theme depend on?
    • User:BenWard likely best knows these things.

wiki feature requests

spam fighting
  • Install AbuseFilter. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.
  • Install TitleBlackList Extension and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.
  • Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)
    • also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)
semantic requests
  • Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.
  • 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)
  • 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.
  • Allow webcal://, javascript: (for posting favelets/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)
  • Can we imply entry-title from h1? Tantek
misc requests

forum

In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.

If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:

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 IRC
  • 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)
  • I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. Garbee 00:43, 3 June 2013 (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

Retrieved from "http://microformats.org/wiki/index.php?title=admin-to-do&oldid=64226"