[Fiware-ops-dev] Configuration of badges

[Miguel Jimenez]

Hi Fernando,

We've realised that StackOverFlow badge is mandatory. However FIDASH (and
other OPS enablers AFAIK) don't have StackOverFlow tag, so it is not
possible. Do you think it is necessary to set that badge, therefore to
create StackOverFlow tags?

Best regards

───────────────────────────
Miguel Jiménez Gañán, PhD.
  Dpto. Lenguajes y Sistemas Informáticos e Ingeniería de Software
  Escuela Técnica Superior de Ingenieros Informáticos
  Universidad Politécnica de Madrid (UPM)
───────────────────────────

On Tue, Apr 26, 2016 at 12:45 PM, FERNANDO LOPEZ AGUILAR <
fernando.lopezaguilar at telefonica.com> wrote:

> Dear all,
>
> I was checking the badges of our repositories, taking into account the
> reference:
>
> https://github.com/telefonicaid/fiware-orion
>
> And adapted to the FIWARE Ops chapter, this is our example:
>
> https://github.com/telefonicaid/fiware-glancesync
>
> The badges in order should be the following:
>
>    - License badge (mandatory).
>    - Docs (latest) - link to the ReadTheDocs (for us it is optional).
>    - Docker pull, link to FIWARE docker hub (for us it is optional).
>    - Support to StackOverFlow (mandatory).
>    - Build status badge (optional).
>    - Coverage status of the Unit test badge (optional).
>
>
> None has defined those badged, special attention should be taking to the
> Maintenance Calendar widget and the forked repositories.
>
> Good question is regarding the StackOverFlow, it means that you should
> have the possibility to create labels associated to your components. It
> should be created by a person with enough karma in StackOverFlow. I suggest
> that you contact with José Manuel Cantera (in cc) in order to create them.
>
>
> Please try to resolve this issue.
>
> Fernando.-
>
>
> From: fla <fernando.lopezaguilar at telefonica.com>
> Date: Monday 25 April 2016 at 22:37
> To: fiware-ops-dev <fiware-ops-dev at lists.fi-ware.org>
> Cc: Silvio Cretti <silvio.cretti at create-net.org>
> Subject: [Fiware-ops-dev] Sprint 5.3.1 Closing
>
> Dear all,
>
> Tomorrow we have the Sprint 5.3.1 closing, due to Silvio is in OpenStack
> Summit, I will take the ball to close this sprint. The summary of this
> sprint is the following:
>
> *FI-Deploy*
> 9/11 issues are closed.
> * https://jira.fiware.org/browse/OPS-1055, I reopen the issue due to it
> is pending the next issue.
> * https://jira.fiware.org/browse/OPS-959, closing meeting
>
> *FI-Dash*
> Please, check the status, it presents a low performance in the sprint,
> 1/11 issue is closed.
> * https://jira.fiware.org/browse/OPS-1037, The status is fixed, it should
> be closed before end of the sprint.
> * https://jira.fiware.org/browse/OPS-1042, status is in progress.
> * https://jira.fiware.org/browse/OPS-1043, status is in progress.
> * https://jira.fiware.org/browse/OPS-1054, status is open.
> * https://jira.fiware.org/browse/OPS-1033, status is open.
> * https://jira.fiware.org/browse/OPS-1034, status is impeded.
> * https://jira.fiware.org/browse/OPS-814, status is impeded.
>
> *FI-Health*
> At the moment low performance, 6/21 issues are closed.
> * https://jira.fiware.org/browse/OPS-1051, Status is in progress, update
> it if it is finished.
> * https://jira.fiware.org/browse/OPS-1024, Status is in progress,
> infographics, no changes since 11th April.
> * https://jira.fiware.org/browse/OPS-1023, Status is in progress,
> infographics, no changes since 11th April.
> * https://jira.fiware.org/browse/OPS-1022, Status is in progress,
> infographics, no changes since 11th April.
> * https://jira.fiware.org/browse/OPS-1021, Status is in progress,
> infographics, no changes since 11th April.
> * https://jira.fiware.org/browse/OPS-1020, Status is in progress,
> infographics, no changes since 11th April.
> * https://jira.fiware.org/browse/OPS-1025, still open, Monitoring
> transition stage.
> * https://jira.fiware.org/browse/OPS-1026, still open, Monitoring
> transition stage.
> * https://jira.fiware.org/browse/OPS-1027, still open, Proxy Monitoring
> API.
> * https://jira.fiware.org/browse/OPS-1013, Status is in progress,
> configure Health to execute test in ZurichS region.
> * https://jira.fiware.org/browse/OPS-858, still open, Ceilometer adapt
> new usage data.
>
> *FI-Toolkit*
> At the moment low performance, 8/20 issues are closed.
> * https://jira.fiware.org/browse/OPS-1031, in progress, update
> documentation in Maintenance Calendar tool.
> * https://jira.fiware.org/browse/OPS-1050, in progress, batchvalidator
> downloader.
> * https://jira.fiware.org/browse/OPS-981, in progress, Maintenance
> Calendar notification analysis.
> * https://jira.fiware.org/browse/OPS-1046, in progress, batchvalidator
> subversion.
> * https://jira.fiware.org/browse/OPS-996, in progress, UserArtifacts
> meeting
> * https://jira.fiware.org/browse/OPS-969, in progress, integration of the
> GlanceSync API and GlanceSync core service.
> * https://jira.fiware.org/browse/OPS-1048, still open, OSComponentVersion.
> * https://jira.fiware.org/browse/OPS-1029, still open, FlavorSync
> component description.
> * https://jira.fiware.org/browse/OPS-1028, still open, FlavorSync API
> description.
>
> Currently, I do not appreciate any problem in the backlog tool (
> http://backlog.fiware.org/urgent/upcoming). Please update the status of
> the different issues by tomorrow meeting. Do not forget that the Sprint
> should be closed by the 29th. Provide also the retrospective information
> each of the task leader.
>
> Best regards,
>    Fernando.-
>
> ------------------------------
>
> 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
>
> Since January 1st, old domains won't be supported and messages sent to any
> domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (
> Fiware-ops-dev at lists.fiware.org) instead of the old one.
> _______________________________________________
> Fiware-ops-dev mailing list
> Fiware-ops-dev at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-ops-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ops-dev/attachments/20160505/d445b5ad/attachment.html>