The Joomla! People Portal ™

Hi Matt! Comparing the JED team with the JED team structure (http://extensions.joomla.org/tos/30) more than one year after it was published reveals some gaps, or less polite: not a single one of the 14 team-structure-positions seems to be assigned to one of the 9 team-members. Are there plans to fill the gaps and enlarge the team? Are there current JED team applications (http://extensions.joomla.org/component/breezingforms/?ff_form=17&ff_page=1)? Best regards Andreas

Exactly, it depends. Non-commercial extensions are generally quicker, I have had one approved in under 24 hours. Usually commercial extensions take 2 to 3 weeks in my experience but can be longer.

@Peter van Westen: I am **totally** in agreement with you, Peter. @mandville: I'm pleased to hear that the JED team is discussing this. Even if Joomla only supports, say, three dot-versions (in early 2012 we will have J! 1.5, J! 1.7 and J! 1.8) if extension developers want to show compatibility for more than that number they're out of luck; the JED only properly displays the compatibility badges for the three oldest versions of Joomla that may have existed at one time or another. Either the developer needs to eliminate the "unsupported" compatibility emblems or the JED should remove the ability to search for those things (and by extension that means that the JED should remove the display of unsupported compatibility emblems).

Agree. As someone involved for decades on translating various open source - and not only - codes, I can only support wholeheartedly the initiative. To make a Joomla component/module/plugin translateable is an easy stuff, can be archived easily with large majority of items. And where is not so simple (especially with older, established components, like Community Builder, VirtueMart and couple of similar ones) also can be done with a little goudance - usually eay to found on respective components support forum. I would make it mandatory too.

Thanks Jennifer. To expand, if your submission is still in the queue and has not been screened yet or has been flagged with a extension name error you should be able to change it yourself. Once a submission has been screened the name field becomes locked and can only be changed by a team member through the support system.

@Matt Lipscomb Are there any news on this topic? Best regards Andreas Berger

As stated in the original suspension email to you, an email is required to be sent to the team, a promise that the offence won't happen again must be included. Also in the original suspension email is a notice that reinstatements are done on a first-come-first-serve basis. Sending multiple emails, plus posting on facebook walls, plus posting here on the People site only slows down the process and disrespects the JED Volunteers' time.

I don't think it's a matter of making it easy to find, it's a matter of people being generally lazy. There is no way to verify which version of an extension someone is using short of making them click a link inside their install. I would love to see something like that, but I seriously doubt it would ever be implemented. Having a link inside Joomla would not only solve the version problem, but it would insure that the reviewer at least took the time to install the extension before reviewing it. However, that would certainly cause issues, the least of which being that you couldn't leave a review for an extension that failed to install. Keep in mind that people leave reviews as a service to the community, if you make it hard for them to do it, they won't.

I would leave the ability to vote for the developers too. And I'm also backing the idea to remove the ability to "silently" vote without any explanation why you voted in a given way. The explanation is simple: all of us (or, at least, large majority of us) who have posted their code in JED are also users of the JED, and the most qualified ones to see the ups and downs of a given extensions. Potentially the votes of developers can be the real valuable ones, especially if these votes are followed with opinions. As for bad practices and reducing the number of fraudulent votes: more rules you try to enforce, more additional work you will need to perform. Let's keep it simple, let's keep the rules in the Guidelines. I originally had an idea to implement a way to report fraudulent voting/commenting, but sincerely I'm not sure that will improve things without overloading the staff. People trying to cheat will be always around - and I personally take in consideration only as last resource the feedback of users when I pick up one or another extension I wish to try out. And the score on the votes is mainly irrelevant. From my personal experience I know, that an item which was downloaded 10 times less as my most popular extension, which has not get ANY vote or review, was voted and reviewed surprisingly often. Just because fills up a niche - and couple of guys where excited to find it. But the silent majority is steadily downloading - and using - the other one. So, indeed, an "I use this" button may be something worth considering. And I would leave the developers to use that too.

the problem is what current size of images not suit even for "to show how your extension looks". of cose i have documentation on my site and i know about first_image_will_be_a_logo. my post was about making gallery more useful and modern-looking. i think what it must be like shop window - i want quick observe the extension without going to enother sites...