2016 01_Meeting

See also the 2016-01 Meeting IRC Log

Proposal to close issues

Agenda

• https://github.com/phpmyadmin/phpmyadmin/issues/6078

--Ibennetch 20:09, 11 November 2015 (CET)

• https://github.com/phpmyadmin/phpmyadmin/issues/11688

--Lem9 16:02, 24 November 2015 (CET)

• https://github.com/phpmyadmin/phpmyadmin/issues/11841

--Lem9 12:47, 13 January 2016 (CET)

Meeting

Two issues were closed due to lack of feedback.

Old bugs -> Known limitations ?

Agenda

Some old bugs are probably not worth fixing, either because they are edge case or the solution would be tricky. Maybe we can close them and use FAQ 3 (Known limitations) to document them? Found these examples:

• https://github.com/phpmyadmin/phpmyadmin/issues/9673
• https://github.com/phpmyadmin/phpmyadmin/issues/11231

--Lem9 14:48, 22 November 2015 (CET)

Meeting

One issue was closed and the remaining issue was clarified in the issue tracker.

Enhancements discussion

Agenda

• https://github.com/phpmyadmin/phpmyadmin/issues/6350
  • I would prefer that unhex() in exports be treated as an option (off by default)

--Lem9 11:50, 22 December 2015 (CET)

Meeting

It is agreed to treat it as an option but set 'off' by default.

Vote on membership changes

Agenda

Smita and Hugues wish to step down as a team member.

--Lem9 23:06, 27 December 2015 (CET)

Meeting

Both resignations are accepted, with our thanks for the work of both contributors.

Suggesting a donation amount

Agenda

To increase the amount of donations from the general public, we could suggest a donation amount, on the Donate page, the Download page and maybe as a tooltip on the Download button. I think that some users would be glad to get an hint about how much to donate.

--Lem9 14:35, 7 January 2016 (CET)

Meeting

It's agreed to put a suggested donation amount on the donation page and add some text suggesting a donation to the download page.

LoginCookieValidity

Agenda

After reading https://github.com/phpmyadmin/phpmyadmin/pull/11844 I would like a discussion to confirm that LoginCookieValidity is still a good idea. I believe so but maybe I'm blinded by my inertia.

--Lem9 22:11, 11 January 2016 (CET)

Meeting

We agree that it's still needed, as administrators need a way to be able to restrict session validity and will want better control than relying on the PHP gc_maxlifetime.

Meetings