From: Julien Lepiller <julien@lepiller.eu>
To: "Luis Felipe" <luis.felipe.la@protonmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: "48637@debbugs.gnu.org" <48637@debbugs.gnu.org>
Subject: [bug#48637] [PATCH] website: Add publications page
Date: Wed, 02 Jun 2021 16:28:13 -0400 [thread overview]
Message-ID: <731A5D86-9FBB-4F0F-B139-7AA29B3A6109@lepiller.eu> (raw)
In-Reply-To: <4jhiBWvAzsdTXmZFj_GgZTPWkIZncoQeId2pbbzXXMRNFk0FPGJXxIrp8ysGXNwuZk54pS5l5Ba2jkRcqE8omsfVgItw1gMcDJW1tqMPn-M=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
The patch looks good, but how would people out of science understand what's a conference paper, or the difference between an article and a journal article? Are there better terms?
Le 2 juin 2021 15:31:50 GMT-04:00, Luis Felipe via Guix-patches via <guix-patches@gnu.org> a écrit :
>Hey,
>
>On Friday, May 28, 2021 11:06 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I see that you want to keep it open to non-academic publications,
>which
>> is a good idea. I wonder if there should be a visual distinction
>> between peer-reviewed scientific articles, journal articles, and
>other
>> types of publications?
>>
>> I started adding historical LWN articles (patch below; the titles
>look
>> funny in hindsight :-)), and wondered whether this was a good idea
>since
>> they would come first in the list.
>>
>> Thoughts?
>
>
>Here is a patch that adds publication types.
[-- Attachment #2: Type: text/html, Size: 1275 bytes --]
next prev parent reply other threads:[~2021-06-02 20:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 23:35 [bug#48637] [PATCH] website: Add publications page Luis Felipe via Guix-patches via
2021-05-25 13:44 ` pelzflorian (Florian Pelz)
2021-05-25 14:37 ` Luis Felipe via Guix-patches via
2021-05-25 18:21 ` pelzflorian (Florian Pelz)
2021-05-25 19:46 ` Luis Felipe via Guix-patches via
2021-05-25 19:58 ` Julien Lepiller
2021-05-25 20:16 ` Luis Felipe via Guix-patches via
2021-05-26 2:03 ` Julien Lepiller
2021-05-26 10:00 ` pelzflorian (Florian Pelz)
2021-05-26 14:06 ` Luis Felipe via Guix-patches via
2021-05-26 17:41 ` Julien Lepiller
2021-05-26 18:25 ` Luis Felipe via Guix-patches via
2021-05-26 18:42 ` Julien Lepiller
2021-05-26 19:05 ` Luis Felipe via Guix-patches via
2021-05-25 18:35 ` pelzflorian (Florian Pelz)
2021-05-25 19:14 ` Luis Felipe via Guix-patches via
2021-05-28 11:06 ` Ludovic Courtès
2021-05-28 15:20 ` Luis Felipe via Guix-patches via
2021-05-29 10:25 ` Ludovic Courtès
2021-06-02 19:31 ` Luis Felipe via Guix-patches via
2021-06-02 20:28 ` Julien Lepiller [this message]
2021-06-02 21:52 ` Luis Felipe via Guix-patches via
2021-06-02 23:28 ` Julien Lepiller
2021-06-03 9:40 ` Ludovic Courtès
2021-06-03 10:37 ` Julien Lepiller
2021-06-03 13:39 ` Luis Felipe via Guix-patches via
2021-06-03 19:50 ` Luis Felipe via Guix-patches via
2021-06-03 20:37 ` Ludovic Courtès
2021-06-03 21:50 ` Luis Felipe via Guix-patches via
2021-06-04 15:38 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=731A5D86-9FBB-4F0F-B139-7AA29B3A6109@lepiller.eu \
--to=julien@lepiller.eu \
--cc=48637@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=luis.felipe.la@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).