From: Jerome L. <je...@le...> - 2015-02-28 21:06:00
|
Hi list A few months ago, I enabled write access to our repositories on Github; thanks to a helpful Python script I wrote, we have mirroring not just from git.lxde to github, but also from github to git.lxde. Currently, two thirds of our commits are made on git.lxde, and one third on github. I would like, in the future, to simplify our infrastructure a bit and turn git.lxde into a read-only mirror for the LXQt repositories. Reasoning: - We require Github accounts already, this should add no extra burden to our developers. - We currently maintain contributors in two different places. This is fairly annoying. The contributor list in gitolite is actually out of date - all our recent contributors are only on Github. - While HelixBot is awesome, it's nicer to know which developers actually close issues and merge PRs. - Gitolite forces a sysadmin to handle the developer public keys. Practically, that means nobody can change ssh key on git.lxde without contacting me first. Github avoids that. - The same logic applies to new repositories, I'm bringing this up because HelixBot has some trouble with branches and tags. He sometimes restores things that were deleted because of a push in the other direction. This caused painful problems during our 0.9 release and I'm wondering if it's worth fixing since we don't have a solid reason to keep him around anymore. I'd like some comments, please. For the time being, unless you really need to commit on git.lxde, please do change your remotes to gi...@gi...:lxde/$repo.git. J. Leclanche |
From: Helio C. de C. <he...@kd...> - 2015-02-28 22:19:04
|
+1 to do that. Take out the burden of admin by yourself the repository administrative tasks is a very good thing. On Sat, Feb 28, 2015 at 6:05 PM, Jerome Leclanche <je...@le...> wrote: > Hi list > > A few months ago, I enabled write access to our repositories on > Github; thanks to a helpful Python script I wrote, we have mirroring > not just from git.lxde to github, but also from github to git.lxde. > > Currently, two thirds of our commits are made on git.lxde, and one > third on github. > I would like, in the future, to simplify our infrastructure a bit and > turn git.lxde into a read-only mirror for the LXQt repositories. > > Reasoning: > - We require Github accounts already, this should add no extra burden > to our developers. > - We currently maintain contributors in two different places. This is > fairly annoying. The contributor list in gitolite is actually out of > date - all our recent contributors are only on Github. > - While HelixBot is awesome, it's nicer to know which developers > actually close issues and merge PRs. > - Gitolite forces a sysadmin to handle the developer public keys. > Practically, that means nobody can change ssh key on git.lxde without > contacting me first. Github avoids that. > - The same logic applies to new repositories, > > I'm bringing this up because HelixBot has some trouble with branches > and tags. He sometimes restores things that were deleted because of a > push in the other direction. This caused painful problems during our > 0.9 release and I'm wondering if it's worth fixing since we don't have > a solid reason to keep him around anymore. > > I'd like some comments, please. > > For the time being, unless you really need to commit on git.lxde, > please do change your remotes to gi...@gi...:lxde/$repo.git. > > > J. Leclanche > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: <chr...@su...> - 2015-02-28 22:51:12
|
+1 br. Chr. 2015-02-28 22:05 GMT+01:00 Jerome Leclanche <je...@le...>: > Hi list > > A few months ago, I enabled write access to our repositories on > Github; thanks to a helpful Python script I wrote, we have mirroring > not just from git.lxde to github, but also from github to git.lxde. > > Currently, two thirds of our commits are made on git.lxde, and one > third on github. > I would like, in the future, to simplify our infrastructure a bit and > turn git.lxde into a read-only mirror for the LXQt repositories. > > Reasoning: > - We require Github accounts already, this should add no extra burden > to our developers. > - We currently maintain contributors in two different places. This is > fairly annoying. The contributor list in gitolite is actually out of > date - all our recent contributors are only on Github. > - While HelixBot is awesome, it's nicer to know which developers > actually close issues and merge PRs. > - Gitolite forces a sysadmin to handle the developer public keys. > Practically, that means nobody can change ssh key on git.lxde without > contacting me first. Github avoids that. > - The same logic applies to new repositories, > > I'm bringing this up because HelixBot has some trouble with branches > and tags. He sometimes restores things that were deleted because of a > push in the other direction. This caused painful problems during our > 0.9 release and I'm wondering if it's worth fixing since we don't have > a solid reason to keep him around anymore. > > I'd like some comments, please. > > For the time being, unless you really need to commit on git.lxde, > please do change your remotes to gi...@gi...:lxde/$repo.git. > > > J. Leclanche > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: Alf G. <ag...@si...> - 2015-02-28 23:09:42
|
+1 Greetz Alf On Sat, 28 Feb 2015 21:05:32 +0000 Jerome Leclanche <je...@le...> wrote: > Hi list > > A few months ago, I enabled write access to our repositories on > Github; thanks to a helpful Python script I wrote, we have mirroring > not just from git.lxde to github, but also from github to git.lxde. |
From: Andrej N. G. <an...@re...> - 2015-03-01 00:07:10
|
Hello! Jerome Leclanche has written on Saturday, 28 February, at 21:05: >Currently, two thirds of our commits are made on git.lxde, and one >third on github. >I would like, in the future, to simplify our infrastructure a bit and >turn git.lxde into a read-only mirror for the LXQt repositories. Interesting thing - you want to abandon the place where the most of the commits are made. ;) Well, I know how much you love github and treat lxde.org infrastructure as a burden. :) Anyway, I hope you will not break LXDE components at the very least, they should stay at git.lxde.org still as they don't exist elsewhere. Thank you. With best regards, Andriy. |
From: Jerome L. <je...@le...> - 2015-03-01 00:48:48
|
Hi, On 1 March 2015 at 00:06, Andrej N. Gritsenko <an...@re...> wrote: > Hello! > > Jerome Leclanche has written on Saturday, 28 February, at 21:05: > >>Currently, two thirds of our commits are made on git.lxde, and one >>third on github. >>I would like, in the future, to simplify our infrastructure a bit and >>turn git.lxde into a read-only mirror for the LXQt repositories. > > Interesting thing - you want to abandon the place where the most of the > commits are made. ;) I believe most commits are made on git.lxde because that is where developers were originally supposed to commit, and simply nobody changed the remotes since. Until I set up mirroring, there was massive demand to make the mirroring available from Github. > > Well, I know how much you love github and treat lxde.org infrastructure > as a burden. :) Anyway, I hope you will not break LXDE components at the > very least, they should stay at git.lxde.org still as they don't exist > elsewhere. Thank you. Please don't say that. If I thought the lxde.org infrastructure was a burden, I wouldn't be doing this ;) I enjoy it a lot, I just believe this is better for the project. Either way, of course, the GTK projects will remain as they currently are (unless a maintainer wants to move theirs to github, in which case let me know I'm happy to oblige). Mirroring *from* Github will also stay in place, but if this goes through I will revoke write permissions from everyone on LXQt repositories on git.lxde. J. Leclanche > > With best regards, > Andriy. > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |
From: Andrej N. G. <an...@re...> - 2015-03-01 01:08:02
|
Hello! Jerome Leclanche has written on Sunday, 1 March, at 0:48: >> Well, I know how much you love github and treat lxde.org infrastructure >> as a burden. :) Anyway, I hope you will not break LXDE components at the >> very least, they should stay at git.lxde.org still as they don't exist >> elsewhere. Thank you. >Please don't say that. If I thought the lxde.org infrastructure was a >burden, I wouldn't be doing this ;) I enjoy it a lot, I just believe >this is better for the project. >Either way, of course, the GTK projects will remain as they currently >are (unless a maintainer wants to move theirs to github, in which case >let me know I'm happy to oblige). Mirroring *from* Github will also >stay in place, but if this goes through I will revoke write >permissions from everyone on LXQt repositories on git.lxde. Thank you very much! Have a happy beautiful spring! :) With best regards, Andriy. |
From: Jerome L. <je...@le...> - 2015-03-02 09:07:40
|
Hi list The LXQt repositories on git.lxde.org are now read-only. Please update your remotes to reflect this. The legacy LXQt repositories (appswitcher, liblxqt-mount, etc) are still RW+ as they are only hosted there. On 1 March 2015 at 01:07, Andrej N. Gritsenko <an...@re...> wrote: > Hello! > > Jerome Leclanche has written on Sunday, 1 March, at 0:48: >>> Well, I know how much you love github and treat lxde.org infrastructure >>> as a burden. :) Anyway, I hope you will not break LXDE components at the >>> very least, they should stay at git.lxde.org still as they don't exist >>> elsewhere. Thank you. > >>Please don't say that. If I thought the lxde.org infrastructure was a >>burden, I wouldn't be doing this ;) I enjoy it a lot, I just believe >>this is better for the project. > >>Either way, of course, the GTK projects will remain as they currently >>are (unless a maintainer wants to move theirs to github, in which case >>let me know I'm happy to oblige). Mirroring *from* Github will also >>stay in place, but if this goes through I will revoke write >>permissions from everyone on LXQt repositories on git.lxde. > > Thank you very much! Have a happy beautiful spring! :) > > With best regards, > Andriy. > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list |