admin-to-do: Difference between revisions

Latest revision as of 17:12, 28 April 2021

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.

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:

Note that requests from 88.190.13.197 are for a mirror server run by neuro at 88.190.224.126.
...

next actions and projects

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

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! - Tantek 13:33, 15 September 2013 (UTC)

irc

Pibb integration for the #microformats IRC channel. It is relatively simple to 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. 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. Tantek 13:32, 15 September 2013 (UTC)

ex: 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: https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800.
- Todo: Publish all theme sources on GitHub: https://chat.indieweb.org/microformats/2018-06-28/1530198611202600

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? - Tantek 13:32, 15 September 2013 (UTC)
- MediaWiki has a config for this as of v1.21.0. Reference: https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink gRegor 01:14, 21 June 2018 (UTC)
- IIRC new MediaWiki has an option to do real redirects as well Aaronpk 18:27, 15 February 2019 (UTC)

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
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. 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.

IndieAuth login

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

wiki problems

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

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. 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

handle feedback

Process wiki-feedback and add items here accordingly.

spam fighting

Install 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 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 Version Page for a list of currently installed extensions on the English Wikipedia.
- I'd personally advise getting Cite, ParserFunctions --JimboJW 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)
- HTML Profiles - allows people editing the wiki to add URIs to <head profile> TobyInk 16:52, 9 March 2009 (UTC)
  - +1 Tantek 09:58, 25 June 2009 (UTC)
- Link Attributes - allows easy-ish setting of rel/rev/class attributes on links. TobyInk 16:52, 9 March 2009 (UTC)
  - +1 Tantek 09:58, 25 June 2009 (UTC)
add a class, noprint 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 webcal://, javascript: (for posting favelets/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified
- +1 Tantek 09:58, 25 June 2009 (UTC)
Would be great to have a video template that embeds an object. Tantek 09:58, 25 June 2009 (UTC)
Can we imply entry-title from h1? 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 input 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 help page on mediawiki.org and 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 pages awaiting deletion

waiting for

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

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)
- ping Tantek to finish user renaming fix (who can't remember what was the user renaming fix issue/task now Tantek (talk) 17:12, 28 April 2021 (UTC))

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

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)

Investigate possibility/feasibility 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

done

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

2020-07-18 the admin mailing list has been moved to Google Groups (talk)

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.

This migration has been completed! Some notes and resources are available on GitHub (admin-only repo) Aaronpk (talk) 17:23, 19 July 2020 (UTC)

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:

check that the theme works in a new version of WordPress
check that the current WordPress database can handle being upgraded to new WordPress

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:

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. gRegor 20:01, 31 May 2019 (UTC)

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.
Certificate is running, but http-to-https redirects are not in place, pending further discussion Aaronpk (talk) 17:27, 19 July 2020 (UTC)

upgrade PHP

Investigate an upgrade of PHP
- PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [1]. Upgrading to PHP7 might be a good idea currently. gRegor 19:40, 9 May 2017 (UTC)
- +1 agreed. Pfefferle 17:58, 28 June 2018 (UTC)
- this will be taken care of in the server migration project above Aaronpk 18:27, 15 February 2019 (UTC)
The server is running PHP 7.4 now Aaronpk (talk) 17:23, 19 July 2020 (UTC)

wiki problems

reCAPTCHA replacement

reCAPTCHA replacement needed

had to edit out the https from a link above to get this to save.
reCAPTCHA has been removed, account creation currently requires contacting an admin Aaronpk (talk) 17:23, 19 July 2020 (UTC)

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. Aaronpk 21:48, 4 December 2017 (UTC)
The wiki has been updated, reverted to the default Vector theme Aaronpk (talk) 17:23, 19 July 2020 (UTC)

@@ Line 1: / Line 1: @@
-<entry-title>admin to-do</entry-title>
+{{DISPLAYTITLE:admin to-do}}
 Filtered and processed [[to-do]] items specifically for [[admins]].
@@ 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]].
+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)
+=== 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)
+=== 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.
@@ Line 19: / Line 40: @@
 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 ===
+==== 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 .
@@ Line 28: / Line 54: @@
 * 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 ====
+* about
+** create [[about]] from updated version of http://microformats.org/about
+** change "about" link to /wiki/about
-Mirror server requests:
+* get-started
-* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.
+** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2
-* ...
-== 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]]
+===== update wiki skin to mf2 =====
-** noted here for tracking purposes.
+See:
-*** 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)
+* 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
+* 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)
-=== web server ===
+==== more spec styling ====
-* redirect www.microformats.* to canonical microformats.org URLs.
+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.
-* Investigate an upgrade of PHP from 5.2.
-=== irc ===
+We should do the same for [[stub specifications]] and update [[process]] accordingly as well.
-* 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.
+==== IndieAuth login ====
+* 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))
-=== wiki ===
 ==== wiki problems ====
 Problems with the microformats wiki that an admin needs to look at and resolve:
-* MediaWiki needs updating
+===== Password reset page problems =====
-** Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]
+Password reset page doesn't work:
+* http://microformats.org/wiki/Special:PasswordReset
-* http://microformats.org/wiki/Special:Version looks weird
+* 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]
-** 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 doesn't work:
-** http://microformats.org/wiki/Special:PasswordReset
 ==== wiki documentation ====
@@ Line 75: / Line 97: @@
 ==== wiki feature requests ====
+===== handle feedback =====
+* Process [[wiki-feedback]] and add items here accordingly.
 ===== 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.
-* Create an equivalent to Wikipedia's [https://en.wikipedia.org/wiki/Wikipedia:User_access_levels#Autoconfirmed_users autoconfirmed right] and add the equivalent of semi-protection. See [https://www.mediawiki.org/wiki/Manual:Autoconfirmed_users mediawiki.org documentation]. Suggested by [[User:TomMorris|tommorris]] on [http://indiewebcamp.com/irc/2013-03-14#t1363275893 #indiewebcamp on 2013-03-14]. This will allow admins to semi-protect key pages (main page, hCard spec and other popularly referred to specs): given that WHATWG/W3C now point to microformats.org from the HTML spec, ensuring it is spam-free seems sensible.
-** 2013-083 I've created autoconfirmed with a couple of settings for time and number of edits, and disabled page moves for non-autoconfirmed users. What do you mean by "add the equivalent of semi-protection" ? - [[User:Tantek|Tantek]] 17:50, 24 March 2013 (UTC)
-* Require email confirmation of new users before they can create or edit pages.
-** requiring email confirmation is pretty easy, just a tweak to LocalSettings.php - http://wiki.johnjosephbachir.org/Requiring_Email_Confirmation_to_Edit_in_MediaWiki (from Tom Morris)
 * 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)
@@ Line 136: / Line 156: @@
 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:
+* 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)
-* 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)
+** ping [[Tantek]] to finish user renaming fix (who can't remember what was the user renaming fix issue/task now [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]]) 17:12, 28 April 2021 (UTC))
-** 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.
-*** 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?
-**** You could always install the OpenID extension and then use Apache to block access to ''Special:OpenIDServer''.
 == someday maybe ==
@@ Line 155: / Line 171: @@
 * 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
+* Investigate possibility/feasibility 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
@@ Line 206: / Line 223: @@
 =====Github=====
 * + Git repository for test cases, libraries
-* - Issue tracking is external (Lighthouse)
+* + Issue tracking is integrated
 * - No OpenID
+== done ==
+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
+* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] ([[User talk:Aaronpk|talk]])
+=== 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.
+This migration has been completed! Some notes and resources are available [https://github.com/microformats/wiki on GitHub (admin-only repo)] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)
+==== 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:
+* check that the theme works in a new version of WordPress
+* check that the current WordPress database can handle being upgraded to new WordPress
+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.
+Things to check:
+* 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)
+=== 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.
+* Certificate is running, but http-to-https redirects are not in place, pending further discussion [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:27, 19 July 2020 (UTC)
+==== 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)
+** +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)
+* The server is running PHP 7.4 now [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)
+=== wiki problems ===
+===== reCAPTCHA replacement =====
+reCAPTCHA replacement needed
+* had to edit out the https from a link above to get this to save.
+* reCAPTCHA has been removed, account creation currently requires contacting an admin [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)
+===== 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)
+* The wiki has been updated, reverted to the default Vector theme [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)
 == related ==

admin-to-do: Difference between revisions

Latest revision as of 17:12, 28 April 2021

inbox

next actions and projects

irc

web site

home page

blog

wiki

proper redirects to avoid dupes

for site update to microformats2

update wiki skin to mf2

more spec styling

IndieAuth login

wiki problems

Password reset page problems

wiki documentation

wiki feature requests

handle feedback

spam fighting

semantic requests

misc requests

forum

ongoing

waiting for

someday maybe

someday actions

someday maybe projects

improved issue tracking

Custom Install of Trac

Google Code

Launchpad

Github

done

server migration project

blog

wiki

web server

HTTPS

upgrade PHP

wiki problems

reCAPTCHA replacement

MediaWiki needs updating

related

Navigation menu

Search