Lets see who else steps up. I am a slow e-lisper as well, but a lot of this is organization and minor fixes.
Right now, I feel there are two barriers to entry to have people contribute: bzr and launchpad. Git just has a far larger mind share. Launchpad has lots of great features for large project development, but this also is a barrier to entry. I would start with moving the source to git and migrating to github. Including all branches and tickets. That would be a good starting point for incorporating fixes and working towards a new release. Mark Göran Uddeborg <[email protected]> writes: > Mark Diekhans skrev: > > If anyone is interested, lets start a conversation. VM is an > > amazing pieces of software. We might be able to attract others > > if we can seed a modern approach to collaborative development. > > I'm packaging VM for Fedora, and I would LIKE to participate in > keeping VM up-to-date. For each version of emacs, it is showing the > lack of development. I'm not sure how much I CAN contribute, given > time and elisp competence constraints. For example, with emacs 29.3 > the coloring of the summary buffer sometimes gets into some kind of > busy loop using 1 cpu full time. So far I haven't been able to figure > out what the problem is and what to do about it. > > At the same time, there are circulating patches on this list. Also, of > the issues reported at launchpat.net/vm since way back do include > fixes but seem to stay ignored. If someone creates a repository > somewhere and collects all the patches, that could be a good start. > For "somewhere" there are several options, the weak part is "someone". > > /Göran
