-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
2013 09_Meeting
IRC meeting for September 2013, there is also 2013-09 Meeting IRC Log.
I will report current status of our membership in Conservancy. Nijel 17:18, 11 September 2013 (CEST)
- We've solved all obstacles which blocked joining Conservancy.
- The official announcement should come in next days.
- We will close our PayPal account and use Conservancy one.
- We will add some mentions to our website, something like on https://git-scm.com
Currently phpMyAdmin server is shared with Michal's stuff as well. This hardware was partially funded by the project in the past. Now Michal got new hardware for other projects and can move phpMyAdmin bits to that as well, but maybe it would be better to have separate server for phpMyAdmin related stuff (see Infrastructure for more details what is there).
The old server is about 4 years old, but it would work fine in case we won't add any intensive workloads (like running Selenium tests).
The old server would have to be anyway reinstalled/upgraded because it is currently running Debian oldstable and vservers, what is not easily upgradable.
So basically there are following options:
- Move phpMyAdmin to new Michal's server, discard the old one, stay with current hosting setup.
- Keep old server solely for phpMyAdmin purposes, phpMyAdmin will pay hosting.
- Use some other hosting provider and transfer phpMyAdmin services there.
Nijel 11:48, 21 August 2013 (CEST)
Chosen was:
- Keep old server solely for phpMyAdmin purposes, phpMyAdmin will pay hosting.
Michal will go in this direction, though it will take some time.
Who wants to participate in Infrastructure maintenance? The most important thing is that there would be backup for me in case I'm not available.
Nijel 11:48, 21 August 2013 (CEST)
- Several people stepped up as possible backup.
- In the end ibennetch and ruleant will do that.
Would it be better to merge bug and feature tracker to single one and only tag issues like bug/feature?
It would allow to have better overview what is reported by users and also more freedom in moving things (currently moving can be only done by tracker admins).
Nijel 11:48, 21 August 2013 (CEST)
- Most people are lightly in favor of merging.
- Let's call the new tracker Issues.
- Merge features tracker into bugs ones to save IDs of bugs.
- nijel will ask sf.net support to do the merge.
Marc suggests that at the beginning of October 2013, we release 4.1.0-alpha1. Looking back, 4.0.0-alpha1 was released on 2013-01-21 because of the numerous issues to solve after GSoC 2012.
--Lem9 14:37, 21 August 2013 (CEST)
- Looks like a doable plan after most of GSoC code is merged.
Moved to 2013-10 Meeting.
Now that the announcement has gone out and we're starting to offer support through Stackoverflow, we should discuss whether it's working as intended.
With the announcement of consolidating support to Stackoverflow, some users have brought up reasonable objections. One such objection is that the Stackoverflow community and moderators are not friendly to new people. Additionally, as the -users mailing list is generally low-volume, I propose keeping the mailing list opening and discussing whether we should consider an alternative to Stackoverflow (Google Groups was suggested by one user).
--Ibennetch 09:56, 25 August 2013 (CEST)
The page https://sourceforge.net/projects/phpmyadmin/support?source=navbar should be updated with our decision, too.
--Mynetx 14:35, 11 September 2013 (CEST)
The page should be fixed now.
Nijel 17:19, 11 September 2013 (CEST)
- It works quite well.
- Only about 15% of #phpmyadmin tagged questions are actually about phpMyAdmin.
Moved to 2013-10 Meeting.
Popular destinations:
- Team meetings
- GSoC home
- Developer guidelines
- How to install on Debian and Ubuntu
- Issue and pull-request management
User resources: