[Fiware] Question and Answer platform to be used in FIWARE Open Source Community

Donato Cohen, Malena malena.donato at atos.net
Wed Apr 15 22:37:21 CEST 2015


Dear Juanjo, all,

We think it's a great idea to have Q&A, we have been dealing with all types of questions and with the JIRA ticketing system itself and I honestly think having a good and sound Q&A blog or site will decrease our dedication to answer many repetitive questions. We have been managing all different lists, like general-help, collaboration, speakers request and we also coach 2 accelerators. Here in ATOS we have a lot of good answers very detailed in some cases. Also, I have some good text that we've used provided by Miguel Carrillo.

So count with us in setting up this system, we can contribute in providing inputs for specific Q&A.

Best regards,

Malena

From: fiware-bounces at lists.fi-ware.org<mailto:fiware-bounces at lists.fi-ware.org> [mailto:fiware-bounces at lists.fi-ware.org] On Behalf Of Juanjo Hierro
Sent: Monday, April 13, 2015 12:01 PM
To: fiware at lists.fi-ware.org<mailto:fiware at lists.fi-ware.org>
Cc: fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>; fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>; fiware-wg-leaders at lists.fi-ware.org<mailto:fiware-wg-leaders at lists.fi-ware.org>
Subject: [Fiware] Question and Answer platform to be used in FIWARE Open Source Community

Dear all,

  As you know, one of our goals is to launch the FIWARE Open Source community before summer.   During the last weeks we have been thinking about new mechanisms intended to improve the relationships between the different FIWARE stakeholders.   This community should arrive together with some new tools and ways of working.

  At this stage, we have identified the need to incorporate a Question&Answer Tool as a way to leverage the visibility and openness of our incipient community, together with enabling the participation and contribution of the different stakeholders.   We have been evaluating several options and we have initially identified askbot.net as the engine which would be more suitable to power our Q&A system.   The advantages of askbot.net are: open source solution, well documented and easy to install/configure, as well as availability of an API which may help to support integration with other tools.    Besides, Askbot is currently used by some relevant communities, as openstack, which gives us some trust about sustainability in the medium-long term.

  In order to implement askbot.net for FIWARE, the overall plan is as follows:

  *   We will setup a new subdomain called http://ask.fiware.org , that will be the reference site on which to raise questions about FIWARE in general.
  *   We will have a set of tags in order to categorize the Q&As.  A firs set of tags will be based on the different categories/channels defined at http://www.fiware.org/contact-us/ (fiware-general, fiware-acceleration, fiware-lab, etc).   Note that not all the tags will be of technical nature.
  *   We will continue encouraging developers to use Stackoverflow for those support questions which require thorough technical knowledge. If one of such questions comes to the regular Q&A system we will have a procedure to derive the question to SoF.
  *   We will have well documented procedures on how to derive other questions, for instance, new bugs discovered, or questions that lead to definition of new features, to the adequate platforms, namely Jira.
  *   We will consider follow-up integrations with other tools that might be used by the Community, for instance, slack.
  *   current procedures based on mailing list would be migrated to the new tool. We will consider what mailing lists should remain and what should be closed.

  We aim at making a final decision at the chapter wg/chapter leaders follow-up confcall planned for April 27th.  We are now making important decisions for the future of our project and community, so your feedback is needed.   P lease read this email with attention and let us know what your thoughts are.   Silence will be considered as agreement with the proposed plan.

  Many thanks for your contributions and feedback

  All the best,

-- Juanjo Hierro




________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware/attachments/20150415/6ca31aad/attachment.html>


More information about the Fiware mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy