admin to-do

(Difference between revisions)

Jump to: navigation, search
(document current state of server migration project)
(some more details)
Line 26: Line 26:
== server migration project ==
== server migration project ==
-
The current web server is so far out of date that any sort of incremental migration plan is a futile effort. (PHP is too old to upgrade MediaWiki, the OS is too old to upgrade PHP, etc.) Instead, we need 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.
+
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 ===
=== blog ===
Line 44: Line 44:
* 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
* 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
-
** (please list out extensions here)
+
** 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?
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?
Line 61: Line 62:
==== upgrade PHP ====
==== upgrade PHP ====
-
* Investigate an upgrade of PHP from 5.2.
+
* 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)
** +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 95: Line 97:
* 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)
* 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)
** 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 ====
Line 109: 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 ====
==== more spec styling ====

Revision as of 18:27, 15 February 2019

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

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: Wednesday, December 31st, 1969

Views