Proposal for a Consolidated Support and Documentation Model

ericbsd

grahamperrin Issues templates should always be used to ensure quality issue reporting. That said templates can be improved.

vimanuelt

We might consider this thread as being dead. There is no interest in the proposal. :-)

ericbsd

I am just starting to read this. I am not done yet.

grahamperrin

Thanks.

ghostbsd/issues265 is an example of an issue that might not benefit from a template.

ericbsd

A template should be added for website or link issues.

ericbsd

I have been thinking about whether we should have the Contributors' documentation on a GitHub Wiki, although it might be more complex to push changes to a wiki.

grahamperrin

ericbsd are pull requests possible?

From what I have seen (including content that's FreeBSD-oriented), GitHub wikis are no more likely to be maintained than other wikis.

vimanuelt

It would be helpful to have a single tool for managing all documentation workflows. For example:

ghostbsd-doc -web to update the website
ghostbsd-doc -wiki to maintain the wiki
ghostbsd-doc -rtd to publish to Read the Docs

Consolidating these tasks into one command-line utility would simplify documentation management and reduce duplication of effort.

ericbsd

vimanuelt wiki, most go, it might be a disaster waiting to happen. I do not log it to that. It is old and not up-to-date.

The website is on Drupal, so updating it is probably better than updating it manually.

vimanuelt

It was just an idea. :-)

ericbsd

If the website were static, that would be a nice tool to do.

ericbsd

grahamperrin I only referred to the contributors' docs. But keeping it with ghsotbsd/documentation is probably better.

vimanuelt

Wikis are still alive, but the classic open-edit wiki model has declined outside of specific use cases. Static documentation sites and structured knowledge bases have largely overtaken them for professional and polished documentation.

ericbsd

vimanuelt That is true.

vimanuelt

ericbsd
We are continually seeking more effective ways to communicate, even within the scope of the GhostBSD project. :-)
This is a perennial subject.

« Previous Page