Thread: [Vim-latex-devel] which github repository is more official?
Brought to you by:
srinathava,
tmaas
From: Peng Yu <pen...@gm...> - 2012-06-30 21:30:50
|
Hi, I have the feeling that sf sucks. Many developers has already been setting up github repositories. But it is not clear to me which one is the most official. I think that it is time to migrate the development to github and maintain a central repository there. Is there one that is the most official in giihub? https://github.com/jcf/vim-latex -- Regards, Peng |
From: Ted P. <te...@te...> - 2012-07-01 01:53:43
|
Peng - git is git regardless of the host. Moreover, sf provides much more than just a repo to the latex suite. How has sf caused you trouble using the official git repo hosted there? Or are you just saying it would be easier for you to submit pull requests rather than patches? Note that git itself is maintained via patches posted to a mailing list rather than pull requests via github. Or do you just like that LinkedIn provides a module for showing off your latex suite contributions? Why don't you just setup a clone on github that automatically pulls from the sf git repo? Or are you saying that there are already so many clones by people not accustomed to anything but pull requests that the latex suite is getting fragmented? (despite all the documentation hooks back to sf) --Ted -- Sent from the mobile device of Ted Pavlic Please excuse typos, swypos, or very brief responses On Jun 30, 2012 2:30 PM, "Peng Yu" <pen...@gm...> wrote: > Hi, > > I have the feeling that sf sucks. Many developers has already been > setting up github repositories. But it is not clear to me which one is > the most official. I think that it is time to migrate the development > to github and maintain a central repository there. Is there one that > is the most official in giihub? > > https://github.com/jcf/vim-latex > > -- > Regards, > Peng > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Peng Yu <pen...@gm...> - 2012-07-01 01:58:21
|
On Sat, Jun 30, 2012 at 8:48 PM, Ted Pavlic <te...@te...> wrote: > Peng - > > git is git regardless of the host. Moreover, sf provides much more than just > a repo to the latex suite. How has sf caused you trouble using the official > git repo hosted there? sf is a badly designed website. I have a much harder time to find the things that I need on sf than on github. > Or are you just saying it would be easier for you to submit pull requests > rather than patches? Note that git itself is maintained via patches posted > to a mailing list rather than pull requests via github. Or do you just like > that LinkedIn provides a module for showing off your latex suite > contributions? I haven't serious compared sf with github. But I've seen more people start using github rather than sf (some people also quit google code for github), but I have not seen a single example that quit sf for github. So I feel that github is the trend. Its pull request feature is also very convenient. > Why don't you just setup a clone on github that automatically pulls from the > sf git repo? > > Or are you saying that there are already so many clones by people not > accustomed to anything but pull requests that the latex suite is getting > fragmented? (despite all the documentation hooks back to sf) Why these people start cloning into github? My interpretation is that github is much more convenient and more people are using github. In this case, why not just host the main repository in github and stop using sf. -- Regards, Peng |
From: Ted P. <te...@te...> - 2012-07-03 05:57:35
|
> sf is a badly designed website. I have a much harder time to find the > things that I need on sf than on github. sf and github have two completely different purposes. github is primarily meant for hosting git repositories and provides some limited ability to distribute documentation. Cloning a repo from github is equivalent to cloning a repo from SF (unless you are using a software package put together by the github folks). > I haven't serious compared sf with github. But I've seen more people > start using github rather than sf (some people also quit google code > for github), but I have not seen a single example that quit sf for > github. So I feel that github is the trend. Its pull request feature > is also very convenient. Again, I really think that github is not meant to be a substitute for SF. If anything, it's complementary. Google Code, however, is much more like an SF alternative. It provides a mechanism for distributing documentation, gathering bug requests, scrutinizing patches, and other SF-like features. Although github has some ability to do these things, github is primarily meant to enable developer collaboration on particular projects. It is not meant to be the end-user front end. > Why these people start cloning into github? My interpretation is that > github is much more convenient and more people are using github. In > this case, why not just host the main repository in github and stop > using sf. How do *you* feel that github is more convenient? Cloning is cloning, regardless of where you are cloning from. At the level of distributing source via a git repository, the two are equivalent. They differ in the additional services provided to collaborating developers, but in both cases developers can collaborate effectively without using any of those features. --Ted -- Ted Pavlic <te...@te...> |
From: Peng Yu <pen...@gm...> - 2012-07-03 12:49:40
|
> How do *you* feel that github is more convenient? Cloning is cloning, > regardless of where you are cloning from. At the level of distributing > source via a git repository, the two are equivalent. They differ in > the additional services provided to collaborating developers, but in > both cases developers can collaborate effectively without using any of > those features. As I said in the previous email, "sf is a badly designed website. I have a much harder time to find the things that I need on sf than on github." -- Regards, Peng |
From: Ted P. <te...@te...> - 2012-07-03 16:37:13
|
> As I said in the previous email, "sf is a badly designed website. I > have a much harder time to find the things that I need on sf than on > github." Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge page is at: http://vim-latex.sourceforge.net/ What problem do you have with this page *that is related to SF* and *that could be fixed by migrating to github*? There is nothing particularly sourceforge-y about this page, and so any trouble you're having finding the information you want here would be replicated on a github site. So it seems like your gripe is more with the layout of the Vim-LaTeX page than with SF itself. If I am not understanding you correctly, then please explain what aspect of the LaTeX-suite SF page is causing you the most trouble in finding the information you want, and how would github improve things? --Ted -- Ted Pavlic <te...@te...> |
From: Peng Yu <pen...@gm...> - 2012-07-04 16:15:15
|
On Tue, Jul 3, 2012 at 11:36 AM, Ted Pavlic <te...@te...> wrote: >> As I said in the previous email, "sf is a badly designed website. I >> have a much harder time to find the things that I need on sf than on >> github." > > Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge > page is at: > > http://vim-latex.sourceforge.net/ You can always configure the above page to make it better. What I don't like is the default sf pages. http://sourceforge.net/projects/vim-latex/ The organization of this default sf page is not friendly to a developer. A developer usually want to see the code directory directly just as in https://github.com/jcf/vim-latex. On the default sf page, some less important things are shown on the main page, developers have to do a few more clicks. -- Regards, Peng |
From: Ted P. <te...@te...> - 2012-07-05 17:41:31
|
>> Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge >> page is at: >> >> http://vim-latex.sourceforge.net/ > > You can always configure the above page to make it better. What I > don't like is the default sf pages. > > http://sourceforge.net/projects/vim-latex/ > > The organization of this default sf page is not friendly to a > developer. A developer usually want to see the code directory directly > just as in https://github.com/jcf/vim-latex. On the default sf page, > some less important things are shown on the main page, developers have > to do a few more clicks. FYI, you're looking for: http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=summary which is linked directly from the Vim-LaTeX web page on the left-hand bar near the bottom: http://vim-latex.sourceforge.net/ Once you find that link and clone the corresponding repo on your machine, you don't even need the website. I guess that's why I don't understand all the commotion. --Ted -- Ted Pavlic <te...@te...> |