Proposal for changes to the way we have to name our extensions
Before I write anything please don't take anything in my post as an accusation or whatever - I'm just proposing :)
Background:
It was strange for me that my extension didn't get any reviews for the last couple of weeks, so finally today I decided to open the jed. I was astonished to find out that the extension was renamed from CompojoomComment to just Comment - I guess that this is the reason why nobody is reviewing it. When someone buys it - they buy compojoomComment and not Comment.
After a short discussion with fellow developers I understood that there have been changes to the way JED handles extensions. If the extension xml file says: com_comment, then the name of the extension have to be comment.
Ok, so now if I want to have compojoom in the name I have to change the folder to com_compojoomcomment .
As far as I understand if developers are offering different version of their extension like free and pro - they will have to further rename directories like this
com_compojoomcommentfree
com_compojoomcommentpro
Am I the only one here hating long directory names???
I think that it would be cool if we could simulate namespaces like in php 5.3
For example
instead of having all words of the extension name in the folder name we could change it to something like this:
com_compojoom / comment
Model:
com_companyName / extensionName
or instead of companyName we could use domain names?
This way every extension developer will have his own domain(namespace). The benefit of this would be that every developer will be responsible for his domain - there he can decide how to name his extension.
I can call my extension - THE MOST AWESOME EXTENSION IN THE WORLD , then I won't have to name it like this:
com_themostawesomeextensionintheworld
but like this
com_compojoom / awesome
What do you think?
I know that such change would require changes to the installer, but I think it is much better to have our own domains, then to write long directory names.
Background:
It was strange for me that my extension didn't get any reviews for the last couple of weeks, so finally today I decided to open the jed. I was astonished to find out that the extension was renamed from CompojoomComment to just Comment - I guess that this is the reason why nobody is reviewing it. When someone buys it - they buy compojoomComment and not Comment.
After a short discussion with fellow developers I understood that there have been changes to the way JED handles extensions. If the extension xml file says: com_comment, then the name of the extension have to be comment.
Ok, so now if I want to have compojoom in the name I have to change the folder to com_compojoomcomment .
As far as I understand if developers are offering different version of their extension like free and pro - they will have to further rename directories like this
com_compojoomcommentfree
com_compojoomcommentpro
Am I the only one here hating long directory names???
I think that it would be cool if we could simulate namespaces like in php 5.3
For example
instead of having all words of the extension name in the folder name we could change it to something like this:
com_compojoom / comment
Model:
com_companyName / extensionName
or instead of companyName we could use domain names?
This way every extension developer will have his own domain(namespace). The benefit of this would be that every developer will be responsible for his domain - there he can decide how to name his extension.
I can call my extension - THE MOST AWESOME EXTENSION IN THE WORLD , then I won't have to name it like this:
com_themostawesomeextensionintheworld
but like this
com_compojoom / awesome
What do you think?
I know that such change would require changes to the installer, but I think it is much better to have our own domains, then to write long directory names.
-
Comment by Daniel Dimitrov on September 8, 2010 at 1:36am -
Hey Brian,
A long folder name is not that of a problem... What I consider a problem is that there is no real naming convention.
We have naming conventions for our controllers, models, views, but we don't have such for extensions.
On the other hand I want to have a freedom as a developer - if I wish to call my extension com_1 then I want to be able to make it. If I don't hurt anyone - why shouldn't I do it??? But in the future another developer will also decide to name his extension com_1 and that is where we have problems.
Perhaps we as developers can have a system where we can register our mark - when we do this, then we will have our domain and in this domain we can do whatever we want. That way my com_1 won't make any problems with another com_1.
We have 5000+ extensions on the jed. It is impossible to know all the names of those extensions...
-
Comment by Mike Carson on September 8, 2010 at 10:26am -
No offense Daniel, but I see this only as a way to tip-toe around the fact that the JED team has made up a new rule that greatly affects all developers and the fact that THEY have NOT communicated this to the developer community in any way shape or form. The decision that the JED team made did not consider how much this would affect the developer community and our users. I could very easily understand that this could be implemented for all NEW listings on the JED, but to force 5000+ existing extensions that have been around as long as Joomla and in some cases longer to all the sudden change their names and files is completely ridiculous to me.
So I will give you two perfect examples of how the JED Team is not being fair to all developers.
I will use two extensions that Joomla uses themselves but yet they have not bothered to change the names of these extensions names on the JED. However they are changing other developer's listings without notifying the developers or even a public notice about it.
Mosets Tree is com_mtree and the listing on the JED is "Mosets Tree"
JomSocial is com_community and is listed on the JED as "JomSocial"
Yet according to the JED Team's own rules these should both be renamed as Mtree and Community.
This is exactly what what they have done to both Daniel and my listings, as well as many others. So how is this fair? It isn't!
You know, if the JED Team would just stop making up the rules as they go along and actually publicly notify the developer community that they are considering these types of changes BEFORE they just silently make the switch it would go a hell of a lot further in forging better relationships with the developer community as a whole. Maybe even ask us for our opinions and views would be nice for a change. With actions like this it is obvious that someone just screwed up and had no clue about how it would affect the developers and the users, OR, they just flat out don't give a crap.
Personally, I do not see any legitimate benefit that this change would have to the JED staff, the community, or the project itself. Someone just had too much time on their hands with this one.
-
Comment by Mike Carson on September 8, 2010 at 10:36am
-
@Brian, would this not fall into the TOS? http://extensions.joomla.org/tos
Looks like they are not following the rules of point number 16.
Just another example of people that do try to follow the rules seeing others allowed to not be in compliance with the guidelines.
-
Comment by Amy Stephen on September 8, 2010 at 2:27pm
-
+1 Mike
Good post, Daniel.
-
Comment by lafrance on September 8, 2010 at 3:12pm
-
I will not reply much as that why extension forum on jed is for.
@Daniel
For me as long once your extension name is the same once install I published them,if it not then developer is inform of what need to be change.
@Mike.
I think you miss the point on rule 16 [rule under revision]
To accuse editor the way you do considering all of us are volunteers spending countless hours with no reward I think is a bit of a low blow.Mind you it always easier to trash someone out side of Joomla maybe?
In case you are not aware the Team Leader we had Toni as quit and CLT as taken over the role of co-team leader In the mean time.
All TOS are under reviews and will not lower myself to any others comments.
Thanks to Brain with the search of 777 jed is going to be changing again for the better.Call it growing pain :)
So please instead of accusing others have the courage to post your view on J forum were all editors can reply.
Pierre
-
-
Pierre -
We are free to talk in this community. We all volunteer - every single one of us responding to this topic volunteer in this community to make things happen.
But, our volunteer efforts does not mean others give up the right to discuss topics that impact them, or that they find interesting, or that they just want to comment on, on the basis that volunteer in that area.
We are going to have to get rid of the "castle" and "townspeople" concept and embrace community.
You are the very first JoomStew Contributor of the Week, Lafrance, and if Robert and I had not named you first, then you would have been named the next week, or the next one. You work hard. We all love you.
-
-
Thank You Amy as always you make sense.
It just sometime frustrating to see complaint here instead of forum
As editor cannot reply so it a 1 way conversation.
There many great points and view however those not help jed to improved with those change if there are not discuss on the forum.
As you know I try to stay away from any politics.
And I try always my best to work with all developer within the rule I been told to follow.
I agree with Nicholas up to a point.
Now I can see why other would be upset. If it was me approving Akeeba I would of rejected it.
As the name once install should be the same as the extension name Akeeba Backup
I do not ask much just that once install name should be both the same.
Why was it approved that way I do not know was it strong wording bulling of an editor have no idea
By making another exception it confuse other developer why can mine not be like Akeeba
The folder issue I think it mostly from one of our editor as I never worry about it as long the name are the same
So it is up to developer to agree of any changes to the TOS and again on the forum
-
-
You know - it's really hard to not be defensive about the things we invest so much of our time and heart into making possible.
I always chuckle at the use of the word "politics" - because most of the time, it means "people issues" or opinions. And that, we ain't ever going to get around.
I personally think ATAAW has become a kind of cool place where folks who are key contributors - people like you Lafrance - can come and shoot the sh*t with one another without worrying that "the general public" will see and get confused. I really do believe in the power of community to sort out right and wrong. But, for that to start happening, it first has to be safe to talk - and to talk obnoxiously or clearly or without concern about hurting people's feelings.
I worked on the very best team of geeks a few years back. We got to the point where we could have the *most* passionate arguments about data models and UML diagrams and security access processes. It got very loud in our meeting rooms - and the loud voices were frequently interrupted by even louder laughter.
We had one rule - and that was people individually matter more than what we do as a team. So, because of that rule, we could easily separate discussion of process from our support of one another. I do hope we get there and I do believe we are heading in that direction.
Respect to you, Lafrance, and to your team who support the JED, and to all who support this amazing community. Sometimes, things that happen in the Bug Squad are too much for me to ignore. I have to make a stand and step out. But, that does not mean I don't have respect for people in there or care about them as people. Sometimes things have to change. The less folks take the personal, the quicker we transition.
OFF OF MY SOAPBOX - even I can't stand it! :-P
-
-
I will never loose respect of you Amy as I always value your opinions.
It just now is the time for any developer if they have issues to post on the forum
If it is jed TOS " that need revamping " to the way extensions are approved or reviews.
By not posting " on the forum" how can change happen?
-
-
Yup - and I expect that is what will happen if folks talk about this, and think on it a bit, and come to an agreement on what they think might be best.
When that happens, it's good to know you'll be there! :)
© 2012 Created by Amy Stephen.
You need to be a member of All Together, As A Whole to add comments!
Join All Together, As A Whole