From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [HS?]: On gnus developement
Date: Wed, 23 Jul 2003 08:18:20 +0200 [thread overview]
Message-ID: <plop878yqprck3.fsf@gnu-rox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hello,
I just want to know how is organized the Gnus developement. I mean are
only patches the solution to make Gnus always more powefull ?
It seems to me that this project is not structured as I used to see in
other projects. Am I wrong ? Is there a \"strong\" kernel developer for
Gnus (apart Lars) or does it work as I always see here by sending
patches and signing obscur documents to be able to publish them ?
Last but (surely) not least, is there any URL you can recommend to
learn what need to be done (TODO list), and how to become a Gnus
developer (even if just occasional) ?
Regards,
zeDek
--
"Most people deserve each other."
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2003-07-23 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 6:18 Xavier Maillard [this message]
2003-07-24 23:25 ` Jesper Harder
2003-07-25 2:04 ` Glenn Morris
2003-07-25 6:07 ` Xavier Maillard
2003-07-25 6:11 ` Xavier Maillard
2003-10-17 21:39 ` Lars Magne Ingebrigtsen
2003-07-25 19:54 ` Matthias Andree
2003-07-25 20:51 ` Xavier Maillard
2003-07-25 21:51 ` Jesper Harder
2003-07-31 1:11 ` Simon Josefsson
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=plop878yqprck3.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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;
as well as URLs for NNTP newsgroup(s).