Do not be surprised to see the repository continue to change and more than likely expect them to try capitalize on what Envato is doing. So, people will buy themes or plugins directly through a wordpress exchange and a fee based upon it to WP. I figured this would happen as Envato is doing quite well on selling Pressables.

SHOULD it happen then you will see that "control" I mentioned in other posts rear its head once again. That is to say, not what is good or bad for theme'rs or plugin coders (not that I am saying it'd be bad) but what is good for them.

This IS THE PROBLEM with ALOT of this Open Source seemingly wonderful wonderful stuff. Third Party developers do not get to see the monetizing that happens or necessarily even how. How would you feel as a developer/theme developer if you found out that company "xxx" is making 40 million a year for a open source cms engine. But the engine is basically just that. Its all the work the plugin authors do and theme authors do that make that CMS really remarkable.

Yet, those authors are disallowed to even protect their work from being pirated or modified by others in areas that can compromise the theme or plugin.

Its not the Joomla core that make Joomla great. Its the plugin and theme designers. Its not Wordpress that makes Wordpress great, its the theme people and the plugin developers.

The question should be put forth to WP core, "Will you state that you will not try monetize on the plugins or theme's in the future at the repository. That even if it is built into a form where consumers can purchase there that WP will not charge any forms of fee's to the developer or consumer for purchase within said repositories".

Again... Its all your work folks, theme's, plugins etc. that make Wordpress do all the neat things it can do. Thats not their doing, its yours.

This is CONTINUALLY the issue with these forms of projects.

Normally one might think, "Well... I as a developer of themes or plugins make money on the WP Core which they make so its good they can make money too off my work as I make money off theirs". Thats absolutely 110% correct.

BUT! In the same respect as a theme or plugin developer you should be able to protect your work having ioncubed or zended callbacks or critical code that should not be altered for whatever the reason.... security if nothing else be able to be protected from sucha matters or piracy.

The fact the core WP does not wish to do so is their decision. It should not be dictated to other developers or even encouraged not to. It should be up to the developer period.

As I stated in another post, I've heard (not that I already was not aware) from two sizable theme houses who do both Joomla and WP themes. For every one theme they sell there are 3-5 of that same theme being used, never were purchased and are in fact pirated.

For a core, they do not care. So that kinda negates "We care about our third party developers" as if that were true they would encourage commercial plugins or themes to protect their work. Instead it is "No no" as even if a site is comprised 110% of pirated theme's/plugins thats one more site still using the free core application which serves to benefit who?

What all developers should be pushing for is that ability to protect their work and thus their income.