Hi Vincent, Le 10 oct. 2013 07:45, "Vincent Massol" <vincent(a)massol.net> a écrit : [SOLVED], so reason we'd like to switch to using the application that Jeremie Bousquet is still developing: http://extensions.xwiki.org/xwiki/bin/view/Extension/MailArchive+Application > @Jeremie: what's the status? Is it still read-only or can you write mails with it too now? Do you have the feature to close a thread? No no reply yet. But that does not prevent managing this "[solved]" thing. Good news is that I'm actively working on it. Currently on finishing the loading UI (I reuse some bits of EM). But this is a quite big task... Because I try to make it simple to use. For thread closing : currently "types" of emails can be configured (with matching regexps on emails parts), linked to auto tagging system. What I'd like to do, is link this kind of event system to more kinds of actions (like, say, updating thread state). The reply feature should not be very complex to implement, but everything takes time :) And I want the archiving feature finalized before moving on. Also I'm not sure of what should be done with a closed thread. I can disable reply from the app, but I can't prevent new mails to be sent from other clients. I think those emails should be archived also (pb is solved but there can be additional info). But if a thread is closed by an admin, as a moderation action, new mails should not be archived... > The other thing I'd like to have in a xwiki forum app is the ability to give points to those who provide good answers. Basically I'd love something like stackoverflow for xwiki. Wouldn'nt it be possible with rating plugin ? I'd say that first there should be a system to identify/vote for those best answers. > Thanks > -Vincent > PS: FYI here's a thread where we discussed this: http://markmail.org/thread/dyfhqyuug7xgjru2 > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users

On Oct 10, 2013, at 1:49 PM, Hamster <teunham(a)hotmail.com> wrote: Yes I know about Area51, see the mail thread I pointed out in my previous reply and especially this part: * http://markmail.org/message/ntiakfz4baxwylwe * http://markmail.org/message/6cqqriz5rylq26nk Can you explain what you mean exactly? :) Thanks -Vincent

Example: http://plone.293351.n2.nabble.com/How-has-stackoverflow-taken-off-td6076614… I have NO IDEA what "plone" is, but they talk about the switch from Nabble to StackOverflow... -- View this message in context: http://xwiki.475771.n2.nabble.com/Marking-topics-as-SOLVED-tp7587493p758750… Sent from the XWiki- Users mailing list archive at Nabble.com.

On Mon, Oct 14, 2013 at 6:53 PM, Vincent Massol <vincent(a)massol.net> wrote: Yes, but sleeping in a burrow does not improve our chances of getting more visibility of the project, does it? Neither does creating our own new underground establishment. If we plan on moving or doing anything in this direction, maybe the "forest" is where the action happens :) Thanks, Eduard

On Mon, Oct 14, 2013 at 9:58 PM, Vincent Massol <vincent(a)massol.net> wrote: My (only) experience with stackoverflow wasn't good either. Someone pointed me to a question regarding something I worked on and so I tried to help. I created an account since I didn't had one and I tried to leave a comment because I needed more information before giving a solution/answer and because the rule was, I think, to not put questions in the answer. Well, I couldn't comment because I did not had enough points.. (obviously because I just created my account) so I deleted my account and went on with my life. Thanks, Marius

On Oct 14, 2013, at 9:53 PM, Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com> wrote: Most people find it too complex to register to a mailing list. Sending the email is ok once you're registered. What I mean is indeed to make it easy for a first time user to find how to post a question. And yes the registration could be done seamlessly by providing an email address/name and once the user has clicked submit send him an email that he needs to reply to to validate his question for example (to ensure the email is valid). Something seamless like this. This is what stackoverflow does (and several other forums I've seen) and it seems to work quite well. Finding questions/answers is a different topic from what I meant here. Search usually works quite well to find existing topics IMO. This is used on a lots of forum apps that exist. The reporter should of course be allowed to say whether his question has been answered to. And the system could also allow committers/some contributors to close topics too by providing a reason to close it. Yes, sending an email is easy. Registering to a mailing list isn't. And searching for message isn't either since you need to find an archiving tool. Also even though sending an email is easy, replying to an existing thread isn't if you don't have the email locally to reply to. So if you're just a occasional user you don't want to receive all emails from everyone but you'd like to be able to reply to a thread from time to time. And you can't do that on a list. Why would they require more moderation than a mailing list? They require maintenance if you wish to do better than a mailing list simply because mailing lists don't offer those features! But if you do want these features then there's no choice anyway since ML don't offer them. "There are also a bunch of nearly empty unmoderated zombie forums on internet"… the same thing can be said for a lot of mailing lists ;) As a dev, I also like mailing list which is why in the previous thread on this topic, I mentioned that the best of both world would be a forum app that bridges with mailing list, if you can solve the issue of seamlessly sending to the list on behalf of the user (not so easy as proved by Nabble which is too complex and a lot of users don't understand why their nabble topics don't make it to the xwiki lists and why they don't get answers)... Your email client is a good example of a faulty email client that wrongly replies to mails ;) (your answers are mixed with the text it's replying to)... Cool! Food for thoughts: http://stackoverflow.com/questions/1576935/open-source-alternative-to-userv… Since one of XWiki's main use case is knowledge base, I still find it logical that we could expand on that to create a Q&A solution. Whether the store is in a mailing list system, inside XWiki's DB itself or even in JIRA is an open question... On a related topic (old now), see http://dev.xwiki.org/xwiki/bin/view/Design/HelpDesk Thanks -Vincent

2013/10/14 Vincent Massol <vincent(a)massol.net> I don't remember having done something very different to register to mailing-lists ... Except that mailman UI is a bit old-school, it's relatively simple. What people maybe find more complex, is that they have to register to another web page, than the one of the list they're interested in. I was not talking about search, I was talking about the fact that it may require time to "find the correct answer" for those who answer questions (not because of search tool, but because it can be complex, require some deep knowledge on some sujects, etc). Ranking and points can be fun and provide some visibility, it could also be seen as some incitement to judge only on "quantity" :) You can for example build great statistics by always answering to questions for which you now a wiki page has the answer, far better statistics than someone who focuses on the others (the ones that need you to explain, and why not create the missing documentation). I do not say that it doesn't work, but to me the "risks" are the same as with any rating/popularity system, it can be frustrating for individuals, depending on how it's implemented and most of all used. Sure but you don't register each time ... What I can say is that XWiki is particularly fine to search for emails from my contrib mail archive :) (thanks to livetable filtering + lucene/solr search). Well, on a list by itself of course, but that's why stuff like nabble, markmail, etc, do exist, and they are fine for that. I don't know the conditions / constraints of these tools, but I wouldn't imagine contributing to a mailing-list that would not be backed by an archive. And that's why I created one in xwiki in first place ;-) You said it above, registering to a list isn't so easy, and not so user-friendly. It naturally attracts mainly people REALLY interested in the topic (and when there is no other way to ask a question). A forum would certainly attract more people - that's the objective after all. So it will require more moderation... Because you have less "filtering" at the entry gate. I'm not saying it's bad, just that it might have to be taken into account for things to work smoothly. Right :) The "problem" of nabble and such is that they act as mailing-list frontend/archive that do not "own" any mailing-list. So users need to register to the real mailing-list anyway, then register themselves to nabble. That's exactly the same issue I will have with the mail archive in xwiki, even if I implement the "reply" and registration in the most seamless fashion possible (and there are chances, to be honest, that it won't be better than nabble). Because to reply you need the email address of the user (the one of the mailing-list, that may not be the same than the one you used to register in xwiki), and in the worst case (corporate environment) you may need a password in order to post emails through outgoing SMTP server (I mean, you might need your email account password in order to send emails from your own account on the SMTP you target). Storing this "external" password in xwiki or somewhere could be considered a security hole, so you might want to ask for it interactively each time a user wants to post a reply ... Of course these (email address, password) could be stored in the user profile or any other place, but it's still like a "second" registration step. And if you used different email addresses to register to different mailing-lists ... A forum doesn't have this problem, it completely owns everything it manages. It might only need some outgoing server configuration if it manages some email notification, and use email to secure registration step once for all (as most applications do anyway). I don't see how to make this email archive / forum bridge more simple, except maybe putting some SSO thing in place so if you authenticate to xwiki, you're authenticated to your email server. But that, is not very simple to do, and you cannot count on it as a pre-requisite anyway. What could be interesting is to find a way to completely forbid a user to post a reply from the "forum/archive" UI, unless he IS registered to the mailing-list. I'm not sure it's feasible - I must admit I have no idea. But it would avoid the problem you listed. Maybe mailman implements some commands you could send by email (or other api), to check if a user is registered to a specific mailing-list. You only would define the mailing-list manager account once in the preferences. Mmm sorry I realize that I'm moving away from your original topic ... :) That was gmail for android ;-) In fact I just discovered that it expects empty line between new content and previous history, or else new content is assumed to be history. Also, it cuts the lines to some length but does not add needed "> " for these new lines ... I hope gmail web app does better (I'm using it currently) :) I was wondering if xwiki ratings plugin could do the trick ...

vmassol wrote Done! :-) -- View this message in context: http://xwiki.475771.n2.nabble.com/Marking-topics-as-SOLVED-tp7587493p758762… Sent from the XWiki- Users mailing list archive at Nabble.com.