Obnam survey results.
I wrote the following recently about participating in Obnam development. It's still quite rough, but perhaps someone has suggestions?
I'm sitting here wearing a t-shirt saying "I'm a knight who says NIH",
which I wear with a little pride and some justification.
I'm now using my own distributed bug tracker to track bugs my own
backup software, both hosted on a git server I helped a bit with, and
all three tested by various automated testing tools I wrote. All this
software runs on an operating system I co-develop using a kernel I
helped get started.
Justified, but a little crazy.
I interviewed @joeyh and it's now an open article on LWN: http://lwn.net/Articles/672352/
Francisco M García Claramonte likes this.
Hey you, Free Software User! Yes you. @conservancy needs your support! Please join, donate, or just spread the word!: https://sfconservancy.org/supporter/
I have just released version 1.19 of Obnam, the backup program. See the website at <http://obnam.org> for details on what the program does. The new version is available from git (see <http://git.liw.fi>) and as Debian packages from <http://code.liw.fi/debian>, and uploaded to Debian, and soon in unstable.
The NEWS file extract below gives the highlights of what's new in this version.
NOTE: Obnam has an EXPERIMENTAL repository format under development, called `green-albatross`. It is NOT meant for real use. It is likely to change in incompatible ways without warning. Do not use it unless you're willing to lose your backup.
- Backup no longer ignores a closed SSH connection. This means it won't keep trying to use it, forever. Instead, it crashes and terminates the backup.
- The Paramiko SSH implementation, which Obnam uses, changed the interface to the `prefetch` method in its 1.16 version. Obnam can now deal with either variant of the method. Found and reported by Kyle Manna, who provided a patch that Lars Wirzenius rewrote to be backwards compatible to older versions of Paramiko.
- The manual now has an appendix listing all Obnam errors, with codes and explanations. This will need to be updated manually from time to time.
- The manual now has sections on turning on full debug logging and reporting problems.
- The output of `obnam generations` now show time zone. Lars Wirzenius implemented based on suggestion by Limdi.
My latest Yakking post:
I just donated to Software Freedom Conservancy as a supporter. They do great work in GPL enforcement, and they some money to continue it.
You can help, too: https://sfconservancy.org/supporter/
Unacceptable excuses for bad behaviour in free software development:
Show all 5 replies> because that's what got them where they are so far.
- Linus and other kernel developers do it.
- You have self-diagnosed as having Asperger's.
- You value code quality over other people's feelings.
- You get angry a lot.
- You think other people are just wrong about everything.
- You thought of a funny insult.
- You're uneasy having people in the project who're unlike you.
They could have gotten where they are so far in spite of (rather than because of) the behaviors. There's always the chance that several people saying "I'm not going to take this anymore" around the same time will shift momentum away from a previously-successful project or organization.
@lnxwalt That's true, the person with the bad behaviour has typically proved they can make the grade, give the company what they want, work hard, demonstrate their talents. At this point they use their value as a kind of credit system to get away with behaviour that others don't seem to get away with.
Claes Wallin (韋嘉誠) likes this.
That's in Finnish. English summary: I got a grant to buy some hardware for Obnam development. (Obnam: http.//obnam.org)
Why did I let my code become a map of the TARDIS flight path? Why? What was I thinking? Was I thinking? Was my brain in a jar on a shelf?
Success of a free software developer? I am spending more time on answering questions from users than actually developing the software now.