[PySide] RFC: Removing PySide rom git-hub?
Hugo Parente Lima
gerrit only sync PySide repositories with gitorious, so the git-hub
repositories will be out dated because nobody will remember to sync them :-/
So, my question is: Should I remove PySide from git-hub? No code will be lost
because the helper repositories found on github and not on gerrit can be found
on gitorious.
--
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia
anatoly techtonik
<hugo...@openbossa.org> wrote:
> Hi,
>
> gerrit only sync PySide repositories with gitorious, so the git-hub
> repositories will be out dated because nobody will remember to sync them :-/
>
> So, my question is: Should I remove PySide from git-hub? No code will be lost
> because the helper repositories found on github and not on gerrit can be found
> on gitorious.
Nooo. Many people can't access Gerrit and can't submit patches therefore.
Gitorious suxx as was discussed many times. I'd like BuildScripts to continue
using GitHub. Because barrier for patch entry to Gerrit is too high.
Why isn't it possible to sync with GitHub?
http://gerrit.googlecode.com/svn/documentation/2.1.5/config-replication.html
It is theoretically possible to sign in into Gerrit using GitHub
account and pull patches from GitHub automatically. After Gerrit will
be decoupled from Jira - this will be the next logical thing to do. I
use GitHub to monitor PySide development. It is convenient.
--
anatoly t.
_______________________________________________
PySide mailing list
PyS...@qt-project.org
http://lists.qt-project.org/mailman/listinfo/pyside
Renato Araujo
I do not like both gitorious or gerrit, but since this is not a
question of choice (this changes was mandatory). In my opinion github
is the best tool to work with git repositories at moment. But I think
we need keep all the changes in the same place to avoid redundancy,
and try to keep the work easy for the maintainers.
+1
Renato Araujo Oliveira Filho
Hugo Parente Lima
> On Fri, Mar 16, 2012 at 2:21 PM, Hugo Parente Lima
>
> <hugo...@openbossa.org> wrote:
> > Hi,
> >
> > gerrit only sync PySide repositories with gitorious, so the git-hub
> > repositories will be out dated because nobody will remember to sync them
> > :-/
> >
> > So, my question is: Should I remove PySide from git-hub? No code will be
> > lost because the helper repositories found on github and not on gerrit
> > can be found on gitorious.
>
> Nooo. Many people can't access Gerrit and can't submit patches therefore.
> Gitorious suxx as was discussed many times. I'd like BuildScripts to
> continue using GitHub. Because barrier for patch entry to Gerrit is too
> high.
>
> Why isn't it possible to sync with GitHub?
> http://gerrit.googlecode.com/svn/documentation/2.1.5/config-replication.htm
> l
I agree, but this configuration isn't up to me, I need to ask to people on qt-
project if they can do this for us. I'm going to ping them after the weekend.
> It is theoretically possible to sign in into Gerrit using GitHub
> account and pull patches from GitHub automatically. After Gerrit will
> be decoupled from Jira - this will be the next logical thing to do. I
> use GitHub to monitor PySide development. It is convenient.
yes, I know, but if the repositories get out-dated you will monitor nothing
:-/.
> --
> anatoly t.
anatoly techtonik
<hugo...@openbossa.org> wrote:
> On Friday 16 March 2012 12:00:44 anatoly techtonik wrote:
>> On Fri, Mar 16, 2012 at 2:21 PM, Hugo Parente Lima
>>
>> <hugo...@openbossa.org> wrote:
>> > Hi,
>> >
>> > gerrit only sync PySide repositories with gitorious, so the git-hub
>> > repositories will be out dated because nobody will remember to sync them
>> > :-/
>> >
>> > So, my question is: Should I remove PySide from git-hub? No code will be
>> > lost because the helper repositories found on github and not on gerrit
>> > can be found on gitorious.
>>
>> Nooo. Many people can't access Gerrit and can't submit patches therefore.
>> Gitorious suxx as was discussed many times. I'd like BuildScripts to
>> continue using GitHub. Because barrier for patch entry to Gerrit is too
>> high.
>>
>> Why isn't it possible to sync with GitHub?
>> http://gerrit.googlecode.com/svn/documentation/2.1.5/config-replication.htm
>> l
>
> I agree, but this configuration isn't up to me, I need to ask to people on qt-
> project if they can do this for us. I'm going to ping them after the weekend.
I was about to sent a request to g...@qt-project.org but then noticed
that PySide and Gitorious repos are in sync:
http://qt.gitorious.org/pyside/pyside/commits/master
https://github.com/PySide/PySide/commits/master
Is GitHub sync still an issue? It may worth to add a note though that
the proper place to sent patches is Gerrit.
BTW, what was the decision about http://www.pyside.org/ ? It can be
hosted on GitHub.
Hugo Parente Lima
> On Fri, Mar 16, 2012 at 8:35 PM, Hugo Parente Lima
>
> <hugo...@openbossa.org> wrote:
> > On Friday 16 March 2012 12:00:44 anatoly techtonik wrote:
> >> On Fri, Mar 16, 2012 at 2:21 PM, Hugo Parente Lima
> >>
> >> <hugo...@openbossa.org> wrote:
> >> > Hi,
> >> >
> >> > gerrit only sync PySide repositories with gitorious, so the git-hub
> >> > repositories will be out dated because nobody will remember to sync
> >> > them
> >> >
> >> > :-/
> >> >
> >> > So, my question is: Should I remove PySide from git-hub? No code will
> >> > be lost because the helper repositories found on github and not on
> >> > gerrit can be found on gitorious.
> >>
> >> Nooo. Many people can't access Gerrit and can't submit patches
> >> therefore. Gitorious suxx as was discussed many times. I'd like
> >> BuildScripts to continue using GitHub. Because barrier for patch entry
> >> to Gerrit is too high.
> >>
> >> Why isn't it possible to sync with GitHub?
> >> http://gerrit.googlecode.com/svn/documentation/2.1.5/config-replication.
> >
> > I agree, but this configuration isn't up to me, I need to ask to people
> > on qt- project if they can do this for us. I'm going to ping them after
> > the weekend.
>
> I was about to sent a request to g...@qt-project.org but then noticed
> that PySide and Gitorious repos are in sync:
>
> http://qt.gitorious.org/pyside/pyside/commits/master
> https://github.com/PySide/PySide/commits/master
>
> Is GitHub sync still an issue? It may worth to add a note though that
> the proper place to sent patches is Gerrit.
Yes, it still a issue, and a note should be posted on all repositories
description besides setting them read-only.
>
> BTW, what was the decision about http://www.pyside.org/ ? It can be
> hosted on GitHub.
I really don't know, Matti is taking care of this but I think he's on
vacation/traveling/or something else.
Matti Airas
> Hi,
>
> gerrit only sync PySide repositories with gitorious, so the git-hub
> repositories will be out dated because nobody will remember to sync them :-/
>
> So, my question is: Should I remove PySide from git-hub? No code will be lost
> because the helper repositories found on github and not on gerrit can be found
> on gitorious.
Hi,
I think it's OK to have the repos mirrored there, but in a read-only
mode. If the GitHub repos would be read-write, in that case I think the
GitHub project name have to be something else than PySide to indicate
that the repos are a fork of the official project.
Cheers,
ma.
anatoly techtonik
> On 16.03.2012 13:21, ext Hugo Parente Lima wrote:
>> Hi,
>>
>> gerrit only sync PySide repositories with gitorious, so the git-hub
>> repositories will be out dated because nobody will remember to sync them :-/
>>
>> So, my question is: Should I remove PySide from git-hub? No code will be lost
>> because the helper repositories found on github and not on gerrit can be found
>> on gitorious.
>
> Hi,
>
> I think it's OK to have the repos mirrored there, but in a read-only
> mode. If the GitHub repos would be read-write, in that case I think the
> GitHub project name have to be something else than PySide to indicate
> that the repos are a fork of the official project.
How about killing those Gerrit repositories and leaving them archived on Github?
They are not needed for development anymore.
pyside/apiextractor
ssh://codereview.qt-project.org:29418/pyside/apiextractor.git
pyside/generatorrunner
ssh://codereview.qt-project.org:29418/pyside/generatorrunner.git
--
anatoly t.
Hugo Parente Lima
> On Mon, Mar 19, 2012 at 2:56 PM, Matti Airas <matti....@nokia.com>
wrote:
> > On 16.03.2012 13:21, ext Hugo Parente Lima wrote:
> >> Hi,
> >>
> >> gerrit only sync PySide repositories with gitorious, so the git-hub
> >> repositories will be out dated because nobody will remember to sync them
> >> :-/
> >>
> >> So, my question is: Should I remove PySide from git-hub? No code will be
> >> lost because the helper repositories found on github and not on gerrit
> >> can be found on gitorious.
> >
> > Hi,
> >
> > I think it's OK to have the repos mirrored there, but in a read-only
> > mode. If the GitHub repos would be read-write, in that case I think the
> > GitHub project name have to be something else than PySide to indicate
> > that the repos are a fork of the official project.
>
> How about killing those Gerrit repositories and leaving them archived on
> Github? They are not needed for development anymore.
>
> pyside/apiextractor
> ssh://codereview.qt-project.org:29418/pyside/apiextractor.git
> pyside/generatorrunner
> ssh://codereview.qt-project.org:29418/pyside/generatorrunner.git
They can still archived everywhere, this doesn't hurt because they all are
synchronized, the problem with this multi-repository issue we have is that
users may get out dated code from a git repository.
> --
> anatoly t.
> _______________________________________________
> PySide mailing list
> PyS...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
--