Three Questions

[winuser]

Question 1. Why do you (the extension directory mods) continue to publish user questions as review entries? I have transcripts from moderators assuring me months ago that you both desired and needed to stop publishing comments that were not reviews. I am confused. Is the review site now to function as a discussion board between developer and user?   :laugh:

Question 2. How do authors control line breaks in lengthy (or itemized) descriptions? 

Question 3. Can you kindly add another license option called "Free License" without "Other Open Source." The four or five that are available are not sufficient; and having to chose one is that is not legally accurate is problematic. 

Happy holidays

[ot2sen]

Hi winuser,

Answer 1: No excuse on this 
Picked up the comment that was the reason for your question and made sure it was unpublished. Thanks for the reminder.
In case a comment should mistakenly be approved for your extension, then feel welcomed to use the 'Report' button for the particular review (visible when logged in), and we will be directed to the excact problematic review/comment. Thanks.

Answer 2: ...will check up on that.
Answer 3: ...will check up on that.

Happy holidays for you too 

[Vimes]

I would recommend that you establish what you mean by 'Free License' as the term can be considered very broad. Perhaps you could define your intentions regarding the software so that we can understand what you mean. Check out this link http://www.gnu.org/philosophy/license-list.html for suggestions on 'free licenses'

[winuser]

The extensions directory already uses the term "Free License" in a more confusing context: it is paired (slashed) with the express "Other Open Source," as though the two terms were interchangeable.

A software license governs use. The software is not open source; but it is free to use under the terms of the license. The license does not grant any ownership or distribution rights to the end user. It grants them use of the software.

I would even settle for "shareware" or "freeware" -- each is far more precise on the issue of ownership and re-distribution.

How about "Limited Free-Use" ?

Or, allow authors to select "OTHER" (or a blank) because they have already specified the licensing terms elsewhere.

My last suggestion might be the best from a legal standpoint.

[winuser]

Vimes, you were so quick to jump into this thread and ask a question, so why not take the time to follow up on it?

Let's just consider my third request a moot point; nothing more needs to be done. I will remove my listing, but I need some help because the delete function is failing. I also sent a note from the extensions directory (to an unknown moderator).

If you would delete the J! Reactions entry (under 'Comments'), that would be great.

Happy (Western) New Year to everyone!

[Vimes]

Apologies, it got lost in the flood of everyday stuff. As you are removing your listing it is, as you say, moot. Regarding points 1 & 2, I believe ot2sen has them in hand.

[ot2sen]

Hi winuser,

Your extension removed as requested. 
We are aware that there´s an issue with deleting. Hopefully this is fixed soon.

[mjaz]

Question 2. How do authors control line breaks in lengthy (or itemized) descriptions? 

Any news on this? It would be great to be able to make nice lists of features, have some paragraphs etc. '\n' and '
' are stripped.

Ideally, there should be an intro text (with line breaks etc stripped) and a main text with some basic html or bbcode.

[ZorkFox]

Question 2. How do authors control line breaks in lengthy (or itemized) descriptions? 

Any news on this? It would be great to be able to make nice lists of features, have some paragraphs etc. '\n' and '
' are stripped.

It sounds funny, but try using <br />.  I had a bit of a run-in with this problem when I was experimenting with allowing users to submit content from the Joomla! front end.  Every
tag I put in became a literal carriage return in the text, which is, of course, useless in an HTML context.  When I used the HTML entities, it seemed to work better.  I know that's not an idea solution, but it might help.

[mjaz]

It doesn't work -- the JED shows them as literal '
' in the text, not as line breaks.