[Fiware-technical-committee] Focusing TSC meetings more on focused FIWARE roadmap activities

[FERMIN GALAN MARQUEZ]

Dear TSC,

“Just have a look at Orion Context Broker changelog for the upcoming 3.8.0 release and you will realize how NGSIv2 is strongly evolving”

In particular, those currently in https://github.com/telefonicaid/fiware-orion/blob/master/CHANGES_NEXT_RELEASE:

- Add: json field in httpCustom and mqttCustom subscriptions to implement JSON-based payloads in notifications (#2560)
- Add: ngsi field in httpCustom and mqttCustom subscriptions to implement NGSI payload patching in notifications (#4085)
- Add: ${service}, ${servicePath} and ${authToken} macros in custom notifications (#4159)

Best regards,

------
Fermín

De: MiguelA Pedraza <telefonica.fiware at gmail.com>
Enviado el: jueves, 22 de diciembre de 2022 9:14
Para: Juanjo Hierro <juanjose.hierro at fiware.org>
CC: fiware-technical-committee at lists.fiware.org
Asunto: Re: [Fiware-technical-committee] Focusing TSC meetings more on focused FIWARE roadmap activities

Dear colleagues

After reviewing the proposed topics after the December 19th TSC (minutes here<https://docs.google.com/document/d/16GQJclMuBSV9eW-V7gOpDNtJl77qMA6Cp-8xx1f6N5g/edit>) we, as Telefónica, have some concerns regarding all the tracks and components listed to review.

In particular, the name (as scope, of course) of “NGSI-LD evolution” track should be changed to “NGSIv2/NGSI-LD evolution” or “NGSI evolution” (in this case, considering that the term “NGSI” covers both “NGSIv2” and “NGIS-LD”). It is wrong to think that all NGSI evolution happens only in the NGSI-LD space. Just have a look at Orion Context Broker changelog for the upcoming 3.8.0 release and you will realize how NGSIv2 is strongly evolving.

It also applies for a big amount of components on the catalog, being a big part of them full GE, having a defined roadmap, and being in production with several references, with an active development and maintenance.

Thus, the “NGSI-LD evolution”track should be re-scoped to general “NGSI evolution” and similar changes in all other tracks where a similar comment applies.

Thanks for your comprehension

El lun, 19 dic 2022 a las 7:23, Juanjo Hierro (<juanjose.hierro at fiware.org<mailto:juanjose.hierro at fiware.org>>) escribió:

Hi everyone,

  Today is the last TSC of this year and, rather than run the standard follow up on status of components, I would like to devote the time to initiate an open discussion on the agenda of topics to be covered in TSCs during 2023 and potential changes how we may organize TSCs aiming at bringing more focus on roadmap activities.

  I have brought some initial thoughts in the pre-minutes<https://docs.google.com/document/d/16GQJclMuBSV9eW-V7gOpDNtJl77qMA6Cp-8xx1f6N5g/edit?usp=sharing> of the FIWARE TSC call of today.

  Goal is to initiate the discussion during the TSC of today, allow further discussion offline through the TSC mailing list along the coming weeks and try to come up with a decision during the first TSC of 2023, that would be on January 9th.

  I look very much for a fruitful start of the discussion today.  Don't miss it!

  Cheers,
--
Juanjo Hierro
Chief Technology Officer
juanjose.hierro at fiware.org<mailto:juanjose.hierro at fiware.org>
www.linkedin.com/in/jhierro<https://www.linkedin.com/in/jhierro>
Twitter: @fiware<https://twitter.com/fiware> @JuanjoHierro<https://twitter.com/JuanjoHierro>
[cid:image001.png at 01D916D0.4E7E77E0]







__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the following links:
- https://fiware-legal.readthedocs.io/en/latest/PersonalDataProtectionPolicy.html
- https://fiware-legal.readthedocs.io/en/latest/FIWARECookiesPolicy.html


fiware-technical-committee mailing list
fiware-technical-committee at lists.fiware.org<mailto:fiware-technical-committee at lists.fiware.org>

To unsubscribe from fiware-technical-committee mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-technical-committee

________________________________

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 confidential and privileged 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20221223/233b7cdd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8201 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20221223/233b7cdd/attachment-0001.png>