Comment Re:Come on! (Score 1) 583
Justice Minister Vic Toews [...] is a divorced philanderer and has fathered children outside his own marriage.
Source?
Justice Minister Vic Toews [...] is a divorced philanderer and has fathered children outside his own marriage.
Source?
Some sources:
* https://en.wikipedia.org/wiki/IPv6_deployment
* http://www.circleid.com/posts/20090609_verizon_mandates_ipv6_support_for_next_gen_cell_phones/
* https://www22.verizon.com/opendev/Forum/LTE_Document_Archives.aspx
* https://en.wikipedia.org/wiki/IPv4_address_exhaustion#Regional_exhaustion
One thing that is not mentionned here is that the 4G specs actually mandate IPv6 and deprecate IPv4 support - something that should really push IPv6 adoption forward, especially with providers that offer both cell phone and traditionnal internet connectivity...
Good thing too. Getting those suckers in would have been difficult otherwise. With IPs running out in Europe this year, we are really starting to feel the pressure now...
First, read the PSNA if you haven't already, it features good ideas on documentation and especially process and how to deal with "layer 8" (management, users, whatever is the "real world" for you).
Next step is the wiki. You seem to already have that, good. People here have suggested SemanticWiki, but I'll point you towards Ikiwiki as it has the advantage of (a) being git based so completely decentralised (have a copy of your files on your laptop during a downtime!) and (b) written in perl so you can probably extend it.
Make sure people know where your wiki is and *use* it, so it doesn't become this rotten piece of outdated documentation out there. You have only started to understand how this is going to be a pain: documenting is hard long-term work. there's a (bad) reason why people don't do it effectively: it takes time and dedication.
Next you can consider using dedicated tools for certain things like inventory or issue tracking. We have used Request Tracker with good success. It's a very solid product that does a lot, also in Perl, coincidentally enough. It also has the Asset Tracker plugin to follow inventory, but i haven't personnally used that, although I had good feedback from peers that used it successfully in an heterogeneous environment. An alternative is OCS inventory, which I haven't used either.
So, just bite the bullet: you're going in the right direction. Just consider the right tool for the right job is your next step, i guess.
I happened to have scanned my modest book library here (~500 items) with GCstar, which works pretty well. It can download covers and details from Amazon and so on, based on the ISBN (although the latest version in Debian fails to do that properly for some reason). Before deciding on GCstar, I had evaluated multiple solutions, including Koha and custom-based solutions, none of which being simple enough for my uses, which made me settle on GCstar... The full details of the evaluation are in the Koumbit wiki.
Since then I have started looking into e-book readers, and family have pointed me to Calibre, a e-book management software. Now it's not necessarily very good with real libraries, but since I am likely to get such a device in the near future (and therefore accumulate digital books), this looks like a very good choice, especially since it seems to have a more complete interface (especially for batch entering ISBN numbers) and a more robust engine to talk with Amazon and friends. It also seems to be better maintained and have a stronger community.
I am not sure that is so helpful in your case, but I thought I could chime in since, well, I have a small library and most of the work is automated.
... and while i won't go as far as signing this comment (i admire the dedication folks, but really...), i try to use it as much as possible. I have done PGP trainings for the masses (see this and this, in french) and I'm doing my best to strenghten the web of trust.
I am also very curious to see where the STEED project leads us, it looks like a nice way to popularize PGP.
"Everything should be made as simple as possible, but not simpler." -- Albert Einstein