From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Way forward with FSF
Date: Thu, 30 Oct 2003 17:22:00 -0000 [thread overview]
Message-ID: <3FA148B9.3000608@eCosCentric.com> (raw)
Us guys at eCosCentric have been thinking a little about ways to move
forward with the FSF. I have just prodded the FSF again, in a slightly
more forceful way. I can imagine the SCO stuff is taking up their time
which won't help.
At the same time, there seems to be evidence that RH are sitting on
assignments, although one has just come through just now. How many others
are affected? I seem to recall at least one.
A compromise has been suggested that won't cause problems with the FSF
later, but will make us more independent of RH (which as we know stops
some people from contributing). However it needs the buy-in from everyone,
naturally.
The idea is that instead of assigning to RH, contributors could assign
direct to individual maintainers. When the FSF is sorted out, the
individual maintainer(s) will assign everything at that point to the FSF.
Another possibility is to assign to eCosCentric, and eCosCentric would
make a public commitment to assign to the FSF immediately once everything
is going. That might be easier logistically, but I can understand it if
others here are hesitant about this. But the public commitment may address
this.
Certainly of the eCosCentric maintainers (me, Bart, Nick, John), we are
able to at least offer eCosCentric's facilities: mail, phone, fax, etc.
and are prepared to deal with the admin overhead of doing so. If this
becomes new policy we'll want new assignments from existing contributors
so there'll be quite a few to deal with, at least at first.
To be clear, this isn't an attempt to take over :-). All your eCos do not
belong to us :). As such, if any other maintainer wants to accept
assignments (and put up their mail, phone, fax details on the web, mail
back executed assignment, etc.etc.) then we can easily list more than one
option to contact on the website. Although in that case, if someone opts
for that option, they should take care they do not have something in their
own employment contract that will mean all the IP assigned to them goes to
their employer! Mark and Andrew would probably be affected by this.
Also, in the case of Andrew, it would probably be advisable to explicitly
write to RH legal to "cancel" your assignment. For Mark, I guess until the
FSF arrangement is set up, its probably least problematic to continue
allowing RH copyright contributions.
Or if people aren't happy with this suggestion, we can just maintain the
status quo until the FSF is sorted out. We're just looking for a
constructive way forward. If people want to just wait until the FSF
resolved since, of course, it should be Real Soon Now, then it may not be
worth the effort putting this temporary compromise in place. I would like
to hope this would be the case, but also want to cut our losses.
Thoughts?
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next reply other threads:[~2003-10-30 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 17:22 Jonathan Larmour [this message]
2003-10-30 18:54 ` Andrew Lunn
2003-10-30 19:48 ` Jonathan Larmour
2003-10-31 10:43 ` Andrew Lunn
2003-10-31 11:07 ` Jonathan Larmour
2003-10-31 8:39 ` Gary Thomas
2003-10-31 11:15 ` Jonathan Larmour
2003-10-31 10:36 ` Andrew Lunn
2003-10-31 11:04 ` Jonathan Larmour
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=3FA148B9.3000608@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).