Ok so there are no errors, there were but I corrected them. I also submitted a ticket about an error with the JED application page which I was thanked for and it is now fixed.

So with the talk of new Transparency and such relating to JED matters, could someone tell me how much longer I need to wait??? Been waiting since 19 March 2013 and there is the specific notice that "Listing approval time may be up to 21 days if no errors are found"

So because a few minor errors were found and I corrected them does that mean I have to wait another month? There is only the message "Your extension is currently in queue awaiting review".

And no I am not posting a support ticket because I am afraid... as per:

"Submitting a ticket often delays approval time."

I have never really taken stock of the many comments around that Joomla is not 3 Party developer friendly, but after my experience in trying to post an extension I am beginning to wonder, is Joomla Extension developer friendly?

BTW I have volunteered to help with the JED, and no one even had the courtesy to reply to me... so IDK...

I am getting very sad about this whole process, I had actually cancelled a trip with my wife so that I could be around for the release of my extension, yet that time came and went...

So why not say the truth in the application page, ie that extension approval will take over a month, maybe 2 months, maybe more...

also there are no minor errors, just a few errors or lots of errors as my examiner used to say

Yes I applied there a week or so ago to be a volunteer.

Ok so after waiting "up to 21 days" and if some error is found, ie didn't add gpl headers to 3rd party libraries that you are using you need to wait another "up to 21 days"?

All of my "errors" were related to 3rd party libraries being used, some of them think it is a bit overkill adding a GPL license header to every freakin' php file. But I conformed and added the header to a few hundred files just to make the JED editors happy...

This whole thing is strange, since the whole object of people creating libraries is for them to be used without being hacked... but who ever makes the JED rules seems to think otherwise.

1. My component is free, I am not trying to somehow rort Opensource matters to make money of their back...
2. My component is completely GPL, I am not trying to "sneak" other licensed files into the package
3. I am adding to the solutions that Joomla users have for their website, adding to Joomla it's self, so why do I get the feeling that it is some kind of "privilege", or great concession to be added to the JED?

It has been said before that the JED editors do not check security of a component, so what are they here for? Just to make sure it conforms to GPL and installs? I am sure the end users can easily enough monitor this or there extensions can be checked randomly AFTER being published instead of this guilty until proven innocent type of mentality that seems to prevail.

All I want is for my component to be published so that people can use it and provide feed back so that it can become better and more useful. I do not want to have to wait for months for this to happen, such a waiting period is ridiculous.

Is there not something wrong here? Maybe the process is a little too "bureaucratic" for the volunteers to handle. Surely is it going to end the world if a few files don't have a gpl header, or dear lord there is no JEXEC check on some file?

I just thought of something that could be helpful, what if there was a probation period, ie new extensions get posted but are flagged as probationary and thus people should use at their own risk. There could also be an invitation for those that have the time and expertise to check out the component and post their findings, I am totally sure that there would be many that would enjoy doing this, I for one love looking at other peoples code and I am sure that others do also. This would also at least make sure extensions are thoroughly tested before being added to the main JED.

I understand that this could be an issue for commercial components, but even then commercial components could be approved using the old process - I am pretty sure there are more free extensions than commercial ones anyway so this would take a huge load off the JED editors backs.

Just an idea as I have been complaining a lot, but not offering any ideas lol!

brian wrote:I have not seen your extension or the reports BUT as listed on the JED site I am available to anyone who needs assistance ensuring that their extension is GPL

Thank you Brian I really appreciate that.

My component is basically an integration of wordpress to work in Joomla, called WP4J. I ran it thru the JED checker and it come up with no GPL header licence for all of the wordpress files as well as the files of another library called QueryPath. These libraries do not include GPL licence details in the headers of all PHP files but are GPL and LGPL (respectively). In the end I manually added the GPL licence info to all the PHP files of wordpress and querypath (quite a chore) but in the end it ended up checking out.

So I think that should be ok now? The trouble is that I am concerned that I am going to have to hack Wordpress and Querypath every time I make a new release which is going to be horrible... at least Wordpress updates directly from it's admin area so I am thankful for that...

In regards to shipping Wordpress, it is shipped in the exact same zip that is downloaded from wordpress.com (no hacks, not even unzipped) - well it was until I had to alter all the files and add the gpl headers, now it is hacked and rezipped. Which is ridiculous, but required it seems, I did explain but got the warning back from teh JED editors - and as we al know 3 strikes and you are out so I just added the headers manually so I didn't have to resubmit the component...

I have flagged your extension recently for PH1 and PH2. Looks like you have fixed these issues and I have approved your listing. It was flagged for the Joomla files, not the jQuery libraries/wordpress files.

FYI, out of the 350 listings that were went through over the weekend by the JED team, only 150 were approved. A majority of them being basic errors that are highlighted in the documentation, and also a majority of them failing the JEDChecker.

Next time please use the JEDChecker, as Brian Teeman suggested, and review documentation before submitting a listing. It would save yourself a lot of trouble.

Warm Regards,

Tessa Mero

Tessa MeroJED Team Assistant Manager
Production Leadership Team Member

I am also facing the same issue. My component Name is "Yendif Music Share" and ID is "27679". We submitted it on 30th June 2014 and in next few days we were suggested to change the Download URL which we changed it immediately and added "X" in the box mentioned and submitted again. After that, it is more than 21 days and still showing "Your extension is currently in queue awaiting review".

yendifplayer wrote:I am also facing the same issue. My component Name is "Yendif Music Share" and ID is "27679". We submitted it on 30th June 2014 and in next few days we were suggested to change the Download URL which we changed it immediately and added "X" in the box mentioned and submitted again. After that, it is more than 21 days and still showing "Your extension is currently in queue awaiting review".