On Wed, May 29, 2002 at 12:06:22PM -0700, Andriy Palamarchuk wrote:
Changelog: Added bugzilla responsibilities page.
Hi,
hmm, I'm not 100% sure about this.
- why did you remove bug tracking link ? - "Talking Back" probably isn't very descriptive. I'd add something like "... (bugs etc.)" - that's Albe*r*telli - Application owners play *an* important role in the bugs handling process. - why add a whole new talkback.inc ? isn't that a bit overkill ? - why is <li>Bugs Hunting Guide</li> non-functional text ?
Wow, questions over questions :-)
Good job with bugz_resp.inc, BTW !!
Needless to say I'll add this immediately as soon as these questions are covered :)
--- Andreas Mohr [email protected] wrote:
- why did you remove bug tracking link ?
I was going to put it on the talkback page. Feel free to return the link to the original position if you do not agree with me. See below.
- "Talking Back" probably isn't very descriptive.
I'd add something like "... (bugs etc.)"
- that's Albe*r*telli
- Application owners play *an* important role in the
bugs handling process.
Oops, sorry Guy. Please fix misspellings or bad English you find.
- why add a whole new talkback.inc ? isn't that a
bit overkill ?
Bug tracking activities are very close to AppDB maintaining activities. Both present feedback to Wine developers and processing of this feedback. The idea is to have one page to describe both activities. Users, wanting to provide feedback or help to handle such feedback will have one page to start from. Information I want to have on this page: * link to Bugzilla * link to AppDB * link to guidelines for Wine bugs tracking process - finding, submission, research, fixing, testing. Of cause these guidelines will have tons of references to existing documents. * link to AppDB maintainer guide
Remove this page if you think this is too much, we can regroup information later.
Do you have better name? "User Feedback" does not sound good either.
- why is <li>Bugs Hunting Guide</li> non-functional
text ?
FIXME reminder :-) Please remove it.
Andriy
__________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
On Wed, May 29, 2002 at 12:48:07PM -0700, Andriy Palamarchuk wrote:
- "Talking Back" probably isn't very descriptive.
I'd add something like "... (bugs etc.)"
- that's Albe*r*telli
- Application owners play *an* important role in the
bugs handling process.
Oops, sorry Guy. Please fix misspellings or bad English you find.
Hehe, ok :-)
- why add a whole new talkback.inc ? isn't that a
bit overkill ?
Bug tracking activities are very close to AppDB maintaining activities. Both present feedback to Wine developers and processing of this feedback. The idea is to have one page to describe both activities. Users, wanting to provide feedback or help to handle such feedback will have one page to start from. Information I want to have on this page:
- link to Bugzilla
- link to AppDB
- link to guidelines for Wine bugs tracking process -
finding, submission, research, fixing, testing. Of cause these guidelines will have tons of references to existing documents.
- link to AppDB maintainer guide
Remove this page if you think this is too much, we can regroup information later.
This sounds *a lot* like what www.winehq.org/about/index.php?contrib already lists.
I really don't think adding a sort of "duplicate" page is going to help with the Wine users that already in some cases seem to be going out of their way to make sure that they don't contribute to Wine activities. (because it might even leave those people that do want to do Wine activities confused) My reasoning is: how many external winehq maintainers do we have ? how many main AppDB maintainers ? How many FAQ-O-Matic maintainers ? How many documentation writers ? How many translators ? How many regular application testers ? (Almost) all are tasks that even a non-programmer can easily handle given some dedication...
So how should this page conflict be resolved ? I'm open to anything - well, probably except to having two separate pages with some sort of "Wine contribution" content.
Do you have better name? "User Feedback" does not sound good either.
"Getting involved in Wine activities" ? That might be the link to a combined page, at least.
- why is <li>Bugs Hunting Guide</li> non-functional
text ?
FIXME reminder :-) Please remove it.
I'd comment it out, then.
--- Andreas Mohr [email protected] wrote:
- why add a whole new talkback.inc ? isn't that
a
bit overkill ?
Bug tracking activities are very close to AppDB maintaining activities. Both present feedback to
Wine
developers and processing of this feedback. The
idea
is to have one page to describe both activities. Users, wanting to provide feedback or help to
handle
such feedback will have one page to start from. Information I want to have on this page:
- link to Bugzilla
- link to AppDB
- link to guidelines for Wine bugs tracking
process -
finding, submission, research, fixing, testing. Of cause these guidelines will have tons of
references to
existing documents.
- link to AppDB maintainer guide
Remove this page if you think this is too much, we
can
regroup information later.
This sounds *a lot* like what www.winehq.org/about/index.php?contrib already lists.
Sounds good for me.
I really don't think adding a sort of "duplicate" page is going to help with the Wine users that already in some cases seem to be going out of their way to make sure that they don't contribute to Wine activities. (because it might even leave those people that do want to do Wine activities confused) My reasoning is: how many external winehq maintainers do we have ? how many main AppDB maintainers ? How many FAQ-O-Matic maintainers ? How many documentation writers ? How many translators ? How many regular application testers ? (Almost) all are tasks that even a non-programmer can easily handle given some dedication...
So how should this page conflict be resolved ? I'm open to anything - well, probably except to having two separate pages with some sort of "Wine contribution" content.
Agree. Lets remove talkback.inc, make a link to the contrib page from development page too. The contrib page may also have a link to the bugzilla repsponsibilities page. In future I'll add information I consider necessary to contrib.inc.
Andriy
__________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
On Thu, 30 May 2002, Andriy Palamarchuk wrote: [...]
I really don't think adding a sort of "duplicate" page is going to help with the Wine users
Agreed. The web site already has way too much redundancy and off-topic stuff (making progress though).
My reasoning is: how many external winehq maintainers do we have ? how many main AppDB maintainers ? How many FAQ-O-Matic maintainers ? How many documentation writers ? How many translators ? How many regular application testers ? (Almost) all are tasks that even a non-programmer can easily handle given some dedication...
All these should be listed on the 'How to contribute' page.
For the above, a call for volunteers posted on wine-dev, wine-users, the newsgroup and the WWN would probably help too.
Agree. Lets remove talkback.inc, make a link to the contrib page from development page too. The contrib page may also have a link to the bugzilla repsponsibilities page.
The 'How to Contribute' page should be made more visible. I would put it as a top-level item, same as About, Development, etc. It may require a web site reorganization but I think it is worth it.
For a proposal see: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=608
-- Francois Gouget [email protected] http://fgouget.free.fr/ Dieu dit: "M-x Lumière". Et la lumière fut.
-
Andreas Mohr -
Andriy Palamarchuk -
Francois Gouget