Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-members@lists.openembedded.org,
	openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: Minutes: OpenEmbedded eV Board meeting, 11-Jul-2011
Date: Sun, 17 Jul 2011 12:34:47 -0400	[thread overview]
Message-ID: <20110717163447.GF21964@denix.org> (raw)

Minutes: OpenEmbedded eV Board meeting, 11-Jul-2011

Attendees:

Michael Lauer (mickey)
Philip Balister (Crofton)
Florian Boor (florian)
Denys Dmytriyenko (denix)


00) action items from last meeting:
* call for TSC elections (Mickey) - done
* call for OE eV General Assembly (Crofton) - done
* status update on sending money for the switch
  ** florian is waiting for additional info (bank address) from Jeff (OSUOSL) to initiate the transfer
  ** once received, florian has to go to the bank in person to make the transfer
  ** sent the reminder to Jeff, the required info was received after the meeting
* check and open a credit/debit card for simple money transfers
  ** florian to take care when at the bank
* call for donations
  ** denix checked with TI, waiting for after Yocto budget is approved to see if any money left after LF and Yocto fees
  ** Intel offered a donation too - need to follow up with Dirk or DaveSt
  ** encourage people to make individual donations

01) agenda:
* TSC elections
* LF server donation status
* more financial/donation discussion
* financial contributions to OSUOSL for hosting OE
* some/any financial support from LF/Yocto

02) TSC elections
* call for TSC candidates was made
* 2 weeks period is over - only 1 candidate (RP)
* is call for votes required?
* can one candidate be accepted by acllamation?
* there were no reminders at the end of 2 weeks encouraging more candidates
  ** should the reminder be sent now and period extended by 1-2 days?
  ** Board decides by majority that 2 weeks were enough for anyone interested to propose their candidacy
* Board agrees to suggest electing RP by acclamation on the list (Mickey)
  ** if nobody objects, close the voting and announce the results
* make a note to send reminders next time before the 2-week application/discussion/voting period is over
* during GA we should discuss and/or update the statutes covering this situation (acclamation) in detail

03) LF server donation status
* still in the process - the previous hardware specs were scrapped
* while talking to involved parties, it's not clear who's the legal recipient of the donation
  ** Tom King is in the talks with LF and OSUOSL directly
  ** are the servers donated to OSUOSL/nas-admin or OE eV/Board?
* need to talk to LF to clarify things
  ** who are the people involved, who's overseeing, paperwork?
  ** Crofton on travel, denix to cover for him during next Yocto-AB meeting and raise the above questions
* suggest involved parties (Tom, LF, OSUOSL) to copy the Board (board@openembedded.org) in ongoing discussions instead of direct peer-to-peer emails or random IRC chats
* possibly hold a conference call to make the process more transparent

04) is the corporate donation procedure documented?
* check the Wiki, update if needed
* there is some form needed to be filled
  ** Crofton has the copy from previous TI donation
  ** florian will work with Intel, consult with Crofton for any legal aspects

05) individual donations
* denix makes first individual donation through PayPal
  ** hopes to inspire others to donate... :)
* Crofton to donate an SSD

06) financial contributions to OSUOSL
* Tom reports that OE is consuming most of the free resources provided by OSUOSL to Open Source projects
  ** OE needs to be a good citizen and contribute financially back to OSUOSL, like other projects
* Mickey: what's consuming the resources - web, git?
  ** According to Tom, git traffic is up, plus oe.org source mirror contributes to network traffic
  ** Also autobuilders doing regression testing on Angstrom and oe-core - cpu/disk load
* Estimate the amount of financial contribution to OSUOSL
  ** Still under discussion, Tom suggesting around $300-$500 per year?
  ** to offset the free hosting and bandwidth...
* Tom estimates to have 4-8 physical servers for OE in the near future

07) financial support from LF/Yocto
* LF is already supporting OE
  ** server donation
  ** sponsoring Tom's travel to the site for admin work
  ** offering travel sponsorship to key OE people for big events?
* some OE community members are suggesting that Yocto should provide additional financial support to OE
  ** to help with OE's ongoing expenses
  ** to support oe-core/meta-oe development, hosting and regression testing
  ** not talking about big money though

08) agree on next Board meeting
* next meeting is either Aug 8-12 or short one the last week of July for financial updates
* need to start fomalizing the budget and concrete financial goals

09) anyone attending CCC?
* http://events.ccc.de/camp/2011
* http://en.wikipedia.org/wiki/Chaos_Communication_Camp




                 reply	other threads:[~2011-07-17 17:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110717163447.GF21964@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-members@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