From: david larsson <david.larsson@selfhosted.xyz>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Ryan Prior <rprior@protonmail.com>, jgart <jgart@dismail.de>,
Maxime Devos <maximedevos@telenet.be>,
Guix Devel <guix-devel@gnu.org>,
Guix-devel
<guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org>
Subject: Re: developing javascript with guix
Date: Wed, 03 Aug 2022 16:26:04 +0200 [thread overview]
Message-ID: <cffda4b50d269ec0a56c561464704aa0@selfhosted.xyz> (raw)
In-Reply-To: <mhwV5r5YoT6ZMDnzRbPIc4rVUVwinpock6dLxWlAMLkY87oxmzHna_YHoH_LMH6AkkohiSDYP9aIArfczYZYrhPAfWKZ6m8hG7QbcQp_xq4=@protonmail.com>
On 2022-07-30 15:40, Luis Felipe wrote:
> Using the original design of Guix website, this information could be
> accessible from "Home page → Guix in Your Field → Software
> developement". Clicking on that button would take the user to a
> Software Development page, which would link to language specific
> information to integrate Guix in one's workflow. So there would be
> URLs like these:
>
> https://guix.gnu.org/en/software-development/
> https://guix.gnu.org/en/software-development/javascript/
> https://guix.gnu.org/en/software-development/python/
> https://guix.gnu.org/en/software-development/ruby/
>
> The "Guix in Your Field" idea seems kind of forsaken, but I think it
> is quite important.
>
I'd also like to have a place for this information collected and shared.
Another option, not to imply it's a better one, but maybe worth
considering, is the libreplanet guix wiki. I think that basically anyone
can edit the page there, and it would be a smaller barrier of entry to
contribute (for good and bad).
For guile development there's the information in help-guix with subject:
"Configuring geiser for load paths of Guix environment", that would be
useful to add.
For python: I have a setup with emacs, emacs-jedi and jupyter in a nice
way, and I was leaning towards just sharing it on some git repo of mine,
which would be a waste when it can be shared with a wider guix audience
if we had a set place for it. Personally, I'd be more likely to get
around to share it on the libreplanet wiki, than by sending a patch to
the guix website. Maybe the website can point to the correct wiki
subpage from the "software development" (in your field) page?
Best regards,
David
next prev parent reply other threads:[~2022-08-03 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 0:25 developing javascript with guix jgart
2022-07-27 9:33 ` Maxime Devos
2022-07-27 22:25 ` jgart
2022-07-27 23:15 ` Ryan Prior
2022-07-30 13:40 ` Luis Felipe
2022-07-30 16:04 ` bokr
2022-08-03 14:26 ` david larsson [this message]
2022-07-30 19:36 ` Maxime Devos
2022-07-30 19:44 ` Maxime Devos
2022-07-30 19:50 ` Maxime Devos
2022-07-30 20:22 ` Maxime Devos
2022-08-03 13:18 ` Giovanni Biscuolo
2022-07-30 19:35 ` Maxime Devos
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=cffda4b50d269ec0a56c561464704aa0@selfhosted.xyz \
--to=david.larsson@selfhosted.xyz \
--cc=guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=luis.felipe.la@protonmail.com \
--cc=maximedevos@telenet.be \
--cc=rprior@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).