From: "Francisco Blas Izquierdo Riera (klondike)" <klondike@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status
Date: Sun, 15 Apr 2018 13:44:32 +0200 [thread overview]
Message-ID: <6b94d416-5521-2719-30db-993babefd04c@gentoo.org> (raw)
In-Reply-To: <1523690669.1482.5.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 3049 bytes --]
Hi Michał!
El 14/04/18 a las 09:24, Michał Górny escribió:
> W dniu pią, 13.04.2018 o godzinie 23∶28 +0200, użytkownik Francisco Blas
> Izquierdo Riera (klondike) napisał:
>> Hi Michał,
>>
>> Taking into account that the letter and not the spirit of GLEP 39 is
>> usually thrown around as a weapon ("INFORMATIVE", HAH!). I strongly
>> disrecommend having more "informative" policies.
>>
>> Not to say that whether you like it or not, not all non ebuild related
>> developer work is necessarily tied to a project. Even GLEP 39 mentions
>> this: "Not everything (or everyone) needs a project."
> If you have a good example of a developer contributing to Gentoo without
> having commit access and without being tied to a project, I'm all ears.
Here are some randomly picked tasks that don't require belonguing to a
project:
* Keeping the documentation on the wiki up to date and clear.
* Writting new, relevant documentation.
* Helping address users concerns over one of our official channels
(forums, gentoo-user mailing list, IRC, etc.).
* Helping users provide relevant information on bug reports.
All those are tasks making a very significant contribution to Gentoo.
All of those are tasks that don't require being a member of any project
to be performed, just having the relevant experience and skills.
So here is my proof. Where is yours?
Also why have to be the project leads the one determining the activity
non ebuild developers do? After all GLEP39 clearly states too: " Instead
the practical responsibility of a lead is "whatever the members
require", and if that isn't satisfied, the members can get a new lead
(if they can find somebody to take the job!)." Which doesn't names
"determining the activity non ebuild developers do". Or maybe could it
be that you are planning to force project leads to define those
activites in which case you should modify ALSO GLEP 39.
>> As a closing note, I'm really getting tired of all this "Either you
>> write ebuilds or you are a piece of shit" philosophy that is running on
>> the ambient nowadays. If such people want a developer centric source
>> based distro, who gives shit about the non developers I strongly
>> recommend trying Exherbo instead.
>>
> This is highly inappropriate, especially given that you are a public
> representative of Gentoo.
If you want to play the "you more" game I strongly recommend you read
Matthew 7:5.
> The GLEP *explicitly* defines that there are
> both ebuild and non-ebuild contributions, so whatever you're making up,
> it's irrelevant to the topic at hand.
The GLEP defines different requirements for those two sets of peoples
with the second set having harsher constraints (i.e. not having the
possibility of having their contributions not being filtered by a third
party). This second group happens to be "non-ebuild contributors". So
maybe, instead of trying to insult me a "non-ebuild contributor" you
could consider looking at the moon instead of the finger.
Klondike
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next prev parent reply other threads:[~2018-04-15 11:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:31 [gentoo-project] pre-GLEP: Gentoo Developer status Michał Górny
2018-04-13 21:28 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-13 21:57 ` Rich Freeman
2018-04-13 22:07 ` M. J. Everitt
2018-04-13 22:25 ` Rich Freeman
2018-04-13 22:29 ` M. J. Everitt
2018-04-13 22:41 ` Rich Freeman
2018-04-14 1:10 ` Alec Warner
2018-04-14 1:05 ` Raymond Jennings
2018-04-14 1:23 ` Rich Freeman
2018-04-14 1:33 ` Alec Warner
2018-04-14 5:59 ` Ulrich Mueller
2018-04-15 12:01 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 12:25 ` Ulrich Mueller
2018-04-14 7:24 ` Michał Górny
2018-04-15 11:44 ` Francisco Blas Izquierdo Riera (klondike) [this message]
2018-04-15 12:03 ` Rich Freeman
2018-04-15 12:22 ` Michał Górny
2018-04-15 16:55 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 17:22 ` M. J. Everitt
2018-04-22 17:24 ` Kent Fredric
2018-04-23 20:01 ` Robin H. Johnson
2018-04-23 21:30 ` M. J. Everitt
2018-04-24 2:58 ` Kent Fredric
2018-04-15 17:58 ` Michał Górny
2018-04-21 17:21 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-14 6:57 ` Matthew Thode
2018-04-14 7:19 ` Michał Górny
2018-04-14 7:32 ` Matthew Thode
2018-04-14 20:58 ` Daniel Robbins
2018-04-14 21:16 ` Raymond Jennings
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=6b94d416-5521-2719-30db-993babefd04c@gentoo.org \
--to=klondike@gentoo.org \
--cc=gentoo-project@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