public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Thu, 10 Mar 2005 00:57:15 +0200	[thread overview]
Message-ID: <422F7F4B.4090406@gentoo.org> (raw)
In-Reply-To: <e796392205030911103ffd41d8@mail.gmail.com>

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

Stefan Schweizer wrote:

>On Wed, 09 Mar 2005 20:56:51 +0200, Alin Nastac <mrness@gentoo.org> wrote:
>  
>
>>Okay, I buy it.
>>
>>a) Devs, who has a fcdsl, fcdsl2, fcdslsl, fcdslusb and/or fcdslslusb
>>(AVM FRITZ!Card DSL)? Step up and take net-dialup/fcdsl under your wing!
>>    
>>
>I got two of these donated by AVM (fcdslusb and fcdslsl). And
>additionally a fcusb for net-dialup/fritzcapi
>I think all the AVM-drivers in the tree are covered by me.
>
>I dont think that it means that you are a bad maintainer when you do
>not own the hardware. But if you dont like the work you should not do
>it, please tell us then, I am ready to take over as much as I can to
>help you.
>  
>
You already help me a lot, Stefan, and I thank you for that.

I don't really intend to drop my jobs to others - this isn't me, I take 
my responsibilities very seriously. But if you think you'll be doing a 
better job by taking it, please, be my guest. I don't want to appear as 
the guy who broked Gentoo's QA procedures...

I'm only annoyed by the bad attitude of some devs who will get involved 
only what suits them, forgetting that if they would not help, no one 
will. Btw, what is the sense of ~arch if not "testing"? No gentooer 
expects from a ~arch ebuild to be stable, so the sky would not fall if 
you made a mistake and release it under this keyword. When I hear "I 
cannot mark foo library as ~arch because I don't know how to test it" 
smells like excuse to me.

As for QA... does anyone think we *can* have proper QA procedures, with 
our release speed and decentralized development model? And with only ... 
350 devs from which God knows how many are still active?  :-D
Who thinks that clearly doesn't have a clue what QA means. It is 
practically impossible to test every combination of ebuilds/USE/CFLAGS 
so all we do is a surface test, letting the burden of testing on the 
shoulders of our users.
Despite of our unorthodox development process, many people believes 
(including me) that our distro surclass traditional ones and is 
generally more stable (go figure!).

Maybe I'm too exigent, but I only ask from people to do what I do : be 
genuinely interested in helping the devs who need it. Heck, I always try 
to help any gentooer, dev or not. We all have our little systems because 
our predecesors have worked on it, not because they  sit down and 
debated whether to mark foo ebuild as ~arch or not.

>>c)...
>>
>>In fact, who has any device that would work with some driver from
>>net-dialup? I don't have _any_ device at all!
>>    
>>
>Do you have a dsl-connection?
>How do you connect to the internet?
>  
>
I do have a dsl connection, but it is through a modem with an eth 
interface, so I need no driver.

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

  parent reply	other threads:[~2005-03-09 22:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac [this message]
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=422F7F4B.4090406@gentoo.org \
    --to=mrness@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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