Dear Rosa,
The comment by Rajiv was there since a lot of time and we cannot
delay further submission of this deliverable.
I have incorporated some suggested edits in the existing section for
FundingBox which I believe should be acceptable since, with them: a) we
simply describe what FundingBox has offered to experiments selected
through the two open calls of the project, b) leave a door open for DIHs
interested in such a service to contact FundingBox (but no commitment is
made, you may decide whatever :-).
In addition, you may decide to add a simple paragraph stating:
DIHs designing proposals to national or EU funded programs that
incorporate a cascade funding mechanism (Financial Support to Third
Parties in EU funded programs) are invited to consider the
methodology described in chapter 6. This methodology was followed
in the open calls issued within the initial i4Trust program. DIHs
may contact FundingBox to analyze the opportunity to count with
their services for dealing with the management of open call processes.
If by noon Monday I don't receive any response, I will accept the
suggested edits in the document and submit them (note that the above
paragraph will then not be added).
It would be great if you can provide feedback earlier. After all,
the suggested edits and the above paragraph does not enter into any
commitment on your side.
Cheers,
Juanjo
On 2/2/23 08:44, Rosa Villaronga wrote:
> Dear Juanjo and Rajiv,
>
> thanks for the suggestion, as I have mentioned in the document I have
> to check internally what FBOX can offer to the DIH beyond the project,
> I need a couple of days
>
> best,
>
> *Rosa Villaronga* - Reach me at @rosavi
> <https://spaces.fundingbox.com/@rosavi>
>
> Project Manager
>
> <https://fundingbox.com/>
>
> We are #FundingChampions
>
> Facebook <https://www.facebook.com/FundingBoxAccelerator/>|Twitter
> <https://twitter.com/FundingBox>|LinkedIn
> <https://www.linkedin.com/company/the-funding-box-group-s-l-/>
>
> This message is intended only for the person or entity to which it is
> addressed and may contain, together with its attachments, confidential
> information protected by law. If you have received this message by
> accident or by error, please notify the sender immediately and delete
> it together with the eventual attachments from your computer. Thank
> you. Since we have your email address, we would like to inform you
> that the data controllers are all entities in FundingBox Capital Group
> <https://fundingbox.com/trust/company/>as joint controllers
> <https://fundingbox.com/trust/jointcontrollers/>. Joint controllers
> process your personal data for purposes related to the subject of this
> correspondence, in accordance with the provisions of the GDPR.
> Everyone has the right to access and correct their personal data. More
> information can be found in the information clause
> <https://fundingbox.com/wp-content/uploads/2023/01/FBOX_information-clause_-general-communication_art.14.pdf>or
> in the Privacy Policy <https://fundingbox.com/trust/privacy/>. In case
> of privacy-related questions, you can contact us at
> privacy at fundingbox.com <mailto:privacy at fundingbox.com>.
>
> Do you really need to print this email?
>
>
>
> On Thu, 2 Feb 2023 at 05:18, Juanjo Hierro
> <juanjose.hierro at fiware.org> wrote:
>
>
> Great.
>
> @Rosa: please provide something for section 2.4.3 which can work
> not only beyond the project duration but also for DIHs which may
> approach us now but are not involved in any experiment selected
> through the 2nd Open Call. If you cannot commit anything, that is
> fine: we will drop out the entire section. If you allow me to
> make a proposal, I believe FundingBox may offer partnering with
> DIHs that are willing to develop proposals towards EU open calls
> that contemplate cascade funding for the selection of pioneer
> experiments using i4Trust building blocks, FundingBox taking care
> of managing the cascade funding. Those DIHs participating in the
> original consortia of the mentioned projects and designing the
> challenges for the open calls to publish and helping to mentor and
> bring support, since they will have LEBDS in their staff, to
> selected pioneers experiments (very much along the lines how DIH^2
> works). You could make a reference to the methodology described in
> chapter 6.
>
> Cheers,
>
> Juanjo
>
>
> On 1/2/23 14:45, Rajiv Rajani | iSHARE wrote:
>> Thank you Juanjo for updating the deliverable. I have reviewed
>> and accepted your suggestions. Only open point is for @Rosa
>> Villaronga <mailto:rosa.villaronga at fundingbox.com> to provide the
>> input as you already pointed out. Once she provides I think the
>> document is good to go for submission.
>>
>> Regards,
>> Rajiv Rajani
>>
>>
>> On Wed, Feb 1, 2023 at 7:34 AM Juanjo Hierro
>> <juanjose.hierro at fiware.org> wrote:
>>
>> Hi Rajiv,
>>
>> The review process took longer than expected because still
>> there were changes needed to transform this deliverable into
>> the basis for an Onboarding Kit for DIHs that may work not
>> just along the duration of the project but beyond. You may
>> remember that was the most important reason that justifies
>> creation of this new version of the deliverable.
>>
>> Now I have produced a version
>> <https://docs.google.com/document/d/1m9j9kUES2JHg076aJXR73pVprX9nwI7FmR6GgujN2GQ/edit?usp=sharing>
>> that, to my taste, is ready for submission if all suggested
>> edits are accepted. Major changes:
>>
>> * I produced quite a number of suggestions here and there
>> to allow this DIH Onboarding Kit becomes "atemporal",
>> that is, can work beyond duration of the project. I keep
>> them as suggested edits so that you can perform a very
>> final review.
>> * I make some major re-structuring of the document which I
>> have implemented already rather than keeping as suggested
>> edits (because otherwise the document would show to many
>> changes):
>> o I dropped the contents related to definition of KPIs
>> for the Ambassador Programme since they are already
>> covered in another deliverable and including them
>> here would make that part obsolete once the current
>> project ends
>> o I added opportunities of collaboration with i4Trust
>> core partners as a section within the chapter on the
>> role of DIHs, rather than in the chapter where it was
>> before.
>> o I moved the section describing the i4Trust Community
>> platform into a new chapter, leaving the chapter on
>> the role of DIHs very clean and focused on that, the
>> role of DIHs
>> o I moved the chapter on open calls to the end
>> * I change the wording of the chapter on open calls to make
>> it generic. I have accepted all my changes so that you
>> have a clean section to review.
>>
>> @Rajiv: please review remaining suggested edits to confirm
>> you are ok with those changes.
>>
>> @Rajiv: please review contents of the section on
>> collaboration opportunity with iSHARE
>>
>> @Rosa: please review contents fo the section on
>> collaboration opportunity with FundingBox. As already
>> commented by Rajiv, the existing text taken from the goodbye
>> letter to consortium that finalized their experiments during
>> the first i4Trust mentoring program (open call 1) doesn't
>> look as valid beyond duration of the current project.
>>
>> @All: please review contents of the generic open call
>> chapter I have produced.
>>
>> I'm this week in Arizona so bear in mind I won't be able to
>> react until your night. However, I don't see why we
>> shouldn't be able to finalize the deliverable between today
>> and tomorrow and submit it.
>>
>> Cheers,
>>
>> Juanjo
>>
>>
>> On 31/1/23 09:06, Rajiv Rajani | iSHARE wrote:
>>> Hi Juanjo,
>>>
>>> As has been discussed yesterday, can you either finish the
>>> deliverable D1.7 or send extension request to PO. I still
>>> see that this deliverable has not been worked upon.
>>>
>>> Regards,
>>> Rajiv Rajani
>>>
>>>
>>> On Tue, Jan 24, 2023 at 6:03 PM Rajiv Rajani | iSHARE
>>> <rajiv at ishare.eu> wrote:
>>>
>>> Hi Juanjo,
>>>
>>> Thank you for the review and comments. I have gone
>>> through them. There are still some open comments if you
>>> can have a look at them. On section 4, I have added
>>> comments and shared with you my rationale of having that
>>> section.
>>>
>>> Regards,
>>> Rajiv Rajani
>>>
>>>
>>> On Tue, Jan 24, 2023 at 12:52 PM Juanjo Hierro
>>> <juanjose.hierro at fiware.org> wrote:
>>>
>>> Hi Rajiv,
>>>
>>> I have conducted a careful revision of D4.1.
>>>
>>> In general, the document is well structured, with
>>> a lot of details which helps the reader to
>>> understand what happened. Very good in that respect.
>>>
>>> However, it was a surprise to find that there were
>>> several parts of the document which apparently were
>>> copy and paste of communications of the experiments
>>> or global coordination meeting minutes. As a
>>> consequence, the tone used (e.g., "during the
>>> workshop ... your experiment ..." or "... Juanjo
>>> tends to think that we should run it virtually
>>> ..."). Thanks god I decided to go for this careful
>>> review instead of taking as granted everything was
>>> ok (and it seemed from a high level review).
>>>
>>> The decisions on verb tense to use were sometimes
>>> rather strange. I found inconsistencies in the verb
>>> tense being used when describing a stage and what
>>> happened during the stage. Thus, stage 0, 1 and 2
>>> were described in present tense (a bit strange)
>>> while the description of stage 3 was in past tense.
>>> I then have changed them all to be past tense since
>>> this is a report of something that happened, this
>>> way also making them consistent). It was strange
>>> that a future tense was used in some cases referring
>>> to things that took place in the past (overall, when
>>> the date was given, e.g., "The Welcome event will
>>> take place virtually ... until January 28th 2022").
>>> I moved them also to past tense. Bottom line, I
>>> tried to do my best to leave things as harmonized
>>> and meaningful as possible but took quite some time
>>> and rather detailed review.
>>>
>>> Besides, that lot of suggested edits here and there.
>>>
>>> Please review the suggested edits and produce a
>>> clean version we can submit.
>>>
>>> I will take care of D1.7 tonight.
>>>
>>> Cheers,
>>>
>>> Juanjo
>>>
>>>
>>> On 23/1/23 11:35, Juanjo Hierro wrote:
>>>>
>>>> Hi,
>>>>
>>>> As explained on whatsapp, review of the Playbook
>>>> kept me busy all the time I had booked for reviews
>>>> during the weekend. Now deliverables 1.7 and 4.1
>>>> are top priority.
>>>>
>>>> I'm currently on D4.1 as you explained to me that
>>>> is a longer hanging fruit.
>>>>
>>>> Cheers,
>>>>
>>>> Juanjo
>>>>
>>>>
>>>> On 23/1/23 10:37, Rajiv Rajani | iSHARE wrote:
>>>>> Hi Juanjo,
>>>>>
>>>>> It's been days and no updates from your end are
>>>>> still part of the document. Can you finish the
>>>>> updates today as we had discussed. I would like
>>>>> that these deliverables are submitted today itself.
>>>>>
>>>>> Regards,
>>>>> Rajiv Rajani
>>>>>
>>>>>
>>>>> On Tue, Jan 17, 2023 at 6:36 PM Juanjo Hierro
>>>>> <juanjose.hierro at fiware.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I plan to finalize my final review tonight.
>>>>> Unfortunately, I couldn't spend the time I was
>>>>> planning during the weekend and yesterday and
>>>>> today got very busy.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Juanjo
>>>>>
>>>>> On 17/1/23 09:32, Rajiv Rajani | iSHARE wrote:
>>>>>> Dear Partners,
>>>>>>
>>>>>> Can you please finish your part in D4.1 and
>>>>>> D1.7 deliverables. As was discussed last
>>>>>> Friday, I was expecting updates in D1.7 but I
>>>>>> do not see any updates.
>>>>>> For D4.1 there are only a few comments, if
>>>>>> you can close them, we can prepare that
>>>>>> deliverable for submission.
>>>>>>
>>>>>> Regards,
>>>>>> Rajiv Rajani
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 9, 2023 at 10:24 AM Rajiv Rajani
>>>>>> | iSHARE <rajiv at ishare.eu> wrote:
>>>>>>
>>>>>> Dear Partners,
>>>>>>
>>>>>> I have not seen a single edit in any of
>>>>>> these deliverables from any of you. Can
>>>>>> you please make sure that you finish the
>>>>>> deliverables today so we can submit them
>>>>>> asap?
>>>>>>
>>>>>> Especially, D1.7 has quite some edits
>>>>>> pending and have been tagged to
>>>>>> relevant people, please look into it
>>>>>>
>>>>>> Regards,
>>>>>> Rajiv Rajani
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 3, 2023 at 4:29 PM Rajiv
>>>>>> Rajani | iSHARE <rajiv at ishare.eu> wrote:
>>>>>>
>>>>>> Dear Partners,
>>>>>>
>>>>>> As have been sent earlier following
>>>>>> deliverables have been shared for
>>>>>> your contribution and review many
>>>>>> times. Given that the deadline was
>>>>>> already the end of December, can we
>>>>>> please expedite its finalisation?
>>>>>>
>>>>>> D1.4 - Train the Trainers Program
>>>>>> <https://docs.google.com/presentation/d/1HS86OinRd5SU4gpncqpXD5uooXhbIR4UDeEm30g4wKs/edit#slide=id.p>
>>>>>> - I see some contribution is still
>>>>>> pending, can you finish the same at
>>>>>> earliest?
>>>>>> D1.7 - i4Trust Onboarding Kit
>>>>>> <https://docs.google.com/document/d/1m9j9kUES2JHg076aJXR73pVprX9nwI7FmR6GgujN2GQ/edit#heading=h.xwd6v0nwb2xe>
>>>>>> - I have updated the document as per
>>>>>> our last discussion for my part,
>>>>>> remaining contributions are pending
>>>>>> D4.1 - Report on B2B Data Sharing
>>>>>> Mentoring Program
>>>>>> <https://docs.google.com/document/d/1WG8KEXu1cigQP-VfoIuAcB1YTh-yIk5A_LpC_rAAbxs/edit#heading=h.xwd6v0nwb2xe> -
>>>>>> I see mostly the content is updated,
>>>>>> however, still some of the items are
>>>>>> pending. Can you finish and review
>>>>>> the document?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Rajiv Rajani
>>>>>> CTO
>>>>>>
>>>>>>
>>>>>>
>>>>>> iSHARE Foundation
>>>>>> +31 61 796 2003 <tel:+31617962003>
>>>>>> iSHARE.eu <https://www.ishare.eu/>
>>>>>> rajiv at ishare.eu
>>>>>>
>>>>>> <https://iSHARE.eu>
>>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/i4trust/attachments/20230203/9ad5733c/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy