-
Notifications
You must be signed in to change notification settings - Fork 196
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
Email notifications about webcompat project #55
Comments
@sesam I changed a bit the name of the issue. Let me know if it covers what you would like. As I understand it: "A possibility to receive emails of what has been added to the project, changed." To be sure to understand, we currently have Btw we could deploy the changelog as an atom feed. That might help people to follow what has changed instead of remembering to come here. @sesam What type of information would you like to receive by email
|
RSS would be good enough for me. mvh On Thu, Nov 13, 2014 at 8:54 AM, karl notifications@github.com wrote:
|
I think this is a great idea! Mailchimp has an RSS to email feature if that's helpful. http://mailchimp.com/features/rss-to-email/ We could start with the blog posts @miketaylr has been writing. Those are great. |
The issue with using Mailchimp is that we make the data visible to Mailchimp. Email addresses and so on. So it's another privacy policy. Privacy sensitive persons will not like it. It means trusting 9. Your Distribution Lists and be sure the policy is not changed in time or/and if MailChimp is sold to someone else in the future. |
I think the experience for anonymous reporters could be improved with options for email notifications. I'm not disputing the privacy challenges @karlcow has mentioned, I agree with them. I think it's fair to say that anonymous reporters begin their process with a website issue. They are likely at the point of wanting to take action but not sure how exactly. This part is fuzzy, but somehow they come across webcompat.com (possibly through search, see screenshot). Once the issue has been reported, the process for getting updated is manual. They would need to record the bug link somehow and remember to check on it. Sometimes people report good bugs and we begin to work on them very quickly. Except for weekends, our initial triage is pretty quick. This is a good opportunity to let the user know they made a difference and update them along with the process. If they feel rewarded, they might be open to learning what a compatibility bug is and repeat the process. The sooner they see progress, the more likely they will be to stay engaged (I've heard). |
We decided this isn't something we have the bandwidth to take on right now. |
I'd like a field where I add myself to a mail list to get news about this project. After adding email, why not ask a yes/no question if I want a (persona!) login to simplify further interaction with your site. May fit in well with if you need to handle taking bug reports without requiring github account incl. readwrite access to all my repo:s, which I'd prefer not handing out.
The text was updated successfully, but these errors were encountered: