I'm firmly and completely on the fence on this one. On one hand, on general principles I suppose it would be nice and maybe even useful to someone to have a formal PMX source code repository. On the other, there are various issues: (1) My own limited experience with github has been less than thrilling (2) There hasn't been much action at all on PMX development for the last 5 years or so. (3) Part of the reason for (2) is that my own very robust FORTRAN development system (Visual FORTRAN) will not run under Windows 7 64-bit, and I refuse to invest the $500 or so to upgrade it. For the very limited features I've added since then, I've had to merge all subroutines into a single file and use gfortran, which lacks a useful debugging capability. Another side of that coin is that PMX has reached a pretty stable level of development. (4) Judging from the activity on the mailing list, not many folks at all are using PMX.
I could possibly be convinced to pursue this, but I'm not at the moment. If someone else wants to take the reins, be my guest. --Don Simons > -----Original Message----- > From: TeX-Music [mailto:[email protected]] On Behalf Of David > Allsopp > Sent: Tuesday, November 24, 2015 1:41 AM > To: Werner Icking Music Archive <[email protected]> > Subject: [Tex-music] Source code repositories > > I've had a quick search, so I believe the answer is already "no" - are the > sources for MusiXTeX and related tools really configured only in a directory of > released versions (http://icking-music-archive.org/software/musixtex/) or > are there some proper source code repositories? > > If there aren't, can I suggest there should be (and offer assistance in setting it > up)? The "obvious" solution would be a GitHub organisation (free for open- > source, of course). Having been a victim of name-grabbing before, I have > taken the liberty of reserving www.github.com/tex-music but other options > are available. I'm not aiming to take any kind of lasting control of this, so if > there were interest in doing it, I'd very willingly transfer management of the > Organization to another account and be removed completely. > > Thoughts from maintainers? Very happy to list the myriad benefits of proper > source code configuration and indeed those of using GitHub to manage it if > necessary... > > > David > > ------------------------------- > [email protected] mailing list > If you want to unsubscribe or look at the archives, go to > http://tug.org/mailman/listinfo/tex-music ------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
