<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><span></span><blockquote type="cite"><blockquote type="cite"><span>Maybe it is easier for</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>you to have an wiki and bugtracker like gitlab or gitlab, where</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>everybody can get the informations he need, show bugs, get infos about</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>bugs and ask questions to other users.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That's what the list is supposed to be for, though. Maybe it's just a</span><br></blockquote><blockquote type="cite"><span>matter of SNR?</span></blockquote></div><div><br></div><div>Just my two cents on matter based on personal experience:</div><div><br></div><div><b>Issue trackers:</b> I personally suspect as adoption increases the popular expectation will be for a more ticket oriented (i.e. Github like) experience for filing bugs and feature requests. For better or worse people seem to feel there’s a large commitment increase on their part from filing a ticket and being part of a community mailing list.</div><div><br></div><div><b>Wikis:</b> As for wikis, I always have had mixed feelings about them. For large projects like Gentoo or Arch they’re great, in my opinion, for community knowledge accumulation. But for smaller projects I’ve found having something to the effect of a community maintained `docs/` directory with markdown is just simpler and easier. Plus you can always go back and generate some pretty webpages out of the `docs/` markdown files if you’ve reached the adoption level where people expect documentation to be in webpages.</div><div><br></div><div>Cheers,</div><div>Ferris</div><div><br></div></body></html>