In reply to Xerfyre.

Nope! It is NOT clear. Meaning: clear which developer's code was at substantially disenfranchising WordPress users; and then what arbitration was taken to solidify the choice that w.org moderators made to before removing WPSS. Not to point-fingers; as it can be said that PluginOrganizer DID do what was asked of them. But why would there have to be a war of words rather than civil arbitration of the matter(s)? Answer: Continue reading.

The only reason I choose to enter this conversation is related to what Paul just posted in this seam of the thread: "I saw no mention of an appeals process developers can use that will be perceived as professional and impartial and disassociated in any way from emotions or passive-aggressive actions such as ignoring the developer or plugin for long periods of time. If there is such an appeals process in place and I missed it and that is the whole reason why...." He also brings up rule #18 which I have to agree: IS ambiguous to take advantage of.

I am and have always been pro Open Source. Yet there needs to be a more robust vehicle to handle privies and quirks which stem from large decisions made by smaller discourse. Explaining this using a quote from Zach Rosen.

"Dries Buytaert and Matt Mullenweg recently posted calls to arms in defense of the "open web." I, too, am a believer in the open web. It delivers on the promise of the Internet: a world in which everyone is connected, and you can command as much attention as your content deserves. But I agree with them that it is threatened by dominant technology companies who have an economic interest in creating their own “walled gardens” of Internet content that they control and monetize. [....] How many paid contributors to WordPress and Drupal are there? Maybe a few dozen. WordPress and Drupal lack the corporate sponsors of Linux because our open web companies have yet to get to critical mass. [....] Creatives, website designers and developers should all have an amazingly powerful set of tools that automate ALL the plumbing and grunt work so they can focus their precious time on creating amazing fast, responsive, web experiences. "

We as developers for little ole' WP do not have the billions of dollars for infrastructure which means in order to make things fair and efficient there needs to be good/better tools to make things run good/better. Paul hits on this rather well in this thread. I respect him for this and hope that all devs---and enthusiasts---can jump on board to be more proactive, just like everyone in this comments quorum has been.

If we don't get involved then WP, Drupal... Open source becomes less extensible and we will NEVER get control of its quirks.