From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: aspell-el added
Date: Sun, 03 Nov 2019 23:41:43 +0100 [thread overview]
Message-ID: <20191103224143.USyDnX4k4F_kVb_mK4sAK4GBj0bXGjyxyq5RJvEpNwY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16043@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]
New comment by flexibeast on void-packages repository
https://github.com/void-linux/void-packages/pull/16043#issuecomment-549186824
Comment:
Thanks for your feedback!
i'm actually new to Void myself: i've only just started contributing, primarily in the area of documentation (though i've also added a package, `hunspell-en_AU`, in #13620). So i'm not one of the Void devs, and i can't comment on everything you've mentioned; but i can speak to some of the things you mentioned.
> what is xbump and where is the manual?
`xbump` is part of the `xtools` package; the man page for `xtools` says:
> xbump pkgname [git commit options] – Git commit a version bump
Could you please point to the place where `xbump` was mentioned but not explained?
> you need a forum for each subporject (like the documentation
This is already in place: see the projects listed at https://github.com/void-linux/, amongst which is the void-docs project, which has its own issue tracker.
> Also there is a wiki-void but link is not in the main site, why? how do you expect ppl to find this?
This is deliberate, as the wiki is deprecated; see [issue #104 in the void-docs repo](https://github.com/void-linux/void-docs/issues/104). i agree that whilst the wiki is still online and visible to search engines, it would be good to let people know that it should no longer be used. Myself and @bobertlo have made some suggestions about this ([here](https://github.com/void-linux/void-docs/issues/104#issuecomment-529082008) and [here](https://github.com/void-linux/void-docs/issues/104#issuecomment-546606159)), but as Void is a volunteer-run project, it relies on the relevant Void devs having the time and space to address these suggestions.
> The void site need to be rewritten with the major resources on the top.
Well, the navigation bar at the top of the Void home page has a "Documentation" entry which links to https://docs.voidlinux.org/; and, yeah, the wiki is not listed alongside it because the wiki is no longer considered an official resource.
next prev parent reply other threads:[~2019-11-03 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 1:13 [PR PATCH] " voidlinux-github
2019-11-02 4:15 ` voidlinux-github
2019-11-02 14:05 ` voidlinux-github
2019-11-02 14:05 ` [PR PATCH] [Closed]: " voidlinux-github
2019-11-02 23:01 ` voidlinux-github
2019-11-03 4:28 ` voidlinux-github
2019-11-03 15:16 ` voidlinux-github
2019-11-03 22:41 ` voidlinux-github [this message]
2019-11-04 0:30 ` voidlinux-github
2019-11-04 14:43 ` voidlinux-github
2019-11-05 6:05 ` voidlinux-github
2019-11-05 8:04 ` voidlinux-github
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=20191103224143.USyDnX4k4F_kVb_mK4sAK4GBj0bXGjyxyq5RJvEpNwY@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).