From: Mo DeJong <supermo@bayarea.net>
To: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: Back online...
Date: Mon, 08 Apr 2002 16:04:00 -0000 [thread overview]
Message-ID: <20020408080816.519b9181.supermo@bayarea.net> (raw)
In-Reply-To: <20020406123236.6aae8802.irox@sbcglobal.net>
On Sat, 6 Apr 2002 12:32:36 -0800
irox@sbcglobal.net wrote:
> The first thing I'd like to talk about is Copyright
> assignments. While I was still working for RH I
> brought the idea of making Source-Navigator a
> multi-copyright holder project to as many people in
> RH as I could. This would mean people who contribute
> code to Source-Navigator don't have to sign over thier
> copyrights to Red Hat. I was never able to get a firm
> yes or no from anybody, but I would like to implement
> this (long over due) change anyway.
I too think it is about time this change was made. The copyright
stuff has been standing in the way of progress for far too long.
We should add a tag to the CVS to mark the last point where
assignment to Red Hat was the norm and move on. If anyone
objects, we could always make a tar ball and move everything
to sourceforge.
Mo
prev parent reply other threads:[~2002-04-08 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 11:17 irox
2002-04-07 16:13 ` Khamis Abuelkomboz
2002-04-08 16:04 ` Mo DeJong [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=20020408080816.519b9181.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=sourcenav@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).