On Tuesday, 5 September 2017 at 03:15:58 UTC, Adam D. Ruppe wrote:
On Monday, 4 September 2017 at 11:15:08 UTC, Joakim wrote:
While it's an interesting suggestion, dub has 355 open issues,
would be better if more people pitched in on those:
I have zero interest in fixing dub issues since I have zero
interest in using dub.
If one of the libraries were compelling... and I actually knew
about it though, that equation may change.
Making the code repository show documentation will do a lot to
make the library more discoverable and valuable, which in turn,
can drive dub use and bring with it more contributors.
I think this is a good idea (and I bought a VM to set up to do
it myself, but I went too cheap and the 512 MB of memory isn't
enough to actually build the docs! ugh.)
If you want a larger VM email me specs and I will set one up for
you.
I guess the doc generation doesn't need much changing on dub.
Maybe an extra command line option to build and publish docs that
calls a field specified in dub.sdl like postgenerate command
because you don't want to build docs every time and creating
separate build configurations means you now have double the
number, with and without docs. And custom command allows you to
use a different doc generator. But we could have a default
command to generate those for dub the repository.
And then the template for the web site would just need to have a
link to appropriate directory added?
We have contributed to dub in past - John Colvin worked on this.
One problem was lack of bandwidth to review pull requests. If we
get better review and still don't have contributions then one can
address that directly, but for now review seems the bottleneck.
