From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: Re: FSL Community BSP Meeting - 09/08/2014 - 13:00 UTC
Date: Sat, 30 Aug 2014 16:32:26 +0200 [thread overview]
Message-ID: <5401E07A.7080102@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKpPeswzTa0KSmqFOqcPtgnOZT-JRRmxzi5SZo0Su6Ce_w@mail.gmail.com>
This is perhaps a good opportunity to improve the contact to other OS
developers, especially the developers of the CuBox-i 3.14 kernel the
etnaviv people. I would also be interested to participate. What do you
think?
On 08/30/2014 03:44 PM, Otavio Salvador wrote:
> Hello everyone,
>
> We ended not doing the meeting last month; it is important we don't
> lose the pace and I'd like to propose we do this one in:
>
> Date: September 8th
> Time: 13:00 UTC
>
> The proposed FSL Community BSP Meeting Agenda is:
>
> Status
> * Short testing status from maintainers/testers
> * Upcoming board
> * Upstream
>
> Status of actions of last meeting
> * Mario is going to review the user guide and FAQ to help checking
> spelling and more
> * Otavio, Daiane and Eric are going to help with Bugzilla entries
> * Eric, are going to draft of a "Statement of Purpose"
> * Documentation
> * What is FSL Community BSP
> * Motivation
> * What the FSL Community BSP is not
> * What to expect (production X basic feature)
>
> meta-fsl-ppc
> * Release Notes
> * Technical implications
>
> Document
> * Release Notes: Use cases (what is missing?)
> * User guide: help
> * How to use/why DirectFB/Wayland/FB/X11 on i.MX6?
> * Documentation
> * (1.7) License = CC - share-alike, attribution
> * What is FSL Community BSP
> * Motivation
> * What the FSL Community BSP is not
> * What to expect (production X basic feature)
> * (1.7) UG
> * Sanity Test (double check step-by-step)
> * Start automatization
> * Include “Yocto Training Tasks”
> * Document PACKAGEGROUP and IMAGES
> * Document BSP variables
> * RN
> * Update versions (1.6 and 1.7)
> * (1.8) FAQ: pending issues to make it public
> * (1.8) FAQ: process of adding new question
>
> Topics raised in last meeting
> * How to get more people involved in future
> * Get sub-maintainers for specific areas
> * Define the sub areas
> * How to get it promoted
>
> I have sent the invite to the people who has participate in the previous[1].
>
> 1. https://plus.google.com/events/c8lu6lls7jq06npl6gbifmlagi4
>
> In case you didn't receive the invite send me your e-mail address so I
> include it.
>
> Best Regards,
>
next prev parent reply other threads:[~2014-08-30 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 13:44 FSL Community BSP Meeting - 09/08/2014 - 13:00 UTC Otavio Salvador
2014-08-30 14:14 ` Bob Cochran
2014-08-31 19:21 ` Otavio Salvador
2014-09-01 14:17 ` Daiane Angolini
2014-08-30 14:32 ` Carlos Rafael Giani [this message]
2014-08-31 19:18 ` Otavio Salvador
2014-09-03 8:47 ` Carlos Rafael Giani
2014-09-08 14:17 ` Bob Cochran
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=5401E07A.7080102@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.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.