Share this comment
Hi Steve,
thanks for this article on opensource.radio. You are absolutely right regarding the challenge of insuring "its survival as an information database". Please read here with the solution I came up with: dk1mi.radio/open-sourci…
I would be interested what you think about this.
73 de
Michael, DK1MI / N1BSD
Hi Steve,
thanks for this article on OpenSource.radio. You are absolutely right regarding the challenge of insuring "its survival as an information database". Please read here with the solution I came up with: https://dk1mi.radio/open-sourcing-opensourceradio/
I would be interested what you think about this.
73 de
Michael, DK1MI / N1BSD
Mike - I think that is a great solution! At least the individual contributions will be protected on a daily basis, but is there an automated method to recreate OpenSource.radio Wiki? Can one start with a blank DocuWiki and "roll in" all of the daily snapshots to effectively recreate OpenSource.radio Wiki?
One of the bigger lessons I've experienced about online resources by individuals or small groups is (sometimes called) "Hit by a bus" planning.
Companies and (and large organizations that hire staff) handle this by paying people to manage such risks - create backups, migrate to new servers or services as needed, software updates, etc. But there is less rigor for non-corporate / non-organizational projects like OpenSource.radio Wiki.
But, things HAPPEN - illness or death, changes of circumstances such as hosting becomes expensive or free hosting is withdrawn, loss of interest, changes of club administration, passwords are lost, etc.
How MUCH "hit by a bus" planning is appropriate depends on the importance of the data, and I think the OpenSource.Radio Wiki is sufficiently important to take steps, such as you've done, to preserve the data if something were to happen to the primary site.
Anyone with read access to the Github repository can use the 2 included folders to clone OpenSource.Radio. Dokuwiki is a wiki system that doesn't use a database and only relies on plain text files stored in the filesystem. The only things that are missing are the files that include the change history and the user database. The reason why I don't make them public is that I have identified them to be PII and I can't publish them out of legal and ethical reasons.
So if I get hit by a bus or if someone is not happy with OpenSource.radio, anyone can build a clone of it in under an hour and make their own thing.