View source

You do not have permission to edit pages, for the following reason:
The action you have requested is limited to users in the group Users.
You can view and copy the source of this page:
<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#Admins|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#Admins|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. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)

ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .


Wiki area suggestion:
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .

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? - [[User:Tantek|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 [[User:Neuro|neuro]] at 88.190.224.126.
* ...

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

* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]
** noted here for tracking purposes.
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)

=== web server ===
* Investigate an upgrade of PHP from 5.2.
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)

=== irc ===
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ 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.

* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)

=== wiki ===
==== for site update to microformats2 ====
* about
** create [[about]] from updated version of http://microformats.org/about
** change "about" link to /wiki/about

* get-started
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2

===== update wiki skin to mf2 =====
See: 
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]
* update any other classic microformats markup in the 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
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)

===== 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: 
** do a diff between microformats.org wiki and the old version of MW
** see what's different between the two, then we can see what the likely cause of the problems are
** perhaps document differences on our [[mediawiki customization]] page for future better troubleshooting

===== Password reset page problems =====
Password reset page doesn't work:
* http://microformats.org/wiki/Special:PasswordReset
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]

==== 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 [https://www.mediawiki.org/wiki/Extension:AbuseFilter 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 [http://www.mediawiki.org/wiki/Extension:TitleBlacklist 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 [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* add a class, <code>noprint</code> 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 <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and  perhaps (other) x-protocols to be linkified
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]

===== misc requests =====
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.
* 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 admins sidebar (quick ban list access)
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> 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.
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.

=== 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:

* consider create a new forum on microformats.org
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)

== 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 [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]

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

Waiting-for: 
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))

== 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 ====
<div class="discussion">
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. [[User:Tantek|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. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)
</div>

* 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 integrated
* - No OpenID


== related ==
* [[to-do]]
* [[admins]]
* [[admin-how-to]]
Return to admin-to-do.
Retrieved from "http://microformats.org/wiki/admin-to-do"
Views

Microformats Wiki

Toolbox

Hey! You're not logged in
