Website Text

Website Text

[Jack Mitchell]

Good Morning All,

First off, I hope a lot of you are having fun at OEDAM, I wish I could 
have been there but while my company will pay for entrance and ticket 
fees, they won't pay for the expensive part, travel and hotels.

I have seen on the OEDAM wiki page that the wiki/website is on the 
agenda so I thought it would be a good time to send out an update on my 
involvement. It's been a slow 6 months since I volunteered to help out 
with the project and while a lot has gotten done, it's not quite as much 
as I hoped. However, that aside I think now would be a good time to try 
and get some collaboration on the website text while you're all in a 
room together.

The current website address is http://frontpage.openembedded.org/

All the text probably needs some work, most of it is copied from the 
current OE site with some slight tweaks but I was concentrating on 
design at the time. So, I will list all sub categories of text below 
along with my concerns and anybody else can chime in with their thoughts 
and views. If you want to re-write a portion for review as it's 
completely wrong, please do, I'm not going to be offended.

* Header Text

	- Can we still claim to be best-in-class as a cross compilation 
environment? It seems a touch... arrogant IMO, thoughts?

* Support/Advantages/Available Recipes

	- General input; can you think of any better subheadings or things we 
should be advertising?

* OpenEmbedded and The Yocto Project

	- This needs a complete re-write, what I am envisioning here is a quick 
explanation of how OE and YP are related to clear up initial confusion 
about OE being superseded etc...

* Recent News

	- There is talk about integrating an auto updating feed here with git 
commits/new recipes from the layer index. This will come last when me 
and Paul have had chance to discuss what changes need to be made to the 
Layer Index to make this possible.

When these points are hashed out, then I will create the 
Community/FAQ/Download and Documentation pages and we can discuss these 
on list again.

Slightly off topic, I am having trouble with pushing to the oe-website 
git repo, if anyone at the meeting can help with this then please drop 
me an email. Philip, you were CC'ed in on the problem that I sent to 
ka6sox with the error if someone wants to know the details.

I will try and be about on IRC today if anyone needs me, I'll be in and 
out of the house and the timezone differences will obviously cause some 
issue, but just ping me if you want to know anything.

Cheers all,
Jack.
-- 
_______________________________________________
Openembedded-members mailing list
Openembedded-members@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-members

Re: Website Text

[Samuel Stirtzel]

2014-05-03 11:15 GMT+02:00 Jack Mitchell <martin.jansa@gmail.com>:

> * Support/Advantages/Available Recipes
>
>         - General input; can you think of any better subheadings or things
> we should be advertising?

Hi,

KDE desktop is not really "supported", it is at a stale tech preview stage.
Since my priorities have been shifted, there is no time to look into a
KDE Frameworks 5 port.
(Patches are welcome, but it may be easier to just fork the layer).


-- 
Regards
Samuel

Re: Website Text

[Jack Mitchell]

On 05/05/14 09:46, Samuel Stirtzel wrote:
> 2014-05-03 11:15 GMT+02:00 Jack Mitchell <martin.jansa@gmail.com>:
> 
>> * Support/Advantages/Available Recipes
>>
>>         - General input; can you think of any better subheadings or things
>> we should be advertising?
> 
> Hi,
> 
> KDE desktop is not really "supported", it is at a stale tech preview stage.
> Since my priorities have been shifted, there is no time to look into a
> KDE Frameworks 5 port.
> (Patches are welcome, but it may be easier to just fork the layer).
> 
> 

Do we have any version of KDE working at this moment in time?

-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 

Re: Website Text

[Khem Raj]

On Tue, May 6, 2014 at 8:52 AM, Jack Mitchell <ml@communistcode.co.uk> wrote:
> Do we have any version of KDE working at this moment in time?

with master its probably stale but with 1.5 it worked.

Re: Website Text

[Trevor Woerner]

On 3 May 2014 05:15, Jack Mitchell wrote:
> The current website address is http://frontpage.openembedded.org/

My feeling is that there is a chance people will be coming to the OE
website with a board already in front of them, looking to find out if
OE supports it and how they might go about creating an image for
what's on their desk.

As such I think a set of links to various OE project website might be
useful, organized by board:

freescale: http://freescale.github.io/
gumstix: https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md
beaglebone: http://www.angstrom-distribution.org/ (?)
various intel boards: ??

Re: Website Text

[Jack Mitchell]

On 06/05/14 16:47, Trevor Woerner wrote:
> On 3 May 2014 05:15, Jack Mitchell wrote:
>> The current website address is http://frontpage.openembedded.org/
> 
> My feeling is that there is a chance people will be coming to the OE
> website with a board already in front of them, looking to find out if
> OE supports it and how they might go about creating an image for
> what's on their desk.
> 
> As such I think a set of links to various OE project website might be
> useful, organized by board:
> 
> freescale: http://freescale.github.io/
> gumstix: https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md
> beaglebone: http://www.angstrom-distribution.org/ (?)
> various intel boards: ??
> 

This would probably be best implemented as a link to Wiki page from the
'Documentation' header. The list of boards is always in a state of flux
so should be able to edited by anyone in the know.

With a new front page taking the place of the wiki front page, there
will also be a lot more scope for interesting links on the wiki
frontpage to interesting content, it would make a good candidate to go
there too IMO.

-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 

Re: Website Text

[akuster@mvista]

On 5/6/14, 8:47 AM, Trevor Woerner wrote:
> On 3 May 2014 05:15, Jack Mitchell wrote:
>> The current website address is http://frontpage.openembedded.org/
>
> My feeling is that there is a chance people will be coming to the OE
> website with a board already in front of them, looking to find out if
> OE supports it and how they might go about creating an image for
> what's on their desk.

Or maybe I have this processor, is there support for this already and 
which BSP are available.

- Armin

Re: Website Text

[Paul Eggleton]

On Tuesday 06 May 2014 11:47:00 Trevor Woerner wrote:
> On 3 May 2014 05:15, Jack Mitchell wrote:
> > The current website address is http://frontpage.openembedded.org/
> 
> My feeling is that there is a chance people will be coming to the OE
> website with a board already in front of them, looking to find out if
> OE supports it and how they might go about creating an image for
> what's on their desk.
> 
> As such I think a set of links to various OE project website might be
> useful, organized by board:
> 
> freescale: http://freescale.github.io/
> gumstix:
> https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md
> beaglebone: http://www.angstrom-distribution.org/ (?)
> various intel boards: ??

So I'd hope that the machine listing in the layer index could be made to help 
with that. It is fairly primitive at the moment (mainly because there's not 
much in the way of meta-information to record against each machine, at least 
not that we can extract from the metadata itself) but we can look at ways to 
extend it if it would help.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Website Text

[Trevor Woerner]

On 05/06/14 12:12, Paul Eggleton wrote:
> So I'd hope that the machine listing in the layer index could be made
> to help with that.

Absolutely, for raw recipe information or information on which MACHINEs
are supported the layer index would be a good choice.

But there's a fair amount of difference between "MACHINE, layer, and
recipe definitions" versus "here's the FSL community information, they
use repo, here's where they keep their manifests, here are the manifests
they have available, these are the boards they support, and here is how
you run their setup script".

Unless you're suggesting the layer index could also inform users of
manifests and setup script conventions?

Re: Website Text

[Paul Eggleton]

On Tuesday 06 May 2014 23:35:09 Trevor Woerner wrote:
> On 05/06/14 12:12, Paul Eggleton wrote:
> > So I'd hope that the machine listing in the layer index could be made
> > to help with that.
> 
> Absolutely, for raw recipe information or information on which MACHINEs
> are supported the layer index would be a good choice.
> 
> But there's a fair amount of difference between "MACHINE, layer, and
> recipe definitions" versus "here's the FSL community information, they
> use repo, here's where they keep their manifests, here are the manifests
> they have available, these are the boards they support, and here is how
> you run their setup script".

Excuse my ignorance, but what do you mean by "manifests"?

> Unless you're suggesting the layer index could also inform users of
> manifests and setup script conventions?

On a per layer basis that is the intention of providing the "Setup 
information" URL field - it's a link to further information about how to use 
the layer. For example, OE-Core has one:

http://layers.openembedded.org/layerindex/layer/openembedded-core/

This can be either an external URL or a pointer to a file within the repository 
(if it doesn't have the http:// prefix).

That might not be fine-grained enough to handle what we're talking about but it 
is something along the right lines I think.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Website Text

[Christopher Larson]

On Wed, May 7, 2014 at 1:49 AM, Paul Eggleton <paul.eggleton@linux.intel.com
> wrote:

> On Tuesday 06 May 2014 23:35:09 Trevor Woerner wrote:
> > On 05/06/14 12:12, Paul Eggleton wrote:
> > > So I'd hope that the machine listing in the layer index could be made
> > > to help with that.
> >
> > Absolutely, for raw recipe information or information on which MACHINEs
> > are supported the layer index would be a good choice.
> >
> > But there's a fair amount of difference between "MACHINE, layer, and
> > recipe definitions" versus "here's the FSL community information, they
> > use repo, here's where they keep their manifests, here are the manifests
> > they have available, these are the boards they support, and here is how
> > you run their setup script".
>
> Excuse my ignorance, but what do you mean by "manifests"?


A repo manifest is rather like a .gitmodules file, but out of band, in its
own repository. The manifest controls what repositories of what
branches/revisions get pulled down. A git url to the manifest is passed to
'repo init' to initialize the setup.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics