all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: Catonano <catonano@gmail.com>
Cc: 26006@debbugs.gnu.org, David Thompson <davet@gnu.org>
Subject: bug#26006: [Website] Integral update proposal
Date: Tue, 4 Jul 2017 19:45:37 -0500	[thread overview]
Message-ID: <9715cc08-dd74-e728-ec79-b731abefd415@zoho.com> (raw)
In-Reply-To: <CAJ98PDynVgo0-TyykX6e2xoXr6F3mpPXZ9s8ej4QzbX3aV5GFQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4892 bytes --]

On 04/07/17 15:09, Catonano wrote:
>
>
> 2017-07-04 22:00 GMT+02:00 sirgazil <sirgazil@zoho.com 
> <mailto:sirgazil@zoho.com>>:
>
>     Hey :)
>
>
>
>     On 01/07/17 09:26, Ludovic Courtès wrote:
>
>         Hi sirgazil,
>
>         Slowly trying to catch up…
>
>         sirgazil <sirgazil@zoho.com <mailto:sirgazil@zoho.com>> skribis:
>
>             This implementation is missing the following parts:
>
>             1. New screenshots
>             2. Packages pages
>                 1. Package detail page
>                 2. Packages issues page
>                 3. Packages reproducibility page
>                 4. Packages JSON file
>
>             To complete part (1) someone could provide the screenshots
>             (ideally
>             1920×1080 px) in JPG and add them to the
>             "static/media/img" directory,
>             and update the list of screenshots in "apps/base/data.scm".
>
>         Since “someone” has not shown up yet ;-), maybe we can delay
>         (1), no?
>
>             To complete (2), there are some package related procedures
>             missing
>             (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open
>             <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>).
>             I tried to use the code that is already in the current
>             website, but
>             couldn't figure things out.
>
>             To complete part (2.1), there is an issue to solve:
>             package pages go in
>             paths like "/packages/blender-3.0/", but running "haunt
>             build" with
>             pages on paths that include "." will render the pages with
>             all the HTML
>             content inside a pre element. David, the maintainer of
>             Haunt, does not
>             know yet why this would happen. If this issue is solved,
>             there are
>             already helper builders in "apps/packages/builders.scm" to
>             generate all
>             the pages.
>
>         Was this issue fixed in the meantime?  David?
>
>             So, for now, the packages pages are working as in the
>             current website,
>             but not using tables (to make it easier to adapt the page
>             to several
>             screen widths), and packages are distributed in numbered
>             pages to avoid
>             big HTML pages that take too long to load.
>
>             Also, the JavaScript code that gets package build status
>             is not
>             integrated (couldn't figure this one out either).
>
>         Did you have a chance to look at whether you could include the
>         existing
>         code?  After all, the code is already there so we should be
>         able to just
>         “move” it to its new home without further ado.
>
>         If that’s more complicated that this, then maybe we can ask
>         for help
>         from Alex Sassmannshausen, or simply delay it.
>
>             To complete (2.2), (2.3), and (2.4) someone could add
>             helper builders to
>             the packages app, and recycle the related SXML pages
>             already used in the
>             current website.
>
>         Likewise, can’t we just reuse the existing code?  I haven’t looked
>         closely but I imagine we won’t have to rewrite all of these from
>         scratch.
>
>         How can we proceed?  I wouldn’t want to let the fancy web site
>         bitrot!
>         I’m a bit swamped though so it would be more productive if you
>         could
>         directly hack on it on the repo, but I think you were
>         unwilling to do
>         this?  Thoughts?  :-)
>
>
>     I was going to take a look again, and see what I could do to
>     complete the thing, but during the application setup of guix
>     0.13.0 many things were being built and the computer turned off
>     three times. It seems it can't take that job (I didn't have this
>     problem with 0.12.0, though).
>
>     So I don't know what to do 
>
>
> computers need manteinance
>
> This could be a sign that your computer needs a refreshing of its 
> thermal grease and a cleaning of its grates.
>
> Usually when you do that, it becomes an almost new machine and can 
> compile lots of stuff. That's my experience, by the way.

I'll see if I can do something about it.

> Another thing you could do is wait for a better building servers park 
> to be available for Guix
>
> Rekado has mentioned that an improvement is in the pipe, to be 
> delivered soonish
>
> With that you could find way more binaries ready for use and you won't 
> need your own computer to compile them
>
> Ludo is way more competent and informed than I am, though, so he might 
> have some better suggestion.

Thanks, Catonano :)

-- 
https://sirgazil.bitbucket.io/


[-- Attachment #2: Type: text/html, Size: 9010 bytes --]

  reply	other threads:[~2017-07-05  0:46 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  2:02 bug#26006: [Website] Integral update proposal sirgazil
2017-03-07 11:16 ` ng0
2017-03-07 12:53 ` Catonano
2017-03-07 14:13 ` Ludovic Courtès
2017-03-10 16:46   ` sirgazil
2017-03-10 21:05     ` Ludovic Courtès
2017-10-01 11:02   ` ng0
2017-10-02  7:50     ` Ludovic Courtès
2017-10-02  8:36       ` ng0
2017-10-02  9:10         ` Ludovic Courtès
2017-06-08 19:06 ` sirgazil
2017-06-13 22:08   ` Ludovic Courtès
2017-06-14 20:36     ` sirgazil
2017-06-15  7:59       ` Ludovic Courtès
2017-06-16  2:52         ` sirgazil
2017-06-16  7:05           ` Ludovic Courtès
2017-06-16 14:46             ` sirgazil
2017-06-17  4:57               ` Catonano
2017-06-17  7:16                 ` Catonano
2017-06-17 15:46                   ` sirgazil
2017-06-17 16:09                     ` Catonano
2017-06-17 16:41                       ` sirgazil
2017-06-17 17:12                         ` Catonano
2017-06-17 18:11                           ` sirgazil
2017-06-17 15:19                 ` sirgazil
2017-06-17 15:19                   ` Catonano
2017-07-29 17:53               ` Ludovic Courtès
2017-08-01 22:13                 ` sirgazil
2017-12-06 17:10                   ` bug#26006: New web site is on line! Ludovic Courtès
2017-12-06 17:55                     ` Alex Sassmannshausen
2017-12-06 22:10                       ` Adonay Felipe Nogueira
2017-12-06 22:10                     ` Adonay Felipe Nogueira
2017-12-07  8:54                       ` Ludovic Courtès
2017-12-07  3:01                     ` sirgazil
2017-12-07  9:16                     ` Chris Marusich
2017-12-07 17:10                     ` pelzflorian (Florian Pelz)
2017-12-07 20:58                       ` Ludovic Courtès
2017-12-08 18:42                       ` Quiliro Ordonez Baca
2017-12-08 19:07                         ` pelzflorian (Florian Pelz)
2017-07-01 14:26   ` bug#26006: [Website] Integral update proposal Ludovic Courtès
2017-07-04 20:00     ` sirgazil
2017-07-04 20:09       ` Catonano
2017-07-05  0:45         ` sirgazil [this message]
2017-07-04 21:24       ` Ludovic Courtès
2017-07-05  1:26         ` sirgazil

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=9715cc08-dd74-e728-ec79-b731abefd415@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=26006@debbugs.gnu.org \
    --cc=catonano@gmail.com \
    --cc=davet@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.