Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
I welcome any comments
Steven
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
Nifty. My only comment: How can we make sure that the workflow/interface for SugarZilla is what its intended userbase needs? (It's easy for us to sit here and say "yes, that will be better for 8-year-olds," but how do we know that?)
Might be a good thing to get a Design team consultation on.
--Mel
Mel Chua wrote:
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
Nifty. My only comment: How can we make sure that the workflow/interface for SugarZilla is what its intended userbase needs? (It's easy for us to sit here and say "yes, that will be better for 8-year-olds," but how do we know that?)
Might be a good thing to get a Design team consultation on.
--Mel
I had planned to get some design folks involved, in fact I will need help in that area. I am shooting for the simplest interface possible that is able to gather the needed info.
Steven
On 08/18/2009 11:19 AM, Steven M. Parrish wrote:
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
I welcome any comments
I dislike the idea of anonymous opening of bugs and anonymous commenting in bugzilla. It's not clear from the proposal if that's a proposed feature or not. Can you clarify if it is and if so, how you'll minimize the problem of: 1) SPAM 2) Bug reports with insufficient information to fix the problem with no point of contact to get additional information.
-Toshio
On 08/18/2009 11:19 AM, Steven M. Parrish wrote:
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
I welcome any comments
I dislike the idea of anonymous opening of bugs and anonymous commenting in bugzilla. It's not clear from the proposal if that's a proposed feature or not. Can you clarify if it is and if so, how you'll minimize the problem of:
- SPAM
- Bug reports with insufficient information to fix the problem with no
point of contact to get additional information.
-Toshio
I haven't had time to fully check out ABRT but are they requiring the user to have a valid bugzilla account? If I remember the original discussion around ABRT at FUDCon Boston was not to require one.
SPAM can be handled through a captcha if needed.
As far as not being able to contact the reporter, that is why they have the option of being cc'd to the report. They will be advised when filing the bug that without a point of contact if the developer has questions and cannot contact them that the bug could be closed as insufficient info.
There are still some finer points which need to be worked out.
Steven
===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar
On 08/19/2009 06:29 PM, Steven M. Parrish wrote:
On 08/18/2009 11:19 AM, Steven M. Parrish wrote:
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla
I welcome any comments
I dislike the idea of anonymous opening of bugs and anonymous commenting in bugzilla. It's not clear from the proposal if that's a proposed feature or not. Can you clarify if it is and if so, how you'll minimize the problem of:
- SPAM
- Bug reports with insufficient information to fix the problem with no
point of contact to get additional information.
-Toshio
I haven't had time to fully check out ABRT but are they requiring the user to have a valid bugzilla account? If I remember the original discussion around ABRT at FUDCon Boston was not to require one.
I can see that being a good thing but I'm not sure it got implemented. abrt-bugzilla has a config file in /etc/abrt/plugins/Bugzilla.conf that has this::
# your login has to exist, if you don have anyone, please create one Login = # your password Password =
It looks like we (Fedora packager) could fill those in with a bz user and password pair to give the equivalent of anonymous reporting to users but have chosen not to at the moment.
SPAM can be handled through a captcha if needed.
<nod>. So that would be a requirement before hooking it up to production bz.
As far as not being able to contact the reporter, that is why they have the option of being cc'd to the report. They will be advised when filing the bug that without a point of contact if the developer has questions and cannot contact them that the bug could be closed as insufficient info.
There are still some finer points which need to be worked out.
<nod> That makes sense although finding better and better ways to get the reporter to CC will be good. Might also want to ask the triage team if they might want to go through these types of bugs and triage them for more information and close them if there's no reporter on CC right off the bat or something.
-Toshio
infrastructure@lists.fedoraproject.org
-
Mel Chua -
Steven M. Parrish -
Toshio Kuratomi