From: Jason Zaman <perfinion@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Better way to direct upstream bugs upstream?
Date: Thu, 3 Sep 2015 17:32:21 +0800 [thread overview]
Message-ID: <20150903093221.GA15167@meriadoc.omgwtfbbq> (raw)
In-Reply-To: <55E74B3C.5060704@gentoo.org>
On Wed, Sep 02, 2015 at 09:17:16PM +0200, Paweł Hajdan, Jr. wrote:
> On 8/30/15 12:02 PM, Kent Fredric wrote:
> > Or upstream might be a monolithic giant like Google where their
> > upstream bug tracking is some pointless forum where you get ignored by
> > the people actually working on things.
>
> Ouch.
>
> Do you have specific examples?
>
> I'm not denying they exist. I just had mostly positive experience with
> <https://code.google.com/p/chromium/issues> . Because I'm also Chromium
> developer, I know that's what people "actually working on things" use.
>
> I admit with 85000+ open issues not all of them are getting enough
> attention. But if you know an upstream developer, it's easier to get the
> right people to look at the bug.
>
> Of course above is not the only Google project, and I don't have much
> experience with the other ones.
>
> Paweł
I dont know what ones he's talking about, but I have this one:
https://code.google.com/p/android/issues/detail?id=175284
https://bugs.gentoo.org/show_bug.cgi?id=533178
Android Studio is released as a compiled binary for windows/mac/linux
but there is no source code for it. And to make matters even worse they
don't have proper tags in the git repos for it so I can't even just make
the tarballs myself because I dont know which commits correspond to the
releases. They just closed the bug as declined with no reason given :(.
-- Jason
next prev parent reply other threads:[~2015-09-03 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 19:53 [gentoo-dev] Better way to direct upstream bugs upstream? Matt Turner
2015-08-30 7:03 ` Kent Fredric
2015-08-30 7:20 ` Daniel Campbell
2015-08-30 7:54 ` Kent Fredric
2015-08-30 7:59 ` Daniel Campbell
2015-08-30 9:37 ` [gentoo-dev] " Duncan
2015-08-30 10:02 ` Kent Fredric
2015-09-02 19:17 ` Paweł Hajdan, Jr.
2015-09-03 9:32 ` Jason Zaman [this message]
2015-09-03 11:28 ` Kent Fredric
2015-09-03 20:16 ` Andrew Udvare
2015-09-07 19:51 ` Paweł Hajdan, Jr.
2015-09-07 23:47 ` Alec Warner
2015-08-30 12:15 ` [gentoo-dev] " Peter Stuge
2015-08-30 12:38 ` Kent Fredric
2015-08-30 17:59 ` [gentoo-dev] " Chí-Thanh Christopher Nguyễn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150903093221.GA15167@meriadoc.omgwtfbbq \
--to=perfinion@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox