Hi!
Jwb in http://jwboyer.livejournal.com/44908.html wrote:
Now I have a question for you, whether you were at this talk, have seen a similar one at a different FUDCon, or want to speak up in general: Are these talks worthwhile to you?
I haven't been to Paris and just listened to two (or was it just one? can't remember) Fudcon kernel talks from davej years ago. I found them useful, as they gave some new insights and I learned a thing or two about how the Fedora's kernel crew worked back then.
But the real reason why I write this mail: I like to thank Fedora's kernel team and especially Josh for blog entries like the one mentioned above. Those are IMHO more important than FUDCon talks, as everybody interested can get information this way -- at a time they want and without travelling long distances. Further: a text like this can transfer more information in less time than a talk or a video recording from a talk (which in the FUDCon Paris case afaik doesn't even exist); and in a text it's a lot easier to skip details one is not interested in.
In addition: Thanks for the public IRC meetings and the summaries from them. They give a good insight, too.
I hope this mail encourages you guys to keep on writing blog posts and meetings summaries (or maybe even do it more often). I know the feedback and responses to them are rare, which can be frustrating and easily lead to a "nobody seems to read that stuff, so why do I bother and spend time on it" attitude (trust me, I know what I'm talking about ;-) ). But be assured: I read them, and I'm sure many others do, too; so keep up with it, it helps a lot! :-)
Cu knurd
On Thu, Oct 25, 2012 at 06:37:58PM +0200, Thorsten Leemhuis wrote:
But the real reason why I write this mail: I like to thank Fedora's kernel team and especially Josh for blog entries like the one mentioned above. Those are IMHO more important than FUDCon talks, as everybody interested can get information this way -- at a time they want and without travelling long distances. Further: a text like this can transfer more information in less time than a talk or a video recording from a talk (which in the FUDCon Paris case afaik doesn't even exist); and in a text it's a lot easier to skip details one is not interested in.
In addition: Thanks for the public IRC meetings and the summaries from them. They give a good insight, too.
I hope this mail encourages you guys to keep on writing blog posts and meetings summaries (or maybe even do it more often). I know the feedback and responses to them are rare, which can be frustrating and easily lead to a "nobody seems to read that stuff, so why do I bother and spend time on it" attitude (trust me, I know what I'm talking about ;-) ). But be assured: I read them, and I'm sure many others do, too; so keep up with it, it helps a lot! :-)
Thanks! Knowing at least someone is reading them certainly helps. I'm happy to continue doing things like that, and we appreciate the words of encouragement.
josh
On Thu, Oct 25, 2012 at 06:37:58PM +0200, Thorsten Leemhuis wrote:
In addition: Thanks for the public IRC meetings and the summaries from them. They give a good insight, too.
I hope this mail encourages you guys to keep on writing blog posts and meetings summaries (or maybe even do it more often).
Thanks for the feedback.
We've mentioned a few things in the past in kernel meetings which I hope we find some more time to do at some point to give more insight into how we work etc. One idea that came up at one point was documenting a lifecycle of a bug, where we pick a bug, and show what happens from the day it gets reported, what steps we go through to diagnose them etc, and get them fixed etc. It's something we're currently not finding the time for unfortunatly other than for really big bugs.
I've had a number of people emailing about the bug summary posts I create on my blog. When I started doing them, I went into a lot more depth about the bugs from that week, but it turned out to be very time consuming, so it's become a lot more automated now, with a smaller summary. Perhaps one day we'll get to a situation where we aren't quite so buried alive in bugs, and I can go back to deeper explanations.
We're also starting to think more about different things we could be doing at fudcons to try and make our kernel sessions more 'interactive'.
Any suggestions for ways we can improve our visibility within the community are welcomed.
Dave
kernel@lists.fedoraproject.org