On 05/24/2016 07:04 AM, Sankarshan Mukhopadhyay wrote:
On Wed, May 18, 2016 at 2:43 PM, Amye Scavarda <amye@xxxxxxxxxx> wrote:
Said another way, if you wanted to be able to have someone contribute a
feature idea, what would be the best way?
Bugzilla? A google form? An email into the -devel list?
Whether it is a new BZ/RFE; a line item on a spreadsheet (via a form)
or, an email to the list - the incoming bits would need to be reviewed
and decided upon. A path which enables the Gluster community to
showcase in a public manner the received ideas and how they have
enabled features in the product would be the best thing to do.
The individual contributing the feature idea needs to know that
something was done with it and it wasn't a /dev/null
I would like to broaden this topic, and suggest, can we have a 3 month
cadence on something like design summits (like the update releases)?
So that we can have a focused point at which we gate* some of the
features being done or being proposed.
Why I think this broadens this discussion, is due to the fact that, to
have such a summit (virtual of course), we need a list of proposals, and
a way to get something to that list, which is the current topic of
discussion.
*gate: technical correctness and compatibility to existing stack, or
maybe some other factors that ensures that the features are inline with
how we want something done for Gluster
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
