Re: [Openstack] Cloud Computing StackExchange site proposal
Stefano Maffulli wrote: On Mon, 2011-12-05 at 09:51 +0100, Thierry Carrez wrote: AskBot (Python/Django, GPL) - http://askbot.com/ Used by Fedora at http://ask.fedoraproject.org/questions/, can use Launchpad OpenID for auth. I looked at AskBot doesn't seem to have any mechanism to build a FAQ or to mark a question as 'solved' or 'obsolete'. I noticed that people edit the questions adding the word [solved] in the question, which is not very elegant. I also couldn't make the authentication with Launchpad but it worked with my other openID provider (claimID): Launchpad having problems with OpenID? Twitter's OAuth worked. The customization of UI seems to be limited but it will need more investigation. Launchpad OpenID worked for me. The URLs are of the form: https://launchpad.net/~USER; -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
Stefano Maffulli wrote: Here is the list of requirements we gathered: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * Tagging * Use of a reputation system to encourage participation and get a better handle on authoritative answers * a method or process for flagging topics which should migrate into documentation and/or the wiki. In details: (1) a way of flagging a question or discussion as a doc bug, a potential enhancement, or even a product bug. 2) A way of closing the loop, and updating the question to indicate the issue is resolved/fixed, and no longer relevant. * a way to assign a question to a particular version (or milestone) in order to better mark questions (and answers) as obsolete I would add an extra requirement: that the tool itself must be 'free as in freedom' software. I'm assuming we want all of these requirements satisfied. We should start talking about tools now. What tool do you know that allows us to satisfy these requirements? Help me build a list of tools to evaluate. I'm especially interested in seeing whether we can improve upon the tools we already have. I think a stackexchange clone could, with proper use of tagging, satisfy all these. There are a lot of unfinished projects... The most interesting candidate probably is: AskBot (Python/Django, GPL) - http://askbot.com/ Used by Fedora at http://ask.fedoraproject.org/questions/, can use Launchpad OpenID for auth. The next two in line are: Shapado (Ruby) - http://shapado.com/ : Very active, but confusing UI... OSQA (Python) - http://www.osqa.net/ : No activity in the last 8 months -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
Something like www.reddit.com/r/openstack has the reputation, promotion and FAQ capabilities. I'm not sure what software they use. DL -Original Message- From: openstack-bounces+donal.lafferty=citrix@lists.launchpad.net [mailto:openstack-bounces+donal.lafferty=citrix@lists.launchpad.net] On Behalf Of Stefano Maffulli Sent: 02 December 2011 22:37 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Cloud Computing StackExchange site proposal On Mon, 2011-11-28 at 08:17 -0800, Stefano Maffulli wrote: Leaving aside naming the tools, what would be the most important features to have? Here is the list of requirements we gathered: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * Tagging * Use of a reputation system to encourage participation and get a better handle on authoritative answers * a method or process for flagging topics which should migrate into documentation and/or the wiki. In details: (1) a way of flagging a question or discussion as a doc bug, a potential enhancement, or even a product bug. 2) A way of closing the loop, and updating the question to indicate the issue is resolved/fixed, and no longer relevant. * a way to assign a question to a particular version (or milestone) in order to better mark questions (and answers) as obsolete I would add an extra requirement: that the tool itself must be 'free as in freedom' software. I'm assuming we want all of these requirements satisfied. We should start talking about tools now. What tool do you know that allows us to satisfy these requirements? Help me build a list of tools to evaluate. I'm especially interested in seeing whether we can improve upon the tools we already have. thanks stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Mon, Dec 5, 2011 at 11:44 AM, Stefano Maffulli stef...@openstack.org wrote: On Mon, 2011-12-05 at 09:51 +0100, Thierry Carrez wrote: AskBot (Python/Django, GPL) - http://askbot.com/ .. OSQA (Python) - http://www.osqa.net/ : No activity in the last 8 months Uhm... Jira activity is low http://jira.osqa.net/browse/OSQA but I see a few recent commits on trunk http://svn.osqa.net/changelog/OSQA/osqa/trunk. How did you base your estimate of 8 months inactivity? /stef Webfaction run osqa, as a replacement for their old forums. The support openid, as well as local logins. You can see it in action at http://community.webfaction.com/ mike ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
I think that the main problem is that we have many places to search for information, but a few people giving helpful answers. A lot of newcomers join the forum but particular setups problems sometimes leads to packaging problems, bugs and we as moderators have to redirect the user to re-post his problem on launchpad, starting over. I think that we have to split packaging and developing questions vs implementations doubts, concept misunderstanding, etc. The main reason of people dropping Openstack on pre-production or testing environments its cause they aren't even mid experienced python developers, and they cant find a solution in a matter of time that they experience with the product leaves them a good taste to invest more time trying to implement it later. I read a lot of that's and end-user question, etc don't you guys forget that actually the end-users are Companies sysadmins maybe trying to deliver an real IaaS based on an Opensource product like Openstack. We have a huge Openstack implementation using almost every core product, and our environment is growing everyday faster than we expected, but when we approach to implement a new service, or integrate for example Keystone with Swift or Nova, we fought for days, fixing a lot of code and ended-up on a packaging problem, cloning the Cloudbuilders repo were the code was already fixed. That sensation to cross up docs, and blogs, and examples, and launchap question to get just to a test env, ends on companies leaving Openstack as a possible solution. We're pretty comfortable at python so we love to face issues like this, but imagine a sysadmin reading the docs, following line but line ending up with a non-working environment asking himself why he did wrong, and maybe a magic oh you have to chmod all this folder was missing on the docs. docs.openstack.org must be the bible for users that want to try openstack out, the forums and the IRC to help final users out, and launchpad for issuing bugs, we need to work on getting an updated documentation, getting a my instances get stucked on scheduling or i cannot ssh into instances should not exist with a clean and clear doc. We see a lot of people stuck in a single node installation, or on his devstack setup thinking about going back with they 3 vmware esxis nodes to create they VMs, and they never experience the real benefits of running a true IaaS all the way. Leaving the people googling or blogging up a few minutes after their setup is not good at all for the platform, we try to write up very detailed installation posts on the forums that are very usefull for the users, with tips and common issues that we faced installing the product. We're helping out everyday on the IRC and the forums to reduce the traffic o users hitting common issues, and of course Anne you can count on us to improve the docs, so that sysadmins loose their fears and feeling of this being too greeny to production and surprise themselves like we do everyday after 5 months later running all of our applications and our productive infrastructure over Openstack ( +1000 phy +6000 instances ) Sorry for the long writing . My two cents! Regards Leandro Reox Sr. Infrastructure Engineer at mercadolibre.com On Tue, Nov 29, 2011 at 10:37 PM, Lloyd Dewolf lloydost...@gmail.comwrote: On Tue, Nov 29, 2011 at 11:16 AM, Stefano Maffulli stef...@openstack.org wrote: On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: Where do I find this previous discussion? around here: https://lists.launchpad.net/openstack/msg02169.html What do you think of the requirements we're gathering for the QA system? I'd like your opinion on that as we move on. Thanks Stefano. I really like everyone reframing the discussion to figure out what our needs are as opposed to ... shiny! I do think stackexchange (SE) is miles [1] ahead and the only system that will meet the majority of our requirements. If we can get our own Area51 then it's by far the best immediate solution. I spoke to a friend at Area51, and he suggested we might have different results if we tried again. So I feel like this is on the table if we want to pursue. Of course, having very active SE participants (high reputation) put the proposal forward and committing to it carries a lot of weight. My reputation [2] is weak today, but I'm sure myself and others could ramp up the levels quickly over the next few months. Cheers, Lloyd -- 1. See I'm getting used to United States customary units, http://en.wikipedia.org/wiki/Customary_units 2. http://stackexchange.com/users/25765?tab=accounts ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net
Re: [Openstack] Cloud Computing StackExchange site proposal
Hi guys. When we have any kind of trouble, we hit the logs right away, and when we see the stacks, what i want to do is to copy paste the error, and wait for the search engine to do its job, since at this point i consider myself a user, so, i try to think like one, and most of the time what i want, is not to ask for a problem, but to see if someone already has it. Today i think there are enough data on launchpad to solve, or al least, give a very accurate hint about 90% of the problem a user may face (nova, swift, glance, maybe keystone) when they are stuck, but some times the search are not accurate enough for a search regarding an issue i know its there. so ... maybe i ended up using google search to look into lauchpad. So ... first, launchpad works pretty well as a QA site for openstack projects, but at least, i feel theres no a good way to show all the experience is stored there to a fresh user, so a more than good search engine i think is a must, mainly because having lack of resources for showing an answer that is already solved to a user, lead to the user to, 90% of the time, duplicate a question, and so .. a lot of admin work ( maybe deleting those, or teling the user it was already answered on THIS link), or the feeling of the QA system to be forsaken because of the amount of questions unsolved. A forum is more than ok also, because it gives the feeling of community and unity where the user feels confortable, but mixing that with a QA system, its a little difficult. Making posts promoted to FAQS or post becoming GUIDES and going into the FAQS, and the search engine suggesting something like Ok, if you didnt find your answer, maybe you are having troubles because of an implementation or a setup problem, why dont you go to the IMPLEMENTATION AND MOST IMPORTANT GUIDES to see if you can improve that and fix your real problem ?? is a nice to have, make the user confortable that they can find what they need, whitout asking for it ... in wich case, they actually can. As a last note, from mercadolibre since we have a lot already tested, and working into production ( nova clusters, nova volumes, keystone, swift, glance ) we can really share our experience in the form of THE DEFINITVE GUIDE TO ... or something that, maybe doesnt actually fix a certain user problem, but helps them understand how things gets configured, and actually how they work 2gether, we can really help on this, but i think this guides need to be put in a place where the user actually knows they exists, and no like just one post on the forum, or a question on launchpad. The official documentation is a great starting point, its has been greatly improved and we've always used it every time we tried a new openstack part of the solution, so .. nicely done there Anne. hope this gives a little user perspective. --- Alejandro mercadolibre.com On 11/30/2011 06:39 AM, Leandro Reox wrote: I think that the main problem is that we have many places to search for information, but a few people giving helpful answers. A lot of newcomers join the forum but particular setups problems sometimes leads to packaging problems, bugs and we as moderators have to redirect the user to re-post his problem on launchpad, starting over. I think that we have to split packaging and developing questions vs implementations doubts, concept misunderstanding, etc. The main reason of people dropping Openstack on pre-production or testing environments its cause they aren't even mid experienced python developers, and they cant find a solution in a matter of time that they experience with the product leaves them a good taste to invest more time trying to implement it later. I read a lot of that's and end-user question, etc don't you guys forget that actually the end-users are Companies sysadmins maybe trying to deliver an real IaaS based on an Opensource product like Openstack. We have a huge Openstack implementation using almost every core product, and our environment is growing everyday faster than we expected, but when we approach to implement a new service, or integrate for example Keystone with Swift or Nova, we fought for days, fixing a lot of code and ended-up on a packaging problem, cloning the Cloudbuilders repo were the code was already fixed. That sensation to cross up docs, and blogs, and examples, and launchap question to get just to a test env, ends on companies leaving Openstack as a possible solution. We're pretty comfortable at python so we love to face issues like this, but imagine a sysadmin reading the docs, following line but line ending up with a non-working environment asking himself why he did wrong, and maybe a magic oh you have to chmod all this folder was missing on the docs. docs.openstack.org http://docs.openstack.org must be the bible for users that want to try openstack out, the forums and the IRC to help final users out, and launchpad for issuing bugs, we need to
Re: [Openstack] Cloud Computing StackExchange site proposal
On Wed, 2011-11-30 at 10:26 -0300, Alejandro Comisario wrote: Today i think there are enough data on launchpad to solve, When you say 'enough data in launchpad' what do you mean exactly? A forum is more than ok also, because [...] lets avoid talking about tools. I'd like to understand what features we want to offer to new users searching for answers to their questions. And I'd also like to understand what features are important for experts and developers in order for them to participate in giving answers, when needed. Making posts promoted to FAQS or post becoming GUIDES and going into the FAQS, and the search engine suggesting something like [...] If I understand correctly, you would like to have a system where a question from a new user can be marked as FAQ and that question, with the relevant answer can go populate a list of FAQs. Is that what you have in mind? Ok, if you didnt find your answer, maybe you are having troubles because of an implementation or a setup problem, why dont you go to the IMPLEMENTATION AND MOST IMPORTANT GUIDES to see if you can improve that and fix your real problem ?? The Documentation and Guides should be the first stop for anybody looking for answers, right? /stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
I would like to see a way to identify the version (or milestone) the question pertains to, perhaps via a select box. OpenStack is moving quickly and I expect many questions will become irrelevant just as quickly. There could also be an All option, if the question is about something fundamental (e.g. ping and ssh don't work). Maybe there could also be an option for people with enough reputation/karma/points to edit the version. Of course you could do this with a tag but that's easily forgotten and people will often invent their own tags for the same version. Everett On Tue, Nov 29, 2011 at 12:16 PM, Stefano Maffulli stef...@openstack.orgwrote: On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: Where do I find this previous discussion? around here: https://lists.launchpad.net/openstack/msg02169.html What do you think of the requirements we're gathering for the QA system? I'd like your opinion on that as we move on. thanks stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
Stefano Maffulli wrote: Leaving aside naming the tools, what would be the most important features to have? Here is my personal list, in no particular order: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * possibility to turn question into bug report (nice to have) anything else? Please focus on features, we'll shop around for tools at later stage. * Tagging * Use of a reputation system to encourage participation and get a better handle on authoritative answers -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, Nov 29, 2011 at 2:35 AM, Thierry Carrez thie...@openstack.org wrote: Stefano Maffulli wrote: Leaving aside naming the tools, what would be the most important features to have? Here is my personal list, in no particular order: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * possibility to turn question into bug report (nice to have) anything else? Please focus on features, we'll shop around for tools at later stage. * Tagging * Use of a reputation system to encourage participation and get a better handle on authoritative answers * a method or process for flagging topics which should migrate into documentation and/or the wiki ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: Where do I find this previous discussion? around here: https://lists.launchpad.net/openstack/msg02169.html What do you think of the requirements we're gathering for the QA system? I'd like your opinion on that as we move on. thanks stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
It was here: http://area51.stackexchange.com/proposals/31788 It was rejected on the grounds of being able to be covered on StackOverflow and ServerFault. Vish On Nov 29, 2011, at 10:10 AM, Lloyd Dewolf wrote: On Fri, Nov 18, 2011 at 10:38 AM, Anne Gentle a...@openstack.org wrote: We had put forward an OpenStack StackExchange proposal earlier this year which was rejected Hi Anne, Where do I find this previous discussion? Thank you, Lloyd ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, 2011-11-29 at 10:14 -0800, Michael Pittaro wrote: * a method or process for flagging topics which should migrate into documentation and/or the wiki Sounds interesting. If I understand you correctly, you want to have a way to mark questions about topics that may be improved in the official docs. Would this be something like 'transform this question into a bug filed against the documentation project' or something different? Can you elaborate a bit more on the use case? How would this work? thanks, stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
Thanks Vish. Now my failed search makes more sense. Awesome how they delete it -- invitation to resubmit every month, jokes. On Tue, Nov 29, 2011 at 11:35 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: It was here: http://area51.stackexchange.com/proposals/31788 It was rejected on the grounds of being able to be covered on StackOverflow and ServerFault. Vish On Nov 29, 2011, at 10:10 AM, Lloyd Dewolf wrote: On Fri, Nov 18, 2011 at 10:38 AM, Anne Gentle a...@openstack.org wrote: We had put forward an OpenStack StackExchange proposal earlier this year which was rejected Hi Anne, Where do I find this previous discussion? Thank you, Lloyd ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, Nov 29, 2011 at 11:54 AM, Stefano Maffulli stef...@openstack.org wrote: On Tue, 2011-11-29 at 10:14 -0800, Michael Pittaro wrote: * a method or process for flagging topics which should migrate into documentation and/or the wiki Sounds interesting. If I understand you correctly, you want to have a way to mark questions about topics that may be improved in the official docs. Would this be something like 'transform this question into a bug filed against the documentation project' or something different? Can you elaborate a bit more on the use case? How would this work? thanks, stef Maybe the anti-pattern I'm trying to avoid here is a better place to start :-) A lot of knowledge discovery happens on a QA site, as well as lists and forums. However, a common problem with those tools is where the all the knowledge ends up being scattered in those locations (and often replicated), and the real documentation and/or wiki never gets updated. ( This seems to be more common with lists and forums than QA sites.) This is compounded by the natural aging of a discussion or question - at some point, it's just no longer relevant. I think two pieces are required: 1) As you suggest, a way of flagging a question or discussion as a doc bug, a potential enhancement, or even a product bug. 2) A way of closing the loop, and updating the question to indicate the issue is resolved/fixed, and no longer relevant. The method I've used in the past is where the 'question' had a link to a one or more 'bugs', and when a 'bug' was fixed the 'question' got updated automatically. There are various ways to do this; I think the important point is just to close the knowledge loop in some way, and to avoid having to do it manually. mike ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, 2011-11-29 at 16:06 -0800, Michael Pittaro wrote: A lot of knowledge discovery happens on a QA site, as well as lists and forums. However, a common problem with those tools is where the all the knowledge ends up being scattered in those locations (and often replicated), and the real documentation and/or wiki never gets updated. ( This seems to be more common with lists and forums than QA sites.) This is compounded by the natural aging of a discussion or question - at some point, it's just no longer relevant. Got it, very clear now. Thanks, stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Tue, Nov 29, 2011 at 11:16 AM, Stefano Maffulli stef...@openstack.org wrote: On Tue, 2011-11-29 at 10:10 -0800, Lloyd Dewolf wrote: Where do I find this previous discussion? around here: https://lists.launchpad.net/openstack/msg02169.html What do you think of the requirements we're gathering for the QA system? I'd like your opinion on that as we move on. Thanks Stefano. I really like everyone reframing the discussion to figure out what our needs are as opposed to ... shiny! I do think stackexchange (SE) is miles [1] ahead and the only system that will meet the majority of our requirements. If we can get our own Area51 then it's by far the best immediate solution. I spoke to a friend at Area51, and he suggested we might have different results if we tried again. So I feel like this is on the table if we want to pursue. Of course, having very active SE participants (high reputation) put the proposal forward and committing to it carries a lot of weight. My reputation [2] is weak today, but I'm sure myself and others could ramp up the levels quickly over the next few months. Cheers, Lloyd -- 1. See I'm getting used to United States customary units, http://en.wikipedia.org/wiki/Customary_units 2. http://stackexchange.com/users/25765?tab=accounts ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
On Nov 28, 2011, at 11:17 AM, Stefano Maffulli wrote: Hi Anne, thanks for bringing this up. On Fri, 2011-11-18 at 12:38 -0600, Anne Gentle wrote: a new possibility for QA. I think we should have a better system for users to find answers to their questions. The number of users is increasing and the traffic on this list is becoming hard for newcomers. The objective of the QA system is to provide a place for users of OpenStack to find answers about installing, operating and get started developing Openstack. Leaving aside naming the tools, what would be the most important features to have? Here is my personal list, in no particular order: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use * custom domain (like ask.openstack.org) * layout customizable, to give it the openstack.org look * use Launchpad login * possibility to turn question into bug report (nice to have) anything else? Please focus on features, we'll shop around for tools at later stage. - Users should be able to follow a question, (e.g., email notifications per question and/or RSS feed per question). - An effective way of filtering out spam (I see lots of spammy content in the RSS feed for forums.openstack.org). Lorin -- Lorin Hochstein, Computer Scientist USC Information Sciences Institute 703.812.3710 http://www.east.isi.edu/~lorin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cloud Computing StackExchange site proposal
Anne Gentle wrote: We had put forward an OpenStack StackExchange proposal earlier this year which was rejected, but it seems we could fit well into this proposed new site: http://area51.stackexchange.com/proposals/12383/cloud-computing Please vote if you are so inclined. My intention is not to re-start the forums debate but to let you know about a new possibility for QA. This site looks more oriented towards client practices (for end users of cloud computing services) than towards implementation of a software stack to provide such services... So I bet most OpenStack-related questions would be out of scope there (but would belong to ServerFault). Maybe that's a question to ask on the site ? -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
