LinaroComponents

Summary

Provide a simple website at components.linaro.org that monitors a list of projects and displays links to the latest releases of components, their source (bzr/git), and PPAs, and possibly things such as dependencies. It could also provide RSS feeds. It should be easy to add new projects to track, be simple to maintain, and look good.

A conceptual demonstration may be found at: https://gomockingbird.com/mockingbird/#vg1qdjy/mBiAW (the buttons "work")

This should aim to minimise sub-domains.

Stakeholders

  • Kiko
  • WG leads

Contact

  • James Westby

Deadline

  • ASAP

Estimated Work

  • 3 weeks

Rationale



Requirements

Requirements, and non-requirements (not in scope)

Design

What we will do to meet the requirements and satisfy the user stories

Implementation

How we will implement the design (can be deferred until the work is committed to)

Code changes

What code we need to change and where (can be omitted if the Implementation section suffices)

Delivery and Test plan

How the finished project will be delivered, and how testing will be organised (including acceptance testing)

Questions

If you have any questions you can note them here.




Hi,

Kiko proposed components at the Rally, and I think that one thing we
could do to help this effort is provide a single place to find all of
the latest versions of components.

That will of course be the wiki to start with, but I think a fairly
simple "components.linaro.org" would present this well and be less work
to maintain.

Stakeholders: Kiko, WG leads
Deadlines: ASAP
Estimated work: 3 weeks
Contact: James Westby
Summary: Provide a simple website at components.linaro.org that monitors
a list of projects and displays links to the latest releases of
components, their source (bzr/git), and PPAs, and possibly things such
as dependencies. It could also provide RSS feeds. It should be easy to
add new projects to track, be simple to maintain, and look good.

Anyone else like the idea?

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Mon, Jan 24, 2011, James Westby wrote:
> > Kiko proposed components at the Rally, and I think that one thing we
> > could do to help this effort is provide a single place to find all of
> > the latest versions of components.
> > 
> > That will of course be the wiki to start with, but I think a fairly
> > simple "components.linaro.org" would present this well and be less work
> > to maintain.
 Hmm why not under releases.linaro.org/$component (e.g. gdb-linaro,
 gcc-linaro, linux-linaro), or under
 releases.linaro.org/components/$component ?

-- Loïc Minier _______________________________________________ Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders Post to : linaro-infrastructure-stakeholders@lists.launchpad.net Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders More help : https://help.launchpad.net/ListHelp 


On Tue, 25 Jan 2011 02:35:02 +0100, Loïc Minier <loic.minier@linaro.org> wrote:
> > On Mon, Jan 24, 2011, James Westby wrote:
>> > > Kiko proposed components at the Rally, and I think that one thing we
>> > > could do to help this effort is provide a single place to find all of
>> > > the latest versions of components.
>> > > 
>> > > That will of course be the wiki to start with, but I think a fairly
>> > > simple "components.linaro.org" would present this well and be less work
>> > > to maintain.
> > 
> >  Hmm why not under releases.linaro.org/$component (e.g. gdb-linaro,
> >  gcc-linaro, linux-linaro), or under
> >  releases.linaro.org/components/$component ?
No real reason. It's just a catchier way to talk about the project.

Extending it to cover platform releases would be another option, aside
from the URLs.

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Mon, 2011-01-24 at 19:47 -0500, James Westby wrote:
> > Hi,
> > 
> > Kiko proposed components at the Rally, and I think that one thing we
> > could do to help this effort is provide a single place to find all of
> > the latest versions of components.
> > 
> > That will of course be the wiki to start with, but I think a fairly
> > simple "components.linaro.org" would present this well and be less work
> > to maintain.
> > 
> > Stakeholders: Kiko, WG leads
> > Deadlines: ASAP
> > Estimated work: 3 weeks
> > Contact: James Westby
> > Summary: Provide a simple website at components.linaro.org that monitors
> > a list of projects and displays links to the latest releases of
> > components, their source (bzr/git), and PPAs, and possibly things such
> > as dependencies. It could also provide RSS feeds. It should be easy to
> > add new projects to track, be simple to maintain, and look good.
> > 
> > Anyone else like the idea?
I do.  Makes it easy to find things.

Scott
-- Scott Bambrough Technical Director, Landing Teams _______________________________________________ Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders Post to : linaro-infrastructure-stakeholders@lists.launchpad.net Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders More help : https://help.launchpad.net/ListHelp 


On 25 January 2011 00:47, James Westby <james.westby@linaro.org> wrote:
> > That will of course be the wiki to start with, but I think a fairly
> > simple "components.linaro.org" would present this well and be less work
> > to maintain.
...

> > Anyone else like the idea?
> >
> > Thanks,
> >
> > James
I do we worry that we are getting 'url-creep'. The list of sub-domains
are growing
and I'm not sure we have a comprehensive list anywhere. I would prefer to use
the existing structure at snapshots.linaro.org for any daily releases the team
want to make or releases.linaro.org for any milestone releases.

Regards,
Jamie.

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


Hi guys.

I second the URL creep concern. I would also hate to see this develop into a dead list that is never used by anyone on the team. I have a different solution.

Setup redmine to show our projects (configured only as source code viewer and download zone).

Doing this takes one day and gives you a lot of features for free should we choose to use them (project management, forums, tasks, bugs, schedule, and so on). The point is to consolidate rather than fragment our online resources. This will make it more attractive to both us and outside people. This will keep the site alive


Thanks
ZK
_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Tue, Jan 25, 2011, Jamie Bennett wrote:
> > I do we worry that we are getting 'url-creep'. The list of sub-domains
> > are growing
> > and I'm not sure we have a comprehensive list anywhere. I would prefer to use
> > the existing structure at snapshots.linaro.org for any daily releases the team
> > want to make or releases.linaro.org for any milestone releases.
 +1, it was exactly what I was getting to with my question on using
 releases.linaro.org

 Also, it would mean we'd have something along /platform on
 releases.linaro.org as this folder is sitting a bit lonely there!
 Think of the poor folder!

-- Loïc Minier _______________________________________________ Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders Post to : linaro-infrastructure-stakeholders@lists.launchpad.net Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders More help : https://help.launchpad.net/ListHelp 


On Tue, 25 Jan 2011 09:21:21 +0100, Zygmunt Bazyli Krynicki <zygmunt.krynicki@linaro.org> wrote:
> > Setup redmine to show our projects (configured only as source code viewer and download zone).
> > 
> > Doing this takes one day and gives you a lot of features for free
> > should we choose to use them (project management, forums, tasks, bugs,
> > schedule, and so on). The point is to consolidate rather than fragment
> > our online resources. This will make it more attractive to both us and
> > outside people. This will keep the site alive
Can redmine be set up to mirror all the information from Launchpad?

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


W dniu 25.01.2011 14:49, James Westby pisze:
> On Tue, 25 Jan 2011 09:21:21 +0100, Zygmunt Bazyli Krynicki<zygmunt.krynicki@linaro.org>  wrote:
>> Setup redmine to show our projects (configured only as source code viewer and download zone).
>>
>> Doing this takes one day and gives you a lot of features for free
>> should we choose to use them (project management, forums, tasks, bugs,
>> schedule, and so on). The point is to consolidate rather than fragment
>> our online resources. This will make it more attractive to both us and
>> outside people. This will keep the site alive
>
> Can redmine be set up to mirror all the information from Launchpad?

Probably not out of the box. It only supports looking at lp: repositories for up-to-date code on demand.

What information would you like to mirror?

Redmine has a REST interface for all the "metadata" about things. I could write a small script that mirrors bugs/project descriptions" and other interesting aspects from lp.net and we can simply run it daily/hourly.

For the record. I've setup a test instance at home, I plan to expose it after adding all the projects that I think we are doing. I'm currently somewhat stuck after adding gcc because looking at gcc history over lp: takes ages (it will sync the history and then the process is okay as incremental changes are fast).

Thanks
ZK

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Tue, 25 Jan 2011 15:09:03 +0100, Zygmunt Krynicki <zygmunt.krynicki@linaro.org> wrote:
> > W dniu 25.01.2011 14:49, James Westby pisze:
>> > > On Tue, 25 Jan 2011 09:21:21 +0100, Zygmunt Bazyli Krynicki<zygmunt.krynicki@linaro.org>  wrote:
>>> > >> Setup redmine to show our projects (configured only as source code viewer and download zone).
>>> > >>
>>> > >> Doing this takes one day and gives you a lot of features for free
>>> > >> should we choose to use them (project management, forums, tasks, bugs,
>>> > >> schedule, and so on). The point is to consolidate rather than fragment
>>> > >> our online resources. This will make it more attractive to both us and
>>> > >> outside people. This will keep the site alive
>> > >
>> > > Can redmine be set up to mirror all the information from Launchpad?
> > 
> > Probably not out of the box. It only supports looking at lp: 
> > repositories for up-to-date code on demand.
> > 
> > What information would you like to mirror?
Description, releases, announcements for a start I think.

> > Redmine has a REST interface for all the "metadata" about things. I 
> > could write a small script that mirrors bugs/project descriptions" and 
> > other interesting aspects from lp.net and we can simply run it daily/hourly.
> > 
> > For the record. I've setup a test instance at home, I plan to expose it 
> > after adding all the projects that I think we are doing. I'm currently 
> > somewhat stuck after adding gcc because looking at gcc history over lp: 
> > takes ages (it will sync the history and then the process is okay as 
> > incremental changes are fast).
I look forward to seeing it.

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


W dniu 25.01.2011 16:26, James Westby pisze:

>> What information would you like to mirror?
>
> Description, releases, announcements for a start I think.

Could you please show me some snippets that access this information using launchpadlib?

> I look forward to seeing it.

I'll send an update once this is ready and can be accessed. I setup a dumb port forwarding from suxx.pl:3000 to a server in my LAN. I have started an instance of release 1.1 (configured from a release tarball as there is no up-to-date .deb yet, debian has 1.0.4 or something).

I did not configure hosting properly (I simply launched the developer mode that spawns a single threadded server).

Thanks
ZK

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Tue, 25 Jan 2011 17:33:29 +0100, Zygmunt Krynicki <zygmunt.krynicki@linaro.org> wrote:
> > Would you like to actually fetch and reupload the release to redmine or 
> > simply link there?
Just link there.
>> > > I can't see that announcements are currently exported.
> > 
> > How difficult would it be to implement that on lp.net?
Not difficult I expect.

Please don't spend too much time on this, it's just a proposal at this
stage, and we're not even sure that we would want to commit to
maintaining it even if you provide a working service.

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Mon, 24 Jan 2011 19:47:11 -0500, James Westby <james.westby@linaro.org> wrote:
> > Hi,
> > 
> > Kiko proposed components at the Rally, and I think that one thing we
> > could do to help this effort is provide a single place to find all of
> > the latest versions of components.
Talking to Zygmunt it became clear to me that I didn't do a good enough
job of explaining the intent of this idea.

Kiko presented this idea as a response to the perception that Linaro
only releases every six months. Monthly component releases and Linaro
broadcasts will help with this to some extent.

However, I think that we could go further (nothing prevents us including
evaluation builds here too). We could present a landing page for finding
the projects that Linaro is producing, and getting hold of the latest
of any of them.

I think that to be really successful this should

1. Look good, to keep up with the rest of the free software world and
contribute to a feeling of quality around Linaro: apache directory
listing fails here
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)

I have done a sketch of my thoughts at

  https://gomockingbird.com/mockingbird/#vg1qdjy/mBiAW
  (the buttons "work")

which might help illusrate the idea.

It would be a fairly thin wrapper around launchpad which would host all
the information (at least for components, so that we can easily get
download counts etc.) It could actually be implemented mostly in
Launchpad, but there are some limitations that we would have to fix
first.

I am mainly focused on presentation here, as the problem as explained to
me was mainly a perception one (and where it isn't there are already
efforts underway to correct it), so presentation is very important to
fixing it.

Thanks,

James


_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


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

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Tue, Jan 25, 2011, James Westby wrote:
> > Talking to Zygmunt it became clear to me that I didn't do a good enough
> > job of explaining the intent of this idea.
 I did realize earlier today that you were not thinking of /delivering/
 the releases in terms of having a central place where people can
 technically find them, but that this was all about /marketing/ what
 Linaro is doing, notably monthly releases.

 In this light, please scrap my suggestions about re-using
 releases.linaro.org (well technically we could still re-use it or use
 it more, but that's irrelevant).

 I checked your mockup, and basically I wondered whether the site should
 be structured around the fact that people will interested in a specific
 piece of software, or whether they are interested in the latest stuff.
 Basically, we could either list "These things were recently released:"
 or we could have "Get latest toolchain release", "Get latest kernel
 release" etc.


 In any case, I very much like the idea of a shiny scene for Linaro's
 outputs


 It's tempting to re-visit the problem of URL proliferation and wonder
 whether this should be part of "status.linaro.org", with one angle
 being blueprint progress, another angle being software releases etc.


 But this does feel a bit like creating a modern Linaro website, and
 something in the back of my mind tells me this could easily become a
 really large project!

-- Loïc Minier _______________________________________________ Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders Post to : linaro-infrastructure-stakeholders@lists.launchpad.net Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders More help : https://help.launchpad.net/ListHelp 


On Tue, 25 Jan 2011 23:55:43 +0100, Zygmunt Krynicki <zygmunt.krynicki@linaro.org> wrote:
> > If our primary users are third party developers I would encourage to 
> > include some reference to source code trees.
Indeed, we should include that too.

> > 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.
We could possibly contract the company that did the website, or look
elsewhere. I think it would be useful, but I can't say it will be
possible at this stage.

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp


On Tue, 25 Jan 2011 23:58:05 +0100, Loïc Minier <loic.minier@linaro.org> wrote:
> >  I did realize earlier today that you were not thinking of /delivering/
> >  the releases in terms of having a central place where people can
> >  technically find them, but that this was all about /marketing/ what
> >  Linaro is doing, notably monthly releases.
Indeed.

> >  In this light, please scrap my suggestions about re-using
> >  releases.linaro.org (well technically we could still re-use it or use
> >  it more, but that's irrelevant).
In my mockups I assumed that it would be releases.linaro.org and
included evaluation builds there. I don't have a strong preference at
this stage.

> >  I checked your mockup, and basically I wondered whether the site should
> >  be structured around the fact that people will interested in a specific
> >  piece of software, or whether they are interested in the latest stuff.
> >  Basically, we could either list "These things were recently released:"
> >  or we could have "Get latest toolchain release", "Get latest kernel
> >  release" etc.
I think they could be two useful views. I think people would keep coming
back for the latest toolchain, but casual browsers could be attracted by
seeing something interesting we just released.

> >  It's tempting to re-visit the problem of URL proliferation and wonder
> >  whether this should be part of "status.linaro.org", with one angle
> >  being blueprint progress, another angle being software releases etc.
I'm not sure about that. My understanding is that status.linaro.org is
more targeted to people interested in the operation of Linaro. The
hand-wavy plan is indeed to have several different sources of
information there, workitems, bug and patch metrics, etc., and including
releases there could be a good idea.

I'm not sure that third-party developers are going to be particularly
interested in the workitems progress, they just want the shiny code.

Not to say that we have to reimplement everything, but I'm not sure
directing third-party developers to status.linaro.org is the right thing
to do.

> >  But this does feel a bit like creating a modern Linaro website, and
> >  something in the back of my mind tells me this could easily become a
> >  really large project!
Indeed. I think we can work incrementally, but this proposal is partly
due to not having a world-beating website.

Thanks,

James

_______________________________________________
Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
Post to     : linaro-infrastructure-stakeholders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
More help   : https://help.launchpad.net/ListHelp

internal/archive/Platform/Infrastructure/Specs/LinaroComponents (last modified 2013-08-23 02:14:47)