-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi,
Now that the wiki is being retired, is there a backup of the wiki (database, files etc) so that someone else can host it elsewhere? For archival purposes.
- -- Leah Rowe
Please help me fund my Gender Reassignment Surgery! https://vimuser.org/surgery/
Libreboot developer and project founder.
Use free software. Free as in freedom. https://www.gnu.org/philosophy/free-sw.html
Use a free BIOS - https://libreboot.org/ Use a free operating system, GNU+Linux.
Support computer user freedom https://sfconservancy.org/ https://fsf.org/ - https://gnu.org/
Minifree Ltd, trading as Ministry of Freedom | Registered in England, No. 9361826 | VAT No. GB202190462 Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK | Web: https://minifree.org/
Hi
On Tue, 2018-06-12 at 19:15 +0100, Leah Rowe wrote:
Hi,
Now that the wiki is being retired, is there a backup of the wiki (database, files etc) so that someone else can host it elsewhere? For archival purposes.
The wiki is still reachable at coreboot.org/wiki. It is however read- only.
Kind regards
Leah Rowe info@gluglug.org.uk schrieb am Di., 12. Juni 2018, 20:16:
Now that the wiki is being retired, is there a backup of the wiki (database, files etc) so that someone else can host it elsewhere? For archival purposes.
Various formats are available at https://www.coreboot.org/wikidump
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/06/18 19:15, Leah Rowe wrote:
Hi,
Now that the wiki is being retired, is there a backup of the wiki (database, files etc) so that someone else can host it elsewhere? For archival purposes.
My question was answered by Patrick Georgi. I just wanted a backup of the wiki in case it was shut down in the future.
Since coreboot is important to me, I have now downloaded those dumps of the wiki as suggested. I'm sure that most of the documentation from the wiki will be transferred over to coreboot.git.
Thanks for answering my questions.
I do not like this...
I update the wiki on a regular basis for the boards I use and I can't understand why another critical choice was made without input from the community?
The new system has less features, doesn't look as good and does not feature the current articles.
Policies like this make it very unfriendly to a new user and help ensure that either only expert firmware developers will be able to install coreboot themselves the average person will simply be forced to buy from a company that sells coreboot systems (of course none of them sell systems with real "free firmware")
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 14/06/18 05:28, Taiidan@gmx.com wrote:
I do not like this...
I update the wiki on a regular basis for the boards I use and I can't understand why another critical choice was made without input from the community?
The new system has less features, doesn't look as good and does not feature the current articles.
Policies like this make it very unfriendly to a new user and help ensure that either only expert firmware developers will be able to install coreboot themselves the average person will simply be forced to buy from a company that sells coreboot systems (of course none of them sell systems with real "free firmware")
Git is more portable than MediaWiki. It allows more people to be able to easily submit documentation changes. The documentation is in the repo under Documentation/ as Markdown files.
Markdown is much simpler than the markup language used by MediaWiki.
Plus you can make easy frontends for editing files in a git repository. E.g. GitHub does it. I wouldn't recommend use of GitHub since it's proprietary, but that's just an example. Where a user doesn't even need to understand git, they just log in and click "edit", edit whatever they like in a web interface and then that goes to a pull request for code review. I'm not sure if coreboot does that. We tried in Libreboot but it's currently not possible due to a limitation in Gogs, the software that we use for Git-based code review.
So it's possible to have something wiki-like while being hosted in Git.
I feel like we've discussed this a number of times, but maybe it hasn't happened completely in open forums where everyone involved can see it. If that's the case, I apologize.
This isn't really a decision that can just be voted upon and if enough people want to keep the wiki, the direction would change. This isn't an arbitrary decision on the part of the coreboot leadership, but something that's been a very long time coming, with a number of reasons.
* When the wiki was started, we didn't really think about licensing, so most of what's been written needs to be scrapped as we're not going to go back and contact all of the original authors, many of whom are no longer part of the project, to see if it's OK to update the license on their contribution. As we've joined the SFC and committed to having all of our documentation correctly licensed with an appropriate license, this means that we'd be starting over, regardless of whether we stuck with a wiki or changed to something else.
* The wiki requires a separate login from everything else, which has to be created manually. We've gotten criticism for only allowing wiki access to "a few coreboot elites". People can sign up for a gerrit account and contribute to the coreboot documentation with pretty minimal restrictions.
* The wiki has no integrated method of getting feedback or reviews from people, so documentation written can be, and has been, wrong for a long time before anyone noticed. Moving to gerrit at least guarantees that two people will look at what's added before it's integrated.
* Moving the wiki into git puts the documentation where the source code is, so it's more likely to get updated as the source code changes.
* Most of the wiki is developer oriented, not user oriented, so again, having that documentation alongside the source tree makes sense.
Currently the coreboot admins are mostly focused on development, and while that may be an issue, it's the way that the coreboot project has evolved. We've talked at conferences in the past about having a more user-oriented site, but the decision has generally been that it's something better handled externally. If someone wants to invest the time to start and run a coreboot or open-source firmware related site, we can certainly evaluate adding a link to it from the coreboot.org page. We've got links to various sites already on the "End Users" page (https://coreboot.org/users.html). The website itself is also in git, so feel free to submit appropriate changes.
Martin
On Thu, Jun 14, 2018 at 12:37 AM Taiidan@gmx.com Taiidan@gmx.com wrote:
I do not like this...
I update the wiki on a regular basis for the boards I use and I can't understand why another critical choice was made without input from the community?
The new system has less features, doesn't look as good and does not feature the current articles.
Policies like this make it very unfriendly to a new user and help ensure that either only expert firmware developers will be able to install coreboot themselves the average person will simply be forced to buy from a company that sells coreboot systems (of course none of them sell systems with real "free firmware")
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
-
Arthur Heymans -
Leah Rowe -
Martin Roth -
Patrick Georgi -
Taiidan＠gmx.com