Regenerating my laptop from scratch
2016-08-28T12:54:23Z via social.gl-como.it To: Public* Old laptop.
* New, empty hard disk.
* One Debian basic installation (no gui, just ssh server and basics)
* (one dist-upgrade to stretch, because of course)
* One ansible command (and some waiting)
* One mr command (and even more waiting)
The result: a new shiny installation with almost¹ everything I need on a laptop, including the programs I usually use, my configuration files, my data and my projects.
No proper backup involved, no wasted storage on backupping OS files.
I will properly document what I've done (including how ansible is used to get the starting mr configuration, solving my bootstrapping issues), but right now I'm just celebrating the result.
¹ I still haven't completed the list of packages², and in some cases apt installing at need works probably best.
² but the essential ones are there, including vim, screen, wesnoth and widelands :D
2016-08-26T13:15:23Z via social.gl-como.it To: Public
2016-08-12T07:50:47Z via social.gl-como.it To: Public
2016-08-10T07:55:05Z via social.gl-como.it To: Public
Debian Day a Varese
Come ogni anno, il 16 agosto è il Debian Day, il compleanno del Sistema Operativo Universale.
Dato che in questo periodo molti sono in vacanza, non abbiamo organizzato eventi particolari, ma ci troviamo per una cena presso la Vecchia Varese in via Ravasi.
Per informazioni o per unirvi alla prenotazione contattate prima possibile @Elena ``of Valhalla'' o fate un giro su #lifo@FreeNode.
@Gruppo Linux Como
2016-08-08T07:11:09Z via social.gl-como.it To: Public
Personal git hosting, under https
2016-08-07T19:37:48Z via social.gl-como.it To: PublicI've finally found the time to finish configuring:
* various stuff, including gitolite
* a cgit server
on https://git.trueelena.org/ to host my public git repositories; I now only have to push the missing ones ("only"…).
All of the configuration, especially the one related to letsencrypt, is under ansible, and thus as soon as the relevant people are home from the holidays we can work on configuring it on the @Gruppo Linux Como websites.
2016-08-07T13:03:14Z via social.gl-como.it To: Public
2016-08-05T07:50:29Z via social.gl-como.it To: Public
2016-08-04T11:16:59Z via social.gl-como.it To: Public
2016-08-04T09:44:31Z via social.gl-como.it To: Public
Feminismus und Gleichheit
Hier noch mal auf die Idee von @(: aNNa :) blume hin. :-)
Tags: #feminismus #feminism #egalitarism #gleichheit #emanzipation #comic #comicstrip #ravenbird #2016-07-26
Freemor shared this.
The Cat Model of Package Ownership
2016-08-03T18:03:08Z via social.gl-como.it To: PublicDebian has been moving away from strong ownership of packages by package maintainers and towards encouraging group maintainership, for very good reasons: single maintainers have a bad bus factor and a number of other disadvantages.
When single maintainership is changed into maintainership by a small¹, open group of people who can easily communicate and sync with each other, everything is just better: there is an easy way to gradually replace people who want to leave, but there is also no duplication of efforts (because communication is easy), there are means to always have somebody available for emergency work and generally package quality can only gain from it.
Unfortunately, having such group of maintainers for every package would require more people than are available and willing to work on it, and while I think it's worth doing efforts to have big and important packages managed that way, it may not be so for the myriad of small ones that make up the long tail of a distribution.
Many of those packages may end up being maintained in a big team such as the language-based ones, which is probably better than remaining with a single maintainer, but can lead to some problems.
My experience with the old OpenEmbedded, back when it was still using monotone instead of git² and everybody was maintaining everything, however, leads me to think that this model has a big danger of turning into nobody maintains anything, because when something needs to be done everybody is thinking that somebody else will do it.
As a way to prevent that, I have been thinking in the general direction of a Cat Model of Package Ownership, which may or may not be a way to prevent some risks of both personal maintainership and big teams.
The basic idea is that the “my” in “my packages” is not the “my” in “my toys”, but the “my” in “my Cat, to whom I am a servant”.
As in the case of a cat, if my package needs a visit to the vet, it's my duty to do so. Other people may point me to the need of such a visit, e.g. by telling me that they have seen the cat leaving unhealty stools, that there is a bug in the package, or even that upstream released a new version a week ago, did you notice?, but the actual putting the package in a cat carrier and bringing it to the vet falls on me.
Whether you're allowed to play with or pet the cat is her decision, not mine, and giving her food or doing changes to the package is usually fine, but please ask first: a few cats have medical issues that require a special diet.
And like cats, sometimes the cat may decide that I'm not doing a good enough job of serving her, and move away to another maintainer; just remember that there is a difference between a lost cat who wants to go back to her old home and a cat that is looking for a new one. When in doubt, packages usually wear a collar with contact informations, trying to ping those is probably a good idea.
This is mostly a summer afternoon idea and will probably require some refinement, but I think that the basic idea can have some value. Comments are appreciated on the federated social networks where this post is being published, via email (valid addresses are on my website and on my GPG key) or with a post on a blog that appears on planet debian.
¹ how small is small depends a lot on the size of the package, the amount of work it requires, how easy it is to parallelize it and how good are the people involved at communicating, so it would be quite hard to put a precise number here.
² I've moved away from it because the boards I was using could run plain Debian, but I've heard that after the move to git there have been a number of workflow changes (of which I've seen the start) and everything now works much better.
2016-08-02T16:30:10Z via social.gl-como.it To: Public
2016-07-30T08:11:53Z via social.gl-como.it To: Public
L'articolo va letto fino in fondo — o almeno guardare le figure fino all'ultima.