Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Apply for funding to help develop Open Cloud Mesh within this community #67

Closed
michielbdejong opened this issue Mar 14, 2023 · 9 comments
Closed

Apply for funding to help develop Open Cloud Mesh within this community #67

michielbdejong opened this issue Mar 14, 2023 · 9 comments

Comments

@michielbdejong
Copy link
Contributor

michielbdejong commented Mar 14, 2023 •
edited by labkode
Loading

As discussed at the CS3 2023 conference last week, I offer myself as a contact point for applying for funding to help improve our documentation, specification, test suite, and ultimately also OCM itself.

I already spoke with @schiessle, @moscicki , @glpatcern, @gmgigi96, @labkode, @smesterheide, @andreasfk and @guidoaben about this at the conference and I got the impression (but correct me if I'm wrong) that we all think this is a good idea. Not everybody needs funding, so some people could just add their name as an "advisor" instead of as a team member, or maybe you approve but don't want to link your name to OCM, or to this particular initiative to do some more work on OCM now, that's also fine.

CC also @LovisaLugnegard and @ishank011 from https://github.com/cs3org/OCM-API/graphs/contributors. Is anyone missing from this list who we should ping about this?

I was thinking of applying for a 50,000 euro grant from https://nlnet.nl/entrust/ (deadline: 1 April).
I can create a first draft text and maybe we can have a video call some time next week to discuss it.
I'll also ping each of you individually so we can determine who wants to be involved in which way, and put together a team and some milestones we want to work on.

I think the main goal would be to:

  • improve the documentation (for instance, write the spec down properly, in RFC style)
  • improve the test suite (it's still mostly manual at this point)
  • describe optional features (a number of interesting routes to explore have been proposed)

I think an anti-goal would be to redesign OCM in a way that's incompatible with what exists now. So if you just implement OCM or use it in any way, then hopefully this activity will either benefit you, or it will leave your situation as it is. Given the open nature of this protocol we just want to help improve the quality of the work that already exists, we don't want to end up hijacking or breaking it in any way! :)
@guidoaben
Copy link

guidoaben commented Mar 14, 2023 via email

@andreasfk
Copy link

HIFIS will absolutely participate as well. As for the role, pro bono should be OK for us, whatever this means in terms of "advisor" or such.

@michielbdejong
Copy link
Contributor Author

I found https://nlnet.nl/core/ which is new (since last month) and feels like an even better fit.
I'll draft something here: https://hackmd.io/noVXpB2NT9mSz4OOikboGw

@guidoaben
Copy link

guidoaben commented Mar 20, 2023 via email

@michielbdejong
Copy link
Contributor Author

Thanks! Sorry, I hadn't made the HackMD public, that is fixed now.
I have only written the first half so far, but it's really short and simple anyway.

I think we have a strong case. What I want to emphasise in the proposal:

  1. OCM is awesome,
  2. it's used in practice,
  3. it has already received funding in the past from different vendors. Then from Géant. Then from CS4MESH4EOSC. Now that funding is ending too and we need a relatively small amount of money to not only keep the momentum, but also do some potentially high-impact and much-needed work on it,
  4. we have a very good team coming together to carry out the work.

We are going to have a video call about it on Wednesday and then submit it on Friday 31 March.

@guidoaben
Copy link

guidoaben commented Mar 23, 2023 via email

@guidoaben
Copy link

guidoaben commented Mar 23, 2023 via email

@michielbdejong
Copy link
Contributor Author

tee hee but now in a practical sense you still haven’t made it public!
What’s the URL?

https://hackmd.io/noVXpB2NT9mSz4OOikboGw

including vendor representation

Good point! I'll see if we can make that a bit more explicit in the text still.

@glpatcern
Copy link
Member

glpatcern commented Apr 28, 2023 •
edited
Loading

The request for funding was sent, thanks Michiel!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@michielbdejong @guidoaben @glpatcern @andreasfk