Am Do., 23. Apr. 2020 um 04:24 Uhr schrieb Damian Vicino via Boost < boost@lists.boost.org>:
I think working in moving documentation from one tech used for writing it to another (ie. docbook to asciidoc) its not well tailored for a GSOD project.
You are right, although I have seen in some project that it was the main part.
A good highschool student with enough motivation to do a lot of copy paste and formatting can do that during a google code-in project (or many). Also, after years of following this list I'm pretty sure we will not get half the maintainers to agree in a single tech to document anything.
Agree.
If we get a professional documenter, which is what GSOD provides, it should be for something where a good writer is required skill. ie. tutorials, new docs, completing docs with missed pieces of it. Analysing and fixing consistency in the writing across all libraries, etc...
So you are thinking about a contribution for Boost not single libraries in general?
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost