Good afternoon, I was reviewing the backlog for the Fi-Toolkit component and I have some doubts and questions for Gabriel. I can see that there are two work items that have problems, they are depicted in red: OPS-307 Feature Ops.Toolkit.Git.BrowseRepos OPS-314 Feature Ops.Toolkit.Git.ManageRepos This is because there is an Epic missing. It should be its parent and should be named as: Ops.Toolkit.Git My question is, since you are not going to implement the integration with Git finally, are all these Git related tasks needed? By the way, please remember to add a comment to the sprint close with the results of your work in this sprint (what went well, what to improve). The link to it is below: http://jira.fiware.org/browse/OPS-383 Kind regards, ========================================= ========================================= Sergio García Villalonga Software developer Research & Innovation Avinguda Diagonal 200 08012 - Barcelona (Spain) T. +34 935061490 sergio.garciavillalonga at atos.net ========================================= ========================================= On 28/07/15 15:22, Gabriel Huecas wrote: > Dear Silvio, > > I received the emails, but I checked them late. > > We will proceed as suggested, closing both ticket before Friday, > > best regards, > > Gabriel > >> El 28/7/2015, a las 15:17, Silvio Cretti <silvio.cretti at create-net.org >> <mailto:silvio.cretti at create-net.org>> escribió: >> >> Hi Gabriel, >> we moved the meeting from today to yesterday because at the moment I >> am in Brussels for the FI-Core review. >> Didn't you receive the invitation and the agenda about yesterday meeting? >> In any case I agree with you: if you can close the tickets assigned to >> you before Thursday EOB, then it is enough for the closing of the sprint. >> Best regards, >> silvio >> >> On Tue, Jul 28, 2015 at 3:12 PM, Gabriel Huecas <gabriel at dit.upm.es >> <mailto:gabriel at dit.upm.es>> wrote: >> >> Dear Silvio, Fernando, >> >> Unfortunately I was unaware of this change, so I didn’t attend the >> closing meeting yesterday. >> I wonder if we (UPM-ETSIT) can still join today at 16:00, although >> we do not have FIHEALTH issues. >> >> W.r.t Fi-OPS, we are closing OPS-354 today. OPS-356 (TestBed >> deployment), we can close it by Thursday, >> >> Perhaps this is enough for the closing meeting an no further audio >> is needed, but we will available at 16:00 today, >> if you think we can join. >> >> regards, >> >> Gabriel >> >>> El 23/7/2015, a las 20:43, Silvio Cretti >>> <silvio.cretti at create-net.org >>> <mailto:silvio.cretti at create-net.org>> escribió: >>> >>> Dear all, >>> so as discussed the next closing meeting is scheduled for Monday >>> 27th at 3 pm. >>> Only for Fernando (ie FI-Health) we will have the meeting >>> tomorrow at 4 pm. >>> Here the link to the agenda/minutes. >>> https://drive.google.com/open?id=1M6iSQ51ZK-RWaq2aPAjGhVT3vtqaDJe556qZ43irX-M >>> Best regards, >>> silvio >>> >>> On Thu, Jul 23, 2015 at 8:36 PM, FERNANDO LOPEZ AGUILAR >>> <fernando.lopezaguilar at telefonica.com >>> <mailto:fernando.lopezaguilar at telefonica.com>> wrote: >>> >>> Correct, just you and me and yes at (your) 4PM would be nice. >>> >>> De: Silvio Cretti <silvio.cretti at create-net.org >>> <mailto:silvio.cretti at create-net.org>> >>> Fecha: Thursday 23 July 2015 20:16 >>> >>> Para: fla <fernando.lopezaguilar at telefonica.com >>> <mailto:fernando.lopezaguilar at telefonica.com>> >>> CC: fiware-ops-dev <fiware-ops-dev at lists.fi-ware.org >>> <mailto:fiware-ops-dev at lists.fi-ware.org>> >>> Asunto: Re: [Fiware-ops-dev] next closing and planning meeting >>> >>> Hi Fernando, >>> ok for me (but a meeting just between you and me). Call me >>> tomorrow at 3 PM or event at 4 PM if you prefer (I guess you >>> wanted to write 9AM not 9PM, correct?). >>> Then tomorrow we can also discuss about the next planning. >>> Is it ok for you? >>> silvio >>> >>> On Thu, Jul 23, 2015 at 8:10 PM, FERNANDO LOPEZ AGUILAR >>> <fernando.lopezaguilar at telefonica.com >>> <mailto:fernando.lopezaguilar at telefonica.com>> wrote: >>> >>> Inline >>> >>> De: Silvio Cretti <silvio.cretti at create-net.org >>> <mailto:silvio.cretti at create-net.org>> >>> Fecha: Thursday 23 July 2015 10:08 >>> Para: fla <fernando.lopezaguilar at telefonica.com >>> <mailto:fernando.lopezaguilar at telefonica.com>> >>> CC: fiware-ops-dev <fiware-ops-dev at lists.fi-ware.org >>> <mailto:fiware-ops-dev at lists.fi-ware.org>> >>> Asunto: Re: [Fiware-ops-dev] next closing and planning >>> meeting >>> >>> Hi Fernando, >>> I understand. Nevertheless since others cannot attend >>> this Friday, I would prefer to keep it on Monday (agenda >>> will follow). >>> In any case if you prefer to have a check with me this >>> Friday at 3 pm CEST it is not a problem for me. We can >>> use skype. >>> What do you think? >>> >>> I prefer to have it on Friday at 3 PM, my 8AM, I would >>> prefer to take it at 9PM if you do not have any problem, >>> in order to close the sprint and put the content in the >>> minutes of the document on Monday. If you are ok I can >>> fix the meeting for tomorrow. >>> >>> For the planning meeting, is there someone from your team >>> that can attend? Otherwise we can declare that no >>> activity is planned for August sprint. I think it is >>> reasonable. >>> >>> For sure, we will have planned activities for August, we >>> have to close it next week before Friday. The problems is >>> that we do not have enough time to explain for example to >>> Pablo due to I will take my holidays before we comeback >>> to work. If you tell me what do you need to put in the >>> document (send me the link document of the planned >>> activities for sprint 4.4.2), I can write it and give >>> details information to Pablo. >>> >>> silvio >>> >>> On Thu, Jul 23, 2015 at 4:36 AM, FERNANDO LOPEZ AGUILAR >>> <fernando.lopezaguilar at telefonica.com >>> <mailto:fernando.lopezaguilar at telefonica.com>> wrote: >>> >>> I cannot attend neither on Monday 27th at 3PM due to >>> I have to return from Mexico, or August 4th due to I >>> will be on holidays. It is not possible to have it >>> this Friday at 3PM? >>> >>> Fernando >>> >>> De: <fiware-ops-dev-bounces at lists.fi-ware.org >>> <mailto:fiware-ops-dev-bounces at lists.fi-ware.org>> on >>> behalf of Silvio Cretti <silvio.cretti at create-net.org >>> <mailto:silvio.cretti at create-net.org>> >>> Fecha: Tuesday 21 July 2015 16:56 >>> Para: fiware-ops-dev >>> <fiware-ops-dev at lists.fi-ware.org >>> <mailto:fiware-ops-dev at lists.fi-ware.org>> >>> Asunto: [Fiware-ops-dev] next closing and planning >>> meeting >>> >>> Dear all, >>> I have been informed by Manuel that "exceptionally" >>> he won't attend the next closing and planning meetings. >>> For this reason I think we could have the closing >>> meeting on Monday 27th (so I can also attend) at 3 pm >>> and the planning meeting for 4.4.2 on August 4th. >>> Does it fit well for you? >>> Please let me know. >>> >>> Moreover Manuel informed me that there won't be any >>> official Sprint Review Meeting (again >>> "exceptionally") for this sprint. But I have the >>> feeling that we could have it among us. Let's discuss >>> this during the closing meeting. >>> >>> Best regards >>> silvio >>> >>> ------------------------------------------------------------------------ >>> >>> 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 >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> 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 >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> 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 >>> >>> >>> _______________________________________________ >>> Fiware-ops-dev mailing list >>> Fiware-ops-dev at lists.fi-ware.org >>> <mailto:Fiware-ops-dev at lists.fi-ware.org> >>> https://lists.fi-ware.org/listinfo/fiware-ops-dev >> >> > > > > _______________________________________________ > Fiware-ops-dev mailing list > Fiware-ops-dev at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-ops-dev >
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy