dear all, this time our po reacted quite promptly to my answer. this is what i received yesterday night and i'd like to share with you all. there are some requests/ideas from his side that require our attention. in particular the organisation of a dlt4gov day. email from po: "Dear Stefano, thanks for your notes. Regarding the Fiware Smart Fest of Jnauary, not sure if Token will be still featured in some form. If so, please share with me the info. In any case, let’s plan for the end of march for a check. I’d also include a policy discussion with interested colleagues from CNECT and DIGIT. The idea is to update on the activities within DLT4Gov and perhaps the Token Observatory. Or why not having the next workshop of the Observatory concurrently with the check? Could it work? " i'm working these days with fiwaree foundation cmo to understand if it is possible to have token and/or its content in the fiware smart fest (19-20 jan 2020 - virtual). perhaps this is not the case. if so i'll let you all know. concerning the "project check" please note after my email he changed its name (before was "project review") he is clearly raising the goal putting together with it a "political discussion with interested colleagues from cnect and digit". in principle i'm positive and would be inclined to answer yes, ut: 1. we need the use cases having reached at least the deployment and first operation phase 2. we must have a super good observatory workshop honestly saying not to his request will put the project in a weak if not bad perspective. so my suggestion is to accept his second option, i.e. to have the check and observatory workshop together. let me know what you think. of course final decision during our next ebm (13th jan usual time). ciao, stefano On Mon, 20 Dec 2021 at 13:07, Stefano De Panfilis < stefano.depanfilis at fiware.org> wrote: > dear all, > > a couple of days ago i finally received an email from our po. here it is: > "Dear Stefano, > > Thanks for your patience, the update, and the submission of all the > pending deliverables. > > Unfortunately, the anticipated discussion on these revised reports was > stuck in the middle of the evaluations which ate most the reviewers and my > availability. > > > > Here is my revised planning. > > March/April to have a Y2 project check. > > When we can see the status of the project with MS6 reached. This will > allow the reviewers and myself to better understand how the requested > revisions work in the context of the whole project, hear from pilots about > usability, replicability, interoperability of the platform and have a > discussion around policies. > > > > With this meeting we will be more or less 1 year away from the final > review which should be around February/March 2023. > > > > Your thoughts? Any possible date in mind perhaps corresponding to already > planned project’s events? > > > > Kind regards, > Giorgio" to which i replied as follows: > > "dear giorgio, > > thank you for your reply. i understand and well know that sometimes even > good plans can be easily mixed-up by contingencies outside our control. > > although not foreseen in the doa, i can agree a y2 interim review is worth > it, so to have enough time to eventually react and properly take into > account more interesting feedback and concrete suggestions from an external > point of view like that of the reviewers. honestly the sooner the better > which, yes, i think means march/april. > > actually as a project we were planning and working for a project event of > the international observatory to be held during the fiware summit initially > planned for 19-20 january in gran canaria. due to the new growth of the > covid pandemia the event is now completely virtual (it is now called > fiware smart fest) smaller in nature and now completely focussed on data > spaces. so we are missing this opportunity and we have to organise our > project event on our own although i think still in a virtual form. as > this cancellation news arrived just last week, we have still to replan such > an event. Of course if you have suggestions for co-locating our day we are > far more than happy to consider them. > > so if it is ok with you, i'll share your email with the rest of the team > and then have a good discussion on it at our next executive board meeting > on 13th january being 6th holiday in most of the countries of token > beneficiaries. for the time being let's work on the assumption to have the > y2 interim review in march/april for the moment not connected to any f2f > event. > > kind regards, > stefano" to which i did not get any reply yet ... > > as in the text of my reply i'm suggesting to have this email as the core > of our conversations on next ebm which i propose to be on 13th jan (same > time) instead of 6th jan as this day is a holiday in many countries of > token beneficiaries. Unless there is a big objection, within today i'll > send you all an updated ebm invitation. > > let me take this opportunity to wish you all and your beloved my personal > best wishes for the forthcoming festivities and a wonderful 2022 start!! > > ciao, > stefano > > > > > > -- > Stefano De Panfilis > Chief Operating Officer > stefano.depanfilis at fiware.org <charlotte.kotterman at fiware.org> > www.fiware.org > Mob: +393357542567 > Skype: depa01 > twitter: depa01 > > <https://twitter.com/fiware> > > > > -- Stefano De Panfilis Chief Operating Officer stefano.depanfilis at fiware.org <charlotte.kotterman at fiware.org> www.fiware.org Mob: +393357542567 Skype: depa01 twitter: depa01 <https://twitter.com/fiware> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/token-all/attachments/20211222/0ef5eb25/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy