The default opam repository has been getting larger and larger with an ever increasing number of packages. This is somewhat of a good sign for the active community of OCaml developers. But it is also a challenge for its use, for its maintenance, and for the execution of its CI.
A discussion on the future of the opam repository is happening and we (the opam repository maintainers) would like to invite OCaml developers at large to participate.
Hello Thanks, @raphael-proust, for that initiative! IMO it’s an important discussion to have and it’s very nice that you’re making it public.
I won’t be able to make it to the meeting on Wednesday, and I’m also not sure how much I’d contribute, I’m mostly just interested in the discussion. Are you going to put a quick summary either here or on the issue? (no pressure, I know you all already have a lot of work anyways)
Just so it’s clear, I didn’t take this initiative, I’ve just ended up being the one of several maintainers who posted the message. I won’t tag the people who have been actively participating in this conversation nor the ones who have organised the public meeting because I want to spare them the notifications. The github issue has some names if anyone is interested.
As for the summary, yes, we intend to keep notes and make it known what options have been mentioned and pros-and-cons have been listed and, if any, what consensus has been reached. I’ll post a link to the notes on here.
Along with other volunteers, we have taken notes during the meeting. They are available on the github issue.
TL;DR:
There was a general consensus to create an “archive” repository where we can move broken, unmaintained, obsolete packages (specific characterisation still to be defined)
There is another meeting planned on 2024-02-07 to discuss the specifics further
If this topic is important to you:
Please leave comments on the github thread. Please attend the meeting.
The notes for last week’s meeting are available here
For everyone who wants to come to the next meeting, please fill the framadate as soon as you know when you are available, so that we can plan when the meeting is going to be.
Arf, I’m sorry you had this problem and didn’t see this notification from discuss. Jitsi is supposed to let you in automatically when the meeting starts, i think it did for everyone present but not you for some reason.
I also saw your username in the first 15 minutes of the meetings though, you were in the meeting for us, i even marked your name in the people present in the notes. Maybe it’s something to report to the Jitsi folks.
Thanks, 