All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Creating an OpenEmbedded founation
Date: Tue, 12 Jun 2007 16:17:41 +0200	[thread overview]
Message-ID: <466EAB05.40203@kernelconcepts.de> (raw)
In-Reply-To: <B5ACE11E-74AF-468C-AF96-832AD1FBDBD5@selfish.org>

Hi,

Holger Freyther schrieb:

> So the natural question is do we need a foundation at all? Everything  
> seems to work just fine!

judging from the bad experience we had with handhelds.org lately we would have
been able to avoid a major part of the trouble by creating some kind of official
institution to cover GPE (and other projects as well). So even it is currently
looks like a foundation is not necessary you usually would not recognize the
fact that you need one before it is too late.

> So what shouldn't a foundation do?
> 	-Make things more complicated

Well... a foundation will always cause some additional overhead, I guess its
hard to avoid this.

> 	-Doing business as this is where companies are good at. We mean it!

That's quite important, but if our foundation starts to make business that would
cause quite a lot of interest conflicts.

> 	-Own the projects assets. This would include server equipment,  
> devices, hopefully domain-names, etc.

We should consider to make a foundation that is open to cover additional
projects as well. That might be interesting for smaller projects and maybe even
for LinuxToGo.

> 	-Maintain relationship with Companies

This would be really useful if we want to get more contributions from companies
that maybe use OE already but did not get involved into the project itself.

> OpenEmbedded e.V. (e.V. is the german expression for registered  
> associatio):
> 
> 	Pros:
> 		-Tightly regulated by german authorities. This helps us to stick  
> with the DO's and avoid the DON'Ts
> 		-KDE e.V. and probably the GNOME Deutschland e.V.
> 	Cons:
> 		-Quite an overhead. We need to hold  general assemblies, manage our  
> assets ourselves, try to get tax detuctable.
> 		-Managing of members...

I would prefer an e.V. - it is really some overhead, but it has some very
important advantages:
- It is a legal entity based on European law.
- Its basic intention is to cover groups with a common interest like we are.
- It is forced to be transparent.

The last point is the most important in my opinion.

Even if it is some overhead there should be quite a lot examples around that
might provide a good template we could start with.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76



  parent reply	other threads:[~2007-06-12 14:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 23:36 [RFC] Creating an OpenEmbedded founation Holger Freyther
2007-06-08  0:38 ` Rod Whitby
2007-06-09 16:56   ` Holger Freyther
2007-06-08  8:31 ` Rolf Leggewie
2007-06-08  8:50 ` Graeme Gregory
2007-06-10 13:56   ` Smart
2007-06-09 18:01 ` Marcin Juszkiewicz
2007-06-12  9:46 ` Stelios Koroneos
2007-06-12 10:31   ` Holger Freyther
2007-06-12 13:02   ` Gerwin van der Kruis
2007-06-12 14:17 ` Florian Boor [this message]
2007-06-15 14:10   ` Gerwin van der Kruis
2007-06-15 18:25     ` Koen Kooi
2007-06-18 18:31       ` Rolf Leggewie
2007-06-18 19:39         ` Koen Kooi
2007-06-19  0:16           ` Rolf Leggewie
2007-06-21 17:11     ` Holger Freyther
2007-06-21 17:37       ` Koen Kooi
2007-06-21 20:17       ` Marcin Juszkiewicz

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=466EAB05.40203@kernelconcepts.de \
    --to=florian.boor@kernelconcepts.de \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.