2014 01_Meeting

IRC meeting for January 2014; see also the 2014-01 Meeting IRC Log.

Team membership, commit access and so on

Agenda

Currently we don't really have defined project membership and use "team member" quite vaguely. I think there should be some more rules on this.

My proposal is to have team members which have all of following:

• has commit access (GitHub)
• has rights to manipulate issue tracker (SourceForge.net)
• is committee member for interacting Conservancy
• subscription to team mailing list

I don't see much value in splitting up these permissions (as we do currently) as it only causes confusion. This would also mean that we should vote on accepting every new member.

--Nijel 14:47, 17 December 2013 (CET)

is committee member for interacting Conservancy

I don’t have that, have I? Does that have any consequences?

--Mynetx 16:04, 18 December 2013 (CET)

@Mynetx : You are a committee member, see the FSA, section 6, 2nd paragraph, mailed by Michal to Conservancy on August 20th, 2013.

--Ruleant 11:22, 19 December 2013 (CET)

Meeting

The proposal is accepted: no splitting of the permissions.

Committee voting rules

Agenda

Currently we vote on IRC during the meeting. Is this comfortable for everybody or should we switch to email voting? Vote will be discussed during the meeting and resulting options sent for vote on team mailing list.

Meeting

Normal voting will happen during the meeting, but occasional voting can happen by email.

Committee membership voting

Agenda

We should vote on committee member changes:

• remove Rouslan (on his own request)
• possible outcome of previous topic:
  • add Hugues Peccatte
  • add Piotr Przybylski

--Nijel 14:47, 17 December 2013 (CET)

Meeting

• Rouslan's resignation: accepted (majority)
• Hugues's new member: accepted (unanimity)
• Piotr's new member: rejected (unanimity, due to too infrequent contributions)

Light version/mobile support

Agenda

On October we decided that we may have a mobile-readiness project for GSoC 2014, and that we need to decide on the details of such mobile version. How does https://sourceforge.net/p/phpmyadmin/feature-requests/1484/ relate to this? Can/should/may we have a phpMyAdmin Light? How does the team feel about this? Who could/would work on it? Which features might be useful and which ones removable?

Meeting

• Some are not convinced about the need
• A GSoC student might have a good implementation idea
• We'll continue the discussion on the devel mailing list, to see whether we should add this to the GSoC ideas list

How to remain a team member

Agenda

Should we put together a list with ways to follow in order to avoid being taken out of the team?

--Lem9

Meeting

• We hope that a member no longer active enough will voluntarily step down
• The project admins may initiate a private vote (maybe coordinated thru Conservancy) to remove team member status from a perceived inactive member

Next IRL meeting

Agenda

LinuxTag 2014 is suggested.

--Lem9

Meeting

Everybody present is in favor and most will be available, so the decision is done.

Meetings