Changes to our Feature Requests page in the Wiki

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Changes to our Feature Requests page in the Wiki

Peter Sampson-2
With some help from Gale and notivated by recent dicussions on Feature Requests etc
I have been doing some tifying work on our Wiki page for Feature Requests:
http://wiki.audacityteam.org/wiki/Feature_Requests


1) In particular I moved all the requests that were previosly in the "Highest Rated" secrtion
back to the top of their functional group.  This should make it easier for any developer
interested in a particular functional group to find all the requests for that group in one place.


2) To replace the former contents of the Highest Rated section I created a Custom TOC
ordered by vote count:
http://wiki.audacityteam.org/wiki/Feature_Requests#Highest-rated_Feature_Requests

Feature Reqests are eligible for listing in that Custom TOC once they gather 20-plus votes.

I may consider later turning that Custom TOC into a table with the three columns:
Request, votes, functional-group.


3) I pruned the Feature Requests page of several items which we have already completed.


Thanks,
Peter.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
To improve this James kindly showed me how to set up a Wiki sortable
table for the index of Highest Rated Feature Requests (actually he did
most of the work - I just had to populate the functional categories).
So many thanks to James for that.

Please see:
http://wiki.audacityteam.org/wiki/Feature_Requests#Highest-rated_Feature_Requests

Thanks,
Peter.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Stevethefiddle


On 4 February 2017 at 12:08, Peter Sampson <[hidden email]> wrote:
To improve this James kindly showed me how to set up a Wiki sortable
table for the index of Highest Rated Feature Requests (actually he did
most of the work - I just had to populate the functional categories).
So many thanks to James for that.

Please see:
http://wiki.audacityteam.org/wiki/Feature_Requests#Highest-rated_Feature_Requests

Thanks,
Peter.
 
Nice :-)

Steve

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
In reply to this post by Peter Sampson-2
This is really good. Very helpful list.

I have a question regarding all these requests. Is there a link somewhere to the related discussions that were most likely on the forum? I ask because one of the items there is one that I am personally very interested in and there was a long, 6 page, discussion with most of the team chiming in on the subject more than a year ago, but I don't see any link to that discussion so was wondering when/if that item comes up to be worked on if the discussion would have to be done all over or would there be access to the previous discussion.

Cliff

On Feb 4, 2017, at 6:08 AM, Peter Sampson <[hidden email]> wrote:

To improve this James kindly showed me how to set up a Wiki sortable
table for the index of Highest Rated Feature Requests (actually he did
most of the work - I just had to populate the functional categories).
So many thanks to James for that.

Please see:
http://wiki.audacityteam.org/wiki/Feature_Requests#Highest-rated_Feature_Requests

Thanks,
Peter.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
Cliff wrote:
>This is really good. Very helpful list.

Glad you like it - it's nothing new really, we've just made it more accessible
and usable (I hope).


>I have a question regarding all these requests. Is there a link somewhere to the
>related discussions that were most likely on the forum?

Not for any that I see in the Feature Requests Page.  LAter on we started an
archive FR section on the Forum - so now there are many iems in the
"Pending Feature Requests" page that do have such a link.


> I ask because one of the items there is one that I am personally very interested in
> and there was a long, 6 page, discussion with most of the team chiming in on the
>subject more than a year ago,

What'e the topic or subject area - and I'll see if I can find it?

Cheers,
Peter.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
Peter,

It was on improving the usability of Zoom Normal (Ctrl/Cmd-2). I see it on the list with 5 votes. I use it all the time, but it's rather inconsistent in display and not as helpful in some ways as it could be.

Cliff

> On Feb 4, 2017, at 10:33 AM, Peter Sampson <[hidden email]> wrote:
>
> Cliff wrote:
> >This is really good. Very helpful list.
>
> Glad you like it - it's nothing new really, we've just made it more accessible
> and usable (I hope).
>
>
> >I have a question regarding all these requests. Is there a link somewhere to the
> >related discussions that were most likely on the forum?
>
> Not for any that I see in the Feature Requests Page.  LAter on we started an
> archive FR section on the Forum - so now there are many iems in the
> "Pending Feature Requests" page that do have such a link.
>
>
> > I ask because one of the items there is one that I am personally very interested in
> > and there was a long, 6 page, discussion with most of the team chiming in on the
> >subject more than a year ago,
>
> What'e the topic or subject area - and I'll see if I can find it?
>
> Cheers,
> Peter.
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
Hi Cliff,

you might then want to take a look at this Proposal I put together
a while back: 
http://wiki.audacityteam.org/wiki/Proposal_new_Zoom_Toolbar

In particular note that this proposal advocates a button for the Zoom Normal
and the creation a user-defined preferred zoom level (also with button).

I'll have atrwl through the Forum to see what I can find.

Peter.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
Hi Cliff,

was it this 6-page one (from the FR Forum archive) by any chance:
http://forum.audacityteam.org/viewtopic.php?f=56&t=88216&hilit=zoom+normal

Peter

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
Oh and if you need that thread unlocking so we can continue discussion
I can do that for you - biut it might be better to start a new thread and just
link to the archived one.

Peter.

On Sat, Feb 4, 2017 at 5:20 PM, Peter Sampson <[hidden email]> wrote:
Hi Cliff,

was it this 6-page one (from the FR Forum archive) by any chance:
http://forum.audacityteam.org/viewtopic.php?f=56&t=88216&hilit=zoom+normal

Peter


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
Hi Peter,

Yes, that was the one. I'm not wanting to restart the discussion right now, but was just hoping all that discussion wasn't lost for when ever there is time and interest to pursue it. I'll have a look at your proposal.

Cliff
On Feb 4, 2017, at 11:24 AM, Peter Sampson <[hidden email]> wrote:

Oh and if you need that thread unlocking so we can continue discussion
I can do that for you - biut it might be better to start a new thread and just
link to the archived one.

Peter.

On Sat, Feb 4, 2017 at 5:20 PM, Peter Sampson <[hidden email]> wrote:
Hi Cliff,

was it this 6-page one (from the FR Forum archive) by any chance:
http://forum.audacityteam.org/viewtopic.php?f=56&t=88216&hilit=zoom+normal

Peter

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Peter Sampson-2
In reply to this post by Peter Sampson-2
>the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of the time
>put the edit cursor in the center of the display where one normally works, but Zoom Normal
>often puts it almost at the lefthand edge of the display or sometimes even out of sight.

Yes, that annoys me all the time too.

IIRC I think we created a Bugzilla entry for that - I'll see if I can find that.


Peter

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
1292 seems to catch the essence of it. Bug 15 which is referenced in 1292 seems related as well. 1292 is marked as Enh so I suppose that means that it isn't pressing to be fixed. At least I'm not the only one it bothers. Maybe it'll get done before too long.

Cliff
On Feb 4, 2017, at 11:55 AM, Peter Sampson <[hidden email]> wrote:

>the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of the time
>put the edit cursor in the center of the display where one normally works, but Zoom Normal
>often puts it almost at the lefthand edge of the display or sometimes even out of sight.

Yes, that annoys me all the time too.

IIRC I think we created a Bugzilla entry for that - I'll see if I can find that.


Peter


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Gale
Administrator
Actually, there have been suggestions we should not track Enh's
on Bugzilla at all. That would make them even less likely to be
addressed, I'm guessing.

For now, enh's have a rating in the main tracker. There may be
some unwritten assumption that an Enh at a given rating is not
quite as important as a Bug at the same rating.


Gale


On 4 February 2017 at 19:10, Cliff Scott <[hidden email]> wrote:

> 1292 seems to catch the essence of it. Bug 15 which is referenced in 1292
> seems related as well. 1292 is marked as Enh so I suppose that means that it
> isn't pressing to be fixed. At least I'm not the only one it bothers. Maybe
> it'll get done before too long.
>
> Cliff
>
> On Feb 4, 2017, at 11:55 AM, Peter Sampson <[hidden email]>
> wrote:
>
>>the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of
>> the time
>>put the edit cursor in the center of the display where one normally works,
>> but Zoom Normal
>>often puts it almost at the lefthand edge of the display or sometimes even
>> out of sight.
>
> Yes, that annoys me all the time too.
>
> IIRC I think we created a Bugzilla entry for that - I'll see if I can find
> that.
>
> This is the one I was thinking of:
> http://bugzilla.audacityteam.org/show_bug.cgi?id=1292
>
> Peter
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
I'm wondering if there should be a separate category for items that are not true bugs as such and not pure enhancements in the sense of adding a feature, but are definitely irritations to people which I see this one as an example. I don't know of too many that would be in that category, but just a thought. Irritations may impact users more than we think.

Cliff

> On Feb 4, 2017, at 1:49 PM, Gale Andrews <[hidden email]> wrote:
>
> Actually, there have been suggestions we should not track Enh's
> on Bugzilla at all. That would make them even less likely to be
> addressed, I'm guessing.
>
> For now, enh's have a rating in the main tracker. There may be
> some unwritten assumption that an Enh at a given rating is not
> quite as important as a Bug at the same rating.
>
>
> Gale
>
>
> On 4 February 2017 at 19:10, Cliff Scott <[hidden email]> wrote:
>> 1292 seems to catch the essence of it. Bug 15 which is referenced in 1292
>> seems related as well. 1292 is marked as Enh so I suppose that means that it
>> isn't pressing to be fixed. At least I'm not the only one it bothers. Maybe
>> it'll get done before too long.
>>
>> Cliff
>>
>> On Feb 4, 2017, at 11:55 AM, Peter Sampson <[hidden email]>
>> wrote:
>>
>>> the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of
>>> the time
>>> put the edit cursor in the center of the display where one normally works,
>>> but Zoom Normal
>>> often puts it almost at the lefthand edge of the display or sometimes even
>>> out of sight.
>>
>> Yes, that annoys me all the time too.
>>
>> IIRC I think we created a Bugzilla entry for that - I'll see if I can find
>> that.
>>
>> This is the one I was thinking of:
>> http://bugzilla.audacityteam.org/show_bug.cgi?id=1292
>>
>> Peter
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

James Crook
On 2/4/2017 8:08 PM, Cliff Scott wrote:
> I'm wondering if there should be a separate category for items that are not true bugs as such and not pure enhancements in the sense of adding a feature, but are definitely irritations to people which I see this one as an example. I don't know of too many that would be in that category, but just a thought. Irritations may impact users more than we think.
>
> Cliff

Enhancement requests that make it into Bugzilla generally are ones
considered to be serious irritations / borderline bugs.  We need to and
do distinguish them from regular bugs, because generally they need
discussion to decide on the desired behaviour, whereas most actual bugs,
we know what the desired behaviour is.  I regard a P2 Enh as just as
serious as a P2 regular bug.  As RM I might prioritise it lower, because
it could need substantial discussion to agree on what desired behaviour
is, even though we have agreement that the current behaviour is not
right.  So agreement about desired behaviour (which should be
discussed/agreed outside the bugtracker ideally) brings the likelihood
of closing the Enh: forward.

Q2A, software that is like stackoverflow and promotes good questions and
good answers, may provide a better way of reaching agreement on desired
behaviours rapidly, so it may be a boost to enhancement requests and
feature requests.  We would write questions like "Where should the
cursor/selection be positioned after Zoom Normal?" and explain it was
related to Bug 1292.  We won't know if it helps until we try it.  It
might instead prove worse than email.

--James.

>
>> On Feb 4, 2017, at 1:49 PM, Gale Andrews <[hidden email]> wrote:
>>
>> Actually, there have been suggestions we should not track Enh's
>> on Bugzilla at all. That would make them even less likely to be
>> addressed, I'm guessing.
>>
>> For now, enh's have a rating in the main tracker. There may be
>> some unwritten assumption that an Enh at a given rating is not
>> quite as important as a Bug at the same rating.
>>
>>
>> Gale
>>
>>
>> On 4 February 2017 at 19:10, Cliff Scott <[hidden email]> wrote:
>>> 1292 seems to catch the essence of it. Bug 15 which is referenced in 1292
>>> seems related as well. 1292 is marked as Enh so I suppose that means that it
>>> isn't pressing to be fixed. At least I'm not the only one it bothers. Maybe
>>> it'll get done before too long.
>>>
>>> Cliff
>>>
>>> On Feb 4, 2017, at 11:55 AM, Peter Sampson <[hidden email]>
>>> wrote:
>>>
>>>> the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of
>>>> the time
>>>> put the edit cursor in the center of the display where one normally works,
>>>> but Zoom Normal
>>>> often puts it almost at the lefthand edge of the display or sometimes even
>>>> out of sight.
>>> Yes, that annoys me all the time too.
>>>
>>> IIRC I think we created a Bugzilla entry for that - I'll see if I can find
>>> that.
>>>
>>> This is the one I was thinking of:
>>> http://bugzilla.audacityteam.org/show_bug.cgi?id=1292
>>>
>>> Peter


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

Cliff Scott
Thanks for the clarification.

Is there the intent to try Q2A some time soon? I've never used it though I've seen the StackOverflow usage so can't say whether it is helpful or not, but I know email discussions can get to have pretty long emails that can make it difficult to figure out what's all been said.

Cliff

> On Feb 4, 2017, at 2:45 PM, James Crook <[hidden email]> wrote:
>
> On 2/4/2017 8:08 PM, Cliff Scott wrote:
>> I'm wondering if there should be a separate category for items that are not true bugs as such and not pure enhancements in the sense of adding a feature, but are definitely irritations to people which I see this one as an example. I don't know of too many that would be in that category, but just a thought. Irritations may impact users more than we think.
>>
>> Cliff
>
> Enhancement requests that make it into Bugzilla generally are ones
> considered to be serious irritations / borderline bugs.  We need to and
> do distinguish them from regular bugs, because generally they need
> discussion to decide on the desired behaviour, whereas most actual bugs,
> we know what the desired behaviour is.  I regard a P2 Enh as just as
> serious as a P2 regular bug.  As RM I might prioritise it lower, because
> it could need substantial discussion to agree on what desired behaviour
> is, even though we have agreement that the current behaviour is not
> right.  So agreement about desired behaviour (which should be
> discussed/agreed outside the bugtracker ideally) brings the likelihood
> of closing the Enh: forward.
>
> Q2A, software that is like stackoverflow and promotes good questions and
> good answers, may provide a better way of reaching agreement on desired
> behaviours rapidly, so it may be a boost to enhancement requests and
> feature requests.  We would write questions like "Where should the
> cursor/selection be positioned after Zoom Normal?" and explain it was
> related to Bug 1292.  We won't know if it helps until we try it.  It
> might instead prove worse than email.
>
> --James.
>
>>
>>> On Feb 4, 2017, at 1:49 PM, Gale Andrews <[hidden email]> wrote:
>>>
>>> Actually, there have been suggestions we should not track Enh's
>>> on Bugzilla at all. That would make them even less likely to be
>>> addressed, I'm guessing.
>>>
>>> For now, enh's have a rating in the main tracker. There may be
>>> some unwritten assumption that an Enh at a given rating is not
>>> quite as important as a Bug at the same rating.
>>>
>>>
>>> Gale
>>>
>>>
>>> On 4 February 2017 at 19:10, Cliff Scott <[hidden email]> wrote:
>>>> 1292 seems to catch the essence of it. Bug 15 which is referenced in 1292
>>>> seems related as well. 1292 is marked as Enh so I suppose that means that it
>>>> isn't pressing to be fixed. At least I'm not the only one it bothers. Maybe
>>>> it'll get done before too long.
>>>>
>>>> Cliff
>>>>
>>>> On Feb 4, 2017, at 11:55 AM, Peter Sampson <[hidden email]>
>>>> wrote:
>>>>
>>>>> the main bug-a-boo that bothers me, is that Zoom In and Zoom Out most of
>>>>> the time
>>>>> put the edit cursor in the center of the display where one normally works,
>>>>> but Zoom Normal
>>>>> often puts it almost at the lefthand edge of the display or sometimes even
>>>>> out of sight.
>>>> Yes, that annoys me all the time too.
>>>>
>>>> IIRC I think we created a Bugzilla entry for that - I'll see if I can find
>>>> that.
>>>>
>>>> This is the one I was thinking of:
>>>> http://bugzilla.audacityteam.org/show_bug.cgi?id=1292
>>>>
>>>> Peter
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to our Feature Requests page in the Wiki

James Crook
On 2/4/2017 9:08 PM, Cliff Scott wrote:
> Thanks for the clarification.
>
> Is there the intent to try Q2A some time soon? I've never used it though I've seen the StackOverflow usage so can't say whether it is helpful or not, but I know email discussions can get to have pretty long emails that can make it difficult to figure out what's all been said.
>
> Cliff
Yes, there's a plan to use it soon.  At least initially it will be
'closed' in the same way that Bugzilla and Wiki are.

--James.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Loading...