linaro-infrastructure-stakeholders team mailing list archive

[Zygmunt Krynicki <zygmunt.krynicki@xxxxxxxxxx>]

W dniu 25.01.2011 23:29, James Westby pisze:

> I think that to be really successful this should

> 2. Give a sense of activity across all the projects, to contribute to
> the feeling that Linaro produces lots of good stuff: a wiki page linking
> to the Launchpad project pages for each component fails here.

> 3. Provide a way for people to find out about new things (the broadcasts
> may provide this)

If our primary users are third party developers I would encourage to 
include some reference to source code trees. I realize that Linaro is 
still struggling with our presentation layer (wiki, website, etc) so 
this might seem redundant but it would help to answer questions like

1) "Where is the "linaro" source code?" a.k.a. "I just heard about those 
guys, I want to check what they are doing and the homepage didn't give 
me anything after 30 seconds of looking"

2) "What kind of activity happens in each tree?" I'm not sure what the 
solution is.

3) "There are many trees for $FOO, which one is for me?" This probably 
needs more research too

4) "I need $BAR which and I cannot find it on your page, where is it?" I 
can imagine that some developers will come looking for things which we 
do not provide (integrated android kernel tree, binary drivers for some 
board, that kind of stuff). We should be able to answer this if possible.

James, is there any way we can request some designer help once the 
requirements are set? This is really a PR/first-impression kind of 
thing, even for developers.

Thanks
ZK