admin to-do

(Difference between revisions)

Jump to: navigation, search
(MediaWiki needs updating)
Current revision (20:01, 31 May 2019) (view source)
(wiki: link to notes on /mediawiki_customization)
 
(15 intermediate revisions not shown.)
Line 13: Line 13:
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]].
-
Main site home page:
+
Mirror server requests:
-
* 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.
+
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.
-
** +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] .
+
Admins Mailing list deliverability
 +
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons
 +
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '
 +
** Authentication-Results: mx.google.com;
 +
      dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;
 +
      spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org
 +
== server migration project ==
-
Wiki area suggestion:
+
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.
-
*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.
+
=== blog ===
 +
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.
-
This implementation should be done on all other duplicate content pages of the website.
+
tasks that need a volunteer:
 +
* check that the theme works in a new version of WordPress
 +
* check that the current WordPress database can handle being upgraded to new WordPress
-
* 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)
+
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.
 +
=== wiki ===
 +
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki.
-
Mirror server requests:
+
Things to check:
-
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.
+
 
-
* ...
+
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW
 +
** is there a new recaptcha plugin? some other way to prevent spam accounts?
 +
** (please list out more extensions here)
 +
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?
 +
 
 +
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)
== next actions and projects ==
== next actions and projects ==
Line 42: Line 57:
=== web server ===
=== web server ===
-
* Investigate an upgrade of PHP from 5.2.
+
==== HTTPS ====
 +
HTTPS / TLS / SSL support:
 +
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.
 +
 
 +
==== upgrade PHP ====
 +
* Investigate an upgrade of PHP  
** 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)
** 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)
 +
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)
 +
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)
=== irc ===
=== irc ===
Line 51: Line 73:
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)
 +
 +
=== web site ===
 +
==== home page ====
 +
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] .
 +
 +
==== blog ====
 +
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.
 +
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki>
=== wiki ===
=== wiki ===
 +
==== proper redirects to avoid dupes ====
 +
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)
 +
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)
 +
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)
 +
==== for site update to microformats2 ====
==== for site update to microformats2 ====
* about
* about
Line 66: Line 112:
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]
* 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
* update any other classic microformats markup in the skin to mf2
 +
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)
 +
 +
==== 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 ====
==== wiki problems ====
Problems with the microformats wiki that an admin needs to look at and resolve:
Problems with the microformats wiki that an admin needs to look at and resolve:
 +
===== reCAPTCHA replacement =====
 +
reCAPTCHA replacement needed
 +
* had to edit out the https from a link above to get this to save.
 +
===== MediaWiki needs updating =====
===== MediaWiki needs updating =====
MediaWiki needs updating
MediaWiki needs updating
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]
* 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)
** 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 problems =====
Line 96: Line 144:
==== wiki feature requests ====
==== wiki feature requests ====
 +
===== handle feedback =====
 +
* Process [[wiki-feedback]] and add items here accordingly.
===== spam fighting =====
===== 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 [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.
Line 153: Line 203:
Per GTD, here are next-actions for admins that are awaiting some external dependency.
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:
+
Waiting-for:  
-
* 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)
+
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:
-
** 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.
+
** 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))
-
*** 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?
+
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)
-
**** You could always install the OpenID extension and then use Apache to block access to ''Special:OpenIDServer''.
+
*** ping [[Tantek]] to finish user renaming fix.
-
 
+
== someday maybe ==
== someday maybe ==

Current revision

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.

Contents

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.

Mirror server requests:

Admins Mailing list deliverability

      dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;
      spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org

server migration project

The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.

blog

The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.

tasks that need a volunteer:

If you would like to help out with either of these, get in touch with aaronpk and he can provide you with a copy of the files.

wiki

MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki.

Things to check:

next actions and projects

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

web server

HTTPS

HTTPS / TLS / SSL support:

upgrade PHP

irc

web site

home page

Main site home page:

ex: Homepage with the right box implemented .

blog

wiki

proper redirects to avoid dupes

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.

for site update to microformats2

update wiki skin to mf2

See:

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:

reCAPTCHA replacement

reCAPTCHA replacement needed

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

handle feedback
spam fighting
semantic requests
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:

waiting for

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

Waiting-for:

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 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)
  • 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

Launchpad

Ben Ward has ‘microformats’ on Launchpad

Github


related

admin to-do was last modified: Friday, May 31st, 2019

Views