<div dir="ltr"><div><div><div><div><div><div><div>I'll wait to respond to the whole email from Bjoern but just two quick points (I'm in heavy moving mode and wife is waiting on me right now ;) )<br><br></div>a) good point about cc....indeed an issue that is unresolvable. <br> <br></div>b) Robinson's main point about ask site is that they don't have the man power to be QA's screeners - I think that summarizes his stance in the nicest way possible :) Basically what we are doing is asking the Ask admins to be QA screeners or for QA to get involved with Ask which - if we do that, they might as well just report on FDO and QA can avoid getting used to the dealings over in the Ask world. <br> <br></div>If we just send people to ask, they report what is a bug but that has to first wait for Ask site admins to clear it as a bug, then either send them over to FDO or if Robinson made a button that just said "this looks like a bug" but doesn't actually do the confirmation so it just jumps over to FDO as an UNCONFIRMED bug waiting for QA to tackle it....this seems very time consuming. <br> <br></div>I'm not sure if other Ask admins have an opinion but I think they (whoever you are) should be involved with this conversation if we're asking them to do more work.<br></div><br></div>Another option (maybe?) is to automatically setup an account for people when they report via BSA - not requiring them to do it but instead when they put in an email address it creates the BSA/FDO account with a random password and instructions on how they can change it. <br> <br><br></div>Just thinking out loud.<br><br><br>Best,<br>Joel<br><div><div><div><div><div><br><br></div></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 12, 2013 at 3:42 PM, Bjoern Michaelsen <span dir="ltr"><<a href="mailto:bjoern.michaelsen@canonical.com" target="_blank">bjoern.michaelsen@canonical.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <div class="im"><br> On Fri, Jul 12, 2013 at 12:06:00PM -0700, Joel Madero wrote:<br> > The idea is that if the user chooses to submit without an account,<br> > the bug will be reported under a default account (possibly<br> > <a href="mailto:bugs@tdfplanet.org">bugs@tdfplanet.org</a>), they will be forced to enter an email address<br> > and do a captcha - then their email address would go into the bug<br> > report as a CC'ed user.<br> <br> </div>Hmm. Two questions:<br> a/ how do you cc an email address that has no bugzilla account? AFAIK, that doesnt work?<br> b/ using unverified emails for such things is icky. How do we know people dont abuse it?<br> <br> (actually a/ is a result of b/)<br> <div class="im"><br> > Currently Mozilla (which we discussed during ESC) doesn't force a<br> > user account so, if we can emulate this and get to a landing page<br> > which avoids having to sign up for accounts - might be a good thing.<br> ><br> > Before we move forward looking for feedback, Robinson feel free to<br> > expand on anything that I missed.<br> <br> </div>I would still let the feedback go to askbot with a easily queriable tag.<br> We could ask people for an OpenID or an email. In the first case we are luring<br> people in (and askbots gamification with badges might do its magic from there<br> on) and for the pure email solution, we would need cronjob polling the<br> generated question on askbot and send updates to the reporter. These updates<br> might lure the reporter back (and _then_ do a OpenID login to keep involved).<br> <br> There are a bazillion problems with the emailing still:<br> - How to unsubscribe (e.g. if the question gets huge activity)?<br> - How to avoid abuse, false and unverified emails etc.?<br> <br> The important part on the mozilla feedback page is not the layout (dont get me<br> wrong: showing a smiley to someone angry at us is a Good Thing for mitigating<br> the pain), but the relevant part is IMHO what to do with the feedback, not some<br> small bandaid for someone who got hurt.<br> <br> So what to do after the happy/sad intro? IMHO it could be something like this:<br> <br> Did LibreOffice made you happy or sad?<br> - LibreOffice made me happy!<br> - Was it something cool, that you might want to share as a tip with others so<br> they can do it too?<br> => askbot, self-answered question (aka knowledgebase entry)<br> - Was it a generic LibreOffice feature you experienced? Describe it below,<br> and click the button, to post this on your twitter/g+/facebook page.<br> - LibreOffice made me sad!<br> - Was LibreOffice doing something unexpected or can we help you solving a<br> specific problem?<br> => askbot, unanswered question<br> - No, I have a different/generic complaint.<br> => these are tricky. Reply to email "Thanks for your feedback" and then<br> send to some private mailing list, for some poor sob to parse through?<br> <br> Im still uneasy about this without a clearer definition of "some poor sob" and<br> a good story how to motivate that work.<br> <br> Best,<br> <br> Bjoern<br> </blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><b><font face="garamond, serif" size="4">Joel Madero</font></b><div><font face="garamond, serif">LibreOffice QA Volunteer</font></div><div><font face="garamond, serif"><a href="mailto:jmadero.dev@gmail.com" target="_blank">jmadero.dev@gmail.com</a></font></div> <div><br></div></div> </div>