[Website] Integral update proposal

DoneSubmitted by sirgazil.
Details
11 participants
  • Adonay Felipe Nogueira
  • Alex Sassmannshausen
  • Catonano
  • Chris Marusich
  • ng0
  • sirgazil
  • Ludovic Courtès
  • ng0
  • pelzflorian (Florian Pelz)
  • Quiliro Ordonez Baca
  • sirgazil
Owner
unassigned
Severity
normal
S
S
sirgazil wrote on 7 Mar 2017 03:02
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
pzFj7W63lwIY85c_wcCCmJBOZk6se9SVwTzz0VGqc-6LwpFUgAhyi6V3DmSTHgWQT-kdQ-FgLyF_B_P7qU7CCm1YggyVycXbTQS03i7qZc0=@protonmail.com
Hi,
I'd like to propose some changes to the website based on my current perception of it and some comments I've read from users:

Navigation bar==============
Bar mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-menu-2017-03-06.png
The current navigation bar is growing, so I think it may be good to define a style so that people can build more complex menus if necessary (but I hope it won't get too complex).
I propose the graphic change you see in the mockup—thin black line at the bottom, navigation items are white while idle, and yellow with a black indicator at the bottom when active— as well as the actual items and their ordering.


Home page=========
Home mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-home-view-2017-03-06.png
I propose the changes in the mockup above because of the following reasons:
1. Some people still confuse Guix with GuixSD.2. Some people still ask if Guix can be used on top of other distributions.3. Some people think pitching GuixSD and Guix to specific crowds is good (of course it is). [1]
To address the first two points, I changed the order of the content so that information refers to GuixSD first, Guix as a part of it, and then added a section that mentions specifically the use of Guix in other distros.
For point three, I added a section that links to blog posts that explain GuixSD and Guix in the context of a particular field (this part requires the current News pages to become a Blog instead. See below).
Finally, Ricardo Wurmus commented that there were too many styles of buttons, and I agree with him, so I made them homogeneous.

News pages==========
News list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-list-2017-03-06.pngNews details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-post-2017-03-06.png
I suggest to convert News into a blog instead. This could make it easier to add information targeted at different audiences without making the website more complex. Additionally, we could move to the blog content like talks, papers, and posts currently listed in the Help page.
I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.
Also, Haunt, the current static site generator used to build the website, can create an atom feed for every tag in the blog, so people can subscribe to whatever topic is more interesting to them. Personally, I'd like to subscribe to a "Security" feed to keep informed about important security updates (see bug #25852). [3]

Packages pages==============
Package list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-list-2017-03-06.pngPackage details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-detail-2017-03-06.png
I actually proposed this update in bug #25227,[4] but decided to review the whole website design, so I put it here for reference.

Help page=========
* Move talks, papers, and posts to the Blog.* Allow little boxes to be distributed along the whole width of the screen.

Contribute page===============
* Allow little boxes to be distributed along the whole width of the screen.

Infrastructure==============
Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.
However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).
To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.
And that's all I'd like to modify regarding the current website.
What do you think?

[1]: https://lists.gnu.org/archive/html/guix-devel/2015-12/msg00873.html[2]: https://gnunet.org/bot/log/guix/2016-02-27#T934268[3]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25852[4]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25227


---https://sirgazil.bitbucket.io/
Attachment: file
N
(name . sirgazil)(address . lizagris@protonmail.com)(address . 26006@debbugs.gnu.org)
20170307111614.wiwgruhg2pd5dkbi@abyayala
Hi,
I don't have very much to comment on, but I just want to express that Ilike the Navigation bar and Home page section changes.On 17-03-06 21:02:39, sirgazil wrote:
Toggle quote (15 lines)> Hi,> > I'd like to propose some changes to the website based on my current perception of it and some comments I've read from users:> > > Navigation bar> ==============> > Bar mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-menu-2017-03-06.png> > The current navigation bar is growing, so I think it may be good to define a style so that people can build more complex menus if necessary (but I hope it won't get too complex).> > I propose the graphic change you see in the mockup—thin black line at the bottom, navigation items are white while idle, and yellow with a black indicator at the bottom when active— as well as the actual items and their ordering.>
I like this proposed style and the possibility of sub navigationitems.
Toggle quote (19 lines)> > Home page> =========> > Home mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-home-view-2017-03-06.png> > I propose the changes in the mockup above because of the following reasons:> > 1. Some people still confuse Guix with GuixSD.> 2. Some people still ask if Guix can be used on top of other distributions.> 3. Some people think pitching GuixSD and Guix to specific crowds is good (of course it is). [1]> > To address the first two points, I changed the order of the content so that information refers to GuixSD first, Guix as a part of it, and then added a section that mentions specifically the use of Guix in other distros.> > For point three, I added a section that links to blog posts that explain GuixSD and Guix in the context of a particular field (this part requires the current News pages to become a Blog instead. See below).> > Finally, Ricardo Wurmus commented that there were too many styles of buttons, and I agree with him, so I made them homogeneous.>
This is very good!
Toggle quote (8 lines)> News pages> ==========> > News list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-list-2017-03-06.png> News details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-post-2017-03-06.png> > I suggest to convert News into a blog instead. This could make it easier to add information targeted at different audiences without making the website more complex. Additionally, we could move to the blog content like talks, papers, and posts currently listed in the Help page.
Good idea!
Toggle quote (11 lines)> I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.> > Also, Haunt, the current static site generator used to build the website, can create an atom feed for every tag in the blog, so people can subscribe to whatever topic is more interesting to them. Personally, I'd like to subscribe to a "Security" feed to keep informed about important security updates (see bug #25852). [3]> > > Packages pages> ==============> > Package list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-list-2017-03-06.png> Package details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-detail-2017-03-06.png
If single packages could have a page or some unique link (similar towhat debian, archlinux, Gentoo etc does), this would be THE solutionfor upstreams who link to the sourcecode in cgit instead currently.
I like the style!
Toggle quote (39 lines)> I actually proposed this update in bug #25227,[4] but decided to review the whole website design, so I put it here for reference.> > > Help page> =========> > * Move talks, papers, and posts to the Blog.> * Allow little boxes to be distributed along the whole width of the screen.> > > Contribute page> ===============> > * Allow little boxes to be distributed along the whole width of the screen.> > > Infrastructure> ==============> > Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.> > However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).> > To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.> > And that's all I'd like to modify regarding the current website.> > What do you think?> > > [1]: https://lists.gnu.org/archive/html/guix-devel/2015-12/msg00873.html> [2]: https://gnunet.org/bot/log/guix/2016-02-27#T934268> [3]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25852> [4]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25227> > > > ---> https://sirgazil.bitbucket.io/
C
C
Catonano wrote on 7 Mar 2017 13:53
(name . sirgazil)(address . lizagris@protonmail.com)(address . 26006@debbugs.gnu.org)
CAJ98PDz6GUjGi8QrNhKKGUnft9RaF3umABv_omWM9A4tvvZr9w@mail.gmail.com
Overall, I like all your proposals.
The one I like best is the proposal about packages. I hope I won't hurtyour feelings if I state that the new layout makes the packages thingsomewhat similar to the "Software" application in Fedora.And I think that a degree of resemblance is good both for GuixSD and forthe users.
Too bad there's this roadblock due to csv but I really can't help with that
Thanks for your work !
Attachment: file
L
L
Ludovic Courtès wrote on 7 Mar 2017 15:13
(name . sirgazil)(address . lizagris@protonmail.com)
87o9xdb2et.fsf@gnu.org
Hello sirgazil!
It’s always a pleasure to read you. :-) Basically, I like all of yourproposals. Some comments below.
sirgazil <lizagris@protonmail.com> skribis:
Toggle quote (9 lines)> Navigation bar> ==============>> Bar mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-menu-2017-03-06.png>> The current navigation bar is growing, so I think it may be good to define a style so that people can build more complex menus if necessary (but I hope it won't get too complex).>> I propose the graphic change you see in the mockup—thin black line at the bottom, navigation items are white while idle, and yellow with a black indicator at the bottom when active— as well as the actual items and their ordering.
Very good idea, definitely an improvement.
Toggle quote (17 lines)> Home page> =========>> Home mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-home-view-2017-03-06.png>> I propose the changes in the mockup above because of the following reasons:>> 1. Some people still confuse Guix with GuixSD.> 2. Some people still ask if Guix can be used on top of other distributions.> 3. Some people think pitching GuixSD and Guix to specific crowds is good (of course it is). [1]>> To address the first two points, I changed the order of the content so that information refers to GuixSD first, Guix as a part of it, and then added a section that mentions specifically the use of Guix in other distros.>> For point three, I added a section that links to blog posts that explain GuixSD and Guix in the context of a particular field (this part requires the current News pages to become a Blog instead. See below).>> Finally, Ricardo Wurmus commented that there were too many styles of buttons, and I agree with him, so I made them homogeneous.
Agreed.
Toggle quote (8 lines)> News pages> ==========>> News list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-list-2017-03-06.png> News details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-post-2017-03-06.png>> I suggest to convert News into a blog instead. This could make it easier to add information targeted at different audiences without making the website more complex. Additionally, we could move to the blog content like talks, papers, and posts currently listed in the Help page.
Sounds great.
Toggle quote (2 lines)> I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.
Yes! There’s also the question of how much work it’ll be to maintainthe talks part (like whether we need to manually make “posters” for eachvideo and so on.) The less work, the better.
At the same time, we should reach out to people who’d like to contributeto Guix in a less-technical way. There’s a lot that could be done tokeep the web site lively, and it would be great to let more people takecare of that.
Toggle quote (2 lines)> Also, Haunt, the current static site generator used to build the website, can create an atom feed for every tag in the blog, so people can subscribe to whatever topic is more interesting to them. Personally, I'd like to subscribe to a "Security" feed to keep informed about important security updates (see bug #25852). [3]
I agree, we should use tags. A first step will be to add tags to theexisting posts.
Toggle quote (8 lines)> Packages pages> ==============>> Package list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-list-2017-03-06.png> Package details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-detail-2017-03-06.png>> I actually proposed this update in bug #25227,[4] but decided to review the whole website design, so I put it here for reference.
There’s still the issue that we don’t have screenshots, but other thanthat it looks great.
Toggle quote (6 lines)> Help page> =========>> * Move talks, papers, and posts to the Blog.> * Allow little boxes to be distributed along the whole width of the screen.
Good.
Toggle quote (15 lines)> Contribute page> ===============>> * Allow little boxes to be distributed along the whole width of the screen.>>> Infrastructure> ==============>> Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.>> However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).>> To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.
There was none.
I don’t think we can get the level of support we’d like from the gnu.orgwebmasters, who are already swamped. With Alex S. (Cc’d) and others atFOSDEM, we discussed this issue and concluded that we should considermoving the web site to infrastructure we control, where we could dothings in any way we like.
We won’t run a Libreboot-based physical machine for that because withthe current lack of IPMI support, we’d easily end up with downtimesunacceptable for a web site. However, we could use some sort ofcommercial hosting.
I’m not much of a Web person so you and other Web-savvy people shouldconsider themselves empowered to come up with a solution. :-) We havesome funding that we could probably use for that.
Thoughts?
Thanks,Ludo’.
S
S
sirgazil wrote on 10 Mar 2017 17:46
(address . ludo@gnu.org)
HGAr1b8lxmlbfoPr6GJZavhMjQqnuFN8-of_lC1hrcrNrv4t5qihAn9FtQwolL3mdPRF2gdY9KFhzAEspzcVgrcQJaT7TTAAx1MaAHdpcKI=@protonmail.com
Thank you all for your feedback :)

-------- Original Message --------Subject: Re: bug#26006: [Website] Integral update proposalLocal Time: 7 de marzo de 2017 9:13 AMUTC Time: 7 de marzo de 2017 14:13From: ludo@gnu.orgTo: sirgazil <lizagris@protonmail.com>26006@debbugs.gnu.org, Alex Sassmannshausen <alex@pompo.co>
[...]

Toggle quote (2 lines)> I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.
Yes! There’s also the question of how much work it’ll be to maintainthe talks part (like whether we need to manually make “posters” for eachvideo and so on.) The less work, the better.
At the same time, we should reach out to people who’d like to contributeto Guix in a less-technical way. There’s a lot that could be done tokeep the web site lively, and it would be great to let more people takecare of that.

Hm, right. Managing static websites with current static site builders is pretty much a technical, and manual job.


Toggle quote (9 lines)> Infrastructure> ==============>> Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.>> However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).>> To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.
There was none.
I don’t think we can get the level of support we’d like from the gnu.orgwebmasters, who are already swamped. With Alex S. (Cc’d) and others atFOSDEM, we discussed this issue and concluded that we should considermoving the web site to infrastructure we control, where we could dothings in any way we like.
We won’t run a Libreboot-based physical machine for that because withthe current lack of IPMI support, we’d easily end up with downtimesunacceptable for a web site. However, we could use some sort ofcommercial hosting.
That sounds good :)


I’m not much of a Web person so you and other Web-savvy people shouldconsider themselves empowered to come up with a solution. :-) We havesome funding that we could probably use for that.
Thoughts?

Many :)
I'd like to say I will take care of this project, but I can't commit right now. However, life permitting, I intend to implement the proposed changes that can be implemented in the current static site, starting next week.
Attachment: file
L
L
Ludovic Courtès wrote on 10 Mar 2017 22:05
(name . sirgazil)(address . lizagris@protonmail.com)
87zigsg7vn.fsf@gnu.org
Hello,
sirgazil <lizagris@protonmail.com> skribis:
Toggle quote (5 lines)> I'd like to say I will take care of this project, but I can't commit> right now. However, life permitting, I intend to implement the> proposed changes that can be implemented in the current static site,> starting next week.
Anytime is fine. Your work and dedication is always appreciated!
Thanks,Ludo’.
S
S
sirgazil wrote on 8 Jun 2017 21:06
[Website] Integral update proposal
(address . 26006@debbugs.gnu.org)
57bc6255-c3a1-61e2-fee4-5b6f523a9885@zoho.com
Hi,
I have an incomplete implementation(https://bitbucket.org/sirgazil/guixsd-website)of a static website thatincludes the features illustrated in the mockups (the features that fitin a static website).
Compared to the current website, this code has a different organization(see the "Framework" section below). I'm sending this message because Ithink this is as far as I can go with the implementation (found someproblems I haven't figured out how to solve, and I'm not skilled enoughto manipulate packages).
This implementation is missing the following parts:
1. New screenshots2. 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 (ideally1920×1080 px) in JPG and add them to the "static/media/img" directory,and update the list of screenshots in "apps/base/data.scm".
To complete (2), there are some package related procedures missing(https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open).I tried to use the code that is already in the current website, butcouldn't figure things out.
To complete part (2.1), there is an issue to solve: package pages go inpaths like "/packages/blender-3.0/", but running "haunt build" withpages on paths that include "." will render the pages with all the HTMLcontent inside a pre element. David, the maintainer of Haunt, does notknow yet why this would happen. If this issue is solved, there arealready helper builders in "apps/packages/builders.scm" to generate allthe pages.
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 severalscreen widths), and packages are distributed in numbered pages to avoidbig HTML pages that take too long to load.
Also, the JavaScript code that gets package build status is notintegrated (couldn't figure this one out either).
To complete (2.2), (2.3), and (2.4) someone could add helper builders tothe packages app, and recycle the related SXML pages already used in thecurrent website.

Framework=========
The website is composed by apps; for example, a base app, a blog app, apackages app. An app is a directory with Scheme modules that *usually*look like this:
apps/abc├── builder.scm├── types.scm├── data.scm├── utils.scm└── templates ├── components.scm ├── some-page.scm └── another-page.scm
The builder file contains a Haunt builder procedure and helper buildersthat build the web resources of an app. In the types file there are datatype definitions for the app (for example: screenshot, download,lint-issue, etc.). The data file contains instances of the defined datatypes. The utils file contains helper procedures for an application. Thetemplate directory contains SHTML, SXML, SATOM, SJSON templates to buildthe web resources provided by an application. The components module inthe templates directory has template components that are used in severaltemplates or even in other apps.
All apps are "plugged" to the website by adding their builders to thesite object in the "haunt.scm" file.
Currently, there is also an aux app that contains procedures notparticular to any app.
If you have some time, take a look at it and let me know what you think.I can change *anything* that you think is inefficient, horrible orwhatever. I hope it is not a mess :)

Best,

-- https://sirgazil.bitbucket.io/
L
L
Ludovic Courtès wrote on 14 Jun 2017 00:08
(name . sirgazil)(address . sirgazil@zoho.com)(address . 26006@debbugs.gnu.org)
87injztuax.fsf@gnu.org
Hi sirgazil,
It’s always a pleasure to hear from you. :-)
sirgazil <sirgazil@zoho.com> skribis:
Toggle quote (5 lines)> I have an incomplete implementation> (https://bitbucket.org/sirgazil/guixsd-website) of a static website that> includes the features illustrated in the mockups (the features that fit> in a static website).
I’ve just built the web site and I like it! The flat buttons look nice,the front page looks cleaner, “GuixSD and GNU Guix in your field” soundslike a good idea, etc. I really like the blog part with tags andeverything.
I found it a little bit confusing that talks and papers now appear as ifthey were blog posts, but after all it’s probably better to have it thisway, especially since tags allow people to find them more easily I guess.
The packages pages look better than what we have (minus the loss of theJS code to display the build status ;-)).
Toggle quote (44 lines)> Compared to the current website, this code has a different organization> (see the "Framework" section below). I'm sending this message because I> think this is as far as I can go with the implementation (found some> problems I haven't figured out how to solve, and I'm not skilled enough> to manipulate packages).>> 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".>> To complete (2), there are some package related procedures missing> (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.>> 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).>> 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.
Sounds good. I haven’t looked at this nor have I looked at the newframework, but I’ll hopefully comment soonish. Hopefully David can helpfor the Haunt part, then people can provide screenshots, and we’llfigure out the issues with packages pages somehow. :-)
I think there are a few little changes that were made in the currentsite that were lost in the process. For example, on the front page, wenow have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seenthat links to the package definitions at git.sv.gnu.org from the packagepages no longer include the commit. Anyway, these are really tinyissues but we should pay attention to them when we migrate.
Anyway, a big thank you for all this work! Really impressive workonce again.
Ludo’.
S
S
sirgazil wrote on 14 Jun 2017 22:36
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 26006@debbugs.gnu.org)
e3cfcfc6-1514-f37f-ceb5-f4bf9b6f8a4d@zoho.com
On 13/06/17 17:08, Ludovic Courtès wrote:
Toggle quote (4 lines)> Hi sirgazil,>> It’s always a pleasure to hear from you. :-)
Hi, glad to hear that :)
Toggle quote (11 lines)> sirgazil <sirgazil@zoho.com> skribis:>>> I have an incomplete implementation>> (https://bitbucket.org/sirgazil/guixsd-website) of a static website that>> includes the features illustrated in the mockups (the features that fit>> in a static website).> I’ve just built the web site and I like it! The flat buttons look nice,> the front page looks cleaner, “GuixSD and GNU Guix in your field” sounds> like a good idea, etc. I really like the blog part with tags and> everything.
Great!
Toggle quote (8 lines)>> I found it a little bit confusing that talks and papers now appear as if> they were blog posts, but after all it’s probably better to have it this> way, especially since tags allow people to find them more easily I guess.>> The packages pages look better than what we have (minus the loss of the> JS code to display the build status ;-)).
About the JS, I couldn't figured out exactly how it works, so that Icould adapt it to the new page structure. Additionally, there is theproblem that the JS looks for packages in the DOM by id, and package idsare not unique, which confuses me. Also, using duplicated id attributesis non-valid HTML.
Toggle quote (49 lines)>>> Compared to the current website, this code has a different organization>> (see the "Framework" section below). I'm sending this message because I>> think this is as far as I can go with the implementation (found some>> problems I haven't figured out how to solve, and I'm not skilled enough>> to manipulate packages).>>>> 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".>>>> To complete (2), there are some package related procedures missing>> (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.>>>> 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).>>>> 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.> Sounds good. I haven’t looked at this nor have I looked at the new> framework, but I’ll hopefully comment soonish. Hopefully David can help> for the Haunt part, then people can provide screenshots, and we’ll> figure out the issues with packages pages somehow. :-)
Sure, no rush.
Toggle quote (7 lines)> I think there are a few little changes that were made in the current> site that were lost in the process. For example, on the front page, we> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen> that links to the package definitions at git.sv.gnu.org from the package> pages no longer include the commit. Anyway, these are really tiny> issues but we should pay attention to them when we migrate.
I updated the download button.
As for the commit in the links, I tried to add it, but couldn't. Iimplemented this website using the Guix API as a user (installing guixwith guix), but it seems that the code to generate the commit part inthe links requires that the guix in the GUILE_LOAD_PATH be a gitrepository, right? Since it uses "git describe" on "guix/config.scm".
Toggle quote (5 lines)> Anyway, a big thank you for all this work! Really impressive work> once again.>> Ludo’.
Thank you for the kind words. I'm glad I can help a bit.
-- https://sirgazil.bitbucket.io/
L
L
Ludovic Courtès wrote on 15 Jun 2017 09:59
(name . sirgazil)(address . sirgazil@zoho.com)(address . 26006@debbugs.gnu.org)
877f0d65qe.fsf@gnu.org
Hello,
sirgazil <sirgazil@zoho.com> skribis:
Toggle quote (2 lines)> On 13/06/17 17:08, Ludovic Courtès wrote:
[...]
Toggle quote (13 lines)>> I found it a little bit confusing that talks and papers now appear as if>> they were blog posts, but after all it’s probably better to have it this>> way, especially since tags allow people to find them more easily I guess.>>>> The packages pages look better than what we have (minus the loss of the>> JS code to display the build status ;-)).>> About the JS, I couldn't figured out exactly how it works, so that I> could adapt it to the new page structure. Additionally, there is the> problem that the JS looks for packages in the DOM by id, and package ids> are not unique, which confuses me. Also, using duplicated id attributes> is non-valid HTML.
The current code that generates the package pages intends to computeunique anchor names for each package (see ‘packages->anchors’), and Ithink it’s those IDs that the JS code uses, isn’t it?
Toggle quote (15 lines)>> I think there are a few little changes that were made in the current>> site that were lost in the process. For example, on the front page, we>> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen>> that links to the package definitions at git.sv.gnu.org from the package>> pages no longer include the commit. Anyway, these are really tiny>> issues but we should pay attention to them when we migrate.>> I updated the download button.>> As for the commit in the links, I tried to add it, but couldn't. I> implemented this website using the Guix API as a user (installing guix> with guix), but it seems that the code to generate the commit part in> the links requires that the guix in the GUILE_LOAD_PATH be a git> repository, right? Since it uses "git describe" on "guix/config.scm".
Indeed, good point. I guess we could have a fallback case for when ‘gitdescribe’ fails.
On a more practical level, what would you like the workflow to be likefrom there on? I would prefer hosting the source on gnu.org rather than{bitbucket,gitlab,github}.com and I would also prefer Git overMercurial, but I don’t want to be a hindrance so I’m open todiscussions. :-)
Thanks!
Ludo’.
S
S
sirgazil wrote on 16 Jun 2017 04:52
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 26006@debbugs.gnu.org)
ad09ce33-bf7c-5bf8-4168-0b3bd86d6989@zoho.com
On 15/06/17 02:59, Ludovic Courtès wrote:
Toggle quote (22 lines)> Hello,>> sirgazil <sirgazil@zoho.com> skribis:>>> On 13/06/17 17:08, Ludovic Courtès wrote:> [...]>>>> I found it a little bit confusing that talks and papers now appear as if>>> they were blog posts, but after all it’s probably better to have it this>>> way, especially since tags allow people to find them more easily I guess.>>>>>> The packages pages look better than what we have (minus the loss of the>>> JS code to display the build status ;-)).>> About the JS, I couldn't figured out exactly how it works, so that I>> could adapt it to the new page structure. Additionally, there is the>> problem that the JS looks for packages in the DOM by id, and package ids>> are not unique, which confuses me. Also, using duplicated id attributes>> is non-valid HTML.> The current code that generates the package pages intends to compute> unique anchor names for each package (see ‘packages->anchors’), and I> think it’s those IDs that the JS code uses, isn’t it?
Right. My mistake :)
Toggle quote (22 lines)>>>> I think there are a few little changes that were made in the current>>> site that were lost in the process. For example, on the front page, we>>> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen>>> that links to the package definitions at git.sv.gnu.org from the package>>> pages no longer include the commit. Anyway, these are really tiny>>> issues but we should pay attention to them when we migrate.>> I updated the download button.>>>> As for the commit in the links, I tried to add it, but couldn't. I>> implemented this website using the Guix API as a user (installing guix>> with guix), but it seems that the code to generate the commit part in>> the links requires that the guix in the GUILE_LOAD_PATH be a git>> repository, right? Since it uses "git describe" on "guix/config.scm".> Indeed, good point. I guess we could have a fallback case for when ‘git> describe’ fails.> On a more practical level, what would you like the workflow to be like> from there on? I would prefer hosting the source on gnu.org rather than> {bitbucket,gitlab,github}.com and I would also prefer Git over> Mercurial, but I don’t want to be a hindrance so I’m open to> discussions. :-)
No worries. The idea was to move the useful parts to guix-artwork ongnu.org.
To be honest, when I started this version of the website I was justmotivated on implementing the designs and exploring a way to organizemodules in a haunt website so that data, builders and templates wereseparated. But I was not very interested in dealing with git workflows,and strict commit messages. Sorry about that :)
So, what do we do? Create a branch on guix-artwork and drop these filesthere to complete what is missing? I don't know...

-- https://sirgazil.bitbucket.io/
L
L
Ludovic Courtès wrote on 16 Jun 2017 09:05
(name . sirgazil)(address . sirgazil@zoho.com)(address . 26006@debbugs.gnu.org)
877f0cjtul.fsf@gnu.org
Howdy!
sirgazil <sirgazil@zoho.com> skribis:
Toggle quote (2 lines)> On 15/06/17 02:59, Ludovic Courtès wrote:
[...]
Toggle quote (15 lines)>> On a more practical level, what would you like the workflow to be like>> from there on? I would prefer hosting the source on gnu.org rather than>> {bitbucket,gitlab,github}.com and I would also prefer Git over>> Mercurial, but I don’t want to be a hindrance so I’m open to>> discussions. :-)>> No worries. The idea was to move the useful parts to guix-artwork on> gnu.org.>> To be honest, when I started this version of the website I was just> motivated on implementing the designs and exploring a way to organize> modules in a haunt website so that data, builders and templates were> separated. But I was not very interested in dealing with git workflows,> and strict commit messages. Sorry about that :)
No problem, this is perfectly understandable (also I’m fine with relaxedconventions on guix-artwork.git).
Toggle quote (3 lines)> So, what do we do? Create a branch on guix-artwork and drop these files> there to complete what is missing? I don't know...
Yes we could do that. Should we investigate the missing bits first? Ihaven’t taken the time to do it yet, sorry about that.
Thank you!
Ludo’.
S
S
sirgazil wrote on 16 Jun 2017 16:46
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 26006@debbugs.gnu.org)
493e9e04-fc8f-2a77-0927-a862f174aa55@zoho.com
On 16/06/17 02:05, Ludovic Courtès wrote:
Toggle quote (28 lines)> Howdy!>> sirgazil <sirgazil@zoho.com> skribis:>>> On 15/06/17 02:59, Ludovic Courtès wrote:> [...]>>>> On a more practical level, what would you like the workflow to be like>>> from there on? I would prefer hosting the source on gnu.org rather than>>> {bitbucket,gitlab,github}.com and I would also prefer Git over>>> Mercurial, but I don’t want to be a hindrance so I’m open to>>> discussions. :-)>> No worries. The idea was to move the useful parts to guix-artwork on>> gnu.org.>>>> To be honest, when I started this version of the website I was just>> motivated on implementing the designs and exploring a way to organize>> modules in a haunt website so that data, builders and templates were>> separated. But I was not very interested in dealing with git workflows,>> and strict commit messages. Sorry about that :)> No problem, this is perfectly understandable (also I’m fine with relaxed> conventions on guix-artwork.git).>>> So, what do we do? Create a branch on guix-artwork and drop these files>> there to complete what is missing? I don't know...> Yes we could do that. Should we investigate the missing bits first? I> haven’t taken the time to do it yet, sorry about that.
Maybe you should learn how to do mitosis. Another civodul would come inhandy. Until that, take your time, no problem :)
I'm fine with investigating the missing parts before or after moving toguix-artwork.git.
-- https://sirgazil.bitbucket.io/
C
C
Catonano wrote on 17 Jun 2017 06:57
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDyDnqXeRQLSO765mPvH3wTUoctmj4-jGocvob2zajYMZw@mail.gmail.com
2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:
Toggle quote (2 lines)>
I'm fine with investigating the missing parts before or after moving to
Toggle quote (3 lines)> guix-artwork.git.>
For what it's worth, I vouch for moving all to gnu.org and possiblyexpressing the issues in the appropriate debbugs instance
Then, I might be able to collaborate in sorting out some issues
I never used Mercurial. I should learn from scratch.
Also, I can't access the issues on bitbucket because the login doesn't workin Icecat (plus some nonsense about upgrading my account and coming mobileapps that require me some voodoo right now)
So I can't see the issues athttps://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open
Attachment: file
C
C
Catonano wrote on 17 Jun 2017 09:16
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDyT8c511VLcHR1LE4M8ii4oho5MzWz6X0BJa3cmm6dpaw@mail.gmail.com
2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com>:
Toggle quote (26 lines)>>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:>>>>> I'm fine with investigating the missing parts before or after moving to>> guix-artwork.git.>>>> For what it's worth, I vouch for moving all to gnu.org and possibly> expressing the issues in the appropriate debbugs instance>> Then, I might be able to collaborate in sorting out some issues>> I never used Mercurial. I should learn from scratch.>> Also, I can't access the issues on bitbucket because the login doesn't> work in Icecat (plus some nonsense about upgrading my account and coming> mobile apps that require me some voodoo right now)>> So I can't see the issues at> https://bitbucket.org/sirgazil/guixsd-website/> issues?status=new&status=open>>
I managed to install mercurial, but I can't build it
[env]$ haunt buildBacktrace:In ice-9/boot-9.scm: 2986:16 19 (try-module-autoload _ _) 2316:4 18 (save-module-excursion #<procedure 11b0d50 at ice-9/boo…>) 3006:22 17 (_)In unknown file: 16 (primitive-load-path "apps/blog/utils" #<procedure 11d0…>)In ice-9/eval.scm: 721:20 15 (primitive-eval (define-module (apps blog utils) # (…) …))In ice-9/psyntax.scm: 1234:36 14 (expand-top-sequence ((define-module (apps blog #) # …)) …) 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …) 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)In ice-9/eval.scm: 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)In ice-9/boot-9.scm: 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _ # _ …) 2879:24 9 (_) 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt …)) …)) 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #)) (#) …)) 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi srfi-1)) …)) 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #)) (#) …)) 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((# #)) #)) 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #)) 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#))) 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)In unknown file: 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)
Attachment: file
S
S
sirgazil wrote on 17 Jun 2017 17:19
(name . Catonano)(address . catonano@gmail.com)
15ef3980-ed85-bdea-1cab-5b88117689f0@zoho.com
On 16/06/17 23:57, Catonano wrote:
Toggle quote (28 lines)>>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com> <mailto:sirgazil@zoho.com>>:>> >> I'm fine with investigating the missing parts before or after> moving to> guix-artwork.git.>>> For what it's worth, I vouch for moving all to gnu.org> <http://gnu.org> and possibly expressing the issues in the appropriate> debbugs instance>> Then, I might be able to collaborate in sorting out some issues>> I never used Mercurial. I should learn from scratch.>> Also, I can't access the issues on bitbucket because the login doesn't> work in Icecat (plus some nonsense about upgrading my account and> coming mobile apps that require me some voodoo right now)>> So I can't see the issues at> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>
Sorry about that. The issue tracker was set to private, but I just madeit public. Also, you can use the tracker "anonymously" (i. e. you don'tneed a Bitbucket account).
-- https://sirgazil.bitbucket.io/
Attachment: file
C
C
Catonano wrote on 17 Jun 2017 17:19
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDyqONbQb=eZorzpa6Q+WC-zwOQuDCrxjCE+C3_rFRhJxg@mail.gmail.com
2017-06-17 17:19 GMT+02:00 sirgazil <sirgazil@zoho.com>:
Toggle quote (10 lines)> On 16/06/17 23:57, Catonano wrote:>> So I can't see the issues at> https://bitbucket.org/sirgazil/guixsd-website/> issues?status=new&status=open>>>>>
Sorry about that. The issue tracker was set to private, but I just made it
Toggle quote (4 lines)> public. Also, you can use the tracker "anonymously" (i. e. you don't need a> Bitbucket account).>
Ok, I could see the issues
Thanks
Attachment: file
S
S
sirgazil wrote on 17 Jun 2017 17:46
(name . Catonano)(address . catonano@gmail.com)
da4fd132-bb72-14e5-69af-75193792e734@zoho.com
On 17/06/17 02:16, Catonano wrote:
Toggle quote (67 lines)>>> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com> <mailto:catonano@gmail.com>>:>>>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com> <mailto:sirgazil@zoho.com>>:>> >> I'm fine with investigating the missing parts before or after> moving to> guix-artwork.git.>>> For what it's worth, I vouch for moving all to gnu.org> <http://gnu.org> and possibly expressing the issues in the> appropriate debbugs instance>> Then, I might be able to collaborate in sorting out some issues>> I never used Mercurial. I should learn from scratch.>> Also, I can't access the issues on bitbucket because the login> doesn't work in Icecat (plus some nonsense about upgrading my> account and coming mobile apps that require me some voodoo right now)>> So I can't see the issues at> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open> <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>>>> I managed to install mercurial, but I can't build it>> [env]$ haunt build> Backtrace:> In ice-9/boot-9.scm:> 2986:16 19 (try-module-autoload _ _)> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at ice-9/boo…>)> 3006:22 17 (_)> In unknown file:> 16 (primitive-load-path "apps/blog/utils" #<procedure 11d0…>)> In ice-9/eval.scm:> 721:20 15 (primitive-eval (define-module (apps blog utils) # (…) …))> In ice-9/psyntax.scm:> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) # …)) …)> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)> In ice-9/eval.scm:> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)> In ice-9/boot-9.scm:> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)> 2879:24 9 (_)> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt …)) …))> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #)) (#) …))> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi srfi-1)) …))> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #)) (#) …))> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((# #)) #))> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)> In unknown file:> 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)>
Catonano, could you try without an environment?
$ cd /path/to/guixsd-website$ guix package -i git glibc-locales guile@2.2 guile-syntax-highlightguix haunt
I actually work without environments, and it works, but will try toreproduce that error.
-- https://sirgazil.bitbucket.io/
Attachment: file
C
C
Catonano wrote on 17 Jun 2017 18:09
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDzGEBnq2eyJF6k-cPAJYZrgjQ+MX6WKaYXWHP5Q3=Y5Mw@mail.gmail.com
2017-06-17 17:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:
Toggle quote (75 lines)> On 17/06/17 02:16, Catonano wrote:>>>> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com>:>>>>>>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:>>>>>>>>> I'm fine with investigating the missing parts before or after moving to>>> guix-artwork.git.>>>>>>> For what it's worth, I vouch for moving all to gnu.org and possibly>> expressing the issues in the appropriate debbugs instance>>>> Then, I might be able to collaborate in sorting out some issues>>>> I never used Mercurial. I should learn from scratch.>>>> Also, I can't access the issues on bitbucket because the login doesn't>> work in Icecat (plus some nonsense about upgrading my account and coming>> mobile apps that require me some voodoo right now)>>>> So I can't see the issues at>> https://bitbucket.org/sirgazil/guixsd-website/issues?status=>> new&status=open>>>>> I managed to install mercurial, but I can't build it>> [env]$ haunt build> Backtrace:> In ice-9/boot-9.scm:> 2986:16 19 (try-module-autoload _ _)> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at ice-9/boo…>)> 3006:22 17 (_)> In unknown file:> 16 (primitive-load-path "apps/blog/utils" #<procedure 11d0…>)> In ice-9/eval.scm:> 721:20 15 (primitive-eval (define-module (apps blog utils) # (…) …))> In ice-9/psyntax.scm:> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) # …)) …)> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)> In ice-9/eval.scm:> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)> In ice-9/boot-9.scm:> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)> 2879:24 9 (_)> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt …)) …))> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #)) (#) …))> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi srfi-1)) …))> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #)) (#) …))> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((# #)) #))> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)> In unknown file:> 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)>>> Catonano, could you try without an environment?>> $ cd /path/to/guixsd-website> $ guix package -i git glibc-locales guile@2.2 guile-syntax-highlight guix> haunt>> I actually work without environments, and it works, but will try to> reproduce that error.>
You're right. Like this, it's working
It's building the pages right now !
Attachment: file
S
S
sirgazil wrote on 17 Jun 2017 18:41
(name . Catonano)(address . catonano@gmail.com)
d5b5ad5b-1fc1-6d5d-9bfc-a629ab79bb9d@zoho.com
On 17/06/17 11:09, Catonano wrote:
Toggle quote (100 lines)> 2017-06-17 17:46 GMT+02:00 sirgazil <sirgazil@zoho.com> <mailto:sirgazil@zoho.com>>:>> On 17/06/17 02:16, Catonano wrote:>>>>>> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com>> <mailto:catonano@gmail.com>>:>>>>>>>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>> <mailto:sirgazil@zoho.com>>:>>>> >>>> I'm fine with investigating the missing parts before or>> after moving to>> guix-artwork.git.>>>>>> For what it's worth, I vouch for moving all to gnu.org>> <http://gnu.org> and possibly expressing the issues in the>> appropriate debbugs instance>>>> Then, I might be able to collaborate in sorting out some issues>>>> I never used Mercurial. I should learn from scratch.>>>> Also, I can't access the issues on bitbucket because the>> login doesn't work in Icecat (plus some nonsense about>> upgrading my account and coming mobile apps that require me>> some voodoo right now)>>>> So I can't see the issues at>> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>> <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>>>>>>> I managed to install mercurial, but I can't build it>>>> [env]$ haunt build>> Backtrace:>> In ice-9/boot-9.scm:>> 2986:16 19 (try-module-autoload _ _)>> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at>> ice-9/boo…>)>> 3006:22 17 (_)>> In unknown file:>> 16 (primitive-load-path "apps/blog/utils" #<procedure>> 11d0…>)>> In ice-9/eval.scm:>> 721:20 15 (primitive-eval (define-module (apps blog utils) #>> (…) …))>> In ice-9/psyntax.scm:>> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) #>> …)) …)>> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# #>> …)) …)>> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e>> (eval) …)>> In ice-9/eval.scm:>> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)>> In ice-9/boot-9.scm:>> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _>> # _ …)>> 2879:24 9 (_)>> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt>> …)) …))>> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #))>> (#) …))>> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi>> srfi-1)) …))>> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #))>> (#) …))>> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((#>> #)) #))>> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))>> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))>> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _>> # _ …)>> In unknown file:>> 0 (scm-error misc-error #f "~A ~S" ("no code for>> modu…" …) …)>>>> Catonano, could you try without an environment?>> $ cd /path/to/guixsd-website> $ guix package -i git glibc-locales guile@2.2 <mailto:guile@2.2>> guile-syntax-highlight guix haunt>> I actually work without environments, and it works, but will try> to reproduce that error.>>> You're right. Like this, it's working>> It's building the pages right now !
Catonano, to avoid building all the packages (3-4 minutes in thismachine), you should run the build like this:
$ GUIX_WEB_SITE_LOCAL=yes haunt build
Also, this way, the website URLs are modified to work locally, and only300 packages will be built for testing.
If you run:
$ haunt build
It will build the website for production, which uses the gnu.org URLpath for projects, so running "haunt serve" after that won't display thewebsite correctly. In this case, what I do is use python server, and nothaunt server. Like so:
$ haunt build$ cd /tmp/gnu/$ python3 -m http.server
Then you can visit http://localhost:8000/,and the site should work asif it were in production.
-- https://sirgazil.bitbucket.io/
Attachment: file
C
C
Catonano wrote on 17 Jun 2017 19:12
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDxw=KegBc4vkNAT25BTD=6_e1bKirR8OAe+4p71u-k_ZA@mail.gmail.com
2017-06-17 18:41 GMT+02:00 sirgazil <sirgazil@zoho.com>:
Toggle quote (26 lines)>> Catonano, to avoid building all the packages (3-4 minutes in this> machine), you should run the build like this:>> $ GUIX_WEB_SITE_LOCAL=yes haunt build>> Also, this way, the website URLs are modified to work locally, and only> 300 packages will be built for testing.>> If you run:>> $ haunt build>> It will build the website for production, which uses the gnu.org URL path> for projects, so running "haunt serve" after that won't display the website> correctly. In this case, what I do is use python server, and not haunt> server. Like so:>> $ haunt build> $ cd /tmp/gnu/> $ python3 -m http.server>> Then you can visit http://localhost:8000/, and the site should work as if> it were in production.>
All this stuff is good to know, thanks
I attempted to chhange te build pat to ./build and when seeing it in IcecatI got the html as plain text, not rendered.
I reset it to what it was and it works like a charm
Why ?
Anyway, now I see the site, I like it but I can't be accurate
I will have to re-red the whole thread to consiider all the issues
Thanks !Ciao
Attachment: file
S
S
sirgazil wrote on 17 Jun 2017 20:11
(name . Catonano)(address . catonano@gmail.com)
da4fc4af-80c0-6a84-facc-9c7efc375687@zoho.com
On 17/06/17 12:12, Catonano wrote:
Toggle quote (31 lines)> 2017-06-17 18:41 GMT+02:00 sirgazil <sirgazil@zoho.com> <mailto:sirgazil@zoho.com>>:>>> Catonano, to avoid building all the packages (3-4 minutes in this> machine), you should run the build like this:>> $ GUIX_WEB_SITE_LOCAL=yes haunt build>> Also, this way, the website URLs are modified to work locally, and> only 300 packages will be built for testing.>> If you run:>> $ haunt build>> It will build the website for production, which uses the gnu.org> <http://gnu.org> URL path for projects, so running "haunt serve"> after that won't display the website correctly. In this case, what> I do is use python server, and not haunt server. Like so:>> $ haunt build> $ cd /tmp/gnu/> $ python3 -m http.server>> Then you can visit http://localhost:8000/, and the site should> work as if it were in production.>>> All this stuff is good to know, thanks
I should write everything in the README.
Toggle quote (8 lines)>> I attempted to chhange te build pat to ./build and when seeing it in> Icecat I got the html as plain text, not rendered.>> I reset it to what it was and it works like a charm>> Why ?
Yeah, for some reason, system paths specified in Haunt objects can'thave dots. See: https://bitbucket.org/sirgazil/guixsd-website/issues/47/.
Toggle quote (8 lines)>> Anyway, now I see the site, I like it but I can't be accurate>> I will have to re-red the whole thread to consiider all the issues>> Thanks !> Ciao
Attachment: file
L
L
Ludovic Courtès wrote on 1 Jul 2017 16:26
(name . sirgazil)(address . sirgazil@zoho.com)
87y3s8cjxc.fsf@gnu.org
Hi sirgazil,
Slowly trying to catch up…
sirgazil <sirgazil@zoho.com> skribis:
Toggle quote (13 lines)> 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?
Toggle quote (13 lines)> To complete (2), there are some package related procedures missing> (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?
Toggle quote (8 lines)> 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 existingcode? 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 helpfrom Alex Sassmannshausen, or simply delay it.
Toggle quote (4 lines)> 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 lookedclosely but I imagine we won’t have to rewrite all of these fromscratch.
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 coulddirectly hack on it on the repo, but I think you were unwilling to dothis? Thoughts? :-)
Ludo’.
S
S
sirgazil wrote on 4 Jul 2017 22:00
(name . Ludovic Courtès)(address . ludo@gnu.org)
697941d7-4bf5-71ff-95fe-1fc33c962b17@zoho.com
Hey :)

On 01/07/17 09:26, Ludovic Courtès wrote:
Toggle quote (60 lines)> Hi sirgazil,>> Slowly trying to catch up…>> sirgazil <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).>> 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 :(
-- https://sirgazil.bitbucket.io/
C
C
Catonano wrote on 4 Jul 2017 22:09
(name . sirgazil)(address . sirgazil@zoho.com)
CAJ98PDynVgo0-TyykX6e2xoXr6F3mpPXZ9s8ej4QzbX3aV5GFQ@mail.gmail.com
2017-07-04 22:00 GMT+02:00 sirgazil <sirgazil@zoho.com>:
Toggle quote (80 lines)> Hey :)>>>> On 01/07/17 09:26, Ludovic Courtès wrote:>>> Hi sirgazil,>>>> Slowly trying to catch up…>>>> sirgazil <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).>>> 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 thermalgrease and a cleaning of its grates.
Usually when you do that, it becomes an almost new machine and can compilelots of stuff. That's my experience, by the way.
Another thing you could do is wait for a better building servers park to beavailable for Guix
Rekado has mentioned that an improvement is in the pipe, to be deliveredsoonish
With that you could find way more binaries ready for use and you won't needyour own computer to compile them
Ludo is way more competent and informed than I am, though, so he might havesome better suggestion.
Attachment: file
L
L
Ludovic Courtès wrote on 4 Jul 2017 23:24
(name . sirgazil)(address . sirgazil@zoho.com)
87van7sxo8.fsf@gnu.org
Hi!
sirgazil <sirgazil@zoho.com> skribis:
Toggle quote (5 lines)> 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).
Ouch, that’s no good. The web site itself needs a few packages ofcourse; if you do ‘guix pull’ (the CPU-intensive part) and then “guixbuild -f guix.scm” in the website directory, that should build the thingand download the prerequisites.
If that goes wrong, I guess I’ll allocate time for this maybe next weekand ask for guidance (every else is welcome to help!).
Thanks,Ludo’.
S
S
sirgazil wrote on 5 Jul 2017 02:45
(name . Catonano)(address . catonano@gmail.com)
9715cc08-dd74-e728-ec79-b731abefd415@zoho.com
On 04/07/17 15:09, Catonano wrote:
Toggle quote (117 lines)>>> 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.
Toggle quote (12 lines)> 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: file
S
S
sirgazil wrote on 5 Jul 2017 03:26
(name . Ludovic Courtès)(address . ludo@gnu.org)
1f83c67b-6f75-3d74-233f-4677b4bbac0f@zoho.com
On 04/07/17 16:24, Ludovic Courtès wrote:
Toggle quote (13 lines)> Hi!>> sirgazil <sirgazil@zoho.com> skribis:>>> 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).> Ouch, that’s no good. The web site itself needs a few packages of> course; if you do ‘guix pull’ (the CPU-intensive part) and then “guix> build -f guix.scm” in the website directory, that should build the thing> and download the prerequisites.
The computer didn't made it through guix pull.
Toggle quote (4 lines)> If that goes wrong, I guess I’ll allocate time for this maybe next week> and ask for guidance (every else is welcome to help!).>
I'll see if I can do something about the thermal grease.
-- https://sirgazil.bitbucket.io/
L
L
Ludovic Courtès wrote on 29 Jul 2017 19:53
(name . sirgazil)(address . sirgazil@zoho.com)(address . 26006@debbugs.gnu.org)
87bmo3i0zk.fsf@gnu.org
Hi sirgazil,
Sorry for the looong delay. I’ve finally incorporated the new web sitein the guix-artwork.git repo along with a couple of fixes:
https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/log/?h=wip-website-update
I think it’s mostly ready to go. There are a few things missing frompackage pages:
• The gnu icon next to GNU packages; it’d be easy to re-introduce, but I’m not sure whether/how it could fit well in the page design.
• The JS build status icons. Likewise, I’m not sure how to make it look good on package pages.
• The reproducibility and issue pages, but we’ve disabled them recently anyway for performance reasons.
Thoughts?
I guess none of these are blockers, though.
Thanks,Ludo’.
S
S
sirgazil wrote on 2 Aug 2017 00:13
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 26006@debbugs.gnu.org)
ee8574c1-57bd-3302-62c8-ae28f65318e3@zoho.com
On 29/07/17 12:53, Ludovic Courtès wrote:
Toggle quote (2 lines)> Hi sirgazil,
Hi Ludo,
Toggle quote (5 lines)> Sorry for the looong delay. I’ve finally incorporated the new web site> in the guix-artwork.git repo along with a couple of fixes:>> https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/log/?h=wip-website-update
No problem :)
Toggle quote (6 lines)> I think it’s mostly ready to go. There are a few things missing from> package pages:>> • The gnu icon next to GNU packages; it’d be easy to re-introduce, but> I’m not sure whether/how it could fit well in the page design.
I forgot to design that part, but I'd try appending a text like "This package is part of GNU" to the package description, and maybe adding a translucent GNU head in the background of the package box (top-right).
Toggle quote (3 lines)> • The JS build status icons. Likewise, I’m not sure how to make it> look good on package pages.
I designed an alternative representation of build status. It is in designs/packages.svg, but here is an image:
https://multimedialib.files.wordpress.com/2017/08/package-with-issues.png
Toggle quote (3 lines)> • The reproducibility and issue pages, but we’ve disabled them> recently anyway for performance reasons.
Then I'd remove them from the main menu and the packages sidebar for now.
Toggle quote (4 lines)> Thoughts?>> I guess none of these are blockers, though.
I'd love to apply the missing changes myself, but I'm currently lacking a guix-enabled computer. But, yes, I think these things should not stop a website update.

P. S.: I hope the new code was not a pain in the neck deal with. I'm sorry if it is :P
-- https://sirgazil.bitbucket.io/
N
(name . Ludovic Courtès)(address . ludo@gnu.org)
20171001110213.kb2tz26yyntchonk@abyayala
Hi,
what's missing for this branch to be merged? I took a quick build on this(and because I like the code as a reference), and it looks good. Builds,maybe some changes from master have to be applied to it (like usinghttps instead of http at the download URLs).
Anything missing we could help out with?-- ng0GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588GnuPG: https://krosos.org/dist/keys/https://www.infotropique.orghttps://krosos.org
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlnQyzUACgkQ4i+bv+40hYiCrQ/8CasDPZLpxYhni7+2MnJVFxjgFtTdM+xRuiLTh1zcyZ5U3dgDPFAVHMhyTrn3Oc+HaVYAZKaNw3D4p8m1r0TjYN9I1bmXCP3Jqusy1RuXpr/W/skwX1rQh4vHivgRM1vDInghyDM6qiV39s1pCPR2pUTF5p3pWNaVASvfnBYps2accS7KhBBsxlKLYrbeGSr1sk2T892a65aMTKTJQ4GqY9PhEtSrzsOfADkpaYBQf6VQNpuX4Sxac3cRfnPl5MnRBTGfYE2bVLdISEvWU+StnXqvsIaxLSLFGxJpiG7wGMwpOts4o8fOeud1hD0SmJzrqLpVa9lNa02usGjCcR0GAh/TmgWgfXQRamyJgDNgiUXEOOskzfwOg/tF4xzBXObFF9A/ea5hHFiiUYaAihuXzPwaYH9/Tg9inWGy/Q8s7UqJGsI2X0bTeB1yeBnToMoNqsu6j2NuN9oVG15AW+oXuvBx7r0mTz8RDC0QdegE6wf7zA8+Xe7J0fkOR1/tOdIR3MLrdZ9lpTUN2GG6PAd5I9ovzKfV0CCFcy3vXTSCaAQCCNmYQZ6MK933g5P2/Wg8k1An99MvKl2HSdMkuKzeupEUpe6t0HVhMfud+RjtBNvDYsbZcXLZwicfyttl8hIVy3+9L7IklK6Gsr6CzzO9IVTTxBg0FSf4IDv1SGh8am8==g+L0-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 2 Oct 2017 09:50
(name . ng0)(address . ng0@infotropique.org)
87zi9aq989.fsf@gnu.org
Hello ng0,
ng0 <ng0@infotropique.org> skribis:
Toggle quote (7 lines)> what's missing for this branch to be merged? I took a quick build on this> (and because I like the code as a reference), and it looks good. Builds,> maybe some changes from master have to be applied to it (like using> https instead of http at the download URLs).>> Anything missing we could help out with?
Sure, not that much is missing. I must say that I’m really sorry thatwe failed to move forward on this after all the great work sirgazil did!
IIRC one of the problems is that the /packages page by default shows allpackages, which is too much. We should fix that.
Then I think there were tiny issues here and there, nothing big though(since the new site was written from scratch, some of the fine-tuning wedid on the old one was lost.)
Last, we’ll need to setup redirects for the old blog post URLs, andperhaps for a few other pages.
If you could build it, browse it, report/fix issues, and identifyredirects that need to be made, that would help tremendously! I’ve feltlonely while working on it, so I’m really happy if you can take a closerlook. ;-)
Let’s team up and get this done!
Thanks,Ludo’.
N
(name . Ludovic Courtès)(address . ludo@gnu.org)
20171002083633.4byszg6mn6ywdiq3@abyayala
Ludovic Courtès transcribed 1.2K bytes:
Toggle quote (34 lines)> Hello ng0,> > ng0 <ng0@infotropique.org> skribis:> > > what's missing for this branch to be merged? I took a quick build on this> > (and because I like the code as a reference), and it looks good. Builds,> > maybe some changes from master have to be applied to it (like using> > https instead of http at the download URLs).> >> > Anything missing we could help out with?> > Sure, not that much is missing. I must say that I’m really sorry that> we failed to move forward on this after all the great work sirgazil did!> > IIRC one of the problems is that the /packages page by default shows all> packages, which is too much. We should fix that.> > Then I think there were tiny issues here and there, nothing big though> (since the new site was written from scratch, some of the fine-tuning we> did on the old one was lost.)> > Last, we’ll need to setup redirects for the old blog post URLs, and> perhaps for a few other pages.> > If you could build it, browse it, report/fix issues, and identify> redirects that need to be made, that would help tremendously! I’ve felt> lonely while working on it, so I’m really happy if you can take a closer> look. ;-)> > Let’s team up and get this done!> > Thanks,> Ludo’.
Aside: I wasn't able to make use of the guix build -f build.scmfor my adaption of its code basebut haunt build on its own worked. The build.scm wascomplaining about this:
user@abyayala ~/src/krosos.org$ guix build -f build.scmsubstitute: updating list of substitutes from 'https://berlin.guixsd.org'... 100.0%substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%The following derivation will be built: /gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv@ build-started /gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv - x86_64-linux /var/log/guix/drvs/jp//qazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv.bz2Backtrace: 9 (primitive-load "/tmp/guix-build-gexp.drv-0/haunt.scm")In ice-9/eval.scm: 721:20 8 (primitive-eval (use-modules ((apps base builder) # …) …))In ice-9/psyntax.scm: 1234:36 7 (expand-top-sequence ((use-modules ((apps base …) …) …)) …) 1181:24 6 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …) 284:10 5 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)In ice-9/boot-9.scm: 3369:20 4 (process-use-modules _) 230:17 3 (map1 (((apps base builder) #:prefix base:) ((# …) …) …)) 3370:31 2 (_ ((apps base builder) #:prefix base:)) 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)In unknown file: 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)
ERROR: In procedure scm-error:ERROR: no code for module (apps base builder)`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/deploy.sh' -> `./deploy.sh'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/haunt.scm' -> `./haunt.scm'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/build.scm' -> `./build.scm'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/.gitignore' -> `./.gitignore'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/COPYING' -> `./COPYING'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/guix.packages' -> `./guix.packages'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/guix.scm' -> `./guix.scm'`/gnu/store/g0f0rsway1cik45kwdwbxfmqpv6nmqyg-krosos-web-site/README' -> `./README'builder for `/gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv' failed to produce output path `/gnu/store/0n9cp4djm8r3gpcdmbbnc2lgcxdicjm1-gexp'@ build-failed /gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv - 1 builder for `/gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv' failed to produce output path `/gnu/store/0n9cp4djm8r3gpcdmbbnc2lgcxdicjm1-gexp'guix build: error: build failed: build of `/gnu/store/jpqazlp2jh66q1yqsxasiqfkwjlx6pcr-gexp.drv' failed

Same for guix-artwork/website:
user@abyayala ~/re-src/guix-artwork/website$ guix build -f build.scmsubstitute: updating list of substitutes from 'https://berlin.guixsd.org'... 100.0%substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%The following derivation will be built: /gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv@ build-started /gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv - x86_64-linux /var/log/guix/drvs/z8//h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv.bz2Backtrace: 9 (primitive-load "/tmp/guix-build-gexp.drv-0/haunt.scm")In ice-9/eval.scm: 721:20 8 (primitive-eval (use-modules ((apps base builder) # …) …))In ice-9/psyntax.scm: 1234:36 7 (expand-top-sequence ((use-modules ((apps base …) …) …)) …) 1181:24 6 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …) 284:10 5 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)In ice-9/boot-9.scm: 3369:20 4 (process-use-modules _) 230:17 3 (map1 (((apps base builder) #:prefix base:) ((# …) …) …)) 3370:31 2 (_ ((apps base builder) #:prefix base:)) 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)In unknown file: 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)
ERROR: In procedure scm-error:ERROR: no code for module (apps base builder)`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/haunt.scm' -> `./haunt.scm'`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/build.scm' -> `./build.scm'`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/.gitignore' -> `./.gitignore'`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/COPYING' -> `./COPYING'`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/guix.packages' -> `./guix.packages'`/gnu/store/cl6zzsjmmq8709zws6zcn0q5vhdz2rfs-guix-web-site/README' -> `./README'builder for `/gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv' failed to produce output path `/gnu/store/cfiba1yi2bdfd019sdiljm5j2a41v0bb-gexp'@ build-failed /gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv - 1 builder for `/gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv' failed to produce output path `/gnu/store/cfiba1yi2bdfd019sdiljm5j2a41v0bb-gexp'guix build: error: build failed: build of `/gnu/store/z8h6fkc6wnimdpd3sj2gzfbrwa94v2qh-gexp.drv' failed-- ng0GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588GnuPG: https://krosos.org/dist/keys/https://www.infotropique.orghttps://krosos.org
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlnR+pEACgkQ4i+bv+40hYht+BAAnoiUbGDvR/WeWZIRJ9g/ImkdcShC1UN+FW9j6nzf7LapZUxuagJkVekRp3gIQsxpF9g5rPPUdwXaPcDswDioM/rU78a10ZjXBiqvbtpRtQVjyPHUvEwHUzUQ6X77lr0TL8il5nP9O6IeONXldhrBibLaIUmaIDLKGHEdvf+AVqJF8Y+sUvjycItwl1zJlnnETsF7T3jZrWbl+ElINJwMCbH1GOY4dRRptQ80yJKxjhA+NCuP0ZNamTM7BiH5MU4Dod7AoZXEBCESO+zuor5MvI/EXSBnPN3IgITWn+2lgzPl2SXJIsxS/iS4eQC6aECCnGV4OAfk6pId630204j6SlKD3C6wQyWmpk3EKWbJ2f29j0Hm0XzCrEpyFmgI3TS2/zopYVN3JGtsBzgz7q6UjWHeJshxKG5mt18xKq71Sb8VrSDFWQbZTrrIOMTmMYuPA6zEUyb45wMNPjTVdbfxssubeRlv6V1ffWryNoL4i6WEZVeRAN22wCo7kc2Qc7R7go/iWZjWxfYZJPRg2lwHgKHifhmRTT06ur+b1OuiUnuWzlWgWvQ2poLVq1myp9RKLUIwmyRzR/OaBDH6gkU49AAeB9QNK0Rxgm8dBuiCu6YkgtDMDE33sKtU7VytdVF1MVhN2wYxzE4OVnhWB3MoNI/nNXDHWTFXIVBXVD+4j5g==USZg-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 2 Oct 2017 11:10
(name . ng0)(address . ng0@infotropique.org)
87mv59rk37.fsf@gnu.org
ng0 <ng0@infotropique.org> skribis:
Toggle quote (5 lines)> I wasn't able to make use of the guix build -f build.scm> for my adaption of its code base> but haunt build on its own worked. The build.scm was> complaining about this:
Yep, you even opened a bug about it. :-)
For now I suggest using “haunt build”.
Ludo’.
L
L
Ludovic Courtès wrote on 6 Dec 2017 18:10
New web site is on line!
(name . sirgazil)(address . sirgazil@zoho.com)(address . 26006@debbugs.gnu.org)
87k1xz93zb.fsf_-_@gnu.org
Hello!
It’s embarrassing that it took us so long, but I’m happy to say that thenew web site is on line!
https://www.gnu.org/software/guix/
I’ve created redirects from the old /news URLs to the new /blog URLs,using the oh-so-elegant script below (I can’t believe it’s not Scheme!).
Please report:
• broken links;
• other pages that need a redirect;
• information that disappeared—I’m thinking in particular of talks, which used to appear under /help, but are now supposed to be made available via a blog post, the advantage being that we get /blog/tag/TOPIC links to the post;
• anything else that’s broken.
For web design issues, I hope sirgazil or someone else can answer andtake action—I’m still not much of a web person and it’s probably betterfor everyone when I stick to writing Scheme. ;-)
Note that the cron job that used to update package pages fromhydra.gnu.org is now broken. I’ll try to come up with something elsewith proper GuixSD integration and run it from berlin.guixsd.org.
Thanks again sirgazil for all the work!
Ludo’.
#!/bin/sh
function gen_redirect{ TARGET_URL="$1" cat <<EOF<!DOCTYPE html><html lang="en"> <head> <meta charset="UTF-8" /> <title>Page has moved! — GNU Guix</title> <noscript><meta http-equiv="refresh" content="0; url=$TARGET_URL"></noscript> </head> <body onload="window.location = '$TARGET_URL';"> Redirecting to the new page location... </body></html>EOF}
URL_PREFIX="/software/guix/"
for page in "$@"do page_without_extension="`echo $page | sed -es'/\.html$//g'`" new_page="`find ../blog -name $page_without_extension -type d | head -1`" if [ -z "$new_page" ] then echo "no new page for '$page'" >&2 exit 1 fi
# Strip '../'. new_page_url="$URL_PREFIX`echo $new_page | cut -c 4-`"
echo "redirect '$page' -> '$new_page_url'" gen_redirect "$new_page_url" > "$page".new && mv "$page".new "$page"done
L
L
Ludovic Courtès wrote on 6 Dec 2017 18:11
control message for bug #26006
(address . control@debbugs.gnu.org)
87indj93xe.fsf@gnu.org
tags 26006 fixedclose 26006
A
A
Alex Sassmannshausen wrote on 6 Dec 2017 18:55
Re: bug#26006: New web site is on line!
(name . Ludovic Courtès)(address . ludo@gnu.org)
87indjbv2j.fsf@pompo.co
Wow, that looks super cool, well done!
Really smooth and modern feel. Joyful to explore :-)
Ludovic Courtès writes:
Toggle quote (73 lines)> Hello!>> It’s embarrassing that it took us so long, but I’m happy to say that the> new web site is on line!>> https://www.gnu.org/software/guix/>> I’ve created redirects from the old /news URLs to the new /blog URLs,> using the oh-so-elegant script below (I can’t believe it’s not Scheme!).>> Please report:>> • broken links;>> • other pages that need a redirect;>> • information that disappeared—I’m thinking in particular of talks,> which used to appear under /help, but are now supposed to be made> available via a blog post, the advantage being that we get> /blog/tag/TOPIC links to the post;>> • anything else that’s broken.>> For web design issues, I hope sirgazil or someone else can answer and> take action—I’m still not much of a web person and it’s probably better> for everyone when I stick to writing Scheme. ;-)>> Note that the cron job that used to update package pages from> hydra.gnu.org is now broken. I’ll try to come up with something else> with proper GuixSD integration and run it from berlin.guixsd.org.>> Thanks again sirgazil for all the work!>> Ludo’.>> #!/bin/sh>> function gen_redirect> {> TARGET_URL="$1"> cat <<EOF> <!DOCTYPE html>> <html lang="en">> <head>> <meta charset="UTF-8" />> <title>Page has moved! — GNU Guix</title>> <noscript><meta http-equiv="refresh" content="0; url=$TARGET_URL"></noscript>> </head>> <body onload="window.location = '$TARGET_URL';">> Redirecting to the new page location...> </body>> </html>> EOF> }>> URL_PREFIX="/software/guix/">> for page in "$@"> do> page_without_extension="`echo $page | sed -es'/\.html$//g'`"> new_page="`find ../blog -name $page_without_extension -type d | head -1`"> if [ -z "$new_page" ]> then> echo "no new page for '$page'" >&2> exit 1> fi>> # Strip '../'.> new_page_url="$URL_PREFIX`echo $new_page | cut -c 4-`">> echo "redirect '$page' -> '$new_page_url'"> gen_redirect "$new_page_url" > "$page".new && mv "$page".new "$page"> done
A
A
Adonay Felipe Nogueira wrote on 6 Dec 2017 23:10
(address . bug-guix@gnu.org)
87a7yvqzhy.fsf@hyperbola.info
This is of course minor issue but we just have to insert propercopyright + license notices in the .scm files. ;)
2017-12-06T18:10:48+0100 Ludovic Courtès wrote:
Toggle quote (75 lines)> Hello!>> It’s embarrassing that it took us so long, but I’m happy to say that the> new web site is on line!>> https://www.gnu.org/software/guix/>> I’ve created redirects from the old /news URLs to the new /blog URLs,> using the oh-so-elegant script below (I can’t believe it’s not Scheme!).>> Please report:>> • broken links;>> • other pages that need a redirect;>> • information that disappeared—I’m thinking in particular of talks,> which used to appear under /help, but are now supposed to be made> available via a blog post, the advantage being that we get> /blog/tag/TOPIC links to the post;>> • anything else that’s broken.>> For web design issues, I hope sirgazil or someone else can answer and> take action—I’m still not much of a web person and it’s probably better> for everyone when I stick to writing Scheme. ;-)>> Note that the cron job that used to update package pages from> hydra.gnu.org is now broken. I’ll try to come up with something else> with proper GuixSD integration and run it from berlin.guixsd.org.>> Thanks again sirgazil for all the work!>> Ludo’.>> #!/bin/sh>> function gen_redirect> {> TARGET_URL="$1"> cat <<EOF> <!DOCTYPE html>> <html lang="en">> <head>> <meta charset="UTF-8" />> <title>Page has moved! — GNU Guix</title>> <noscript><meta http-equiv="refresh" content="0; url=$TARGET_URL"></noscript>> </head>> <body onload="window.location = '$TARGET_URL';">> Redirecting to the new page location...> </body>> </html>> EOF> }>> URL_PREFIX="/software/guix/">> for page in "$@"> do> page_without_extension="`echo $page | sed -es'/\.html$//g'`"> new_page="`find ../blog -name $page_without_extension -type d | head -1`"> if [ -z "$new_page" ]> then> echo "no new page for '$page'" >&2> exit 1> fi>> # Strip '../'.> new_page_url="$URL_PREFIX`echo $new_page | cut -c 4-`">> echo "redirect '$page' -> '$new_page_url'"> gen_redirect "$new_page_url" > "$page".new && mv "$page".new "$page"> done>
-- - https://libreplanet.org/wiki/User:Adfeno- Palestrante e consultor sobre /software/ livre (não confundir com gratis).- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar instantaneamente comigo no endereço abaixo.- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft Office, MP3, MP4, WMA, WMV.- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF (apenas sem DRM), PNG, TXT, WEBM.
A
A
Adonay Felipe Nogueira wrote on 6 Dec 2017 23:10
(address . bug-guix@gnu.org)
87609jqzgs.fsf@hyperbola.info
+1
2017-12-06T18:55:00+0100 Alex Sassmannshausen wrote:
Toggle quote (4 lines)> Wow, that looks super cool, well done!>> Really smooth and modern feel. Joyful to explore :-)>
S
S
sirgazil wrote on 7 Dec 2017 04:01
Re: New web site is on line!
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 26006@debbugs.gnu.org)
ed96410e-15db-d238-2ac6-43e313c6d015@zoho.com
Hey!
On 06/12/17 12:10, Ludovic Courtès wrote:
Toggle quote (8 lines)> Hello!> > It’s embarrassing that it took us so long, but I’m happy to say that the> new web site is on line!> > https://www.gnu.org/software/guix/

It's fine. We need more human resources.
Thank you for taking care it, Ludo :)
L
L
Ludovic Courtès wrote on 7 Dec 2017 09:54
Re: bug#26006: New web site is on line!
(name . Adonay Felipe Nogueira)(address . adfeno@hyperbola.info)(address . 26006@debbugs.gnu.org)
87bmjaex51.fsf@gnu.org
Hello,
Adonay Felipe Nogueira <adfeno@hyperbola.info> skribis:
Toggle quote (3 lines)> This is of course minor issue but we just have to insert proper> copyright + license notices in the .scm files. ;)
sirgazil explicitly waived copyright interest on their work, which iswhy many files only have a short notice as opposed to the usual AGPLheader. But I think each file has a (non-)copyright notice. Or did youfind one without anything?
Ludo’.
C
C
Chris Marusich wrote on 7 Dec 2017 10:16
(name . Ludovic Courtès)(address . ludo@gnu.org)
87374mhp8g.fsf@gmail.com
ludo@gnu.org (Ludovic Courtès) writes:
Toggle quote (4 lines)> I’m happy to say that the new web site is on line!>> https://www.gnu.org/software/guix/
Awesome! It looks really nice!
-- Chris
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlopBwAACgkQ3UCaFdgiRp0JqA/5AYiQSLlJJWJhO7QBR8B35HAUdSsQ2eFflWxfalIekGOLwbz/N4ftO50ypMxHQzY0RCoNx3MtpclflDbpWS1oXVQ1LnoIJlWhK2ge1vZqQsKzqRJAzUw4mT8pVpIHGV7AUaTtoCcMu6FboLWyKk9BPFdkQKrMD61ZyuBAhlnsv/9I6VKdlbTJnM+wZwcFqZs/gYPx75bmEiLSfuEhfvuRxXPmGscpF2/dKNtkhL5ISSD02Tz74MvK9IRQNCnyOVMLGN9LNaY2yELytcjDQt4Gwf1yWxRskFH/aYsXtDoWY2Bp3T73KRFWpGyvu3n7vsNCOF36lIueTrdwJddhDCiuVtRAq8heslFMHRIphUgIXhR6mMjlpp7W3WkebqKHNnrZhaR3kfJAdNklnBKGWO8rSSqELdiSHL3yerCeLkBT7bG7y6u8K2xpn/3NFCgvvkyOuNFgyRaedFAMnW4B65G6Qwa9YPKRjwg0rpEShgn0d0x7tCmu5EZYkecpkxubId2YSYhDQrBJrn85d/2t4j9iTr6nQAFBBPNJIxulsr4qleeZNirry8WfatRN6dCCP1U4viRNFqdb1UtOUgP9ajcV9MTGzqSI3Y96on9oP90aEl6eQdv1Q8ea9vTGH6q5g39DTvM6aIriuXaYThym1T8cWPy/EACOgSCDrW5FTVTkvGc==nICZ-----END PGP SIGNATURE-----
P
P
pelzflorian (Florian Pelz) wrote on 7 Dec 2017 18:10
(name . Ludovic Courtès)(address . ludo@gnu.org)
20171207171053.GA4332@floriannotebook.localdomain
Nice website!
On Wed, Dec 06, 2017 at 06:10:48PM +0100, Ludovic Courtès wrote:
Toggle quote (14 lines)> Please report:> > • broken links;> > • other pages that need a redirect;> > • information that disappeared—I’m thinking in particular of talks,> which used to appear under /help, but are now supposed to be made> available via a blog post, the advantage being that we get> /blog/tag/TOPIC links to the post;> > • anything else that’s broken.>
I believe there is a typo on the home page below the video. „leave“should be „live“:
Toggle diff (16 lines)diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scmindex bf727dd..f7c2d1c 100644--- a/website/apps/base/templates/home.scm+++ b/website/apps/base/templates/home.scm@@ -196,7 +196,7 @@ (p "GNU Guix won't interfere with the package manager that comes- with your distribution. They can leave together."))+ with your distribution. They can live together.")) (div (@ (class "action-box centered-text"))
Regards,Florian
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEwRjGsqAMqXB4uw3y3T6EbElHBVsFAlopdhgACgkQ3T6EbElHBVuSyxAAiyZr+lyRC+fwd3wSDNkVpAXeCJs51kiWJ1AfCPLhscEaftHNdNYwvYiKHUYjyvBtuoWMwRS9E1K1lcVAXseE74zcP2hUPBlaeo7ZwqqB+yxa6MKvZXVZAvBexhOGeS6MRdZdev81kA1Cckbtv6fJ90Hw3SUJH9oa5bSOpNtS0DpRT2KfBzxRrfnmWj/gsX99+W7/RjTSX1iwmBbkFk4E18t+zi12+2UhDM7H6Envk22DHCkAmd9kHyle/66aRy/rN29y6KxRQeGzBqENbhPqCA0QO8gUlCXgik2OE5kX/d6gnFYEXGmeAJnbNtQztEJ3hI6sPc1YTrLbNjt7jkrAc50N7/kRzO/4iSH3o1bHuaNH+jO0JL1VNdZ6831aEtTEfsyDGTglroV0eUx4yhfdUzqV6Jp5jBYzEJpxXZEpO1Jfxvc2JelJHwndT/kgfZa1INsW0KdD7brYaspbiORfmY87u5quNXk8wr/S1mwdonAnQyV83REdNnKUl7WE+IURee2iXMojTxqy1SUX896bSWezydwH8yA0zOWoRG6rvmWoIq3TxF15scopvhcsAnvgZkJp6QxxSCMPT6+iLvuKDYrKuV4J3Z9oS7sSMihpvAPgCeZeIUp1Z9GNbNHrXJ5wMZG3F5xvO9RocsddH6SlGFTq24uEoqP87UGP/niu0EY==GRrn-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 7 Dec 2017 21:58
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)
87374mdzlx.fsf@gnu.org
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
Toggle quote (14 lines)> I believe there is a typo on the home page below the video. „leave“> should be „live“:>> diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm> index bf727dd..f7c2d1c 100644> --- a/website/apps/base/templates/home.scm> +++ b/website/apps/base/templates/home.scm> @@ -196,7 +196,7 @@> > (p> "GNU Guix won't interfere with the package manager that comes> - with your distribution. They can leave together."))> + with your distribution. They can live together."))
Indeed! Will push shortly.
Thanks,Ludo’.
Q
Q
Quiliro Ordonez Baca wrote on 8 Dec 2017 19:42
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)
87374l5aek.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
Toggle quote (18 lines)>> I believe there is a typo on the home page below the video. „leave“> should be „live“:>> diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm> index bf727dd..f7c2d1c 100644> --- a/website/apps/base/templates/home.scm> +++ b/website/apps/base/templates/home.scm> @@ -196,7 +196,7 @@> > (p> "GNU Guix won't interfere with the package manager that comes> - with your distribution. They can leave together."))> + with your distribution. They can live together."))> > (div> (@ (class "action-box centered-text"))
Did you write this patch by hand or did you use some kind of help? Ifyou got help from something such as Emacs, I would like to learn how youdid it so I can contribute with patches to easy stuff such as typos,website and documentation.
P
P
pelzflorian (Florian Pelz) wrote on 8 Dec 2017 20:07
(name . Quiliro Ordonez Baca)(address . quiliro@riseup.net)
20171208190717.GA1738@floriannotebook.localdomain
On Fri, Dec 08, 2017 at 01:42:27PM -0500, Quiliro Ordonez Baca wrote:
Toggle quote (25 lines)> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:> >> > I believe there is a typo on the home page below the video. „leave“> > should be „live“:> >> > diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm> > index bf727dd..f7c2d1c 100644> > --- a/website/apps/base/templates/home.scm> > +++ b/website/apps/base/templates/home.scm> > @@ -196,7 +196,7 @@> > > > (p> > "GNU Guix won't interfere with the package manager that comes> > - with your distribution. They can leave together."))> > + with your distribution. They can live together."))> > > > (div> > (@ (class "action-box centered-text"))> > Did you write this patch by hand or did you use some kind of help? If> you got help from something such as Emacs, I would like to learn how you> did it so I can contribute with patches to easy stuff such as typos,> website and documentation.>
That would be great.
The above is part of the output from the „git diff“ shell commandafter I changed the /website/apps/base/templates/home.scm file in theguix-artwork.git from Savannah.
For a real patch you could use „git format-patch“ to create an e-mailfile which you can open in your e-mail program and then send. Thereare tutorials on-line. Use „git am“ to apply such a patch fromsomeone else after you saved their e-mail to a file. (There also areother methods like „git send-email“, „git am“ and so on.)
Emacs also has Git integration, but I am not familiar with it.
Regards,Florian
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEwRjGsqAMqXB4uw3y3T6EbElHBVsFAloq4uAACgkQ3T6EbElHBVuyjQ//T8xfiwwdvnYhZJZ9PZiYo8g5MkIdwZ3pLCpmQOnS4Fwr5UYJqYZTFxGJSTkbqI0fCHpNWv2L+ftHjaEDSDOyKffZ6x6eME8ejzPnXIO+1yT3gbdZYq9WizN0g4ok6LaCTvwARpW0nX4mtAx59J4ip4w9/WmWVDA8cm6lClVUrNMrj+Q2IEOklU/l5T9QKyT6tpkUGcF3Hmhcmk8Q/H1JLfyGotbNK9XazcOlRFwRH3ELxdranOep9iCvf/E7V6Zui1JyPJEIxwjsZwESVpM5rrZnZB8x+40eJSNFl1I5RoeU7pdlu9zvvV6L4LfU6CXdIByOfzfeL2UqYA1hrolIt5B46JRzkIJ4nwwHeP9uliTfJMJvfyXC+aOdsIGjwaYTZkh23A2xXxhGR8IQGJdw3/x/FSJx+AxkOcMHWpwkeaDYwnPu6HsY7uImLm0yUypR60L52+2TIaxUUfKm/oRuzHlgr87LjJFhSZk6z5T+gwBM5mNKdbi5VQx267PFznhgWMlj9KFx5ywXQN9oHwfUynmL/R2sFcxJOcgsRBwC3gTT/Ud54PK8pm12QJ9U/68k/4r3iGUEo87FcpEYC9g/jDjBFCM5q8au/86VQrzABNZHrrWfaRpcJ2S6u5cIoiy1tgAvepkjOFxU29HXtAvg5+QxnAjM78zBGN6QW+MDzbI==g648-----END PGP SIGNATURE-----

?
Your comment

This issue is archived.

To comment on this conversation send email to 26006@debbugs.gnu.org