Latest posts for tag dcg
I've finally put online slides and notes for my debconf6 talks:
- Mi vida con el software libre (in Spanish)
- Advanced ways of wasting time
- The Debian Community Guidelines -- Or, how to be able to plan total world domination with a public discussion in debian-devel.
Many people had asked me the notes for the "Advanced ways of wasting time" talk: they're finally online, translated and with the links pointing to English Wikipedia pages. Sorry it took me so long.
I've recently received a substantial amount of feedback about the Debian Community Guidelines and went into some reorganization of it.
The previous general section still stands as the Main Guidelines: those are the substantial few things to always keep in mind.
What previously was the long list of checklists is now split in two: the Debian-specific Guidelines, which should be a shorter lists of non-obvious suggestions for people who already have experience with online life, and the General Guidelines, with the fuller checklists with useful suggestions for everyone.
I still haven't gone through the selection and reorganization of the Debian-specific and General part, so at the moment they look fairly similar and most things overlap. But the good news is that I finally found a structure that I like, and that can allow more experienced people to make use of the guidelines without getting bored with simpler things like "google before asking a question".
This division also suggests a little workflow: new suggestions can be added to the Debian-specific part, and then later moved to the general part when they become obvious for everyone.
I'm happy. This layout seems to be good in getting me unstuck with how to think of the DCG. More will come of course, as I'll prepare my DCG talk for Debconf6.
Sustain a discussion towards solving a problem is sometimes more important than solving the problem.
I can't decide if this is trivial or counterintuitive. Anyway it's been quite enlightening when it came out. I once took this note:
I found that with my projects, when someone posted a mail about a problem I would work maybe some days to find a solution, and just post the solution at the end.
However, now I realised it's more costructive to have the problem-solving process itself happen online. This way, instead of keeping people waiting in silence for a few days they can get quicker feedback and extra informations, and they also have a chance to participate to solving the problem before I manage to.
For example, when I have to interrupt to go home or sleep, someone else can pick it up and do another step.
Plus, the entire problem-solving process remains documented, which will provide more written information for future readers.
This note was from a few months ago; however, I still fail to do it. Bad habits are sometimes hard to change. Please kick me about it :)
A friend of mine pointed me to the Debian Community Guidelines being mentioned in a linux.com article.
"[Mako] hopes that Garrett's resignation will give the Debian community an added impetus to adapt its own code of conduct, like the one proposed by Enrico Zini."
I'm very happy to see the DCG geting mentioned, although I don't think that it makes sense to 'adopt' such a document.
what I'd like for it is to be mentioned as a suggested read, and linked from here and there. So today it happened, and I'm happy :)