From: Stephen Hemminger <shemminger@vyatta.com>
To: Daniel Baluta <dbaluta@ixiacom.com>
Cc: Alexandru Juncu <alex.juncu@rosedu.org>,
kernelnewbies@kernelnewbies.org,
Greg Freemyer <greg.freemyer@gmail.com>,
netdev@vger.kernel.org
Subject: Re: Contributing for the first time
Date: Mon, 7 Nov 2011 08:11:20 -0800 [thread overview]
Message-ID: <20111107081120.754f6e0a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAEnQRZA=dwt6TjcBacYaj0ORdi5QjBEXUaPA4GT2tm2oE_LFew@mail.gmail.com>
On Mon, 7 Nov 2011 15:17:38 +0200
Daniel Baluta <dbaluta@ixiacom.com> wrote:
> On Mon, Nov 7, 2011 at 3:05 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> > Alexandru Juncu <alex.juncu@rosedu.org> wrote:
> >
> >>Hello!
> >>
> >>I have been a linux user for many years, and mostly on the networking
> >>side. And I would like to start contributing somehow to the linux
> >>community (in some other way than just promoting it). I guess that I
> >>should start small with something like man pages.
> >>
> >>And there is something that really has been bugging me for some time.
> >>I'm an iproute2 user and I teach linux courses and show people how to
> >>use it. On most questions from my students about new commands, I
> >>redirect them to the man pages and to the Examples section of that
> >>page. iproute2 doesn't have such examples and I always wish it did.
> >>
> >>Do you think that if I submit a patch to the man pages, adding some
> >>examples of how to use the ip command, will it get accepted? Because
> >>this sounds like a simple thing and it's hard to believe that someone
> >>else didn't try do to this before. What do you think?
> >>Alexandru Juncu
>
> > I think it will be accepted, but few people like to work on the man pages.
> >
> > Since this is a userspace package you will need to figure out who the maintainer is and if there is a mailinglist they use to discuss/support the package.
> >
> > Then submit your patch there.
>
> According to [1] maintainer for iproute2 is Stephen Hemminger (CC'ed) and I
> think patches should be sent to netdev mailing list ([2]).
>
> thanks,
> Daniel.
>
> [1] http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
> [2] http://vger.kernel.org/vger-lists.html#netdev
It might also be worth it to break some of the large manual pages into
clearer sections.
prev parent reply other threads:[~2011-11-07 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPhGq=b_DwhbChAm3HPfzTXedRM6qVvVW7an5YkM8hqwhgCjbA@mail.gmail.com>
[not found] ` <4a08f8c6-d02e-40c4-b976-5437270ba5b2@email.android.com>
2011-11-07 13:17 ` Contributing for the first time Daniel Baluta
2011-11-07 16:11 ` Stephen Hemminger [this message]
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=20111107081120.754f6e0a@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=alex.juncu@rosedu.org \
--cc=dbaluta@ixiacom.com \
--cc=greg.freemyer@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=netdev@vger.kernel.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