Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: progress on OE organization issues
Date: Thu, 04 Jun 2009 21:57:51 +0200	[thread overview]
Message-ID: <1244145476.6678.4.camel@port4> (raw)
In-Reply-To: <1243977526.5049.53.camel@lenovo.internal.reciva.com>

On Tue, 2009-06-02 at 22:18 +0100, Phil Blundell wrote:
> On Sat, 2009-05-16 at 08:54 -0400, Philip Balister wrote:
> > Phil Blundell wrote:
> > > On Sat, 2009-05-16 at 00:37 +0200, Michael 'Mickey' Lauer wrote:
> > >> My view on that is: The ideal situation would be that everyone interested in 
> > >> OE -- no matter on which level, technically, supportive, or administrative, 
> > >> becomes a member of the e.V.  This is relatively straightforward and does not 
> > >> require any financial commitments per se as our status include that a member 
> > >> can chose its own membership fee.
> > > 
> > > Sounds good to me.  What exactly needs to be done in order to make this
> > > happen?
> > 
> > Translate the eV papers into English. Someone did feed it through an 
> > internet translator, but I can't find the output on the web. We should 
> > go ahead and put them on the wiki.
> 
> What's the current status with this?  I guess as a first step we should
> at least get the German articles online, if that hasn't already been
> done.  That would make it easier to solicit volunteers for producing an
> English translation.
> 
> p.
There is an interresting part on Legal status here:
http://www.softwarefreedom.org/resources/2008/foss-primer.html#x1-190003

by the way why don't we join an umbrella organization?

Denis.





  reply	other threads:[~2009-06-04 20:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 12:44 progress on OE organization issues Cliff Brake
2009-04-30 14:26 ` Phil Blundell
2009-05-01  1:43   ` Cliff Brake
2009-05-07 11:19     ` Phil Blundell
2009-05-07 12:08       ` Philip Balister
2009-05-15 17:56         ` Phil Blundell
2009-05-15 19:04           ` Philip Balister
2009-05-15 21:54             ` Phil Blundell
2009-05-15 22:37               ` Michael 'Mickey' Lauer
2009-05-16  9:48                 ` Richard Purdie
2009-05-16 10:55                   ` Phil Blundell
2009-05-16 13:03                     ` Mark Brown
2009-05-16 12:02                 ` Phil Blundell
2009-05-16 12:54                   ` Philip Balister
2009-06-02 21:18                     ` Phil Blundell
2009-06-04 19:57                       ` GNUtoo [this message]
2009-06-05 21:43                         ` Cliff Brake
2009-06-06  6:46                           ` Michael 'Mickey' Lauer
2009-06-09  9:21                             ` Michael 'Mickey' Lauer
2009-06-09  9:53                               ` Rolf Leggewie
2009-06-10 13:34                                 ` Cliff Brake
     [not found]                               ` <d2b9ea600906092353o4fe9ea02vbc7df3b103b401c4@mail.gmail.com>
2009-06-10 13:11                                 ` Michael 'Mickey' Lauer
2009-06-11  6:48                                   ` Esben Haabendal
2009-06-11 10:10                                     ` Phil Blundell
2009-06-11 12:35                                       ` Philip Balister
2009-05-15 19:48           ` Cliff Brake
2009-05-24 15:49             ` Alessandro GARDICH
2009-05-24 16:26               ` Philip Balister
2009-05-06 12:44 ` Cliff Brake

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=1244145476.6678.4.camel@port4 \
    --to=gnutoo@no-log.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox