admin to-do

(Difference between revisions)

Jump to: navigation, search
(inbox: yes we need HTTPS - moving here from to-do)
(process a bunch of inbox items into discrete categorized subsections below)
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 microformats.org and 301 redirect HTTP requests to HTTPS.
 
-
 
-
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] .
 
-
 
-
* 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 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)
 
-
 
Mirror server requests:
Mirror server requests:
Line 46: Line 23:
       dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;
       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
       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
-
 
-
reCAPTCHA replacement needed
 
-
* I had to edit out the https from  link above to get this to save.
 
== next actions and projects ==
== next actions and projects ==
Line 58: Line 32:
=== web server ===
=== web server ===
 +
==== 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 from 5.2.
* 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)
** 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)
Line 68: Line 47:
* 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)
 +
==== for site update to microformats2 ====
==== for site update to microformats2 ====
* about
* about
Line 91: Line 93:
==== 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)
-
 
-
 
===== Password reset page problems =====
===== Password reset page problems =====

Revision as of 17:19, 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.

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

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