From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 300] Documentation for the SOC
Date: Mon, 04 May 2020 13:12:38 +0000
Message-ID: <bug-300-13-mnjM90koHW@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-300-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=300
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #0)
> The SOC would benefit from good documentation.
> The wiki is likely not the appropriate place to host documentation.
>
> It seems a number of open source projects host documentation on a static
> site which build from a ./docs folder in the git repository.
> https://github.com/YosysHQ/nextpnr/tree/master/docs
> https://github.com/SymbiFlow/prjtrellis/tree/master/docs
> https://github.com/enjoy-digital/litex/tree/master/doc
this is because they are hosted on github.
> LibreSOC would benefit from following this convention.
> To accomplish this, a gitlab ci.yaml can be placed in the ./docs directory
> of soc.git. This way, it is at least possible to view documentation at
> Kazan-team.salsa.debian.io/docs. The documentation's bootstrap can also be
> modified to match libreSOC’s main site.
salsa is not under our control.
> It is probably fine to link to salsa from the wiki for now. We can always
> bring the static site directly onto libreSOC’s servers later.
we do not have time to discuss this right now.
the priority is to complete the tasks for the hard deadline.
closing this bugreport to indicate that we need to seriously prioritise
and not discuss extraneous non-critical tasks.
it can be re-opened when we have time.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:09 [libre-riscv-dev] [Bug 300] New: " bugzilla-daemon
2020-05-04 13:12 ` bugzilla-daemon [this message]
2020-05-07 6:29 ` [libre-riscv-dev] [Bug 300] " bugzilla-daemon
2020-06-01 19:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-300-13-mnjM90koHW@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git