guys, i think we're not understanding each other, even after the democratic
process, and the github developers views being presented (one was active
and motivated to develop, the other said he can take pull requests --- do
we have any active developer in sourceforge or do we have anyone taking
pull requests here? if we convert to git and keep it in sourceforge, the
only difference is that developers are gonna clone the git repo directly
and push it to github. thus in practice nothing is solved as they are not
going to do pull requests to sourceforge. and even if they did nobody would
review or accept them (i might be wrong).
(1) mailing list import
there's no mailing list in github, so its not possible to import it.
if we move to github, we either keep the mailing list here, or we just use
the github facilities such as issues with tags/labels, as other projects
use.
for example on the spacemacs project, if u want to search for questions in
the issues:
https://github.com/syl20bnr/spacemacs/issues?utf8=%E2%9C%93&q=label%3Aquestion
of course, we would not be able to consult the old mailing list this way,
and i dont think it would be easy to convert it to this format. then we
would have to reference the old mailing list.
(2) issues
regarding bugs, feature requests etc, i think i could do manually as
they're only a bit more than 20 in total (all of them are several years old
and probably not very usefull).
(3) conclusions
github was the chosen option by the developers and mailing list
subscribers.
i think the easiest way would be to keep the mailing list in sourceforge.
put a link to the new github repo in the sourceforge. it should be very
easy to keep sourceforge and github synchronized if needed.
personally i will keep using some github version of matlab-mode, either
official or not. if at some point it exceeds dramatically the sourceforge
version, i would probably pull request melpa to use the github version to
help other users.
thats all from me, im leaving this threat. let me know if help is needed
after a plan of action is ready.
cheers
d
On Fri, Feb 5, 2016 at 12:04 PM, Uwe Brauer <o...@mat.ucm.es> wrote:
> >>> "Eric" == Eric Ludlam <eric.lud...@mathworks.com> writes:
>
> > I can add a git repo to the project, but we'd have to translate the
> > content over ourselves. (As far as I know anyway)
>
> > Eric
>
>
> I just got a reply from the SF team, and yes we do have to convert the
> repo ourselves.
>
> As I said I did this using git --cvsimport successfully.
> So that problem is solved.
>
>
> Please github users: is it possible to import a SF account with the
> mailing list and issues etc????
>
> If not I propose we stay in SF and switch to git.
>
> I propose to wait till Monday before taking any actions.
>
> Comments?
>
> Uwe Brauer
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Matlab-emacs-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
