Clone this wiki locally
See also the 2014-06 Meeting IRC Log.
Revising the README file
In particular, the list of copyrights is outdated, or is it ? What are the implications of this list?
Can we remove the names and just say "The phpMyAdmin team"? (maybe with a link to the team page)
- Moodle: "Copyright 1999 onwards Martin Dougiamas"
- Joomla: they mention the not-for-profit company (Open Source Matters) and a range of years
- Drupal: "All Drupal code is Copyright 2001 - 2012 by the original authors."
According to http://www.gnu.org/licenses/gpl-howto.en.html the Copyright notice should be in each file; I believe we talked about this with Conservancy but I'm not sure of the outcome.
We'll contact Conservancy to see if it's permissible to change the Copyright section to "Copyright © 1998 onwards -- the phpMyAdmin team".
Michal will contact Conservancy and Isaac will prune down README in the next few days. We discussed merging README and README.rst in to one file, but since README is distributed to end users and README.rst is really for GitHub's home page, we decided to leave both as separate files.
Supporting version 4.0
According to our downloads page, support for version 4.0 series will end soon (Jul 1, 2014). Since versions 4.1 and 4.2 required MySQL version 5.5, should the support deadline be extended? Or has MySQL 5.5 enough adoptions for phpMyAdmin to end support on Jul 1, 2014?
--Madhuracj 20:13, 5 June 2014 (CEST)
We feel it's important to continue security updates for 4.0 at least until 1 January 2015. At that time, support for 4.1 also ends; we may continue security fixes for 4.0 without continuing 4.1 (as users can upgrade easily from 4.1 to 4.2, but not from 4.0 to 4.2 if their MySQL is old). We want to encourage users to upgrade their MySQL without angering them.
About the "Navigate away" patch
There are some issues with a patch merged for https://sourceforge.net/p/phpmyadmin/feature-requests/1518/, see https://sourceforge.net/p/phpmyadmin/bugs/4415. Should we revert?
--Lem9 14:33, 6 June 2014 (CEST)
We'll report more bugs and problems in the tracker. This feature will exist for now and we'll try to get it fixed to "release-ready" status by 4.3-alpha, or revert it.