All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [Documentation] FSL Community BSP - Task List
Date: Tue, 09 Sep 2014 12:58:22 +0000	[thread overview]
Message-ID: <87mwa9t0gh.fsf@parenteses.org> (raw)
In-Reply-To: <CA+jg_OXkZDefZ2jP-2C=qnjSzfYtQKwDgBLNSwz2+6ibH1F=hg@mail.gmail.com> (Daiane Angolini's message of "Tue, 9 Sep 2014 09:50:46 -0300")

Hi Daiane,

On Tue, 9 Sep 2014 09:50:46 -0300 Daiane Angolini <daiane.list@gmail.com> wrote:

> On Mon, Sep 8, 2014 at 4:26 PM, Stephano Cetola <stephanoc@gmail.com> wrote:
>> I would like to help with documentation. Is there a place where we are
>> currently tracking tasks?
>
> I´m going to add the list in [1]. I plan to finish it today.
>
> I my point of view, the very first last list would be, with target release:
> (more or less in a priority order)
>
> Documentation
>  * RN
>    * (1.7) License = CC - share-alike, attribution
>    * (1.7) Describe the families (today imx and vybrid)
>    * (1.7) What is FSL Community BSP
>       * Motivation
>           * What the FSL Community BSP is not
>           * What to expect (production X basic feature)
>           * Update versions (1.6 and 1.7)
>       * Document PACKAGEGROUP and IMAGES
>       * Document BSP variables
>    * UG
>       * (1.7) Sanity Test (double check step-by-step)
>       * (1.7) Start automatization
>       * (1.8) Include “Yocto Training Tasks”
>       * (1.7/1.8) How to use/why DirectFB/Wayland/FB/X11 on i.MX6?
>  * (1.8) FAQ: pending issues to make it public
>  * (1.8) FAQ: process of adding new question
>
>
> Meanwhile, I plan to start with some scratch for the addition of
> meta-fsl-ppc. As I haven´t already started, I still don´t have the
> task list for this.
>
> Mario, would you mind to work with task "Document PACKAGEGROUP and
> IMAGES" using the same approach you used to create the version update
> automatic scripts? We can talk offline to me to explain what I really
> mean here if needed.

Sure.  I'll try to extend the current script to extract that information
out of packagegroup and image recipes.

> Daiane
> [1] https://github.com/Freescale/Documentation/issues

Best wishes.
Mario
-- 
http://www.ossystems.com.br


  reply	other threads:[~2014-09-09 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 19:26 [Documentation] FSL Community BSP - Task List Stephano Cetola
2014-09-09 12:50 ` Daiane Angolini
2014-09-09 12:58   ` Mario Domenech Goulart [this message]
2014-09-09 18:21   ` Daiane Angolini

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=87mwa9t0gh.fsf@parenteses.org \
    --to=mario@ossystems.com.br \
    --cc=daiane.list@gmail.com \
    --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.