public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status
Date: Sat, 14 Apr 2018 07:59:48 +0200	[thread overview]
Message-ID: <23249.39124.119818.517500@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <d59ba77f-2d16-89ef-15a4-0362314cd419@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

>>>>> On Fri, 13 Apr 2018, Francisco Blas Izquierdo Riera (klondike) wrote:

> 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.

Sorry, but I don't understand what you are talking about. GLEP types
are defined in GLEP 1 [1]:

,----
| A Standards Track GLEP describes a new feature or implementation
| for Gentoo Linux. An Informational GLEP provides general guidelines
| or information to the Gentoo Linux community, but does not propose
| a new feature.
`----

Michał's GLEP doesn't describe any new feature, but aims to document
current practice. Therefore it cannot be of type "Standards Track".

> [...]

> 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 not helpful.

Ulrich

[1] https://www.gentoo.org/glep/glep-0001.html#kinds-of-gleps

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2018-04-14  5:59 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 [this message]
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)
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=23249.39124.119818.517500@a1i15.kph.uni-mainz.de \
    --to=ulm@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