PINE64 CommunityHey everyone. We've been discussing what to do with the mediawiki website for a while as it has not been actively maintained for over two years now. We have been using the new documentation page hosted directly on the website for a year now in place of the wiki (thanks to community member Funeral).
This change has come with some consequences though, as part of the community enjoys the wiki more than the new documentation page. This poll is to determine which route the majority of the community will be happy with. Below is some information about both to help make a decision.
Mediawiki:
Mediawiki is preferred by some because they can write the syntax it uses every day as mediawiki is used by Wikipedia. There is long term support for the software from the maintainers and it is specially built for this specific use case. It's easy to edit pages quickly.
As of right now the wiki is set to read only (except for the founder of PineStore) because if it is opened bots will ruin the wiki. This is likely due to the severely outdated mediawiki version. The founder is only familiar with mediawiki. The person who maintained the website is no longer active.
The way forward would be to update the mediawiki instance and to implement the anubis bot blocker. This would require a deal of time.
Documentation:
The documentation site is currently working without issue and contains the up to date documentation. It is embedded into the website so it doesn't require another web site. Users edit the wiki by using the GitHub web interface to quickly edit pages or download the website source for bigger edits to the wiki (including new pages). This can be seen as a benefit as it allows people to edit it offline and push changes when they come back online. It also prevents botting as you must submit a pull request when one wishes to edit the wiki.
Though there is a rising concern about the website being hosted on GitHub. Many people are currently moving away from the platform and/or do not wish to have an account on the site. This has prevented some from contributing to the documentation.
The way forward here is to either migrate to a different git hosting provider, mirror to a different git hosting platform or host our own. This would require a lot less effort to achieve.
