On 11 September 2011 15:38, c. <[email protected]> wrote:
>
> On 9 Sep 2011, at 03:00, Carnë Draug wrote:
>> Could a project admin maybe create the different categories (one for
>> each package at least)? And update the web pages to mention that users
>> should use the trackers to report bugs? And when asking for support,
>> what should be the recommended method? The tracker for support request
>> or the mailing list?
>
> Carnë, I just gave you admin access,

Thanks for the admin access.

>would you be able to make such changes yourself?

I can do that no problem. Is one category per package enough? What
about a documentation category? That would be a kind of bug that even
people without knowledge of the package would be able to fix and as
such, something that should be easy to filter.

> I also think the location of the various trackers should be mentioned on the
> website, can you suggest the appropriate location?

I would say they should go in the bugs section. I will try to make
some changes to it? If I make changes to the text in /doc/htdocs/ are
the changes in the site immediate? If so, hI'll try to submit them
elsewhere first for approval.

I noticed we can turn off some of the trackers. Currently there's 4
trackers: bug, patch, feature request and support request.

One of them, support request kind of overlaps with the function of the
mailing list. Wouldn't it be better to have only one place to ask for
support? It would avoid people that need support from asking in two
places and focus people who want to give support in one one place.
Would it be better to turn it off (after closing the ones that are
open there)?

And the patches tracker? If anyone is submitting a patch, it can
probably go in the bug tracker (with a patch attached) or in the
feature request (with new code attached). Should turn it off and make
things simpler?

Carnë

Note: I removed octave-maintainers ML from the list of recipients
since this discussion seems to to no longer affect them.

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to