From: Kevin Buettner <kevinb@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: Spring cleaning of GDB's web pages
Date: Wed, 22 Aug 2001 11:15:00 -0000 [thread overview]
Message-ID: <1010822181526.ZM31436@ocotillo.lan> (raw)
In-Reply-To: <1659-Wed22Aug2001115145+0300-eliz@is.elta.co.il>
On Aug 22, 11:51am, Eli Zaretskii wrote:
> > > http://www.gnu.org/prep/maintain_6.html#SEC6
> >
> > This page is not very helpful to someone who's trying to get the legal
> > documents needed for contributing changes to GNU software.
>
> I don't see why: it clearly says how to get the documents.
It tells maintainers who have access to GNU machines how to get the
documents. The pointers it provides are useless to everyone else.
I've been told that the new way to obtain these documents is to
contact the appropriate maintainer. This individual will *hopefully*
be responsive and send a small questionaire to the contributor. The
contributor answers these questions and the responses allow the
maintainer to send the contributor the correct legal documents.
If this is the case, then the above process needs to be documented
and the responsible maintainer(s) for GDB need to be listed so that
a prospective contributor knows whom to contact...
(Personally, I'd like to see the process streamlined a bit more
so that filling out a web form would cause the appropriate legal
documents to be displayed.)
Kevin
next prev parent reply other threads:[~2001-08-22 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 20:50 Andrew Cagney
2001-08-21 6:52 ` Kevin Buettner
2001-08-21 9:56 ` Eli Zaretskii
2001-08-22 1:17 ` Kevin Buettner
2001-08-22 1:52 ` Eli Zaretskii
2001-08-22 7:27 ` Andrew Cagney
2001-08-22 11:15 ` Kevin Buettner [this message]
2001-08-21 6:53 ` Christopher Faylor
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=1010822181526.ZM31436@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@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