From: Rumen Yotov <rumen@qrypto.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distrowatch and gentoo......
Date: Fri, 30 Jun 2006 17:55:45 +0300 [thread overview]
Message-ID: <44A53B71.4080304@qrypto.org> (raw)
In-Reply-To: <342e1090606300703x6a512884m499bb5fc7b826440@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
Daniel da Veiga wrote:
> On 6/30/06, Marco Calviani <marco.calviani@gmail.com> wrote:
>> Hi list,
>> i've recently read this short article on distrowatch:
>>
>> http://distrowatch.com/weekly.php?issue=20060626#news
>>
>> What about these problems? Someone that's more inside the Gentoo
>> decision process, can explain better what's (if it is true) happening?
>>
>
> Well, the guy got the attention he wanted.
> If you follow GWN, you can see devs that come to the project, and
> others leave, that's only natural, and if you leave a project, you
> simply do not post the entire web with reasons that can only be taken
> as highly personal and regarding the human relations inside Gentoo
> Project. Why aren't the other developers answering? I have only one
> guess... They really don't care... The project is going on and see
> lots of discussions and improvements at all topics on the mailing
> lists and foruns. Gentoo is not dying, not even loosing strenght. Its
> growing, and growing is painfull, we all know that.
>
> Now, distrowatch should pay more attention before posting news that
> can lead to misunderstanding, probably the dev that left the project
> had better relations inside distrowatch than inside Gentoo development
> project ;)
>
Hi,
Don't wanna say anything, but all of you could just search -dev
ML-archives. There are two alternate package-managers in development.
Some sparks about dev/user overlays,sunrise-overlay,GWN etc. etc.
Not seen such turmoil in latest 3 years (and IMHO most things are
personal). No flames intended, just info.
Rumen
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3493 bytes --]
next prev parent reply other threads:[~2006-06-30 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 6:48 [gentoo-user] distrowatch and gentoo Marco Calviani
2006-06-30 10:32 ` Bo Ørsted Andresen
2006-06-30 14:03 ` Daniel da Veiga
2006-06-30 14:50 ` Marco Calviani
2006-06-30 14:55 ` Rumen Yotov [this message]
2006-06-30 15:07 ` Bo Ørsted Andresen
2006-06-30 18:16 ` Rumen Yotov
2006-06-30 18:49 ` Bo Ørsted Andresen
2006-06-30 17:20 ` James Ausmus
2006-06-30 18:37 ` Rumen Yotov
2006-07-07 12:42 ` [gentoo-user] Ignore this message Johnson, Maurice E CTR NSWCDL-K74
2006-07-10 6:25 ` Farhan Ahmed
2006-06-30 19:23 ` [gentoo-user] distrowatch and gentoo Hemmann, Volker Armin
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=44A53B71.4080304@qrypto.org \
--to=rumen@qrypto.org \
--cc=gentoo-user@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