public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Way forward with FSF
Date: Thu, 30 Oct 2003 18:54:00 -0000	[thread overview]
Message-ID: <20031030185438.GC3802@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3FA148B9.3000608@eCosCentric.com>

> 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.

An assignment is a two way thing. Both the assignee and assigner
agree. It would be simple to add a section to the assignemt which says
that eCosCentric agrees to transfer the assignment to FSF imeadiately
they agree to accept the assignments for eCos. This should remove most
peoples worries.

I suppose we should also consider what happens if it all falls through
with FSF. They change there mind, or say they don't have the resources
needed to sort this out until this SCO thing is sorted out, they go
bankrupt paying legal fees, get burnt down in a bush fire,... The
assignments are then in limbo, being held by eCosCentric waiting to be
tranferred to somewhere they cannot go.
 
> 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.

No thanks. I don't have the resources, willingness etc....

One other thing comes to mind. It can be hard for some people to get
the PHB to sign the assignment. Having to get first an eCosCentric one
and then an FSF one signed will be double trouble. Maybe something can
be added to the eCosCentric one so that it can act as an automatic
forwarder to FSF once they are up an running. Signing the FSF
assignment then becomes optional for people with an eCosCentric
assignment.

        Andrew

  reply	other threads:[~2003-10-30 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 17:22 Jonathan Larmour
2003-10-30 18:54 ` Andrew Lunn [this message]
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=20031030185438.GC3802@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.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).