New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sample email templates linked from web app to debian wiki #9
Comments
D'oh, I guess this up to either me or @paultag or maybe @andrewsomething should do, rather than being something just @daveloo should do. Well it should probably wait until the UI is more clear, so waiting on #12 and #10 and #11 . But then maybe I can get one of you two try writing up these email templates; especially @andrewsomething since you presumably have some similar text from Ubuntu. |
In Ubuntu, we've been using the initial contact in order to get feedback on the contributor's experience. This is the template we start with:
I just use this as a rough template though. Here's an example of how we've reported this feedback: http://people.ubuntu.com/~andrewsomething/dat/New_Contributor_Feedback_12.04.pdf The main goal though is to provide the contributor with a point of contact. |
A sample one I'm putting here for the record. Hi, You are receiving this mail because you recently had your first package In order to improve Debian's ability to welcome new contributors, I'd I will write and publish a summary of the collected answers. Your So, here are the questions: Q1: Can you (briefly) introduce yourself? What motivated you to Q2: What are your reasons for starting to contribute to Debian now? Why Q3: What were the biggest surprises you had while going through the process? Q4: What did you find most difficult? Q5: Here are some ideas that have been mentioned, aimed at making it Q6: What other idea should be implemented, or what should be changed, Q7: Can I publicly list your name to thank you for participating in this Thanks! |
I put paultag's version here: https://wiki.debian.org/GreeetingForNewContributors and am marking this as resolved. |
No description provided.
The text was updated successfully, but these errors were encountered: