From: Uwe B. <ou...@ma...> - 2016-02-03 17:24:37
|
>>> "Eric" == Eric Ludlam <Eri...@ma...> writes: > I am not opposed to a move to some other DVCS. I just don't do much > development anymore, and I don't really get time at work to work on > this sort of thing anymore. > If those active on this list would like to do a move, I can facilitate > access, setup a new maintainer on SF, and will always be happy to > research things from the MATLAB side to help out when I can. What do other people think? There are three options as far as I can see: 1 leave things as they are 2 stay in sourceforge but convert to git/HG 3 move to a different server (bitbucket (HG)[1]) or githug (git). So please hands up: 1 or 2 or 3? > In any move, a thing to watch out for is that in the past, many users > don't have access to a CVS program, or any other VC software, so the > special matlab download script was created to enable that. Changes > have been small and few, so full releases were not worthwhile to do. I am not sure I understand: github and bitbucket offer the possibility to download the package as a zip without using git or hg. Are you saying that sourceforge does not offer that but requires a script which where not provided by sourceforge? So in the case of a move that script I think is provided by bitbucket or github. BTW, I mentioned the possibility to generate a MELPA packet for matlab (it cannot be ELPA because of copyright issues). This would simplify the installation for the GNU emacs users, but leave xemacs out.[2] a MELPA packet should dwell in github. Uwe > Eric Footnotes: [1] bitbucket also supports git but I have the feeling that once the decision is for git, github seems the preferred choice. [2] xemacs pkg system is right now in zombie state, all new packages are in the pre-release state. |