* Michael Orlitzky [150923 08:31]:
> On 09/23/2015 04:40 AM, Todd Goodman wrote:
> >
> > We haven't had too many problems with it. Most of our problems seem to
> > be with people having issues with git itself (it was new to almost
> > everyone on the team) and not embracing a
On 09/24/2015 09:59 AM, Todd Goodman wrote:
Again, I'm not arguing for or against Gerrit, just relating my
experience with it.
Hello Todd,
I'm not a dev, but I have over a dozen ebuilds I have hacked together.
They need work, and there are devs who are helping me. Some of these
ebuilds are
* James Le Cuirot [150924 04:55]:
> On Wed, 23 Sep 2015 21:55:00 -0700
> Daniel Campbell wrote:
>
> > I hadn't thought about that angle. If our access backbone is via SSH
> > (and thus the filesystem/machine users) then I'm really not sure how
> > to implement
On Wed, 23 Sep 2015 21:55:00 -0700
Daniel Campbell wrote:
> I hadn't thought about that angle. If our access backbone is via SSH
> (and thus the filesystem/machine users) then I'm really not sure how
> to implement a GitLab or Gerrit instance while hooking into the
> filesystem.
On 09/23/2015 04:40 AM, Todd Goodman wrote:
>
> We haven't had too many problems with it. Most of our problems seem to
> be with people having issues with git itself (it was new to almost
> everyone on the team) and not embracing a good workflow with it (or
> trying to only use git via Eclipse.)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/23/2015 05:30 AM, Michael Orlitzky wrote:
> On 09/23/2015 04:40 AM, Todd Goodman wrote:
>>
>> We haven't had too many problems with it. Most of our problems
>> seem to be with people having issues with git itself (it was new
>> to almost
On Sat, 19 Sep 2015 20:12:06 -0400
Michael Orlitzky wrote:
> Has anyone ever set up Gitlab or Gerrit, managed by a package manager,
> in a way that a small bug won't grant anonymous write access to every
> single repository?
>
> Web projects tend to assume that they're the only
On 09/19/2015 05:16 PM, Daniel Campbell wrote:
>
> We'd just need a developer who's experienced in maintaining and
> setting them up.
>
Has anyone ever set up Gitlab or Gerrit, managed by a package manager,
in a way that a small bug won't grant anonymous write access to every
single repository?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/16/2015 03:07 PM, Maciej Mrozowski wrote:
> On Saturday 12 of September 2015 21:12:25 Michał Górny wrote:
>
> | What are your thoughts? Any other proposals?
>
> Well, there's always an option to set up infra hosted Gerrit or
> Gitlab and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/19/2015 05:12 PM, Michael Orlitzky wrote:
> On 09/19/2015 05:16 PM, Daniel Campbell wrote:
>>
>> We'd just need a developer who's experienced in maintaining and
>> setting them up.
>>
>
> Has anyone ever set up Gitlab or Gerrit, managed by
On Saturday 12 of September 2015 21:12:25 Michał Górny wrote:
| What are your thoughts? Any other proposals?
Well, there's always an option to set up infra hosted Gerrit or Gitlab and
forget about Github workflow altogether...
regards
MM
signature.asc
Description: This is a digitally signed
On Sun, 13 Sep 2015 15:37:17 +0200
Michał Górny wrote:
> Dnia 13 września 2015 11:48:54 CEST, Jason Zaman
> napisał(a):
> >On Sat, Sep 12, 2015 at 09:12:25PM +0200, Michał Górny wrote:
> >> Potential solution: bi-dir github <=> bugzilla integration
> >>
El lun, 14-09-2015 a las 00:19 +0300, Andrew Savchenko escribió:
[...]
> Yes, but as long as choice of core components and infrastructure is
> free one. Read Gentoo Social Contract:
>
> https://www.gentoo.org/get-started/philosophy/social-contract.html
>
> "However, Gentoo will never depend upon
On Sat, Sep 12, 2015 at 09:12:25PM +0200, Michał Górny wrote:
> Potential solution: bi-dir github <=> bugzilla integration
> ==
>
> My current idea would be pretty much that:
>
> 1. a new dedicated Gentoo bug would be automatically created
On Sat, Sep 12, 2015 at 09:12:25PM +0200, Michał Górny wrote:
> Potential solution: bi-dir github <=> bugzilla integration
> ==
I just noticed this:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1308105
it appears to mirror
Dnia 13 września 2015 11:48:54 CEST, Jason Zaman
napisał(a):
>On Sat, Sep 12, 2015 at 09:12:25PM +0200, Michał Górny wrote:
>> Potential solution: bi-dir github <=> bugzilla integration
>> ==
>>
>> My current idea
On 09/13/2015 07:56 PM, Andrew Savchenko wrote:
>
> Gentoo workflow should not depend on a proprietary tools like
> github issue tracker and github pull requests.
>
It doesn't. That's what this thread is about, so people who refuse to
collaborate on github PRs can still collaborate on bugzilla.
Dnia 2015-09-13, o godz. 20:56:07
Andrew Savchenko napisał(a):
> On Sat, 12 Sep 2015 21:12:25 +0200 Michał Górny wrote:
> > Hello, everyone.
> >
> > The current workflow for handling github pull requests is at least
> > suboptimal. Handling pull requests takes a fair effort
On Sun, 13 Sep 2015 20:27:32 +0200 Michał Górny wrote:
> Dnia 2015-09-13, o godz. 20:56:07
> Andrew Savchenko napisał(a):
>
> > On Sat, 12 Sep 2015 21:12:25 +0200 Michał Górny wrote:
> > > Hello, everyone.
> > >
> > > The current workflow for handling github pull requests is
On Sun, 13 Sep 2015 20:21:02 +0200 hasufell wrote:
> On 09/13/2015 07:56 PM, Andrew Savchenko wrote:
> >
> > Gentoo workflow should not depend on a proprietary tools like
> > github issue tracker and github pull requests.
> >
>
> It doesn't. That's what this thread is about, so people who
On Mon, 14 Sep 2015 00:07:26 +0300
Andrew Savchenko wrote:
> On Sun, 13 Sep 2015 20:21:02 +0200 hasufell wrote:
> > On 09/13/2015 07:56 PM, Andrew Savchenko wrote:
> > > Gentoo workflow should not depend on a proprietary tools like
> > > github issue tracker and github pull
On Sun, 13 Sep 2015 22:13:30 +0100 Ciaran McCreesh wrote:
> On Mon, 14 Sep 2015 00:07:26 +0300
> Andrew Savchenko wrote:
> > On Sun, 13 Sep 2015 20:21:02 +0200 hasufell wrote:
> > > On 09/13/2015 07:56 PM, Andrew Savchenko wrote:
> > > > Gentoo workflow should not depend on a
On Sat, 12 Sep 2015 21:12:25 +0200 Michał Górny wrote:
> Hello, everyone.
>
> The current workflow for handling github pull requests is at least
> suboptimal. Handling pull requests takes a fair effort from the few
> developers contributing there, and the progress is often stalled by
> package
Dnia 2015-09-13, o godz. 19:27:17
Jason Zaman napisał(a):
> On Sat, Sep 12, 2015 at 09:12:25PM +0200, Michał Górny wrote:
> > Potential solution: bi-dir github <=> bugzilla integration
> > ==
>
> I just noticed this:
On 09/13/2015 11:19 PM, Andrew Savchenko wrote:
>
> Yes, but as long as choice of core components and infrastructure is
> free one. Read Gentoo Social Contract:
>
> https://www.gentoo.org/get-started/philosophy/social-contract.html
>
> "However, Gentoo will never depend upon a piece of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michał Górny schrieb:
> I don't know if you didn't read the proposal, or if you are unable to
> understand it. You are seriously *offending* me and the few other
> developers who are trying *really hard*.
>
> So let me make this clear: I am trying
I agree. I think that any "master" version of whatever repo we use should
be hosted on gentoo owned infrastructure.
Github might be allowed to take pull requests but I think it should be a
slave to whatever's hosted on gentoo.
That way if anything gets screwed up on github gentoo could always
Dnia 2015-09-14, o godz. 00:19:38
Andrew Savchenko napisał(a):
> On Sun, 13 Sep 2015 22:13:30 +0100 Ciaran McCreesh wrote:
> > On Mon, 14 Sep 2015 00:07:26 +0300
> > Andrew Savchenko wrote:
> > > On Sun, 13 Sep 2015 20:21:02 +0200 hasufell wrote:
> > > >
On Sun, Sep 13, 2015 at 9:02 PM, Raymond Jennings wrote:
> I agree. I think that any "master" version of whatever repo we use should
> be hosted on gentoo owned infrastructure.
>
> Github might be allowed to take pull requests but I think it should be a
> slave to whatever's
Hello, everyone.
The current workflow for handling github pull requests is at least
suboptimal. Handling pull requests takes a fair effort from the few
developers contributing there, and the progress is often stalled by
package maintainers which are either unresponsive or not registered on
github
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Samstag, 12. September 2015, 21:12:25 schrieb Michał Górny:
> Potential solution: bi-dir github <=> bugzilla integration
> ==
The general idea is nice and neat.
> - handling comment edits
On Sat, 12 Sep 2015 21:12:25 +0200
Michał Górny wrote:
> 1. Many of the Gentoo developers have different nicknames on GitHub.
> Some developers don't even set their real names which makes them even
> harder to find.
This isn't directly related to your proposal, but may I jump
On Sat, Sep 12, 2015 at 10:11:27PM +0200, hasufell wrote:
> We should probably auto-attach the patch from the pull request. This
> can easily be done with link-rewriting, e.g.:
> https://github.com/gentoo/gentoo/pull/83 to
> https://github.com/gentoo/gentoo/pull/83.patch
> yields a nice
On 09/12/2015 09:12 PM, Michał Górny wrote:
>
> Potential solution: bi-dir github <=> bugzilla integration
> ==
>
> My current idea would be pretty much that:
>
> 1. a new dedicated Gentoo bug would be automatically created for every
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Samstag, 12. September 2015, 23:31:11 schrieb W. Trevor King:
> Right, thanks. In that case, I think you'll need a hook to push a new
> patch whenever the GitHub branch is updated, rebased, etc. That could
> make for a lot of Bugzilla spam,
On 09/12/2015 11:07 PM, W. Trevor King wrote:
> On Sat, Sep 12, 2015 at 10:11:27PM +0200, hasufell wrote:
>> We should probably auto-attach the patch from the pull request. This
>> can easily be done with link-rewriting, e.g.:
>> https://github.com/gentoo/gentoo/pull/83 to
>>
On Sat, Sep 12, 2015 at 11:15:14PM +0200, hasufell wrote:
> Because that is not a valid bug report. Patches must be attached to
> bugzilla.
Right, thanks. In that case, I think you'll need a hook to push a new
patch whenever the GitHub branch is updated, rebased, etc. That could
make for a lot
On Sun, Sep 13, 2015 at 01:30:44PM +1200, Kent Fredric wrote:
> If the patch is automatedly filed against bugzilla, people will
> assume viewing that patch tells them all they need to know.
>
> But the reality is somebody may rebase/amend/repush to the
> publicised branch location before any
On 13 September 2015 at 09:15, hasufell wrote:
> Because that is not a valid bug report. Patches must be attached to
> bugzilla.
I would recommend against attaching the pull in patch form against
bugzilla. It might lead to unintentionally misleading consequences.
If the
39 matches
Mail list logo