From: Alastair Tse <liquidx@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Public Relations
Date: 02 Jul 2003 12:29:02 +0100 [thread overview]
Message-ID: <1057145341.10019.46.camel@huggins.eng.cam.ac.uk> (raw)
In-Reply-To: <20030702054221.GR1912@squish.home.loc>
[-- Attachment #1: Type: text/plain, Size: 4551 bytes --]
On Wed, 2003-07-02 at 06:42, Paul wrote:
> I have been conditioned to not submit ebuilds anymore, after
> having submitted them regularly for some time; (I touch upon this
> in bug 6808) I still hope to continue contributing bugs,
Hi Paul,
I've always tried to stay out of this "-core being open" debate because
I too don't feel much either way. But that bug reference has pushed me
to answer some of your concerns in this email.
Comment on the your concerns about submitted ebuilds being ignored. At
least on all the bugs I'm assigned, I _try_ to give feedback whenever it
is possible, say what is holding up an ebuild going into portage, and be
frank about what I think about the ebuild or the fitness of the
application/library. Of course, you'll find exceptions to that comments
if you go thru all my bugs :P
In this case with gbonds, given that most, if not all, devs in
gnome@gentoo.org are not US citizens and have no US bond. It was very
difficult for us to support the ebuild to any degree. With committing
the ebuild, comes responsibility and expectation that it would work. For
example, similar situation I encounter now is I'm maintaining
gphoto2/gtkam suite even though I have no digital camera compatible with
that. Users come to me with bugs about it, and I can't do any real
bugfixing on it. Sure it compiles, installs, and launches, but I can't
verify any of the functionality.
Maybe we really need dedicated users who do commit to being responsible
for a particular package because they are very familiar with it, and
actively submit version updates, help to debug problems with the
package, etc. We don't have a system for this right now, although some
time previously, we had the idea of "watchers" who would be similar to
that type of user. But I don't know what happened to the idea or why it
was abandoned.
> preferably with patches. (although I often have better luck just
> pushing them upstream.) This is ok for me, since writing ebuilds
Pushing patches upstream is always easier, because they'll either be
rejected and accepted. The problem with us maintaining patches that are
not officially accepted is that the developers for the package will
blame us for modifying their app/library and refuse to support Gentoo
users, leaving a sour taste in both the developer's and user's mouth.
> Instead of tortured analogies, just say it the way it
> is; "we want core closed, and if you dont like it, you are free
> to choose another distribution, or fork..."
I'm very certain that has never been the view of the dev-team. I've
certainly not encountered anyone who has said anything similar to this.
> organisation. (Ive seen it on my local LUG list-- people saying
> 'Ive heard this and that and this; maybe youd better think twice
> before commiting to Gentoo...') That is to say, these feelings
> and doubts are very real, and I hope that even though core
> members find them baseless, that they find a way to communicate
> that without seeming so condescending.
Well, distro wars are what LUGs are about, or that's what I've heard :)
Anyway, I'll have my small comment about -core opening up. I could write
a whole essay if I wanted to. So, if we do open up -core, what is to say
that devs would not push inter-dev communication on contentious issues
to private CC lists, or a gentoo-core-core?
Also, how open do these lists have to be? Would people comprimise on an
archive that just lists the subjects discussed on -core? This would
alleviate "security matters" being exposed because only the topic would
not provide enough details for anyone to pre-emptively exploit, or would
it?
On the concluding note, before I became a dev, I didn't even know a
-core list existed, and to be honest, I didn't even care. What I was
trying to do was just make the distro I was using better. Getting
involved with a distro is more than reading mail archives of -core,
getting involved is actually contributing to the distro or help other
users.
I understand this issue will never go away. Maybe someone with enough
time on their hands would actually write a summary on all the arguments
presented since the beginning of time about -core. That would be an
interesting read :)
Cheers,
--
Alastair 'liquidx' Tse
>> Gentoo Developer
>> http://www.liquidx.net/ | http://cvs.gentoo.org/~liquidx/
>> GPG Key : http://cvs.gentoo.org/~liquidx/liquidx_gentoo_org.asc
>> FingerPrint : 579A 9B0E 43E8 0E40 EE93 BB1C 38CE 1C7B 3907 14F6
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-02 11:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 19:21 [gentoo-dev] proposal: make gentoo-core publicly read-only Matthew Kennedy
2003-06-27 19:47 ` [gentoo-dev] Re: [gentoo-core] " Jon Portnoy
2003-06-27 20:49 ` Alec Berryman
2003-06-27 21:37 ` Todd Berman
2003-06-28 16:26 ` Daniel Armyr
2003-06-28 17:13 ` Martin Schlemmer
2003-06-28 18:35 ` [gentoo-dev] " Cyrik
2003-06-28 22:40 ` Martin Schlemmer
2003-06-29 13:12 ` Paul de Vrieze
2003-07-02 5:42 ` [gentoo-dev] Re: Public Relations, was: " Paul
2003-07-02 11:29 ` Alastair Tse [this message]
2003-07-02 16:02 ` [gentoo-dev] Re: Public Relations Daniel Armyr
2003-07-02 16:24 ` Aron Griffis
2003-07-02 11:35 ` [gentoo-dev] Re: Public Relations, was: Re: [gentoo-core] proposal: make gentoo-core publicly read-only Stewart Honsberger
2003-07-02 12:18 ` Alastair Tse
2003-07-02 13:45 ` Brian Jackson
2003-07-02 16:03 ` donnie berkholz
2003-06-29 23:27 ` [gentoo-dev] " Matthew Kennedy
2003-06-28 23:42 ` Stewart Honsberger
2003-06-29 23:25 ` Matthew Kennedy
2003-06-27 21:50 ` [gentoo-dev] " Stroller
2003-06-28 7:35 ` Paul de Vrieze
2003-06-28 11:19 ` Svyatogor
2003-06-28 16:02 ` Ned Ludd
2003-06-29 12:50 ` Paul de Vrieze
2003-06-28 2:26 ` Michael Kohl
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=1057145341.10019.46.camel@huggins.eng.cam.ac.uk \
--to=liquidx@gentoo.org \
--cc=gentoo-dev@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