public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Andreas Bringedal" <anbring@frisurf.no>
To: <xconq7@sources.redhat.com>
Subject: Re: your CVS and testing culture?
Date: Wed, 12 Nov 2003 15:22:00 -0000	[thread overview]
Message-ID: <002c01c3a91d$ea3ba8f0$84f74382@andreas> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDEEJOGLAB.vanevery@indiegamedesign.com>


I appreciate candour but that can also be done without rudeness which is
quite a difference.  It might _feel_ like a minor difference but saying
'this piece of coding isn't up to today's standards' instead of 'this sucks
and are the worst kind of crap programming I've seen in ages' (not that you
said that specificly) makes for a much more pleasant working environment for
others as well as gaining you much more support for the changes you'd want
done.  Already some time has been spent quarreling and building
resentment...

I believe you may be quite competent(although I know so little about
programming that I can't really tell for sure) and therefore would be a
great asset to xconq's development. I'd love to see those developments that
you could make. (although I'm 99.99% inactive regarding xconq so my opinions
aren't worth much :-)


Cheers,
Andreas


> You know, unlike a lot of people, I'm not afraid to tell people that
> something sucks.  There's a time for being nice and there's a time for
> telling people what's not up to snuff.  Take, for instance, your Windows
> build.  The only caveat I can think of is it may not suck "for you."  It
> most certainly sucks for any mainstream Windows developer looking to get
> involved in Xconq however.  Maybe you don't basically value getting more
> developers on your project, but you're not going to get any Windows
> developers by making a Windows build every once in awhile by
> hook-or-crook.
>
> It looks like if I joined your project, I'd be the only Windows
> developer.  Am I wrong?
>
>
> Cheers,                     www.indiegamedesign.com
> Brandon Van Every           Seattle, WA
>
> Taking risk where others will not.
>
>

  reply	other threads:[~2003-11-12 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 16:32 Brandon J. Van Every
2003-11-11 19:48 ` Andreas Bringedal
2003-11-11 20:59   ` Eric McDonald
2003-11-12  9:05     ` Andreas Bringedal
2003-11-12 12:49       ` Brandon J. Van Every
2003-11-12 15:22         ` Andreas Bringedal [this message]
2003-11-13 15:15           ` Burying the hatchet Brandon J. Van Every
2003-11-12  0:59   ` your CVS and testing culture? Brandon J. Van Every

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='002c01c3a91d$ea3ba8f0$84f74382@andreas' \
    --to=anbring@frisurf.no \
    --cc=xconq7@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).