ocaml-community / meta Goto Github PK

The current process seems to be to give rights to anyone who wants to move a project over, and since you need admin rights to transfer a project, that's what they get.

Needless to say that this is not going to fly for long. :)

I propose to distinguish various group of people:

1. Admins that can do anything,
2. People that want to maintain/contribute to specific packages, but are not (yet!) people you would trust with life&death power over the entire org. This would be for people who are frequent community member and maintain several packages
3. Maintainer of a single package, such as newly migrated packages. Those don't have to be org members and can simply be given rights to that package.

When migrating a repository, the person who wants to migrate would transfer the repository to one of the admins, who would then move it to the organization. That person would then be given rights to the specific packages, or added as org member in group 2., as deemed appropriate.

Thoughts ?

Propose to move a project to ocaml-community

Project name: ocaml-fileutils

Initial author(s): me (gildor478@)

Current URL: https://github.com/gildor478/ocaml-fileutils

License: LGPL + OCaml Exception

Description: A collection of file utilities (mv, cp...) using POSIX semantics

Do the current maintainer(s) agree with the move: Yes.

New maintainer: looking for a volunteer

An OPAM maintainer (Kate) has contacted me but I am not sure if they want to take over the maintenance. I would be mainly interested in allowing more people to do maintainance releases, since I am not very active in OCaml right now.

These were all factored out of Lwt recently (ocsigen/lwt#532. ocsigen/lwt#524, ocsigen/lwt#511, ocsigen/lwt#517).

I maintain them, and will be happy to continue doing so. Each package already has a working CI setup.

Almost no work is required on these, but sometimes something needs to be tweaked, especially when there are changes in major versions of Lwt.

I'd like to propose the three following projects I wrote:

• https://github.com/diml/utop
• https://github.com/diml/lambda-term
• https://github.com/diml/zed

utop is a popular alternative to the OCaml toplevel. It provides nice features such as line edition and completion. The code hasn't changed much in a while, so it is stable and overall the project is low maintenance. However, as it uses the compiler-libs, it does often require small adjustments and a new opam release when a new version of the compiler is released.

lambda-term is a terminal library for OCaml. It is a dependency of utop and is used by a few projects in opam. As utop, the code hasn't changed in a while and is even lower maintenance. I believe that https://github.com/pqwy/notty is now a better alternative but utop and a few other projects are still using lambda-term.

zed is an abstract edition engine. It is a dependency of lambda-term and is used to implement line edition.

It'd be nice to move bigstring here, it's really mostly a compat package

Although it's precedented from the elm-community and coq-community organizations, the "manifesto" repository should probably be named something clearer, like "admin" or some such. Opinions solicited.

I already transferred cppo to ocaml-community. We're looking for a volunteer to take over its maintenance. No new features are planned and bugs are infrequently found. The maintainers will need to ensure that cppo remains compatible with old and new versions of OCaml. Currently, 57 public opam packages depend on cppo.

Project name: cppo

Initial author(s): Martin Jambon

Current URL: already transferred

License: BSD

Description: C-style preprocessor for OCaml

Do the current maintainer(s) agree with the move: yes

New maintainer: looking for a volunteer

The README suggests setting up Travis CI for imported projects, however the file was last updated 6 years ago, and things have changed since. In particular I found https://earthly.dev/blog/migrating-from-travis/ via Wikipedia and https://discuss.ocaml.org/t/best-practices-for-continuous-integration-ci-in-2023/12380. So, is it time to replace the reference to Travis CI with a more generic suggestion or a different recommendation?

Propose to move a project to ocaml-community

Project name:

OCaml-MariaDB, ocaml-mariadb, mariadb (opam)

Initial author(s):

Andre Nathan

Current URL:

https://github.com/andrenth/ocaml-mariadb

License:

MIT

Description:

OCaml-MariaDB provides Ctypes-based bindings for MariaDB, including its nonblocking API. I think this is our best maintained client to MariaDB and MySQL, and the one use by Caqti (maintained by me).

Do the current maintainer(s) agree with the move:

Yes, the move has been agreed between the original author, current maintainer, and me in ocaml-community/ocaml-mariadb#53.

New maintainer:

I suggest @ygrek, who current has commit rights, and who I think will be making releases, and maybe myself as a backup, at least I plan to help out in the near future and with the move.

Propose to move a project to ocaml-community

Project name: linenoise

Initial author(s): Edgar Aroutiounian (fxfactorial)

Current URL: https://github.com/fxfactorial/ocaml-linenoise

License: BSD

Description: self-contained readline alternative, without dependencies on system libraries

Do the current maintainer(s) agree with the move: yes, see ocaml-community/ocaml-linenoise#9

New maintainer: @c-cube (been maintaining it for a while)

Is this on purpose or just forgot to enable option?

It's even linked in the manifest, where it leads to an empty page.

We should update the documentation to note that every repository, as it is accepted, should have:

0. A grep done through the code checking for references to any old repositories, and appropriate updates should be made.
1. A CODEOWNERS file designating the initial maintainers/gatekeepers for pull requests. See https://help.github.com/articles/about-codeowners/
2. opam package files, pointing at the correct updated repository if there was an old opam package.
3. Travis CI implemented to make sure that the repository builds. The exact supported versions should be discussed, but generally it should be the latest several versions, on Linux and on MacOS.

Thoughts solicited.

Propose to move a project to ocaml-community

Project name: awesome-ocaml

Initial author(s): rizo (that's me)

Current URL: https://github.com/rizo/awesome-ocaml

License: N/A

Description: A curated collection of awesome OCaml tools, frameworks, libraries and articles.

Do the current maintainer(s) agree with the move: I do.

New maintainer: Me again...

I'm proposing this move not because I don't want to maintain awesome-ocaml, but because I believe having it in a more "official" location than my personal account is better for the project.

Since I started the awesome-ocaml list it has attracted dozens of contributors (special thanks to @gasche and @Drup for their reviews) and has been very popular on GitHub (it currently has 1466 stars). I hope that by moving it to the ocaml-community we can bring even more contributions, collectively improve it and keep it up to date.

I will continue maintaining the project, but everyone in the community organization is welcome to join me.

Seems abandoned but a great deal (not sure why Clang project doesn't adapt them)
https://github.com/Antique-team/clangml

I really like the idea of, in addition to having individual repositories for each project managed by ocaml-community, having a centralized workspace for maintainers/contributors to work and build all projects at once – this might speed up development, contribute to consistency across projects and ensure reliability over time.

Duniverse is a tool that does exactly that. See a detailed explanation by @lpw25 of the benefits here.

I suggest we create the ocaml-community/duniverse repository and add a configuration to include all packages we currently have as an experiment.

In addition, our feedback might be helpful to duniverse creators (cc @avsm).

Thoughts/objections?

Yojson is a widely-used json parsing and pretty-printing library. It was designed as the runtime for atdgen with performance in mind. If anyone would like to become the new lead maintainer, please step forward.

Project name: yojson

Initial author(s): Martin Jambon

Current URL: already transferred to ocaml-community

License: BSD

Description: json parsing and printing library for OCaml designed to be used by type-aware code generators

Do the current maintainer(s) agree with the move: yes

New maintainer: looking for a volunteer

Francois Berenger (@UnixJunkie), a long-time member of the ocaml open-source community would like to take over the ocamlscript project. I think ocaml-community is a fitting home for the project.

Project name: ocamlscript

Initial author(s): David Mentré, Martin Jambon

Current URL: https://github.com/mjambon/ocamlscript

License: Boost software license

Description: compiles ocaml scripts starting with #! /usr/bin/env ocamlscript just in time with ocamlopt and runs them. Supports libraries specified as ocamlfind packages, and multiple source files.

Do the current maintainer(s) agree with the move: yes

New maintainer: Francois Berenger (@UnixJunkie)

Propose to move a project to ocaml-community

Project name: ocaml-cstruct

Initial author(s):

Current URL: https://github.com/mirage/ocaml-cstruct

License: ISC License

Description: Access C-like structures directly from OCaml

Do the current maintainer(s) agree with the move: unknown - no response, project looks dead

New maintainer: I am a volunteer

Maybe it'd make sense to list out users with the Owner and Admin role. It'd help people know who to contact, in-case of issues with CI, or other actions that need admin privilege.

In this post, I expressed the fact that projects should still have dedicated maintainers.

I think new projects should always come with a sort of "Call for Maintainship" and that having a volunteer for the job would be a condition for bringing in ocaml-community. Of course, not all projects require the same amount of attention, and some of them just requires small updates to compile on OCaml versions, but even then, we should have one person that takes ownership. A call for maintainship would of course make explicit the state of the project.

Ideally, the process should not be too rigid, of course, so I'm not sure exactly how to make it nice in practice. We should definitely send out the calls on various mediums, such as discuss/planet on a regular basis.

Hey all, I'm considering moving some of the projects at @mjambon to here, as it requires too much expertise to manage all the facets of project development and distribution. Before getting involved, I'd like to know if the organization has a code of conduct. The goal is to ensure everyone (including me!) feels comfortable contributing, so that the community can grow. We could probably reuse a document that's already in use by another community in order to save efforts.

Thoughts?

I just cut a list of projects I think would be good to migrate from mjambon to ocaml-community. I'd be the initial lead maintainer of these projects until we find someone else.

Let me know if you have immediate thoughts or reactions. I'll make a proper request for inclusion for each project when I have more time.

The list includes all the projects which match the following criteria:

• I'm the primary or original author. Copyright may be shared with past or current employers. All the projects come with a license that allows further development and distribution. To the best of my knowledge, nobody would be upset by moving them to a more community-oriented development style.
• The project is being used by others or is at least considered useful to a general audience (as opposed to a narrow domain of application).
• Maintaining the project doesn't require highly specialized domain knowledge. Any advanced OCaml programmer would have enough technical knowledge to contribute to the project.
• Help is needed primarily for maintenance tasks more than bold new features. This includes sorting issues, reviewing pull requests, managing releases, and helping and encouraging new contributors.

This is the list of projects I'm considering for migration:

• atd
• biniou
• caml2html
• cmitomli
• cppo
• dum
• dune-starter
• dutop
• easy-format
• ocamlscript
• sampl
• wcl
• yojson

Consider mirroring to and accepting contributions to some or all of this org's repos on codeberg, notabug, or framagit. Thanks for considering. Feel free to close if this is not of interest.

Travis is very unreliable for CI testing these days, and it's likely to get worse as they've lost a lot of staff. The MacPorts project has been very successfully using Azure Pipelines for the last few months as a secondary test system; it almost never has spurious failures. It would be good for us to set the same thing up for ocaml-community.

Propose to move a project to ocaml-community

Project name: ISO8601

Initial author(s): @sagotch

Current URL: https://github.com/sagotch/ISO8601.ml

License: MIT

Description: parser and printer for the standard representation of datetime

Do the current maintainer(s) agree with the move: yes

New maintainer: I (@c-cube) am willing to do it, not expecting a lot of new features to be added.

Propose to move a project to ocaml-community

Project name: Camomile

Initial author(s): https://github.com/yoriyuki

Current URL: https://github.com/yoriyuki/Camomile

License: LGPL 2 or above

Description: Unicode library for OCaml

Do the current maintainer(s) agree with the move: yes

New maintainer: Romain Beauxis plus anyone interested to contribute

Camomile is very valuable library in the OCaml ecosystem. It is the only one that provides output capacities in legacy string encodings. The code has been in need of some love, most importantly an update to support OCaml 5.

The move and initial development plans have been discussed and approved by the original author.

Propose to move a project to ocaml-community

Project name: biniou

Initial author(s): Martin Jambon (me)

Current URL: https://github.com/mjambon/biniou

License: BSD

Description: runtime for an extensible binary format. Usable in a safe manner via atdgen, see https://atd.readthedocs.io/en/latest/

Do the current maintainer(s) agree with the move: yes

New maintainer: looking for a volunteer

Propose to move a project to ocaml-community

Project name:
Calendar/CalendarLib

Initial author(s):
Copyright © 2003-2011 Julien Signoles

Current URL:
http://calendar.forge.ocamlcore.org

License:
LGPL (version 2.1), with the usual OCaml linking exception.

Description:
The Calendar Library (Calendar for short) is an Objective Caml library for handling dates and times in your program.

Do the current maintainer(s) agree with the move:
There is an email listed in the README
I haven't yet contacted Julien, as I'm a bit shy about it. I'd be very happy if some more established member of the community does the initial contact.

The current issue tracker/website of the project seems abandoned and we haven't seen new releases since 2014.

New maintainer:

I volunteer to be the new maintainer if Julien doesn't want to continue maintaining the library.
I already have new features in the pipeline which I don't know how to contribute (especially since the library doesn't use git, pull-requests etc. and I don't know svn well. This is also the main reason for me proposing that we include the code in ocaml-community (I'd like a modern, standardized workflow)

Propose to move a project to ocaml-community

Project name: easy-format

Initial author(s): Martin Jambon (me)

Current URL: https://github.com/mjambon/easy-format

License: BSD

Description: functional pretty-printing library

Do the current maintainer(s) agree with the move: yes

New maintainer: looking for a volunteer

I'd like to propose the yaml bindings for community maintenance. They most already work, but need to keep up with Yaml versions, and some of the more advanced features like Yaml aliases need to be implemented carefully.

Propose to move a project to ocaml-community

Project name: ocaml-language-server

Initial author(s): Darin Morrison (me)

Current URL: https://github.com/ocaml-lsp/ocaml-language-server

License: Apache 2.0

Description: Language server for OCaml implemented in TypeScript using MS component libs

Do the current maintainer(s) agree with the move: Yes

New maintainer: looking for additional maintainers to help with project maintenance

ocaml does that.

Propose to move a project to ocaml-community

Project name: obus

Initial author(s): Jérémie Dimino (diml)

Current URL: https://github.com/diml/obus

License: BSD

Description: Pure OCaml implementation of D-Bus IPC protocol

Do the current maintainer(s) agree with the move: yes (https://discuss.ocaml.org/t/should-obus-be-moved-to-ocaml-community/3946)

New maintainer: I could take it so far (Eugene Bulavin @Freyr666)