Menu
▾
▴
matlab-emacs-discuss
|
From: Uwe B. <ou...@ma...> - 2016-02-04 15:28:44
|
Hi I just wrote the sourceforge team to see whether it would be possible to convert the account from CVS to git. (And so save the mailing list archive) If somebody knows how to export/convert a sourceforge account to github, transferring the mailing list archive, please speak up. Regards Uwe Brauer |
|
From: Eric L. <Eri...@ma...> - 2016-02-04 19:58:17
|
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 -----Original Message----- From: Uwe Brauer [mailto:ou...@ma...] Sent: Thursday, February 04, 2016 10:29 AM To: matlab-emacs <mat...@li...> Subject: [Matlab-emacs-discuss] sourceforge github Hi I just wrote the sourceforge team to see whether it would be possible to convert the account from CVS to git. (And so save the mailing list archive) If somebody knows how to export/convert a sourceforge account to github, transferring the mailing list archive, please speak up. Regards 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 Mat...@li... https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss |
|
From: Uwe B. <ou...@ma...> - 2016-02-05 11:04:46
|
>>> "Eric" == Eric Ludlam <Eri...@ma...> 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 |
|
From: Cayetano S. <cay...@in...> - 2016-02-05 13:11:17
Attachments:
signature.asc
|
On 05-02-16 11:04:36, Uwe Brauer wrote: >>>> "Eric" == Eric Ludlam <Eri...@ma...> 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? As far as I know, it's not. Now, once we decide to move to GitHub, is it really that necessary to keep the old mailing list ? I mean we can track in GitHub issues, announces, releases, etc, similar to the way other huge projects are doing. The old mailing list would be kept as a read-only reference on SF. -- Cayetano Santos >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 >Mat...@li... >https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss |
|
From: dl <fri...@ho...> - 2016-02-07 11:26:39
|
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 <ou...@ma...> wrote: > >>> "Eric" == Eric Ludlam <Eri...@ma...> 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 > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss > > |
|
From: Uwe B. <ou...@ma...> - 2016-02-08 11:24:46
|
>>> "dl" == dl <fri...@ho...> writes:
> guys, i think we're not understanding each other, even after the
Ok let us try to sort this out then. Recall the starting point was when
Eric asked for help to apply some patches (I recall 2 but there might be
more). I answered saying that I almost forgot what I ever knew about CVS
and whether we could switch to a DVCS like git or hg. So we had a
discussion and a vote and git won, so far so good.
It is true that some people, among them, developers of other
emacs-matlab versions expressed their interest to switch to github,
however what I did not realise at that point, was that we did not
discuss of how to export the mailing list (and maybe other stuff like
issues etc, but I believe there is besides the mailing list nothing
really interesting, if there is, please speak up).
So I think it is best to discuss this issue now, and may be vote again.
- I ask: if we use a DVCS, like git, then the very nature of it is as follows:
people can
clone the repo
add their code, apply patches, merge etc
and then push it back.
This is a *decentralised* program, this is the beauty of it, no
central server needed as in CVS or subversion.
So once we have decided for git, I don't see any difference
between sourceforge/github/bitbucket etc, save the graphical
interface.
Does everybody agree with that? A CVCS makes the question of the
server less important, no?
Or does github has some shiny wonderful feature I oversee?
- how important is the mailing list and its archive to people on
this list? I admit for me it is quite important and that is why I
argue for staying in sourceforge but switching to git. What do
other people think?
Regards
Uwe Brauer
|
|
From: Simon B. <li...@70...> - 2016-02-08 13:09:06
|
On Mon, 8 Feb 2016, at 11:24 AM, Uwe Brauer wrote: > So once we have decided for git, I don't see any difference > between sourceforge/github/bitbucket etc, save the graphical > interface. > Does everybody agree with that? A CVCS makes the question of the > server less important, no? > Or does github has some shiny wonderful feature I oversee? The feature github has is the large community that uses it and that it has become the de facto standard hosting location. There are multiple forks of matlab-mode on github because that is the easiest place for many people to publish their changes. If we want to collect those changes we have to make it as easy as possible for people to contribute and for many people a github pull request is the easiest way to do that. Working with SF is only slightly more effort, but we have to aim for the minimum. At the least we should have a github mirror that people can raise pull requests against. But if we do that then the SF repo is just extra effort. Simon |
|
From: Uwe B. <ou...@ma...> - 2016-02-08 14:21:04
|
> On Mon, 8 Feb 2016, at 11:24 AM, Uwe Brauer wrote:
> The feature github has is the large community that uses it and that it
> has become the de facto standard hosting location. There are multiple
> forks of matlab-mode on github because that is the easiest place for
> many people to publish their changes. If we want to collect those
> changes we have to make it as easy as possible for people to contribute
> and for many people a github pull request is the easiest way to do that.
> Working with SF is only slightly more effort, but we have to aim for the
> minimum.
> At the least we should have a github mirror that people can raise pull
> requests against. But if we do that then the SF repo is just extra
> effort.
That sounds very reasonable to me, the question is how to set it up. I
mean opening a github account is easy and cloning the repo as well,
but how can we set up the mirror?
Uwe
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X