unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dsmich@roadrunner.com
To: "'Blake Shaw'" <blake@sweatshoppe.org>
Cc: "'Luis Felipe'" <luis.felipe.la@protonmail.com>,
	"'guile-user@gnu.org'" <guile-user@gnu.org>,
	"'Guix Devel'" <guix-devel@gnu.org>
Subject: RE: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?
Date: Tue, 28 Jun 2022 19:57:53 +0000	[thread overview]
Message-ID: <7b8a790bc50503116dd79e9aaf92d15d29dc27cc@webmail> (raw)

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

> From: "Blake Shaw" 
> Subject: Wiki && Re: [feature request] merge sxml->html from (haunt
html) into guile?
> 
> Since getting feedback on my presentation for Guix Days, where I
think a
 > lot of good criticism was raised, I've been thinking about ways to
organize
 > contributions to the docs. An idea I've had is to create a wiki
that has a
 > basic system of tags that can link with Mumi so that while folks
are
 > looking things up they can also get a sense if there are "TODOs"
concerning
 > a subject they reading up on, even beyond contributing to the docs.
Many
 > folks have expressed that they want to start chipping in, but
aren't quite
 > sure where to start. Perhaps something like this could help ease
that
 > process, and make updating information more dynamic and less
critical than
 > in the main docs.
> 
 > Any thoughts?

Spam! Spam! Spam!

Please plan on having some kind of controls in place to prevent
spammers.

-Dale



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

             reply	other threads:[~2022-06-28 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 19:57 dsmich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-29 22:19 Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile? Nathan Dehnel
     [not found] <CAKjmbcBO3YZSjD2zZvQ5Z21NGy78bO-d2FGBSPM=LD1nkwU1Kw@mail.gmail.com>
     [not found] ` <skHXeytJhh-XZOWnqaD3Qi1z6uaXri9bDjPfcSBLVCZWzpsrNHqQ_aKLFiKN9Hhd4T2Ftu8Fqk_P6R7sHcZ5kqnfrr6L3Xk7SBDBYar09f8=@protonmail.com>
2022-06-28 18:34   ` Blake Shaw
2022-06-28 20:13     ` Maxime Devos
2022-06-28 21:05       ` Maxime Devos
2022-06-29  3:26       ` bokr
2022-06-29  6:19       ` Dr. Arne Babenhauserheide

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=7b8a790bc50503116dd79e9aaf92d15d29dc27cc@webmail \
    --to=dsmich@roadrunner.com \
    --cc=blake@sweatshoppe.org \
    --cc=guile-user@gnu.org \
    --cc=guix-devel@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).