After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 485125 - Use the new GNOME website layout for build.g.o
Use the new GNOME website layout for build.g.o
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: build.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: GNOME Web maintainers
GNOME Web maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-09 17:15 UTC by Vincent Untz
Modified: 2008-06-27 12:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2007-10-09 17:15:02 UTC
+++ This bug was initially created as a clone of Bug #485120 +++

It'd be great to move build.g.o to use the new website layout. library.gnome.org is a good example :-)
Comment 1 Iago Toral 2007-10-18 16:54:33 UTC
Sure, actually the current web is quite awful and lacks any kind of layout. Since the day we published it I always had a "gnomish design" ToDo task, but was delayed because there were other tasks with higher priority and, I have to admit it, I have a rather bad taste for this kind of design stuff :). So, if anyone wants to help with this, it'd be more than welcome! Otherwise, we'll get to it at some moment in the future for sure.
Comment 2 Jaap A. Haitsma 2007-12-02 13:31:18 UTC
Is the code that's running on build.gnome.org somewhere in SVN?

Comment 3 Alejandro Piñeiro Iglesias (IRC: infapi00) 2007-12-03 15:07:32 UTC
The code is at this moment on a CVS. Move it to SVN is a item on the b.g.o TODO list.

If you want to get this code, there are a guide that explains how get and install this code:
http://live.gnome.org/BuildBrigade/DocsAndGuides/GnomeBuildbotInstallation

Comment 4 Jaap A. Haitsma 2007-12-03 22:09:41 UTC
(In reply to comment #3)
> The code is at this moment on a CVS. Move it to SVN is a item on the b.g.o TODO
> list.

I'd encourage you to do that as soon as possible, because in that way it will be easier for people to contribute

Comment 5 Iago Toral 2007-12-11 07:38:42 UTC
Olav, Frederic, we've been talking for a while about this in the past.
How can we plan to do it? I can provide the source code (which is actually available via public CVS) and any necessary stuff that's required for this to be done.
Comment 6 Frederic Peters 2008-05-08 11:07:12 UTC
As I missed API on IRC; I'll answer here...

<API> hi  fredp, I have a question about the bug 485125
<API> this is about the website layout on build gnome org
<API> the bug said that this page should use the "new layout" like library.gnome.org
<API> I supposed that somewhere will be a page guide about that (similar to the HIG) but I didn't found anything you solved that bug for damned lies you simply start to redesign the page taking the files from library gnome org?

Library started off copying/adapting what was on the beta plone www.gnome.org, other sites followed, copying/adapting what I did on library.  I guess the plan is all the same for build.gnome.org, as there is no guideline document about GNOME websites.
Comment 7 Frederic Peters 2008-05-08 11:46:32 UTC
I did a quick mockup for the homepage, using CSS straight off library, and adding some customisation inline, available on [1].

A goal I had was to free horizontal space, so it is possible for new buildbots to join without getting the layout all messed up.  This meant:

 - removal of meta packages as they are not really useful and have very long names
 - keep only one feed, and use smaller and "official" feed icon

I also had to cleanup HTML, adding more meaningful elements, removing meaningless classes and attributes, and so on; major changes: dividing table in <thead> and <tbody> and marking header cells with <th>.

[1] http://www.0d.be/tmp/build.gnome.org/
Comment 8 Alejandro Piñeiro Iglesias (IRC: infapi00) 2008-05-08 13:19:34 UTC
Thank you for this mockup, is has a really good appearance ;)

But I have a doubt about the meta packages removal. At this moment the master/slave is merely compiling the modules delegating on jhbuild and then showing that. 

I'm not sure if add on the master some kind of rule to hide some modules (like a list on the multimaster conf file) could be a good idea, as it seems a kind of hack

Anyway the mockup is a good base to start, thank you again
Comment 9 Frederic Peters 2008-05-08 14:54:16 UTC
Well, the motivation for meta package removal was to shorten the first column; an alternative way would be to ellipsize long module names:

 <span title="meta-gnome-devel-platform-upcoming-deprecations">meta-gnome-devel (...)</span>

Also I have not been involved in technical work for build.gnome.org for a long time but I can sure lend a hand when it comes to HTML/CSS/JavaScript hacking.

Also we should get back thinking about importing all of this in GNOME subversion, scripts and files as currently present in Igalia CVS, but also all this web stuff we are about to work on.
Comment 10 Alejandro Piñeiro Iglesias (IRC: infapi00) 2008-05-08 15:09:31 UTC
Yes, I was talking with Iago just now and he is proposed too the ellipsize solution.

And of course that this web stuff should be along the other files. In fact, the current css used on buildbot is included yet. 

About move it to the GNOME subversion: yes, this is a long time item on the b.g.o. TODO list, and probably when we finished some details we can take up again this, although this is a different bug/problem 
Comment 11 Iago Toral 2008-06-27 12:15:37 UTC
Thanks to Frederic and Piñeiro!  We have a new website layout now!
Comment 12 Frederic Peters 2008-06-27 12:21:53 UTC
Thank you!