DAPSI call deadline 20/01/2021

Funding
#93

Agenda for the 1on1 mentoring scheduled Wednesday June 16th, 2021:

Context

· See past record below

Agenda proposal

· Feedback on interviews made : Loïc and Pierre-Louis

· Expose the plan of solution’s development for MVP and further possible versions : Loïc and Pierre-Louis

· Clarify the costs’ parameters for a MVP solution in operation and especially the volume impact

· Conclusion

Actions, next steps

· According to conclusion

Record
Minutes of 26-05-2021 meeting

  • FedeProxy aims first at allowing interactions of subscribers of forge’s services with non-subscribers (those later ones may want to interact with developers of specific forge services without being users of those services).
  • A second FedeProxy may come later, allowing subscribers of a forge service to move own data to another forge service (but this second function have to be proved relevant as developers (from entreprises or independent ones) do not seem to really needing that portability facility).
  • FedeProxy has made 10 (1-hour long) interviews of users of forge services and plan to analyse them in June and July.
  • It is unclear what part of potential users would be keen to pay for the FedeProxy service, but the costs of operation are rather low (a simple server would operate the identity translation between the person’s and that in the targeted forge). Various possible business model could be foreseen.
  • FedeProxy aims at operating a PoC involving some users to validate the interest, seize the potential market, clarify the usage and the possible business models.

Actions, next steps

  • Analyse the interviews made, identify the top priority pains and needs : FedeProxy/Loïc, Pierre-Louis
  • Next meetings : June 16th and July 7th, 11:00 to 12:00am : Jean-Paul to send corresponding invitations.

Initial invitation
Context

  • Dapsi program propose a coaching session series

Agenda

  • Pitch of the project, at the point where it is now and its perspectives : Loïc
  • Review of the main KPIs for the rest of the year
  • Review of the plan to achieve the targets
  • Review of the means available and needed, the ways to obtain and use them
  • Review of the main challenges for the weeks ahead
  • Open discussion
  • Conclusion and set up the next recurrent time slots for the months to come

Expected outcomes

  • Clear view of the project, its goals, difficulties and solutions.
#94

Received yesterday:

Dear all,

NGIatlantic.eu and US NSF are co-organising a workshop on the Open call 4 topics and initial discussions about open call 5 on 18 June 2021 (1400 CEST – 1800 CEST) – information and registration available at https://ngiatlantic.eu/events/ngiatlanticeu-nsf-eu-us-networking-workshop-open-call-4

This workshop will present some nice opportunities for you to take your results forward to team up with US partners to carry out experiments with US partners via the NGIatlantic.eu project’s open calls.

The topics for Open call 4, which opens 15 June with a closure on 15 Sept. are introduced in the workshop agenda and at https://ngiatlantic.eu/ngiatlanticeu-4th-open-call, so it would be especially of interest to projects coming from ESSIF-LAB**, DAPSI**, NGI Pointer, FED4FIRE+, and others also. So please have a loo. You will also have an opportunity to make a pitch during the event.

Best Regards,

#95

Received yesterday:

Dear All,

A short email to let you know about an event of relevance!

The Horizon 2020 HORIZON CLOUD project is organising a Community Event on Open Source Initiatives for Cloud Computing. During this event, the three Open Source Cloud Initiatives Eclipse Foundation, OpenNebula, and Sovereign Cloud Stack will present their work and engage with European Cloud Community.

The event is part of a series of Technical Community Events for the European Cloud Community. Aim of the event series is to foster synergies and collaboration between European Cloud Projects.

Register now HERE and get your token to participate to the event!

Kind Regards,

#96

Dear participants,

Thanks a lot for your attendance in our last session. As promised

:fire: Attached Week 3 workshop slides

:fire: Please provide feedback here

:fire: Your homework is to complete the Lean Canvas and Value Proposition Canvas, from the excel attached or separately (if you have done it separately that is fine too). Each project should email it directly to me at [redacted] in one email. I will then evaluate them. Please send by 21st June and if you would like some very specific feedback, specify it in your email.

  • There is no right or wrong, and there is just your own learning that is seen here.

:fire: Next session invite for June 23rd at 10am

[redacted] is inviting you to a scheduled Zoom meeting.

Topic: DAPSI Value Proposition Training
Time: Jun 23, 2021 10:00 AM Madrid

Join Zoom Meeting
https://us02web.zoom.us/j/89064674277?pwd=elJydXZ1bWVsbjJ0cnFMSXlycG9zZz09

Meeting ID: 890 6467 4277
Passcode: 197697
One tap mobile
+442034815240,89064674277#,*197697# United Kingdom
+442039017895,89064674277#,*197697# United Kingdom

Dial by your location
+44 203 481 5240 United Kingdom
+44 203 901 7895 United Kingdom
+44 208 080 6591 United Kingdom
+44 208 080 6592 United Kingdom
+44 330 088 5830 United Kingdom
+44 131 460 1196 United Kingdom
+44 203 481 5237 United Kingdom
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 929 436 2866 US (New York)
+1 253 215 8782 US (Tacoma)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
Meeting ID: 890 6467 4277
Passcode: 197697
Find your local number: https://us02web.zoom.us/u/kce62Z9H7E

–

+34 608 374133/+44 7962215774

Dapsi_Value Training 2021_week3.pdf (851.5 KB)

#97

Minutes of today’s conference call with the mentor:

Minutes of June 16th meeting

· Early results of the user research : users claims to be able to :

  1. connect their bug reports with other forges

  2. get notifications from other forges traced back to their original bug reports.

è FedeProxy thus becomes more than a simple SSO manager. It’s an issue federator tool

· The development plan is about June and July dedicated to build solution to be able to open and test a MVP in August FedeProxy is hosted on one forge and will be replicated on other ones.

· Discussion on plan to start presenting FedeProxy to friendly forges and challenger-forges, with the scope that they add it to their list of services.

· Proposal to build a presentation slide deck and a draft business model case, based on reasonable hypothesis, showing on loss side the possible traffic and hosting costs for the forge, and on the benefits side the time developers could hope to save on average on their development projects, thanks to FedeProxy linking issues throughout various forges.

· Proposal to think about KPIs and related counters in FedeProxy code, based on the business case thoughts.

#98

Mail sent to the mentor today:

Hi [redacted],

It was a pleasure discussing with you today. Your perspective is precious to us because we mostly have developer’s background. I looked over the project milestones[0] and that reminded me we’re committed to reach out to forge makers as a first step. And then to forge users (admin & devs) later. It would be great to discuss with you the strategies to best communicate with the forge makers (i.e. GitLab & Gitea) during our next meeting. Also, I’m happy to say that the user research project was completed today[1] and we can consider this milestone (due M4) complete. Last but not least, the core of our work for the next two months will be development. I realize this is not in your comfort zone and we can keep the update on that part brief, unless you’re curious about it, of course :wink: With this in mind, would you agree to the following agenda:

  • Communication strategy to approach the forge makers (i.e. GitLab & Gitea)
  • Updates on the software development

And we keep these items for the meeting we’ll have after, once the MVP is complete:

  • Review of possible draft business case to argument FedeProxy benefits for Forge and developers community
  • Discussion on plan to convince the forge providers and users

What do you think ?

Cheers

[0] https://forum.fedeproxy.eu/uploads/short-url/67QsDhlh47dpvuJxZf4hAsffZF9.pdf
[1] https://lab.fedeproxy.eu/fedeproxy/ux/-/wikis/2021-06-user-research-report

#99

Mail received from the mentor today:

Hello Loïc and thanks for your feedback and proposal.

I agree with putting communication strategy in the agenda for July meeting.

I would however keep the item business case as I feel it would be a strong argument fuelling the communication towards the Forge providers.

The business case should be kept simple :

  1.  Hypothesis on the average numbers of bugs reports per lines of code per year (or month if more appropriate)

  2.  Hypothesis on the average code size expressed in number of lines

  3.  Hypothesis on the average number of programs maintained and in development per developer

  4.  Hypothesis on the average time currently spent without Fedeproxy to report bugs and follow up bugs solving up to trace back to what issue generated it.

  5.  Hypothesis on the average time which could be spent with Fedeproxy in place to have the same bug tracing back and forth

  6.  Hypothesis on the number of developers for each Forge

Calculation step A : hypothesis 1 x hypothesis 2 gives the number of bug reports per program

Calculation step B : That step A result x hypothesis 3 gives the number of bug reports per developer

Calculation step C : That step B result x hypothesis 4 gives the average time currently spent by a typical average developer per year without FedeProxy (if hypothesis period is month, then x 12 months)

Calculation step D : That step B result x hypothesis 5 gives the average time currently spent by a typical average developer per year with FedeProxy (same as above for periodicity)

Calculation step E : Step D result – step C result gives the average time saved by a typical average developer per year

Calculation step F : Step E x 50 % as only part of the developers may use FedeProxy (of course ideally we would there make hypothesis on ramp-up rate over several years, but let’s keep it simple at this stage).

Calculation step G : Step F x hypothesis 6 gives the time saved by the community of developers of each Forge

There is a bias as each developer may be part of several Forges and adding time saved of each Forge for the same developer could be refined, but let’s keep simple the calculation as this stage.

Note : if that ease the thought, hypothesis may result from ranges having each each its hypoithesis level, and each range being allocated a % share to rebuilt an global average

My 2 cents,

#100

I replied today:

Hi,

Ok, let’s keep this item for discussion on the next meeting then. There is something I’m not seeing and it would obviously be beneficial to have your expertise on the matter :slight_smile:

Cheers

#101

Received today:

You are invited to our first technical workshop organized by Fraunhofer IAIS. In this session, Abdel will give a presentation about `Linked Data & Semantic Web Technologies’.
The agenda will be:

  • Ontology development
  • Hands-on using Protégé
  • SPARQL query language
  • Existing technologies
    The attendance is mandatory.
    Regards,
#102

Received today:

Dear all,

In collaboration with NGI TETRA we are organising a workshop according to your interests. Help us to define it with the topics you choose.

Some options:

    Community engagement
    Funding for open source
    Visibility for non-profit and open source projects
    Crowdfunding
    Consumer and digital rights

Essentially we can plan for different specialized topics within the broad topics or you can also suggest other topics to be included (and we will check if it is possible).

Please, reply to this email indicating the topic(s) of interest (if any) by this week.

Best regards,

#103

Received today:

Dear all,

we are experiencing some issues with our cloud infrastructure (https://cloud.lab.fiware.org/). Our technicians are working hard to recover soon the hardware crash but for a while, the infrastructure will remain down.

We would also take “advantage” of this situation to make a big upgrade to the last version of OpenStack in order to offer you an even better experience once everything will be back up and running.

In the meantime… For those of you who were using FIWARE Lab as an experimental/production environment, we can move your resources toward a different node of the federation (for you nothing change, it is just an internal shift of resources).

Please, contact me and I will take care of this procedure!

Also, for those of you who didn’t participate yet to the DAPSI webinars, we are re-arranging the sessions according to this situation. I will let you know soon the new dates.

And last but not least, once again, if you need any technical help, we can arrange one-to-one sessions about FIWARE Lab, FIWARE Generic Enablers, Docker, and more in general, any support on the development side of your solution!

Thanks for your patience,

#104

Received today:

Dear Participants,
See you all tomorrow. Please send me your lean canvases if not already sent, and if you’d like me to review something particular, do let me know too. Tomorrow is Experimentation, a very sought after topic and usually a lot of peer learning to take away from here.

Attached is the Lean Canvas/Deconstruct your business Excel again.

Cheers

Deconstruct Your business.xlsx (31.4 KB)

#105

@dachary could you share the attached file :slight_smile: ?

#106

Is that this one https://cloud.fedeproxy.eu/f/4690 ?

#107

I uploaded it without looking at it. Possibly the same document indeed. Sorry for overlooking the attachment :slight_smile:

1 Like
#108

I will complete it and send it right now, thanks !

#109

The value proposition canvas part was already filled, I slightly updated it and send it by mail to Farid (with Loic in CC).

Deconstruct Your business-fedeproxy.xlsx (26.8 KB)

1 Like
#110

This morning, I followed the [DAPSI] Linked data & semantic web technologies meeting.
Some notes:

  • This videoconference required to install Microsoft meet (an account wasn’t required). The web client wasn’t working at all.
  • There were two presentations, one focused on RDF and protege and the other one on OWL. Some SPARQL sample queries were shared.
  • I encountered an internet connection issue at the very end of the meeting, I asked by mail to the organizer if I missed a list of homework to do before the next session or if an attendee list was shared at the very end ?
1 Like
#111

Mail received today:

Invitation July 9th, 2021 10:00-12:00

Dear all,

In the next workshop I will give a presentation about “Introduction to GDPR and data subject’s rights”. The rough agenda will be:

  • What’s new in GDPR?​
  • What are individual rights?​
  • Lawful basis for processing​
  • Playing around with some interactive tools for GDPR compliance​

Attendance is mandatory.

#112

Reply sent today:

Hi,

Would it be possible to setup the videoconference on a service hosted with Free Software such as https://jitsi.org/ or https://bigbluebutton.org? It would be a nice fit since Jitsi was selected to be funded by NGI[0].

I apologize for this request and would fully understand if you do not provide alternatives. I’m a Free Software vegetarian[1], meaning I do not use proprietary software, even when they are awesome. Very much like a vegetarian would not eat meat, even when it is delicious :slight_smile: It is an ethical and personal choice I made years ago and it sometimes causes problems.

If there is no way to join the meeting other than Microsoft Teams, I could watch the recording afterwards or join using a regular phone number. It’s just an idea though: I’m trying to find all imaginable ways to participate without using proprietary software.

Thanks a lot for your understanding and I look forward to finding the best possible solution.

Cheers

[0] https://nlnet.nl/project/JitsiMeet-E2E/
[1] https://blog.dachary.org/2020/12/19/looking-for-a-free-software-vegetarian-developer-position/