Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Re: [tdf-discuss] Re: Best way to suggest new features ?


On 12-02-29 07:18 PM, Marc Paré wrote:
Le 2012-02-29 11:36, Fabian Rodriguez a écrit :
On 12-02-29 02:46 AM, Charles-H.Schulz wrote:
Le mardi 28 février 2012 à 16:32 -0500, Marc Paré a écrit :
Hi Olivier

Le 2012-02-28 14:49, Olivier Hallot a écrit :

[...]

Heh :) :

http://ask.libreoffice.org/question/63/ask-for-features-new-idea

F.


The question here though is, will the devs actually visit these pages
often?


It would be really nice if they did. Several kernel devs hang out on
Ubuntu's Q&A site, resulting in very detailed, accurate replies - and
the corresponding karma reward.

The current seperation wall (in part implemented by the mailing lists)
between regular users and devs should not be driven to a bug tracker.

Perhaps, this discussion should really be taken up on the dev list
with devs only and you (the devs) tell us the way that you would
prefer to have suggestions funnelled back to you. We could then refine
the process after we know as to which format the devs would like to
receive the feature requests.

IMO, I prefer the method we now have of someone proposing a
feature/enhancement on the discussion list where we can all have a
discussion about it and then someone adding it to the bugzilla once it
has been refined. I don't see much value with people proposing
features and the masses ranking it up or down with little discussion.
But this is only my opinion.

The discussion doesn't have to go away, quite the opposite. In fact in
some questions I've already suggested to bring some topics to the UX
mailing list. Here's an example:
http://ask.libreoffice.org/question/387/how-can-i-get-a-split-view-of-a-document-like-in


Ultimately, whether a feature is accepted or not usually rests on
whether a dev will actually adopt it. Our system of meritocracy pretty
well drives the end process.

This is also a recurring topic on this list, marketing and website
lists. It would be nice if the process could be defined and "wikified".

You're mixing up two things here. A dev can adopt a feature (or even
implement a feature he wants) directly, but it rests on the community to
accept it, not the other way around.

Normally a feature would go through such due process, in some cases it
may be rejected even if several devs line up to implement it.

F.



-- 
--
Fabián Rodríguez



-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.