admin to-do

(Difference between revisions)

Jump to: navigation, search
(Version looks weird: Special:Version fixed thanks to gRegorLove discovering a likely culprit (it was in a nearby file) escape HTML tags in plugin descriptions)
(inbox: yes we need HTTPS - moving here from to-do)
Line 12: Line 12:
== inbox ==
== inbox ==
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].
HTTPS / TLS / SSL support:
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for and 301 redirect HTTP requests to HTTPS.
Main site home page:
Main site home page:

Revision as of 00:54, 31 December 2018

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.



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.

HTTPS / TLS / SSL support:

Main site home page:

ex: Homepage with the right box implemented .

Wiki area suggestion:

To eliminate this problem, the 2nd page, in the <head> section of the source code, should contain the following line <link rel="canonical" href="" />. 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.

Mirror server requests:

Admins Mailing list deliverability

      dkim=neutral (body hash did not verify) header.s=20161025 header.b=NpEH0xA1;
      spf=pass ( best guess record for domain of designates as permitted sender)

reCAPTCHA replacement needed

next actions and projects

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

web server



for site update to microformats2

update wiki skin to mf2


more spec styling

We have specifications and draft specifications which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.

We should do the same for stub specifications and update process accordingly as well.

wiki problems

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

MediaWiki needs updating

MediaWiki needs updating

Password reset page problems

Password reset page doesn't work:

wiki documentation

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

wiki feature requests

spam fighting
semantic requests
misc requests


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 and as neeeded duties/tasks:

waiting for

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


someday maybe

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

someday actions

someday maybe projects

improved issue tracking

Issue tracking at 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)
  • Note that a few specs have started tracking issues on GitHub, e.g. h-entry Aaronpk 21:47, 4 December 2017 (UTC)
Custom Install of Trac

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


Ben Ward has ‘microformats’ on Launchpad



admin to-do was last modified: Wednesday, December 31st, 1969