Quotes wanted
Jan. 10th, 2010 09:52 pm![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
For the presentation
mark and I are giving at LinuxConf AU, I'd like to be able to intersperse some good quotes from various Dreamwidth developers in our slides. To that end, if you've got a few minutes, I'd love to hear from some of you, especially people who started programming with us (or are using us to dust off rusty skills).
The topic of the talk is "Building your own contributors", and it's going to be concentrating on the steps we take to a) attract and retain qualified contributors who have a whole host of projects clamoring for their attention, and b) train people who have interest in contributing, but don't necessarily feel like they have the skills out of the box and need some coaching.
I'm looking mostly for soundbite-type comments, but if you tl;dr on the questions I'm sure I'll be able to use what you say somehow. *g*
If you'd like to help out, leave a comment with a quick introduction outlining your background (both your experience with programming in general, and any experience you've had contributing to other open source projects), and then answers to any/some/all of the following:
What first attracted you to contributing to Dreamwidth?
What are some of the things that we (the DW project maintainers) did to make you feel welcome?
What's the best thing we did to help you get up to speed and contribute effectively?
Was there anything in particular, big or small, that made you decide that DW was the kind of project you wanted to contribute to?
If you've had experience on other OSS projects, what makes DW different? Better? (Worse?)
What's your favorite part about the DW project culture?
Do you have any good stories to share about awesome moments?
What are some of the things you've learned, both technical and otherwise, while working on DW that you don't think you would have learned otherwise?
(If there's anything else you want to discuss that isn't mentioned specifically in the questions, but that you think someone who's trying to do a DW-style OSS project should know, add that as well!)
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
The topic of the talk is "Building your own contributors", and it's going to be concentrating on the steps we take to a) attract and retain qualified contributors who have a whole host of projects clamoring for their attention, and b) train people who have interest in contributing, but don't necessarily feel like they have the skills out of the box and need some coaching.
I'm looking mostly for soundbite-type comments, but if you tl;dr on the questions I'm sure I'll be able to use what you say somehow. *g*
If you'd like to help out, leave a comment with a quick introduction outlining your background (both your experience with programming in general, and any experience you've had contributing to other open source projects), and then answers to any/some/all of the following:
What first attracted you to contributing to Dreamwidth?
What are some of the things that we (the DW project maintainers) did to make you feel welcome?
What's the best thing we did to help you get up to speed and contribute effectively?
Was there anything in particular, big or small, that made you decide that DW was the kind of project you wanted to contribute to?
If you've had experience on other OSS projects, what makes DW different? Better? (Worse?)
What's your favorite part about the DW project culture?
Do you have any good stories to share about awesome moments?
What are some of the things you've learned, both technical and otherwise, while working on DW that you don't think you would have learned otherwise?
(If there's anything else you want to discuss that isn't mentioned specifically in the questions, but that you think someone who's trying to do a DW-style OSS project should know, add that as well!)