Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: ognus
Date: 02 Nov 2000 20:18:16 +0100	[thread overview]
Message-ID: <rju29qqj2f.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <200011021735.RAA12726@djlvig.dl.ac.uk>

Dave Love <d.love@dl.ac.uk> writes:

> >>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 
>  PA> Well, he used to avoid e.g. Kyle Jones code (which is both
>  PA> relevant and very high quality, but unassigned).
> 
> Please stop giving a false impression of this issue. 

Dave, you are being insulting.  Generally in your latest messages, and
specifically here.  I'm *not* trying to make any "impressions", false
or true.  And I don't care about whatever game you think we are
playing, where "impressions" matter.

> Here's an indication of serious management problems
> [ list of non-FSF copyrights in Gnus]

It is *not* in itself a sign of management problems.  It is only a
sign of management problems, if the project goal includes being
bundled with Emacs.  It *used to*[1] to be a project goal, a factoid
that is relevant when trying to establish what the presents goals are.

That the manager is absent so we can't ask him *is* an obvious
management problem.   

I care about Gnus, and I want Gnus to be part of Emacs (more than half
of all Gnus messages are posted from the version bundled with Emacs,
to bundling probably does more to get Gnus used than any work on
beginner friendliness).  Now, there is a big difference between "Lars
have abandoned the goal of bundling Gnus with Emacs", and "the goal is
unchanged, but the current commiteres haven't been teached properly".
In the first case, there is nothing you can do (except forking Gnus).
In the second case, trying to create a consensus on the list that
non-assigned code can be included is a viable goal.  Whining doesn't
help, carefully phrased non-insulting arguments does.

> CVS is not a substitute for management.  -- the manual

CVS with multiple writers probably require more format management than
the previous "send patch to Lars, wait for next snapshot" situation.
I did ask Lars to write some commit guidelines and he did, but they
should have been more detailed.

Footnotes: 
[1]  Past tense!




  parent reply	other threads:[~2000-11-02 19:18 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:59 ognus Simon Josefsson
2000-10-28  0:25 ` ognus ShengHuo ZHU
2000-10-28 13:41   ` ognus Simon Josefsson
2000-10-28 15:34     ` ognus Kai Großjohann
2000-10-28 15:41       ` ognus Simon Josefsson
2000-10-29 17:47       ` ognus Dave Love
2000-10-31 22:09     ` S/MIME and PGP/MIME (Was: Re: ognus) Bjørn Mork
2000-10-31 23:18       ` ShengHuo ZHU
2000-11-01 20:41         ` Bjørn Mork
2000-10-28 19:22   ` emacs21-branch (Re: ognus) Karl Eichwalder
2000-10-29 17:47     ` Dave Love
2000-10-29 18:48     ` Karl Eichwalder
2000-10-29 19:50       ` Kai Großjohann
2000-10-29 21:26         ` Florian Weimer
2000-10-29 22:53         ` ShengHuo ZHU
2000-10-30 22:53         ` Dave Love
2000-10-30 23:20           ` Denys Duchier
2000-10-30 23:38             ` Laura Conrad
2000-10-31  9:50               ` Denys Duchier
2000-11-02 17:25                 ` Dave Love
2000-11-02 17:34                   ` Gunnar Evermann
2000-11-03 19:09                     ` Dave Love
2000-11-03 22:07                       ` Gunnar Evermann
2000-11-02 21:01                   ` Denys Duchier
2000-11-02 22:53                     ` Kai Großjohann
2000-11-03 14:31                       ` Per Abrahamsen
2000-11-03 14:42                         ` luis fernandes
2000-11-04 11:42                         ` Steinar Bang
2000-11-04  2:52                       ` Russ Allbery
2000-11-03 19:14                     ` Dave Love
2000-11-03 19:42                       ` Denys Duchier
2000-11-04  0:04                         ` Kai Großjohann
2000-11-04 15:04                         ` Per Abrahamsen
2000-11-04 20:15                           ` Denys Duchier
2000-11-04 22:59                             ` Andreas Fuchs
2000-11-05  1:15                           ` Russ Allbery
2000-11-02 17:23             ` Dave Love
2000-10-31  0:17           ` Steven E. Harris
2000-10-31 10:09           ` Kai Großjohann
2000-10-29 17:39   ` ognus Dave Love
2000-10-30 11:35     ` ognus Per Abrahamsen
2000-10-30 13:05       ` ognus Kai Großjohann
2000-10-30 23:24         ` ognus Dave Love
2000-10-31 10:16           ` ognus Kai Großjohann
2000-11-04 20:23             ` ognus Lars Magne Ingebrigtsen
2000-11-04 22:04               ` ognus Kai Großjohann
2000-11-04 22:34                 ` ognus Lars Magne Ingebrigtsen
2000-10-30 23:22       ` ognus Dave Love
2000-10-31  9:07         ` ognus Russ Allbery
2000-10-31 13:06           ` ognus Karl Kleinpaste
2000-10-31 17:00           ` ognus Sean Doran
2000-10-31 17:55             ` ognus Kai Großjohann
2000-10-31 13:36         ` ognus Per Abrahamsen
2000-10-31 16:49           ` ognus Sean Doran
2000-11-02 17:35           ` ognus Dave Love
2000-11-02 18:08             ` ognus ShengHuo ZHU
2000-11-02 19:31               ` uunassigned code (was: Re: ognus) Per Abrahamsen
2000-11-03 19:01               ` ognus Dave Love
2000-11-02 19:18             ` Per Abrahamsen [this message]
2000-11-02 23:01               ` ognus Kai Großjohann
2000-11-03 14:11                 ` ognus Per Abrahamsen
2000-11-03 19:04               ` ognus Dave Love
2000-11-04 15:11                 ` ognus Per Abrahamsen
2000-11-03 15:39             ` ognus Simon Josefsson
2000-11-04 20:31             ` ognus Lars Magne Ingebrigtsen
2000-10-31 16:37         ` ognus Sean Doran
2000-11-02 17:22           ` ognus Dave Love
2000-11-04 11:48         ` ognus Steinar Bang
2000-11-04 11:45       ` ognus Steinar Bang

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=rju29qqj2f.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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 NNTP newsgroup(s).