Openembedded.org - User contributions [en]

Category:OEDEM

2010-01-10T20:01:10Z

Glenn: +Category:Community

OE Developper meetings - see you in the real world

planning and documentation

[[Category:Community]]

SHR

2010-01-10T14:02:37Z

Glenn: +link

* http://shr-project.org/ - main page.
* http://wiki.openmoko.org/wiki/SHR - article at Openmoko.
** http://wiki.openmoko.org/wiki/Category:SHR

[[Category:Distro]]

BitBake

2010-01-10T13:51:23Z

Glenn: +link

'''BitBake''':
*[[BitBake (user)]] - for users.
*[[BitBake (dev)]] - for developers.

Wikipedia:
*http://en.wikipedia.org/wiki/BitBake

Overview of OE supported machines

2010-01-09T08:57:54Z

Glenn: corr micro-sd -> microSDHC, more

== Machines Comparison ==
'''Warning This Comparison could be incomplete'''
{| class="wikitable" border="1"
|-
! Machine
! CPU
! Ram
! Display
! Network
! Storage
! Input
! Other hardware
! Proprietary Drivers
! Last stable Kernel version
! Compatible Distributions(as in conf/distro in the openembedded tree)
|-
| [[BeagleBoard|Beagle Board]]
| OMAP3530@400 500 or 600Mhz
| 128MB DDR
|
|
| 256MB,SD card slot
| 2 buttons
| 3D chip
| 3D chip userland libraries
|
| [[Angstrom]]
|-
| Nokia N800
| OMAP2420@400 MHz
| 128MB
| 800x480 touchscreen
| wifi
| 256MB,2SDHC slots
| touchscreen,2 buttons
| GPS
| sound,power management,wifi(need a proprietary userland calibration tool),dsp are not free
| ?
| mamona,others?
|-
| Openmoko GTA02 ([http://wiki.openmoko.org/wiki/Neo_FreeRunner Neo FreeRunner])
| ARM920T@400Mhz(arm v4t)
| 128MB
| 480x640 vga touchscreen(glamo graphic chip)
| wifi(ar6k)
| 256MB flash,microSDHC slot
| touchscreen
| Ti calypso GSM, GPRS modem, GPS, Bluetooth, 2*3D accelerometers, USB
| 100% free driver (but 3 firmwares: gsm, wifi and gps)
| 2.6.28
| [[Openmoko]], [[Angstrom]], [[SHR]]
|-
| [[OXNAS]]
| ARM926EJ-S@367MHz
| 128Kbyte on-chip SRAM, 128Mbytes DDR1/2 SDRAM
|
| integrated 10/100/1000 Ethernet MAC with MII and GMII support
| 1-2 SATA ports
| 2 buttons
| USB, PCI, 128-bit AES engine
|
| 2.6.24
| [[Angstrom]]
|-
| [[Ronetix]] PM9263
| AT91SAM9263 240MHz System on module
| 64MB DRAM
|
| integrated 10/100 Ethernet MAC with MII support
| 4MB NOR Flash, 256 MB NAND Flash
| touchscreen
| USB, Serial number chip DS2401
|
| 2.6.28
| [[Angstrom]] or the angstrom based [[KaeilOS]]
|-
| [[Marvell]] Sheevaplug
| Marvell Kirkwood MV88F6281 1.2GHz
| 512MB DDR2
| NA
| integrated 10/100/1000 Ethernet MAC with RGMII support
| 512 MB NAND Flash, SD card slot
| 1 button accessible internally, 1 externally
| USB 2.0 host & client ports (com port and ARM JTAG via client)
| None
|
| [[Angstrom]]
|}

[[Category:Machine]]

Overview of OE supported machines

2010-01-09T08:50:37Z

Glenn: +link

== Machines Comparison ==
'''Warning This Comparison could be incomplete'''
{| class="wikitable" border="1"
|-
! Machine
! CPU
! Ram
! Display
! Network
! Storage
! Input
! Other hardware
! Proprietary Drivers
! Last stable Kernel version
! Compatible Distributions(as in conf/distro in the openembedded tree)
|-
| [[BeagleBoard|Beagle Board]]
| OMAP3530@400 500 or 600Mhz
| 128MB DDR
|
|
| 256MB,SD card slot
| 2 buttons
| 3D chip
| 3D chip userland libraries
|
| [[Angstrom]]
|-
| Nokia N800
| OMAP2420@400 MHz
| 128MB
| 800x480 touchscreen
| wifi
| 256MB,2SDHC slots
| touchscreen,2 buttons
| GPS
| sound,power management,wifi(need a proprietary userland calibration tool),dsp are not free
| ?
| mamona,others?
|-
| Openmoko GTA02 (FreeRunner)
| ARM920T@400Mhz(arm v4t)
| 128MB
| 480x640 vga touchscreen(glamo graphic chip)
| wifi(ar6k)
| 256MB flash,micro-sd slot
| touchscreen
| Ti calypso GSM,GPRS modem,GPS
| 100% free driver (but 3 firmwares: gsm, wifi and gps)
| 2.6.28
| [[Openmoko]], [[Angstrom]], [[SHR]]
|-
| [[OXNAS]]
| ARM926EJ-S@367MHz
| 128Kbyte on-chip SRAM, 128Mbytes DDR1/2 SDRAM
|
| integrated 10/100/1000 Ethernet MAC with MII and GMII support
| 1-2 SATA ports
| 2 buttons
| USB, PCI, 128-bit AES engine
|
| 2.6.24
| [[Angstrom]]
|-
| [[Ronetix]] PM9263
| AT91SAM9263 240MHz System on module
| 64MB DRAM
|
| integrated 10/100 Ethernet MAC with MII support
| 4MB NOR Flash, 256 MB NAND Flash
| touchscreen
| USB, Serial number chip DS2401
|
| 2.6.28
| [[Angstrom]] or the angstrom based [[KaeilOS]]
|-
| [[Marvell]] Sheevaplug
| Marvell Kirkwood MV88F6281 1.2GHz
| 512MB DDR2
| NA
| integrated 10/100/1000 Ethernet MAC with RGMII support
| 512 MB NAND Flash, SD card slot
| 1 button accessible internally, 1 externally
| USB 2.0 host & client ports (com port and ARM JTAG via client)
| None
|
| [[Angstrom]]
|}

[[Category:Machine]]

SHR

2010-01-09T08:47:30Z

Glenn: new - OE based distribution

* http://shr-project.org/ - main page.
* http://wiki.openmoko.org/wiki/SHR - article at Openmoko.

[[Category:Distro]]

Openmoko

2010-01-09T08:44:29Z

Glenn: wrong case corr

[http://openmoko.org Openmoko]

[[Category:Distro]]

Overview of OE supported machines

2010-01-09T08:43:43Z

Glenn: wrong case corr

== Machines Comparison ==
'''Warning This Comparison could be incomplete'''
{| class="wikitable" border="1"
|-
! Machine
! CPU
! Ram
! Display
! Network
! Storage
! Input
! Other hardware
! Proprietary Drivers
! Last stable Kernel version
! Compatible Distributions(as in conf/distro in the openembedded tree)
|-
| [[BeagleBoard|Beagle Board]]
| OMAP3530@400 500 or 600Mhz
| 128MB DDR
|
|
| 256MB,SD card slot
| 2 buttons
| 3D chip
| 3D chip userland libraries
|
| [[Angstrom]]
|-
| Nokia N800
| OMAP2420@400 MHz
| 128MB
| 800x480 touchscreen
| wifi
| 256MB,2SDHC slots
| touchscreen,2 buttons
| GPS
| sound,power management,wifi(need a proprietary userland calibration tool),dsp are not free
| ?
| mamona,others?
|-
| Openmoko GTA02 (FreeRunner)
| ARM920T@400Mhz(arm v4t)
| 128MB
| 480x640 vga touchscreen(glamo graphic chip)
| wifi(ar6k)
| 256MB flash,micro-sd slot
| touchscreen
| Ti calypso GSM,GPRS modem,GPS
| 100% free driver (but 3 firmwares: gsm, wifi and gps)
| 2.6.28
| [[Openmoko]], [[Angstrom]]
|-
| [[OXNAS]]
| ARM926EJ-S@367MHz
| 128Kbyte on-chip SRAM, 128Mbytes DDR1/2 SDRAM
|
| integrated 10/100/1000 Ethernet MAC with MII and GMII support
| 1-2 SATA ports
| 2 buttons
| USB, PCI, 128-bit AES engine
|
| 2.6.24
| [[Angstrom]]
|-
| [[Ronetix]] PM9263
| AT91SAM9263 240MHz System on module
| 64MB DRAM
|
| integrated 10/100 Ethernet MAC with MII support
| 4MB NOR Flash, 256 MB NAND Flash
| touchscreen
| USB, Serial number chip DS2401
|
| 2.6.28
| [[Angstrom]] or the angstrom based [[KaeilOS]]
|-
| [[Marvell]] Sheevaplug
| Marvell Kirkwood MV88F6281 1.2GHz
| 512MB DDR2
| NA
| integrated 10/100/1000 Ethernet MAC with RGMII support
| 512 MB NAND Flash, SD card slot
| 1 button accessible internally, 1 externally
| USB 2.0 host & client ports (com port and ARM JTAG via client)
| None
|
| [[Angstrom]]
|}

[[Category:Machine]]

OpenMoko

2010-01-09T08:43:13Z

Glenn: OpenMoko moved to Openmoko: wrong case

#REDIRECT [[Openmoko]]

Openmoko

2010-01-09T08:43:13Z

Glenn: OpenMoko moved to Openmoko: wrong case

[http://openmoko.org OpenMoko]

[[Category:Distro]]

OpenmokoNeo

2010-01-09T08:41:28Z

Glenn: +links, corr

The [http://www.openmoko.org Openmoko] Neo devices are a family of Samsung S3C24xx-based smartphones. The Openmoko devices are currently the only smartphones on the market shipping completely with free software. Targets is OE are:

* OM-GTA01 ([http://wiki.openmoko.org/wiki/GTA01:Neo_1973 Openmoko Neo 1973])
* OM-GTA02 ([http://wiki.openmoko.org/wiki/Neo_FreeRunner Openmoko Neo FreeRunner])

Openmoko devices support in OE is maintained by [[User:Mickey|Michael 'Mickey' Lauer]] and others from Openmoko team.

[[Category:machine]]

BitBake

2010-01-09T08:37:25Z

Glenn: chg

'''BitBake''':
*[[BitBake (user)]] - for users.
*[[BitBake (dev)]] - for developers.

BitBake

2010-01-09T08:37:12Z

Glenn: chg

'''BitBake''':
*[[BitBake (user)]] - for users.
*[[BitBake (user)]] - for developers.

Bitbake

2010-01-09T08:36:24Z

Glenn: chg

#REDIRECT [[BitBake]]

BitBake

2010-01-09T08:35:41Z

Glenn: BitBake moved to BitBake (user)

#REDIRECT [[BitBake (user)]]

BitBake (user)

2010-01-09T08:35:41Z

Glenn: BitBake moved to BitBake (user)

= Introduction =

'''BitBake''' is, at its simplest, a tool for executing [http://en.wikipedia.org/wiki/Task_%28computing%29 tasks] and managing [http://en.wikipedia.org/wiki/Metadata metadata]. As such, its similarities to [http://en.wikipedia.org/wiki/GNU_make GNU make] and other build tools are readily apparent. It was inspired by [http://en.wikipedia.org/wiki/Portage_%28software%29 Portage], the package management system used by the Gentoo Linux distribution.

BitBake is the basis of the OpenEmbedded project, which is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus and Familiar.

= Links =

* Homepage with manual: http://bitbake.berlios.de/
* Project page at Berlios: http://developer.berlios.de/projects/bitbake/
* <strike>Subversion repository: http://svn.berlios.de/svnroot/repos/bitbake/</strike>
* GIT repository: http://cgit.openembedded.org/cgit.cgi/bitbake/

= Version information =

OpenEmbedded require BitBake 1.8.10 or newer. Some features can require <strike>SVN</strike> GIT HEAD.

BitBake "trunk" contain experimental code - use at your own risk.

[[Category:User]]

Bitbake

2010-01-09T08:34:45Z

Glenn: Bitbake moved to BitBake (dev)

#REDIRECT [[BitBake (dev)]]

BitBake (dev)

2010-01-09T08:34:45Z

Glenn: Bitbake moved to BitBake (dev)

''developer homepage''

* First , RTFM ;-) : http://bitbake.berlios.de/manual/
* Don't forget mailinglist :
** https://lists.berlios.de/pipermail/bitbake-dev/
** https://lists.berlios.de/pipermail/bitbake-commit/
* Best documentation for source is via python documentation system.

= Tutorial =

This tutorial focus bitbake developement, not bbclass or openembedded developement that is documented elsewhere.

== "Helloworld" using bb library ==

=== Simplest ===

<pre>
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-

import bb

version = bb.__version__
bb.note("Hello from helloworld using lib bb v%s." % ( version ))
</pre>

=== with data module ===

<pre>
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-

import os , bb
from bb import data

hello = ("Hello from helloworld using lib bb v%s." % ( bb.__version__ ))

d = data.init()
data.setVar('HELLO_MSG', hello, d)

mystring = data.getVar('HELLO_MSG', d, 1)
bb.note(mystring)
</pre>

data module is well documented because it uses doctest.
Enjoy to play with the different methods.

=== with persist_data module ===

Now you want persistant data to exchange data between threads/tasks.
This can be done using bb.persist_data module that uses sqlite via pyslite2.

<pre>
#!/usr/bin/env python
# ex:ts=4:sw=4:sts=4:et
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-

import bb, os, sys
from bb import data, persist_data, fetch

__version__ = "0.0.1"

def main():
"""
The main Method
"""

# persist_data module need debug_level to be set
bb.msg.set_debug_level(0)

# init a data with PERSISTENT_DIR to set where the data will be saved
d = data.init()
data.setVar('PERSISTENT_DIR', os.getcwd(), d)

# create persist_data base in bb_persist_data.sqlite3
pd = persist_data.PersistData(d)

# create a sql table
pd.addDomain("MYBASE")

# add a data in this table
pd.setValue( "MYBASE", "TOTO", "hello world!")

# print it
val = pd.getValue ( "MYBASE", "TOTO")
print val

if __name__ == '__main__':
main()
</pre>

You can edit and watch your base using [http://sqlitebrowser.sourceforge.net sqlitebrowser] for example. Should be useful for debug and test purpose. You can look also at fetch module source that use bb.persist_data.

[[Category:Dev]]

BitBake (user)

2010-01-09T08:32:59Z

Glenn: catspec

BitBake (user)

2010-01-09T08:31:31Z

Glenn: +links

BitBake (user)

2010-01-09T08:29:09Z

Glenn: +links

= Introduction =

BitBake is, at its simplest, a tool for executing [http://en.wikipedia.org/wiki/Task_%28computing%29 tasks] and managing [http://en.wikipedia.org/wiki/Metadata metadata]. As such, its similarities to GNU make and other build tools are readily apparent. It was inspired by Portage, the package management system used by the Gentoo Linux distribution.

BitBake is the basis of the OpenEmbedded project, which is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus and Familiar.

= Links =

* Homepage with manual: http://bitbake.berlios.de/
* Project page at Berlios: http://developer.berlios.de/projects/bitbake/
* <strike>Subversion repository: http://svn.berlios.de/svnroot/repos/bitbake/</strike>
* GIT repository: http://cgit.openembedded.org/cgit.cgi/bitbake/

= Version information =

OpenEmbedded require BitBake 1.8.10 or newer. Some features can require <strike>SVN</strike> GIT HEAD.

BitBake "trunk" contain experimental code - use at your own risk.

[[Category:Categories]]

Using IceCC

2010-01-09T08:26:52Z

Glenn: catspec

== IceCC and OE ==
It is possible to compile on a cluster of machines with OE, and quite easily so. This code is still somewhat experimental, but should rapidly stabilize thanks to the work that Ifaistos has put into it recently and previous work from likewise and zecke (I hope I did not forget anyone). You need to take the following steps to prepare for compilation with icecc. How to set up icecc itself is beyond this intro.

* Put ''INHERIT += "icecc"'' in your local.conf
* copy the customized [http://bugs.openembedded.org/attachment.cgi?id=1032&action=view create-icecc-env.sh] script to /path/to/your/oe/root/tmp/ and make it executable.
* set ''ICECC_ENV_EXEC = /path/to/your/oe/root/tmp/create-icecc-env.sh'' in your local.conf
* set ''ICECC_PATH = /usr/bin/icecc'' in your local.conf (be sure this matches the output of 'which icecc')

User now can specify if certain packages or packages belonging to class should not use icecc to distribute compile jobs to remote machines, but handled localy, by defining ICECC_USER_CLASS_BL and ICECC_USER_PACKAGE_BL with the appropriate values in local.conf

=== ICECC config ===

#
# Nice level of running compilers
#
# ICECC_NICE_LEVEL="5"
ICECC_NICE_LEVEL="5"
#
# icecc daemon log file
#
# ICECC_LOG_FILE="/var/log/iceccd.log"
ICECC_LOG_FILE="/var/log/iceccd.log"
#
# Identification for the network the scheduler and daemon run on.
# You can have several distinct icecc networks in the same LAN
# for whatever reason.
#
# ICECC_NETNAME=""
ICECC_NETNAME="oe"
#
# You can overwrite here the number of jobs to run in parallel. Per
# default this depends on the number of (virtual) CPUs installed.
#
# ICECC_MAX_JOBS=""
ICECC_MAX_JOBS="3"
#
# This is the directory where the icecc daemon stores the environments
# it compiles in. In a big network this can grow quite a bit, so use some
# path if your /tmp is small - but the user icecc has to write to it.
#
# ICECC_BASEDIR="/var/cache/icecc"
ICECC_BASEDIR="/var/cache/icecc"
#
# icecc scheduler log file
#
# ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"
ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"
#
# If the daemon can't find the scheduler by broadcast (e.g. because
# of a firewall) you can specify it.
#
# ICECC_SCHEDULER_HOST=""
ICECC_SCHEDULER_HOST=""

=== Local Configuration ===

A sample local.conf entry for icecc that does not distribute compiles jobs for native packages looks like this.
Change the paths to match your setup

PARALLEL_MAKE = "-j 10"
ICECC_PATH = "/usr/bin/icecc"
ICECC_ENV_EXEC = "/proj/oplinux-0.2/op-linux/branches/oplinux-0.2/tmp/icecc-create-env"
ICECC_USER_CLASS_BL = " native"
INHERIT += "icecc"

=== Successes and Failures ===

This whole explanation is probably highly dependent on the icecc version used. Please do add success reports here. Also note that a lot of packages turn PARALLEL_MAKE off, as they break if compiled on a single machine, although i have noticed that they do not fail under icecc. Any feedback on this would be helpful

* mixing versions of the icecc package can create problems. For example the icecc package from dapper and edgy are incompatible.
* I (Laibsch) have a working setup between two edgy machines now. I had trouble until I set ICECC_NETNAME and ICECC_SCHEDULER_HOST to the respective, pingable hostnames of the machines. This is weird since I am on a LAN (192.168.1.x) for both machines and there is no firewall.

[[Category:User]]

Become Sponsor

2010-01-09T08:25:47Z

Glenn: +cat

= Overview =

This page describes how an organization can help OpenEmbedded.

= Sponsorship =

The OpenEmbedded project encourages organizations that benefit and use OE to become a sponsor. There are three levels of sponsorship, Gold, Silver, and Bronze.

== Gold Sponsorship ==

Annual Cost: EUR 25000

== Silver Sponsorship ==

Annual Cost: EUR 5000

== Bronze Sponsorship ==
Annual Cost: EUR 500

= Project Contribution =

OE is always interested in getting help to improve the project and software. Anyone that has identified problems is encouraged to pitch in and help out. Additionally, help with specifics such as technical writing, design, testing, and other specialized skills would be valued.

[[Category:Community]]
[[Category:Categories]]

Category:Candidates for speedy deletion

2010-01-09T08:24:56Z

Glenn: new

[[Category:Wiki Editing]]

Category:Wiki Editing

2010-01-09T08:24:29Z

Glenn: new

[[Category:Community]]

Template:Delete

2010-01-09T08:23:49Z

Glenn: new - copied from http://www.freesmartphone.org/index.php/Template:Delete

<noinclude>
The template goes like (this is just an example, please do NOT delete @this page):
[[Category:Templates]]
</noinclude>
{| style="background-color:#ffff99;color:#000000;border:1px solid #606060;margin:1em 5% 1em 5%;"
| style="padding:0.5em 0.5em;" |
| style="padding:0.5em 0.5em;" | <b>Proposed for deletion:</b> This page is proposed for deletion by {{{2}}} because <i>{{{1}}}</i>.
|}
<includeonly>{{{category|}}}</includeonly>
<noinclude>
Use this template to mark pages for deletion. Usage:

Add this to the page content:

<pre>

<nowiki>
{{Delete|Reason for deletion|Signature}}
</nowiki> </pre>
</noinclude>
<includeonly> [[Category:Candidates for speedy deletion]] </includeonly>

Using IceCC

2010-01-09T08:21:38Z

Glenn: +cat

Quality assurance

2010-01-09T08:21:23Z

Glenn: +cat

[[Quality assurance]], the process or set of processes used to measure and assure the quality of a product ( cf [http://en.wikipedia.org/wiki/Quality_Assurance wikipedia] )

* [[BitTest]] : [http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000255.html announcement]
* [[oetest]] :

* [[oestats]] / [[TinderBox]] : [[How_do_I_send_automatic_success_and_failure_reports]]
* insane and sanity bbclass...

[[Category:Community]]

OpenEmbedded eV Statutes

2010-01-09T08:21:00Z

Glenn: +cat

The following is a Babelfish translation of http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf

Please clean this up if you speak German.

== Statute of the OpenEmbedded registered association ==
(conditions 22.11.2008)

=== explanation by terms ===
# free software, also “open SOURCE software” mentioned, in the sense of this statute are computer programmes, which are made available free of charge by the author in not backgetable way of the public. The author grants third the freedom to be allowed to use the program for each purpose; examine to be allowed, how the program functions and it to the own needs to adapt; To be allowed to make copies for others; to be allowed to improve and the program and make accessible these improvements general well-being.
# Development of free software in the sense of this statute covers the research and elaboration of the theoretical bases and concepts as well as their testing by programming and test of free software, which realizes these concepts and bases.
# “OpenEmbedded (OE)” is a computer-assisted tool, which contains both infrastructure for programs and user programs of inclusive tones, pictures, documents and translations. As free software is developed and put to the public free of charge at the disposal.

=== 1. Name, seat and financial year ===
# the name of the association OpenEmbedded registered association reads, shortened OE registered association
# the association has its seat in Berlin, Federal Republic of Germany. If no firm office is furnished, the administration follows the residence of the respective member of the board, who notices the management.
# An entry is aimed at into the register of associations of the district court Berlin Charlottenburg.
# Financial year is the calendar year.

=== 2. Association purpose ===
# the purpose of the association is the promotion and spreading of free software in the sense suitor software with special consideration of the program complex “OpenEmbedded”, in order to support the free knowledge exchange and the equal chances with the entrance to software as well as national education, science and research.
# The association purpose in particular realised by
#* a.die promotion of the education, the exchange of views and the co-operation of users, developers and researchers
#* b.Forschung and discussion over the effects of free software and the thought suitor software on society and science
#* c.die advancement and research at free software, as well as their their integration within the home range
#* d.die supply of free software, supporting pictures, tones, to make for data and documentation as well as promotion their availability and the production and spreading of documentation accessible over it
#* e.Beiträge the adept information of the public in the field of activity of the association and participation at fairs and congresses around the information a broader spectrum of users f.Organisation from congresses and generally accessible lectures to the further training of the project participants and User g.das retaining the free rights of the project participants to the protection from commercial interests third
# a change of the association purpose may only in the framework in § 3 (1) of given framework to take place.

=== 3. Non-profit character ===
# the association pursues directly non-profit purposes in the sense of the section tax-privileged purposes of the tax code in the context of its activity in accordance with § 2 of the statute exclusively and (§§ 51ff. AO). It is selbstlos active and pursued not primarily self-economical purposes
# the means of the association is excluding for statutory purposes to be used. The members receive excluding reimbursements of developed costs, but no direct allowances from means association.
# Nobody may by expenditures for association, which are strange to the association purpose or are favoured by disproportionately high remuneration. For the replacement of expenditures, as far as different legal regulations are not to be used, the federal travel expenses law is determining.

=== 4. Kinds of the membership and members of the association ===
# members of the association can become natural and legal entities, who want to carry and support the goals of the association. In order to become fair the international character of the association, in addition, over members the possibility to give of withdrawing itself from the active support of the advancement from OpenEmbedded without giving the membership up, thereby the following kinds are intended by memberships:
#* A) Active members are natural persons, who support the association purpose and the implementation of the association goals by cooperation and the full obligations of a club member take over. In particular cooperation from them, which and the practice of the right to vote expects, becomes participation in the meetings of the members.
#* b) Extraordinary members are natural and legal entities, who explain the support of the association purpose and the association goals by their membership in the association, but do without the practice of the rights of the active members, here the practice of the right to vote. Legal entities designate a natural person as representatives for practice remaining rights and obligations.
#* C) Promoting members are extraordinary members, that promote the association purpose and the association goals in particular by a financial or a special contribution. They are published on own desire on the web page of the association and to have the right to the participation in the meeting of the members, without acquiring thereby a right to vote.
# The active membership is acquired on proposal of an active member with agreement of two of other active members by resolution of the meeting of the members or the active members by Internet choice with simple majority. Main decision criterion for the admission should be the commitment shown by the photograph candidates during a longer period and the contribution made thereby in the sense of the association goals. An active member can change on own request at the executive committee into the extraordinary membership. During default of the obligations of an active member over two following each other tidy meetings of the members, indicated above, the membership changes automatically into an extraordinary. An extraordinary however not promoting member can request the active membership at the executive committee. On the admission of promoting members the executive committee decides.
# The membership ends by withdrawal, exclusion or death, with legal entities also by loss of the juridical personality. The withdrawal of a member is possible only to 31 December of each yearly. It takes place via written explanation opposite the executive committee under adherence to one period from 4 weeks.
# The instrument of the association exclusion is critical situations reserved, whereby in principle to the quality the priority is to be granted clarifying. The exclusion takes place on resolution of the executive committee with immediate effect. Reasons for an exclusion can be
#* a) a heavy offence of a member against the regulations as well as goals and purposes of the association specified in this statute after a unsuccessful attempt of clarifying, as well as
#* b) despite repeated reminder existing arrears at payments of dues during one period of 12 months. Opportunity must be given to the member to the justification and/or statement before the adoption of resolutions. Against the exclusion contradiction can be inserted within four weeks at the executive committee, on which the next meeting of the members decides. Up to the decision of the meeting of the members the rights and obligations of the member rest.
# With separating a member from the association or during dissolution of association no requirement on Rückerstattung of brought in net assets exists.

=== 5. Organs of the association ===
of organs of the association are:
* the meeting of the members as well as
* the executive committee.

=== 6. Meeting of the members ===
# All club members can attend meeting of the members. Only active members receive one voice each.
# The meeting of the members takes place at least once a year. It will call up in writing from the executive committee by post office or email under indication of the provisional agenda. The invitation period amounts to six weeks. The period begins with the day following on the sending off of the invitation letter. It is valid the date of the postmark or the sending off of the email. The invitation letter is considered as happened, if it is addressed to the last address announced by the member of the association in writing. The members can in writing or electronically address further requests for items on the agenda until 2 weeks before the meeting to the executive committee. It is valid the date of the post office and/or email entrance. The executive committee publishes the final agenda in the Internet, the address is in the written invitation to be communicated.
# An extraordinary meeting of the members is to be called up, if it requires the interest of association. On written demand of at least 20% of all club members the executive committee has to call up an extraordinary meeting of the members within six weeks. The desired item on the agenda must have to be inferred from the request of the members.
# The meeting of the members is resolutionable during normal invitation without consideration for the number of appearances. She selects from her center a Versammlungsleiter. Resolutions are met, if the meeting does not determine something else, openly by show of hands with a simple majority of votes. With equality of votes a request is valid as rejected.
# To amendments of the by-laws and to resolutions over the dissolution of the association are deviating from (4) 3/4 of the voices delivered in the meeting of the members, at least however half of the voices of all active club members necessarily.
# An active member, that appears not personal for meeting of the members, can leave itself represented by another member personally present during the meeting of the members. The representative notices the right to vote of the represented member beside his own. The representative legitimizes itself at the beginning of the meeting of the members by presenting a written authority in the original opposite the executive committee. A representative can represent maximally two members.

=== 7. Tasks of the meeting of the members ===
# the meeting of the members as the highest resolution-seizing representative body of the association is in principle responsible for all tasks, if certain tasks did not become to transfer another representative body of the association in accordance with this statute. The meeting of the members selects from the number of the active members the executive committee. The persons, who unite most voices on itself, are selected. The choice secretly takes place with voting cards.
# The meeting of the members can vote members out of the executive committee. For this it needs in deviation from (1) the majority of the voices of all active club members.
# The meeting of the members decides on contradictions of members, whom the executive committee intends to exclude.
# The meeting of the members receives the business report of the executive committee which can be submitted annually and the examination report of the invoice controller and gives the executive committee discharge.
# It is reserved the meeting of the members to decide on amendments of the by-laws and dissolutions of association.
# You are to be submitted in particular the annual account and the annual report for adoption of resolutions over permission and the discharge of the executive committee in writing. She orders two invoice controllers, that belong neither to the executive committee still another committee appointed by the executive committee and are not also employees of the association, in order to examine and report on the result before the meeting of the members record keeping including end-of-year procedure. The invoice controllers have entrance to all reservation and calculation documents of the association.
# the right of representation of the executive committee it is opposite the way limited third that for the following legal transactions the agreement of the meeting of the members is necessary: more
#* a.über on and sale as well as the load of landed property,
#* b.die financial participation in societies as well as
#* c.die admission of loans starting from EURO 10,000, -, to decide.
# She can decide over further affairs, which by the executive committee or from the member shank is submitted to it.

=== 8. Executive committee ===
# the executive committee consists only natural persons of 4 persons, it can belong. The term of office amounts to 3 years. Re-election is permissible. The members of the board officiating in each case remain at expiration of the term of office in the office, until successors are selected
# the executive committee select from his center one chairman and two deputies. One the deputy is a treasurer. Re-election is permissible.
# The executive committee work, in particular regulations for the summoning of board meetings, whose expiration and the execution of votes, regulated by an agenda of the executive committee, which decides the executive committee unanimously.
# The executive committee decides over all association affairs, as far as they do not require a resolution of the meeting of the members. It implements the resolutions of the meeting of the members.
# The members of the executive committee are everyone for itself alone in the name of the association outward entitled to act as substitute.
# In case of separating a member of the board during the term of office the executive committee determines a kommissarisches member of the board according to Internet choice of the active members. The kommissarische member of the board remains up to the next meeting of the members in the office. On a final follow-up in the executive committee the meeting of the members decides.
# The executive committee can order a full-time managing director, who leads the current business of the administration of the association by resolution as special representatives in accordance with §30 BGB and superior of the full-time association coworkers is. Decisions over work contracts, notices as well as admissions of members and member exclusions remain reserving the executive committee.
# The managing director has to participate the obligation to the participation in the meetings of the members and the right as well as on demands of the executive committee the obligation in the board meetings. It has speech right on all meetings and is the representative bodies of the association opposite accountable.
# The executive committee on its part can make amendments of the by-laws, which are required by supervision, court or fiscal authorities for formal reasons. The amendments of the by-laws must be communicated to the next meeting of the members.

=== 9. Agenda ===
the agenda regulates going out details of the association work over the frameworks of the statute. The executive committee puts the agenda into force after the agreement by the members. The agreement of the members takes place via Internet choice with simple majority of the active members.

=== 10. Minutes ===
the resolutions of the executive committee and the meetings of the members are laid down in writing and stand for the members to the insight for order.

=== 11. Collective agreements ===
before the employment full-time persons employed regulates the executive committee their payment in the agenda.

=== 13. Association financing ===
# the necessary financial means of the association constituted by
#* A) of membership dues,
#* b) of subsidies of the country, the municipalities and other public places,
#* C) donations,
#* D) other allowances third,
#* e) repay for activities of the association in the context of the non-profit character, among other things for lectures.
# The members pay contributions in accordance with condition of a resolution of the meeting of the members or the active members by Internet choice with simple majority. The regulation for the height of membership dues becomes a component of the agenda.
# In the case of dissolution of the association or with omission of tax-privileged purposes the fortune of the association falls at the German Unesco Kommision registered association, Colmantstraße 15, 53115 Bonn, which has to use it directly excluding and for non-profit purposes. Resolutions over the future use of the property of the association may be implemented in this case only after consent of the tax office.

=== 14. The entry into force ===
managing statute contents was decided by the founders' meeting to ............. in Brussels, Belgium.

The initial members of the association draw as follows:

[[Category:Community]]

Online Voting Policy

2010-01-09T08:20:41Z

Glenn: +cat

Rules of Procedures for Online Voting

The articles of association of the OpenEmbedded e.V. provide that certain decisions can be taken by online voting. This includes voting about new members and deciding about certain rules of procedures. In addition the OpenEmbedded e.V. allows to use online voting for decisions which aren't covered in the articles of association. There are several different types of votes which slightly differ in procedure and method to calculate results. These rules regulate the procedure of online votes and how results are calculated. The intention of these rules is to provide a fair and pragmatic way to let the OpenEmbedded e.V. take decisions by online voting.

=Voting Administrators=

The board of the OpenEmbedded e.V. assigns one or more voting administrators which are responsible for technically performing the voting. This includes sending out the ballots, receiving the votes, calculating and publishing the results.

The voting administrators must not disclose any information about the identity of the voters or any other information which isn't contained in the published voting results.

=General procedure for online voting=

An online voting is initiated by a voting proposal followed by a discussion period. After the discussion period the voting period is started. The voting is finished by calculating and publishing the voting results.

Results of online votes are effective immediately following publication of the results unless otherwise stated in the voting proposal.

==Voting Proposal==

An online voting is initiated by a proposal for voting which states the subject of the voting. The proposal is sent by email to the membership mailing list and has to include exact and complete information what is voted upon. Only the information which is directly included in the mail sent as voting proposal is subject of the voting.

The voting proposal email has to explicitly be marked as voting proposal by starting the email subject line with the string "Voting Proposal:".

Any active member can initiate a voting by sending a voting proposal.

The member who has initiated a vote can retract the voting proposal by sending an email to the membership list stating the intention to retract the proposal.

A proposal can only be retracted within the discussion period.

==Discussion Period==

The discussion period begins on the date the membership mailing list receives the voting proposal. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the discussion period lasts for two weeks. The discussion period should be used to discuss the voting and form opinions about the options which are available for voting.

==Start of Voting==

When the discussion period has finished the voting is started by sending ballots to all active members. The ballots should include the text of the proposal which is voted about.

==Voting Period==

The voting period is started by sending out the ballots. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the voting period lasts for two weeks. During the voting period the active members cast their votes. Only votes cast within the voting period are considered for the results of the voting.

==End of Voting==

After the voting period all cast votes are counted and the results of the voting are published.

The results of a vote are published to the OpenEmbedded e.V. membership by sending them to the membership mailing list. They have to include the number of persons permitted to vote, the total number of votes, and the number of votes for each available voting option. The results should also include a statement, if the voting was valid according to section 5.

=Types of Votes=

There are three types of votes: Votes about new members (3.1), elections of groups of people (3.2), votes for decision (3.3).

==Voting about new members==

The discussion period is started by sending a new member proposal to the membership mailing list. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.

The discussion period has a duration of one week and is extended to two weeks, if requested by a member.

The voting period has a duration of one week.

For new member votes there are three options: "Yes", "No", "Abstention". The new member is accepted, if there are more "Yes" than "No" votes and the vote isn't invalid according to section 5.

==Electing groups of persons==

For elections of groups of people there is an additional candidacy period before the voting proposal is sent. The person responsible for the execution of the voting sends a call for candidates to the membership mailing list which starts the candidacy period. If there is no explicit rule about who is responsible for execution of the voting, the board of the e.V. is responsible.

The candidacy period lasts two weeks. All members who declare their candidacy in a statement sent to the membership list become candidates for the election.

After the candidacy period the list of candidates is sent as voting proposal. This starts the two-weeks discussion period.

The candidates are voted on as options according to section 3.4.

==Voting about decisions==

The OpenEmbedded e.V. can officially take decisions or decide about official statements on request of at least three active member. One member has to send the voting proposal to the membership mailing list. This starts the discussion period. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.

The responsible party for execution of the voting sends the voting proposal which includes all options. This starts the discussion period.

After the discussion period the voting is started. The options are voted on according to section 3.4.

==Voting System==
===Multiple options===

If there are more than two options (excluding abstention), the following voting system shall be used:

The members are asked to rank the options in terms of their preference into a ballot. A ballot may contain two options of the same rank. All options must be ranked. Each member may make up to one ballot.

The winners are found by:

1. Given two options A and B, V(A,B) is the number of voters who prefer option A over option B.
2. From the list of options, we generate a list of pairwise defeats.
* An option A defeats an option B, if V(A,B) is strictly greater than V(B,A).
3. From the list of pairwise defeats, we generate a set of transitive defeats.
* An option A transitively defeats an option C if A defeats C or if there is some other option B where A defeats B AND B transitively defeats C.
4. We construct the Schwartz set from the set of transitive defeats.
* An option A is in the Schwartz set if for all options B, either A transitively defeats B, or B does not transitively defeat A.
5. If there are defeats between options in the Schwartz set, we drop the weakest such defeats from the list of pairwise defeats, and return to step (iii).
* A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B).
* A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat.
6. If the number of options in the Schwartz set does not exceed the number of required winners, then the winners are the Schwartz set. If the number of members of the Schwartz set exceeds the number of required winners, the board chooses which of the members of the Schwartz set wins.
7. If this results in an insufficient number of winners, then the candidates which have already won according to step (vi) should be removed from the list of options, and then this procedure is repeated from step (i).

Parts of this section are copied from the Constitution for the Debian Project (v1.4), http://www.debian.org/devel/constitution

===Two options===

If the number of options is exactly two (excluding abstension), then:

* Each active member can vote with "Yes", "No" or "Abstain".
* If there are more "Yes" than "No" votes and the vote isn't invalid according to section 5, the decision is accepted.

=Right to vote=

All members of the OpenEmbedded e.V. which are active members at the time the voting period is started have the right to cast a vote. The prerequisite for taking part in online votes is a valid email address in the member database. The member is solely responsible for initially setting and updating his email address in the member database.

=Quorum=

The result of a voting only becomes effective when the number of votes which have chosen an option different from "Abstention" is greater than 20 percent of the number of active members. If this quorum isn't reached the voting is considered invalid. An invalid voting can be repeated, but not before a period of four weeks has passed between publishing the results of the invalid vote and the proposal for the repeated voting.

=Anonymity=

Online votes are anonymous. The information which members participated in the vote and for which option they voted aren't disclosed. The voting administrators are allowed to track this information for technically executing the vote. The information mustn't be used for other purposes and mustn't be made available to any other people.

=Publication of voting results=

All voting results except for rejected votes about new members are published on the OpenEmbedded e.V. web site, excluding the exact numbers of votes.

=Modification of voting procedure=

The board may modify the voting procedures for individual votes upon request of the e.V. membership if good reason for the change, as determined by the good judgment of the board, is provided.

[[Category:Community]]

Oedem2007

2010-01-09T08:20:28Z

Glenn: +cat

==Venue==

GMIT GmbH Novalisstrasse 10 10115 Berlin Germany

==Schedule==

time: Oct 6th - Oct 10th
* arrivals / coding sprint: Oct 6th - Oct 7th
* technical discussions / presentations: Oct 8th - Oct 9th
* departures / coding sprint: Oct 10th

==List of people==

* Holger 'zecke' Freyther
* Rolf 'Laibsch' Leggewie
* Richard Purdie [Oct 7 - Oct 10] - Honigmond RH - Flight arrives 19:30
* PHilipp Zabel * Rodrigo Vivi [Oct 5 - Oct 10] - Honigmond RH - Flight arrives 12:45
* Gerwin van der Kruis * Michael 'Mickey' Lauer [Oct 8 - Oct 10]
* Marcin 'hrw' Juszkiewicz - [Oct 6 - Oct 10] - Casa Holger - Bus arrives ~12 at Alexanderplatz - I will go to the office directly.
* Stelios S. Koroneos [Oct 7 - Oct 10] - Flight arrives 10:10
* Koen Kooi - [Oct 5 - Oct 10] - Casa Holger - Train arrives 13:18
* Henning Heinold (woglinde)
* Florian Boor [Oct 7 - Oct 10] - Flight arrives 21:10
* Graeme (XorA) Gregory [Oct 5 - Oct 11]- Honigmond RH - Flight Arrives 12:45 - Flight Leaves 13:30
* Daniel Willmann (alphaone)
* Philip Balister (Crofton) [Oct 5 - Oct 10] - Hotel * Gästehaus Berlin Mitte * - Flight arrives 10 AM
* Jonas Hurrelmann (jott) * Uli Luckas [Oct 9]
* Jan Lübbe (shoragan)
* Henryk Plötz
* please drop zecke an email if you plan to come

==Quartiers==

inks for rooms in walking distance (same street as the office)
* zecke's flat. I think I can host four of you (5-10 minutes walk to the office)
* [http://www.honigmond-berlin.de]
* [http://www.eastener-hostel.de] further away (a longer walk)
* [http://www.gaestehaus-berlin-mitte.de/]

== Agenda ==

=== Top Level Items ===

* Creating a Foundation. Who is goint to prepare the paper work? zecke and florian could do that
* Should we hold a sprint? Should we do user presentations?
* Reconsider changing SCM

=== 2007.10.08 ===
====[09:55] Assign note taker to collect and publish minutes====
====[10:00] Welcome Branch ====
====[11:00] Review of last years work ====
====[11:30] Discuss and adjust agenda ====
====[12:00] OE Foundation, what was done, what is needed, how to proceed and where to create it====
====[13:30] Lunch ====
====[15:30] OpenEmbedded User Presentations====
=====OpenMoko=====
=====Indt/Mamona=====
=====Tarent=====
=====DigitalOpsis=====
====[17:30] Solutions for vendor discussion====
=====Stable release=====
=====SDK=====
=====Distro's=====
=====Target Hardware issues=====
=== 2007.10.09 ===
====[10:00] Technology====
=====update-alternatives of ipkg=====
=====distro generic=====
=====clean staging(?)=====
=====getting image in-between task-base and task-boot?=====
=====General strategy how to get things smaller=====
=====Features tied to boards on e.g. gumstix=====
=====Quality Issues=====
====[13:30] Lunch ====
====Infrastructure====
=====Autobuilder=====
=====Maintainers=====
=====How to deal with the wiki=====
== To Be Done ==
* Prepare paper-work for an e.V.
* Plan one day for the general assembly of the e.V.
* Decide on the Agenda.
* Should we hold a sprint? What would be the topic? QA, Angstrom polishing, doing our first stable release, creating a GUI for BitBake/OE?
* Sprint: merge .dreambox, get llvm to build, get llvm-cross working, pycurses angstrom setup gui

[[Category:Community]]

Oedem/2010

2010-01-09T08:20:15Z

Glenn: +cat

OpenEmbedded Developers' Meeting 2010 will be in XXX, YY on the weekend of ZZZ.

All developers and other interested parties are welcome.

== Location ==

Call ... if you get hopelessly lost.

== Registration ==

Due to restricted space at the venue, the number of attendees is strictly limited.

== Agenda ==

=== Friday ===

...

=== Saturday ===

...

=== Sunday ===

...

==Travel==

...

==Accommodation==

The nearest full-service hotel is ...

Cheapest accomodation is ...

==Food and drink==

...

==Attending for sure==

...

[[Category:Community]]

Oedem/2009 TSC election

2010-01-09T08:19:59Z

Glenn: +cat

At Oedem/2009 the following people have been proposed for the TSC, but that has nothing to do with the proper proposing protocol, so you can safely ignore this page.

* '''Phil Blundell'''

: ''(Nominated by Stefan Schmidt)''

: Both Holger an Phil have an deep understanding on how OE and bitbake work and was designed to work. Both are thinking about ways to further improve the current situation and contribute code and ideas to reach the goals. Maybe even more important are the way they deal with people who want to contribute. They listen, workout the underlying problems and then helping these people to reach their goals.

* '''Holger Freyther'''

: ''(Nominated by Stefan Schmidt)''

: Both Holger an Phil have an deep understanding on how OE and bitbake work and was designed to work. Both are thinking about ways to furtehr improve the current situation and contribute code and ideas to reach the goals. Maybe even more important are the way they deal with people who want to contribute. They listen, workout the underlying problems and then helping these people to reach their goals.

* '''Chris Larson'''

: ''(Nominated by Phil Blundell)''

* '''Mickey Lauer'''

: As one of the founders of the OE project I have lots of experience with all parts of the system, including the BitBake core, the build classes, and the recipes. In fact, I have contributed a major part of all that.

: I have left the former core team since this failed to provide any transparency to the growing OE community about how decisions were made.

: I have also used OE in commercial projects, hence I know about the different -- and sometimes contradicting -- requirements non-commercial and commercial projects have. I have always tried to improve OE in a way that suits as much stakeholders as possible, trying to prevent isolated solutions. As such, I'd love to serve on the TSC helping to facilitate further OE development.

* '''Richard Purdie'''

: I'm a long standing OE developer and member of the community who has extensive experience with the core elements of the system having successfully developed and handled many significant OE architectural improvements. My role as the lead developer and maintainer of bitbake gives me insight into the core workings of the project and as the architect of Poky, I also understand the needs of derived projects. As part of the former 'core team' I've also experience in mediation and in guiding the project. I'd like to use this experience for the benefit of the TSC.

: ''(Richard was also nominated by Stefan Schmidt.)''

* '''Khem Raj'''

: I would like to nominate myself. Over the last couple of years I have got good understanding of OE's internals and From my experience in past I understand needs of embedded systems and embedded Linux in particularly well. I think I understand the core pieces of OE well now which will help me make right decisions and suggestions in the TSC especially in the areas of toolchain and system libraries.

[[Category:Community]]

Oedem/2009

2010-01-09T08:19:46Z

Glenn: +cat

OpenEmbedded developers' meeting 2009 will be in Cambridge, UK on the weekend of November 7/8.

All developers and other interested parties are welcome.

==Location==

Reciva Ltd have generously offered to host the meeting at their offices: 509 Coldhams Lane, Cambridge, CB1 3JS.

The Reciva offices are on the east side of the city, about 2km from the centre of town. See below for detailed travel information.

Call Phil on +44 7973 869202 if you get hopelessly lost and cannot find the venue.

==Registration==

Due to restricted space at the venue, the number of attendees is strictly limited.

Pre-registration is now closed, although it is possible that more spaces may become available if previously-registered attendees drop out. Send mail to Phil if you wish to attend but missed the deadline for initial registration.

==Agenda==

===Friday 2009-11-06===

20:00 (approx) Pre-meeting beer session at the Red Lion, Histon, CB24 9BD

http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=cb24+9jd&sll=53.800651,-4.064941&sspn=11.25,27.905273&ie=UTF8&ll=52.253684,0.105486&spn=0.011375,0.027251&t=h&z=15&iwloc=A

From the city centre, ride the [http://www.stagecoachbus.com/timetables/Citi7Jan09%5B3%5D.pdf Citi 7] bus towards Cottenham. Pass Histon village green (pond with ducks) on your right, the Boot and Barley Mow pubs on your left, then alight at the next stop and you will be almost directly outside the Red Lion. Travel time from the city is approximately 25 minutes and a return ticket costs about £3. Other travel options include taxi (10-15 minutes, about £10 each way) or walking (50-60 minutes, no charge).

===Saturday 2009-11-07===

10:00-10:15 Welcome + Agenda

: Introductions and discussion/confirmation of agenda
: some entries will need to be moved as few of us will have to leave earlier on Sunday (Henning, Marcin and Marco have train at 17:10)

10:15-12:00 OE e.V. meeting (Mickey Lauer / e.V. board)

: '''e.V. Membership Fees'''

: As per our statutes, members can chose their membership fees. We should create recommendations for corporate entities (also indicate what they would gain by that).
: '''Travel reimbursement policy'''
: '''Financial status'''
: '''Sponsors: announcement, website and memberships'''
: '''Public relations committee'''

12:00-13:00 Establishment of technical steering committee (Phil Blundell)

13:00-14:00 Break for lunch / hacking session

14:00-15:00 OE and Poky (Mickey Lauer)

15:00-16:00 Software development for OE derived distributions

* Quick presentation of KOBE (Eclipse plugin by KOAN for recipe creation and more)

People always want to develop software for the target hardware, what can we do to make developers lives easier? The answer is not always use bitbake. How do we supply toolchains, libraries etc? How are people solving this today?

16:00-16:30 Learning to love USE flags, or, What's a distro for? (Phil Blundell)

16:30-17:00 State of the art in package management (Phil Blundell)

* Why is opkg so bad?
* What alternatives are there?
* What can we do to improve the situation?

17:00-18:00 Hacking session

18:00 Venue closes

===Sunday 2009-11-08===

10:00-11:00 Splitting the recipes tree (Mickey Lauer)

: Many of us feel we should split the recipes up into a couple of smaller categories to be able to handle them in a more efficient way (parsing, switching on/off, etc.), but also to indicate which packages are critical / very well maintained / not maintained at all / ...

11:00-12:00 Future plans for stable branch(es)

* Why stable branch is actually not so stable?
* Creation of long term support branch?

12:00-13:00 Bugtracker Discussion, what to do with the current bugzilla, replace/enhance/abandon. (Graeme 'XorA' Gregory)

13:00-14:00 Break for lunch/hacking

14:00-15:00 Hosting arrangements (Mickey Lauer) (see [[Infrastructure]])

: There are still services on amethyst, although former-admin Mickey has requested them to be moved. Obviously some one needs to take the wheel here.

: Services on Amethyst:

* patchwork.openembedded.org
* wiki.openembedded.org
* www.openembedded.org

: Git repository management issues:

* Clearly identify user branches with a namespace?
* Rename org.openembedded.dev to master?
* CIA commit hook should only report dev branch changes?

15:00-16:00 Death to checksums.ini? (Phil Blundell)

: The current method of tracking and verifying checksums on source tarballs has various drawbacks and, due to a combination of technical and social issues, seems to bring few benefits. Can we do any better?

16:00-17:00 BitBake Future Roadmap (Richard Purdie)

17:00-18:00 OE Core Changes (Richard Purdie)

: Discuss various possible core changes to OE such as those to the do_stage process, layout variable changes, Candian SDK Generation. Any others planned?

18:00 Go home

==Travel==

London Stansted airport is the nearest to Cambridge with regular service.
(There is a small airport in Cambridge itself but I don't think any scheduled
airlines operate from there anymore.)

For those travelling from Europe, Stansted is about a 30-minute train ride from Cambridge city centre and is served by Air Berlin, Ryanair and Germanwings among others. Luton airport is about 1 hour away by bus and is served by Easyjet.

For those travelling from further away, most long-haul flights arrive at Heathrow or Gatwick airports (although there is some transatlantic service into Stansted). Both Heathrow and Gatwick are about 2 hours from Cambridge by train or bus: the train is quicker but involves several changes in London, whereas the bus is slow but cheaper and less complicated.

If arriving at LHR airport, take the [http://thetube.com Piccadilly line] from the Underground station and ride it all the way to Kings Cross St Pancras. Ascend to street level, follow signs to Kings Cross mainline station (not St Pancras: the two stations are different although they share a subway stop) and then look for trains to Cambridge or Kings Lynn on the departure board. There are usually two fast services and two slow services to Cambridge per hour: the slow trains are often overtaken by the fast ones en route so it may be best to wait for a fast service even if this is not the next to depart.

If arriving at LCY, take the [http://www.tfl.gov.uk/gettingaround/2558.aspx#London_City_Airport DLR] to Bank, then change to the Northern Line northbound. From Kings Cross St Pancras, proceed as for LHR, above.

http://nationalrail.co.uk

http://nationalexpress.co.uk/

Alternatively you can take the Eurostar to London St Pancras, which is 50 minutes from Cambridge by train.

=== Directions from Cambridge rail station to Reciva HQ ===

'''By bus''' (approximate travel time 30 minutes)

- take Citi 1 bus towards Fulbourn, alight at St Andrews church in Cherry Hinton, then walk down Coldhams Lane for about 500 metres. Our building will be on your right and has a large sign on the front reading "Semitool". The Citi 1 route runs 7 days a week, about every ten minutes during the daytime, less often (but still fairly frequent) in the evenings.

- alternatively, take any bus to the city centre and then catch service 16 going out of town (the city centre is a terminus on this route). Alight at the first stop after the Rosemary Branch pub on Coldhams Lane and you will be directly outside the office. Note that bus #16 only runs once per hour so check departure times before choosing this route.

http://www.cambridgeshire.gov.uk/transport

http://www.stagecoachbus.com/cambridge

'''On foot''' (approximate travel time 45 minutes) or bike (approx 15 minutes)

- Turn right immediately in front of the station and cross the car park, passing the hotel and cycle shop on your left.

- Upon exiting the car park, go up the steps to the cycle/footbridge and cross to the other side of the railway line.

- Exit the bridge and turn left, then immediately right into Greville Road.

- At the end of Greville Road, go left on Coleridge Road. Cross at the pedestrian crossing and go through the chicane onto the footpath opposite.

- Proceed down Marmora Road. Cross Hobart Road and proceed down the footpath.

- Go left into Montreal Road, then right into Natal Road.

- Go left on Perne Road. At the lights, cross to the other side and go down Brookside.

- When the road bends to the right, do not follow the curve but instead take the footpath directly ahead (across a small bridge). Follow the path until you arrive at the Holiday Inn Express.

- Bear left onto Norman Way. Ascend out of the pit to the traffic lights next to the car dealership.

- Turn right onto Coldhams Lane, then cross to the other side of the street. Pass the yellow self-storage depot, then Reciva HQ is the next building on your left.

See [http://walkit.com walkit.com] for other route suggestions. The train station is at postcode CB1 2JB. The meeting venue is at CB1 3JS, although walkit (and most map sites, including google) place this about 500 metres too far southeast.

===Directions to venue by car===

'''From all points north and west'''

From the A1 or A10, take the A14 eastbound. Proceed along the Cambridge northern bypass. Leave at junction 35 (for Quy, Newmarket) and take the A1303 towards Cambridge, following signs towards the airport. Turn left at the next roundabout (by the corner of the airport) towards Cherry Hinton. At the next roundabout, go straight ahead into the traffic calmed area. Cross one mini-roundabout, then two in quick succession, then turn right at the traffic lights. Look for a building on your right labelled "SEMITOOL"; this is the meeting venue. If you reach the Rosemary Branch pub and Toyota dealership, you have gone too far.

==Accommodation==

The nearest full-service hotel is Holiday Inn Express, http://www.expresscambridge.co.uk/

Cheapest accomodation is probably the YHA hostel, http://www.yha.org.uk/find-accommodation/east-of-england/hostels/Cambridge/index.aspx

There are various bed-and-breakfast establishments nearby, prices start at approx £35/night

Some other hotels in Cambridge:

http://www.crowneplaza.co.uk/

http://www.devere.co.uk/our-locations/university-arms

http://www.hilton.co.uk/cambridgegardenhouse

http://www.arundelhousehotels.co.uk/

==Food and drink==

There are no catering facilities on site at the meeting venue. Coffee, tea and water are provided, but bringing your own snack/lunch is recommended. There are shops within about 15 minutes' walk where provisions can be purchased.

==Attending for sure==

* Philip Balister
* Michael Lauer
* Marco Cavallini
* Richard Purdie
* Marcin Juszkiewicz
* Henning Heinold
* Robert Schuster
* Florian Boor
* Denys Dmytriyenko
* Ken Gilmer
* Esben Haabendal
* Jonathan Cameron

[[Category:Community]]

NewsArchive

2010-01-09T08:19:20Z

Glenn: +cat

'''Older News:'''
* '''''2009-05-27:''''' MontaVista is using OpenEmbedded in their [http://mvista.com/product_detail_mvl6.php MontaVista Linux 6 product]
* '''''2009-03-31:''''' OpenEmbedded opens the stable/2009 [[Stable]] branch. Special procedure is applied to it which results in better support for our downstream users.
* '''''2009-03-24:''''' [http://www.foss-aalborg.dk/ FOSS Aalborg] in Aalborg, Denmark, with a focus on embedded software. [[User:Mickey|Mickey]] gives a talk about OpenEmbedded.
* '''''2009-03-06:''''' [http://www.alwaysinnovating.com Always Innovating] is using OE to build software for their Touch Book.
* '''''2009-02-19:''''' [http://koansoftware.com/index_en.php KOAN Software] company [http://thread.gmane.org/gmane.comp.handhelds.openembedded/21188 announces] it's [http://kaeilos.com/ KaeilOS] distribution will join the OpenEmbedded project.
* '''''2009-02-10:''''' OE has a new Logo -- Many thanks to [http://buglabs.com Bug Labs] who funded the logo development, and [http://mateozlatar.com/ Mateo Zlatar] for designing the logo.

[[Category:Community]]

MVL6

2010-01-09T08:18:40Z

Glenn: + Category:Categories

The [http://mvista.com/product_detail_mvl6.php MontaVista Linux 6] product includes an Integration Platform, which includes BitBake and facilitates delivery of OpenEmbedded based metadata collections, to be used by MontaVista customers in the creation of the Linux Distribution for their devices. This is rather different from the standard usage of OpenEmbedded, as MontaVista is shipping it, rather than just using it themselves.

[[Category:Categories]]

DNS Configuration

2010-01-09T08:18:29Z

Glenn: +cat

DNS

{|
|openembedded.org||A||85.214.40.226
|-
|bugs.openembedded.org||A||80.81.242.146
|-
|cgit.openembedded.org||A||140.211.169.165
|-
|docs.openembedded.org||A||80.81.242.146
|-
|git.openembedded.org||A||140.211.169.165
|-
|gitweb.openembedded.org||A||140.211.169.165
|-
|lists.openembedded.org||CNAME||openembedded.org
|-
|new.openembedded.org||A||80.81.242.146
|-
|patchwork.openembedded.org||A||80.81.242.146
|-
|tinderbox.openembedded.org||CNAME||tinderbox.openembedded.net
|-
|wiki.openembedded.org||A||80.81.242.146
|-
|www.openembedded.org||A||80.81.242.146
|}

[[Category:Community]]

Checklist for the General Assembly

2010-01-09T08:18:14Z

Glenn: +cat

== Checklist to organize the General Assembly ==

=== Preparing the General Assembly ===
# Pick date at least ~7 weeks from now
# Pick a venue for the conference
# Take the last invitation and change the date, location and the year of the assembly
# Change the proxy form to refer to the correct assembly. You will find the ODT in the [http://websvn.kde.org/trunk/www/sites/kde-ev/resources/proxy_instructions.odt?view=log KDE SVN]
# Create a WIKI page for the Agenda (TODO: Come up with a namespace)
# Send the Invitation, Proxyform and Agenda to the members list

=== Holding the General Assembly ===
# Start with the "Welcome"
# Make sure there are no valid objections to hold the assembly
# Make sure someone writes the protocol. It needs to include at least the following items:
## Beginning and end of the GA
## Attending members and proxies
## Agenda
## Decisions made by voting w/ vote stats

=== Paper work ===
# Turn the minutes into a proper protocol (whole sentences prefered)
# Send the protocol to the member list
# Send the protocol to the german authorities. The address is:
## TODO: Address / Club number for Amtsgericht

[[Category:Community]]

BitBake (user)

2010-01-09T08:17:28Z

Glenn: + Category:Categories

= Introduction =

BitBake is, at its simplest, a tool for executing tasks and managing metadata. As such, its similarities to GNU make and other build tools are readily apparent. It was inspired by Portage, the package management system used by the Gentoo Linux distribution.

BitBake is the basis of the OpenEmbedded project, which is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus and Familiar.

= Links =

* Homepage with manual: http://bitbake.berlios.de/
* Project page at Berlios: http://developer.berlios.de/projects/bitbake/
* <strike>Subversion repository: http://svn.berlios.de/svnroot/repos/bitbake/</strike>
* GIT repository: http://cgit.openembedded.org/cgit.cgi/bitbake/

= Version information =

OpenEmbedded require BitBake 1.8.10 or newer. Some features can require <strike>SVN</strike> GIT HEAD.

BitBake "trunk" contain experimental code - use at your own risk.

[[Category:Categories]]

Become Sponsor

2010-01-09T08:17:19Z

Glenn: + Category:Categories

Bbfile

2010-01-09T08:16:57Z

Glenn: + Category:Categories

A BitBake (.bb) file is a logical unit of tasks to be executed. Normally this is a package to be built. Inter-.bb dependencies are obeyed. The files themselves are located via the BBFILES variable, which is set to a space seperated list of .bb files, and does handle wildcards.

See [http://bitbake.berlios.de/manual/ http://bitbake.berlios.de/manual/]

[[Category:Categories]]

Category:User

2010-01-09T08:10:26Z

Glenn: + Category:Categories

You want to compile some package for your device? Maybe some of the pages here are interesting for you.

[[Category:Categories]]

Category:Software Components

2010-01-09T08:10:17Z

Glenn: + Category:Categories

Information about major software components in OE such as Java, Python, Qt, etc.

[[Category:Categories]]

Category:Machine

2010-01-09T08:10:08Z

Glenn: + Category:Categories

This page contains information about devices (machines) that are supported in OE.
* Machine Conf files are found in the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/conf/machine conf/machine directory] in the OE metadata.

[[Category:Categories]]

Category:Distro

2010-01-09T08:09:59Z

Glenn: + Category:Categories

Various distributions included in OE or based on OE.

[[Category:Categories]]

Category:Dev

2010-01-09T08:09:50Z

Glenn: + Category:Categories

Pages for OE developers with commit rights.

[[Category:Categories]]

Category:Community

2010-01-09T08:09:12Z

Glenn: + Category:Categories

Various Community resources

[[Category:Categories]]