The system already prompts the user to accept answers when warranted, so please do not continue to add additional notices to your posts or add comments prodding users to accept answers.
While well intentioned, as these "gentle reminders" start to accumulate across the system, the whole thing starts to look somewhat harassing to new users — so I ...
If a user posts on SE, you can suggest they use JSE instead and mentione that it's a dedicated Stack Exchange site for Joomla related questions. This will ensure they are aware of JSE and will most likely use it for future questions.
If you also feel that a question does not belong on SE or will get more attention on, you can flag it and request it be ...
I believe that despite the question has received no attention (upvotes, comments, answers), if it is a good question, then we could upvote it and try to draw attention to it, or even answer it.
I believe we should not be closing good questions, even if they don't have answers or other activity already.
At some point, someone could post a really good answer ...
It's understandable that people who have stake in technology choices (esp. considering the investment of time, energy and financial consequences) want definitive answers and a high-level of confidence when selecting a technology platform.
However, there is no quick and easy answer to your question:
Is [sic] there any statistics, usages or trend that ...
When referring to it on meta and the stackexchange site, it should't be necessary. Purely due to the fact that people coming on this site will know exactly what Joomla is, therefore the exclamation mark at the is is simply pointless. I think including it in the except/site description would be a good idea for branding purposes.
I would be much more worried about the quality of the answers than the quality of the questions. Simple questions, or questions that are fairly open ended, are not necessarily bad, since I think that lots of people new to Joomla would have them. Also, the fact that they have been answered elsewhere (on blogs and things) is not enough to rule out asking them ...
I think it depends on how the question is worded. This is always how I decide whether I vote to close or not. A lot of the time, people say they have a code snippet (usually something they haven't even written themselves) and then go on to mention it doesn't work and ask what the solution is. This I do not like as it shows no effort.
If the user has started ...
I'm Grace Note, a Community Manager at Stack Exchange.
There is no defined length of time that a site stays in public beta. The important thing to understand is that a long beta is not a sign of struggling or problems, at least not from the community side of things. There's nothing wrong with being in public beta.
At raw, we like to see things like ...
Right, I've created an organisation on Github, and added the first repository there:
If any of you would like access, let me know your Github username and I'll add you to the list.
If you don't have much experience with Github, feel free to go on the Joomla Chat Group and I'll be more than happy to point you in the ...
I'll split this into 2 sections:
Reason for the question count on WP and Drupal being higher:
The one thing you have to realise is that the majority of Joomla related question are asked on either Stack Overflow (not JSE) or the Joomla forum.
The joomla tag alone has 13k questions associated with it, not to mentioned other tags such as joomla2.5, joomla3.0,...
Yes, when referring to anything Joomla related, its always best to include the version in your question. I have seen a lot of people add the version specific tags and when answering the question, they have replied saying they're using a different version of Joomla, therefore I think if one manually types the version in, there is less room for mistakes.
The only currently available way I can see to handle this is to implement appropriate tags.
This seems to work OK on other Stack Exchange websites.
Maybe there could be a "not-version-specific" tag or similar?
Ok that answer would be a bit short ;-).
I think its important to have correct spelling and good looking answers and questions ^^, we have many not native English speaker, like me, that would really appreciated to be corrected in spelling and grammar.
At this point, the answer is "no one" and "everyone" at the same time.
Before explaining further, here are the boilerplate help sections from Stack Exchange:
Where moderators will eventually be listed: https://joomla.stackexchange.com/users?tab=moderators
What the moderators do: https://joomla.stackexchange.com/help/site-moderators
It is likely that ...
IMO it's really about answer the question. If the supplied answer is only giving opinion like "don't use that, use this" and does nothing to answer the question, it's not a good answer and should be deleted.
There are so many variations for types of extensions available, it's possible the author of a competing extension that the OP is asking about could ...
I can think of cases where both database and jdatabase would be appropriate.
If a question is about a more general database question (maybe "how to join content data with data from my custom table"), that should be tagged just database.
If you are specifically asking about working with the JDatabase or JDatabaseQuery classes, then tagging those ...
We could change that to:
Specific Joomla Framework problems
Joomla CMS installation, usage and customisation issues
Questions about Joomla extensions
Don't ask about...
Questions you haven't tried to find an answer for (show your work!)
Product or service recommendations or comparisons
Requests for lists of things, polls, opinions, ...
Let's take a step back for a moment, and look at what we, as a site, want to accomplish. Our job here is to solve problems for people who are working in Joomla. Sometimes, a problem is solved with an extension. It doesn't matter if there are multiple extensions available - our system is designed to support the idea that there may be multiple solutions to one ...
Personally I always like to link to JED so that the users gets to see a little information about the extensions, along with user reviews and ratings. If the extension does not suit their needs, then they can simply go to the parent category, where as if they were linked to the developers' site, then they would manually have to search for the ...
I was quite happy they got this up and running as it's a nice handy thing to have.
One thing we need to bare in mind when answering questions by user who are using the free joomla.com subdomain, is that that have no access over server setup or cannot install extensions. Therefore our ability to assist users will be fairly limited. If the question is ...
I've seen this a lot and the first question I always ask is, have they read the extension documentation or contacted the support team.
In my opinion, if they:
have read the extension documentation and cannot find the answer, or
have contacted the support team and have not received a reply, or
cannot find any similar questions, that have answers, on the ...
Searching in the StackExchange network, I came across this Meta Discussion: Close reasons cheat sheet.
I found a simple flow chart, that can act as a brief and easy to follow manual. I slightly modified for our Joomla SE site and am posting it here:
Flagging posts to request Moderators involvement should
be used sparingly, and when ...
I will try to form an answer that we could use in the help page...
Suggested version tags
For mysql and compatible sql servers like mariaDB or Percona Server
Not only spelling can be improved, but some questions tend to have:
an unclear title / question
too much text describing the question / issue
flag questions you think need a moderator attention
So yes, go ahead and edit.