On Mon, Sep 18, 2000 at 09:39:40PM -0700, Seth Cohn wrote:
> Steve Bowman trying to find a good word to compliment debian-mentors:
>
> > Taking these items together, how about making up a really new word that
> > is really Debianspeak? You could have debee and deber :-) OTOH, the
> > best _word_
Steve Bowman trying to find a good word to compliment debian-mentors:
> Taking these items together, how about making up a really new word that
> is really Debianspeak? You could have debee and deber :-) OTOH, the
> best _word_ I've seen so far (that is, one that can be found in an
> (English) d
On Mon, Sep 18, 2000 at 09:39:40PM -0700, Seth Cohn wrote:
> Steve Bowman trying to find a good word to compliment debian-mentors:
>
> > Taking these items together, how about making up a really new word that
> > is really Debianspeak? You could have debee and deber :-) OTOH, the
> > best _word
Steve Bowman trying to find a good word to compliment debian-mentors:
> Taking these items together, how about making up a really new word that
> is really Debianspeak? You could have debee and deber :-) OTOH, the
> best _word_ I've seen so far (that is, one that can be found in an
> (English)
On Sun, Sep 17, 2000 at 11:04:52PM -0700, Steve Bowman wrote:
>
> Taking these items together, how about making up a really ew word that is
^-- new
yeeesh...
--
Steve Bowman <[EMAIL PROTECTED]> (preferred)
Buckeye, AZ <[EMAIL PROTECT
On Sat, Sep 16, 2000 at 08:22:17AM -0700, tony mancill wrote:
> On Sat, 16 Sep 2000, Antti-Juhani Kaijanaho wrote:
>
> > On 2915T060004-0700, Rick Younie wrote:
> > > Sponsee? Tony made that one up didn't he? I can see the
> > > confusion in a couple years when the number of Debian maintaine
On Sun, Sep 17, 2000 at 11:04:52PM -0700, Steve Bowman wrote:
>
> Taking these items together, how about making up a really ew word that is
^-- new
yeeesh...
--
Steve Bowman <[EMAIL PROTECTED]> (preferred)
Buckeye, AZ <[EMAIL PROTEC
On Sat, Sep 16, 2000 at 08:22:17AM -0700, tony mancill wrote:
> On Sat, 16 Sep 2000, Antti-Juhani Kaijanaho wrote:
>
> > On 2915T060004-0700, Rick Younie wrote:
> > > Sponsee? Tony made that one up didn't he? I can see the
> > > confusion in a couple years when the number of Debian maintain
On Sat, 16 Sep 2000, tony mancill wrote:
> (On the other hand, maybe we really *need*
> a new word for "the person whom a sponsor sponsors"
developee ? :')
--
Martin Wheeler -StarTEXT - Glastonbury - BA6 9PH - England
[1] [EMAIL PROTECTED] http://www.startext
On Sat, 16 Sep 2000, tony mancill wrote:
> (On the other hand, maybe we really *need*
> a new word for "the person whom a sponsor sponsors"
developee ? :')
--
Martin Wheeler -StarTEXT - Glastonbury - BA6 9PH - England
[1] [EMAIL PROTECTED] http://www.startex
On Sat, 16 Sep 2000, Antti-Juhani Kaijanaho wrote:
> On 2915T060004-0700, Rick Younie wrote:
> > Sponsee? Tony made that one up didn't he? I can see the
> > confusion in a couple years when the number of Debian maintainers
> > hits a few million. "What's that language you're speaking?
> > D
On Sat, 16 Sep 2000, Antti-Juhani Kaijanaho wrote:
> On 2915T060004-0700, Rick Younie wrote:
> > Sponsee? Tony made that one up didn't he? I can see the
> > confusion in a couple years when the number of Debian maintainers
> > hits a few million. "What's that language you're speaking?
> >
On 2915T060004-0700, Rick Younie wrote:
> Sponsee? Tony made that one up didn't he? I can see the
> confusion in a couple years when the number of Debian maintainers
> hits a few million. "What's that language you're speaking?
> Debian you say?" :-)
Tony who?
You ever heard of deriving wor
On 2915T060004-0700, Rick Younie wrote:
> Sponsee? Tony made that one up didn't he? I can see the
> confusion in a couple years when the number of Debian maintainers
> hits a few million. "What's that language you're speaking?
> Debian you say?" :-)
Tony who?
You ever heard of deriving wo
Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> traini
Hi Rick!
On Fri, 15 Sep 2000, Rick Younie wrote:
> I think a point could be made for including a bogus bug in a
> guy's first package so he can learn the changelog procedure for
> closing it while he's still in close contact with his sponsor.
Since ITPs are now reported as bugs against wnpp you
Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> train
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck on the line if
> something bad happ
Hi Rick!
On Fri, 15 Sep 2000, Rick Younie wrote:
> I think a point could be made for including a bogus bug in a
> guy's first package so he can learn the changelog procedure for
> closing it while he's still in close contact with his sponsor.
Since ITPs are now reported as bugs against wnpp you
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck on the line if
> something bad hap
On 2914T102042-0700, Rick Younie wrote:
> Anyhow, ignore this specific example. I just mean in the general
> case. Get it close or flog the package until it squeaks?
Well, in the final analysis, it's the sponsor's neck on the line if
something bad happens. It's a matter of how much he trust
How exacting should a sponsor be?
A sponsor was reamed on a list a while back because he duploaded
a package with a fairly minor error. He'd identified the problem
and told the packager to fix it in the next version and said that
this was his impression of what a sponsor should do. That is,
get
On 2914T102042-0700, Rick Younie wrote:
> Anyhow, ignore this specific example. I just mean in the general
> case. Get it close or flog the package until it squeaks?
Well, in the final analysis, it's the sponsor's neck on the line if
something bad happens. It's a matter of how much he trus
How exacting should a sponsor be?
A sponsor was reamed on a list a while back because he duploaded
a package with a fairly minor error. He'd identified the problem
and told the packager to fix it in the next version and said that
this was his impression of what a sponsor should do. That is,
get
24 matches
Mail list logo
