I must admit that I do not think Extension Developers should be in, let alone run the JED Team. I have offered my own help over the years, but only because there was a shortage of people (and I wasn't accepted anyway, so that's that).
What is overlooked (once again, as is so often in Joomla) is that neither Extension Developers nor End Users should be the focus of the community. Focussing on those gives you either unhealthy competition (because many extension developers see it as their job to 'sell more than the competition') or disinterested blandness (because, for good reasons, End Users couldn't care less about politics or governing - they often build one site with joomla and only a small percentage hangs around afterwards).
What the JED needs to focus on is the professionals who use the JED and need to use it for a living - Site Developers.
If Site Developers were to govern the JED to their own advantage it would automatically be to the advantage of Extension Developers AND End Users as well. Thus everybody is happy and we can all chill out.
(Well, not yet and not entirely, but more on that below.)Democratic Election Process
Elected - by whom and into what
For whatever reasons, there is no transparency to outsiders as to what is happening behind the curtain. So I am not in a position to judge whether being on the JED Team is a pleasant or desirable experience or what the experience and structure is in the first place. And nobody in this thread, with the exception of JED Team members, should pass any judgment either. I can only imagine - if most of the technology is still outdated Mosets Tree from years ago then it will be neither, considering the volume of input they have to deal with.
To have any kind of democratic process going on, people must understand how the JED works, otherwise we're all just loading ideas and people into a cannon and shooting them into the void. That's not a smart idea (I know, I have tried before).
People need to know what happens, who does it and where help is needed. BUT
they must understand that that will not give them authority to influence the process right away. If they see things that they think go wrong, they should have the power to "run for office" on a promise of certain changes and if the community likes it, we'll all be better off with them in charge.
That's how politics work in the real world - if that was run by armchair politicians who sit in a chair on their lawn, complaining all day how everybody is wrong, we'd have a problem. (Again, I have done that, useless.)
But again - for that, they must be given the opportunity to see
what is going on. And I get that the JED Team is afraid of public scrutiny - because public scrutiny is at an all time high right now. But it has to be understood that that scrutiny is simply the force of the community trying to help... turned sour
Clarifying the processes and properly managing expectations and responsibilities is the way to go.Extension Developers have a role, though
We are problem solvers and we do see a lot of problems with the JED - speaking about technology, not politics. Site Developers need our services and they will need it in the JED as well - we can give them features that will make it easier for them to make life easier for everybody.TL;DR:
- Make the processes transparent, maybe even completely public
- Accept only Site Developers into the JED Team
- Run whatever elections you want, almost any will do
- Have Extension Developers compete to provide development services for the JED (just put the code and a test set of data on github, we'll figure it out)
Developer of the AEC Membership Management Component: http://valanx.org
Fellow of the Free Software Foundation Europe (and so can you: http://www.fsfe.org