A specific part of this (and the reason I'm posting this here) is the inclusion of a JED Council. Jeremy Wilken was kind enough to offer up some ideas and suggestions to the CLT while in San Jose, and while this is not exactly the same as his ideas, this is founded on that. A special thanks to him for being a "visionary" in this and having the guts to recognize a need and offer a solution to it. After much discussion here is the idea...
A group of 6(?) members that consists of 3 end users, 3 developers
The objectives of the council are...
- Review appeals cases where a user and their listings have been suspended (recieved a ban) if the user requests it along w/ a member of the CLT (that is not on the JED Team)
- Provide ideas and Input on changes that broadly affect the JED procedurely and have substantial impact on the community and devs
- Propose enhancements/changes and visionary guides for the future of the JED
One member of the JED Team Manager role will be the liaison between the council and the JED Team.
One member of the CLT will provide oversight and be the liaison between the JED Council and the CLT and have the "swing vote" if needed on appeal cases.
The first selection of 6 will be "appointed" by the CLT, however, the goal is to have this first group outline guidelines/procedures/practices. The idea is that this provides the developer and end-user communities with a strong and balanced voice in decisions that affect them.
I do realize that this first structure is very "undefined", and that is intentional. It would be the job of the first council to structure it logically and then submit that to the CLT for approval rather than one or two people defining it for everyone.
The purpose of the council is not to make decisions for the team, but instead to be visionaries, goal setters and a balance for team decisions.
Thoughts? Ideas? Not looking for an up or down vote on this, just general input.