public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Is Gentoo dying?
Date: Sat, 03 Apr 2010 11:26:01 +0200	[thread overview]
Message-ID: <4BB709A9.2000103@gentoo.org> (raw)
In-Reply-To: <1270286192.18734.3.camel@homer.ob.libexec.de>

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

On 4/3/10 11:16 AM, Tobias Scherbaum wrote:
> Hell no, but ...
> 
> We have lots of quite understaffed areas, to sum up in a positive way.
> Summing it up the negative way one might say, we have lots of areas were
> users might get the idea Gentoo already is dead.
> 
> For example:
> - hardened-sources are nowadays only available in an experimental
> overlay, lots of users keep asking what's happening to the
> hardened-sources on both the -dev but also the -hardened mailinglist.

I recently sent an e-mail to gentoo-dev,
<http://archives.gentoo.org/gentoo-dev/msg_2eb703ee97afc64a29e5d148457ac8d5.xml>

It seems that some work is being done, but there are people who
volunteered to help, like me. What needs to be done with hardened-sources?

Just a note: I'm using it on my servers, so I'm really interested in
them being maintained, and I'm also able to test.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2010-04-03  9:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03  9:16 [gentoo-dev] Is Gentoo dying? Tobias Scherbaum
2010-04-03  9:26 ` "Paweł Hajdan, Jr." [this message]
2010-04-03 10:12   ` Tobias Scherbaum
2010-04-03 11:36   ` hardened-sources development (was: Re: [gentoo-dev] Is Gentoo dying?) Thomas Sachau
2010-04-03  9:37 ` [gentoo-dev] Is Gentoo dying? Brian Harring
2010-04-03 10:10   ` Tobias Scherbaum
2010-04-03  9:38 ` Petteri Räty
2010-04-03 19:12   ` Jacob Godserv
2010-04-03  9:40 ` Robin H. Johnson
2010-04-03  9:46   ` Robin H. Johnson
2010-04-03  9:46 ` [gentoo-dev] Is Gentoo a Phoenix? Patrick Lauer
2010-04-03 10:19   ` Tobias Scherbaum
2010-04-03 11:33     ` Richard Freeman
2010-04-03 11:50       ` Petteri Räty
2010-04-04 18:09       ` Denis Dupeyron
2010-04-05 15:33         ` Richard Freeman
2010-04-05 17:21           ` Denis Dupeyron
2010-04-04 20:19       ` Zeerak Mustafa Waseem
2010-04-05  4:24         ` [gentoo-dev] " Duncan
2010-04-03 12:40     ` [gentoo-dev] " Magnus Granberg
2010-04-03 12:18   ` [gentoo-dev][Gentoo Phoenix] " Ben de Groot
2010-04-03 14:40 ` [gentoo-dev] Is Gentoo dying? Roy Bamford
2010-04-03 14:59   ` Tobias Scherbaum
2010-04-03 16:03     ` Alec Warner
2010-04-03 16:24       ` Matti Bickel
2010-04-03 23:52       ` Sebastian Pipping
2010-04-04 20:48     ` Roy Bamford
2010-04-06  6:24       ` Sebastian Pipping
2010-04-04  1:48 ` Joshua Saddler
2010-04-04  2:40   ` Alec Warner
2010-04-04  4:50     ` Dale
2010-04-05  0:28       ` Jorge Manuel B. S. Vicetto
2010-04-04  8:22   ` Tobias Scherbaum
2010-04-04 10:07     ` Joshua Saddler
2010-04-04  8:25   ` Petteri Räty
2010-04-04  8:44   ` Patrick Lauer
2010-04-04  9:56     ` [gentoo-dev] " Duncan
2010-04-04 10:21       ` George Prowse

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=4BB709A9.2000103@gentoo.org \
    --to=phajdan.jr@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