Dmitry Borodaenko <angdr...@debian.org> writes: > > Generally speaking, the best way to set up collaborative maintenance for > such packages is to put them up on Salsa [0], for that you'll need to > convert them to Git packaging [1] if they aren't already on it (e.g. > blank VCS field for MLton tells me that it's not). >
Thankfully, MLton is indeed using Git. That field will need to be updated. > > [0] https://wiki.debian.org/Salsa > [1] https://wiki.debian.org/PackagingWithGit > >> For example, MLton [0] could use updating, and working through the >> different branches. Likewise for PolyML, and SMLnj. I think helping with >> these three collections of packages would be a good first step into >> possibly helping Debian in the future. > > Sounds like your interests are relevant for the Debian Science team [2] > (which is marked dead) and Debian Science Maintainers team [3], getting > in touch with them would be a good place to start. > > [2] https://wiki.debian.org/DebianScience > Could you explain what "marked dead" means in this context? Is the Debian Science team different from the Debian Science Maintainers team? Thank you for clarifying the issue. -- Brett M. Gilio <bre...@gnu.org> https://brettgilio.com
