[MTOS-dev] proposals and changes protocol?

[Timothy Appnel]

Now that the MTOS code is out there under the GPL I'm wondering what
is the protocol for suggesting changes is. I'm thinking Six Apart
didn't define that so we as a community could work that out.

Hirotaka suggested a change (the option to use the Memcached::Fast
module) by just submitting a patch. (I assume someone at Six Apart is
going to apply it to the code.) That works when the changes are
relatively minor like fixing a bug or adding an additional option like
he did. How should we introduce new features or major changes though?
Just submitting a patch for something major means doing a lot of work,
presumably in a vacuum, that may go nowhere. It also means the rest of
the community has to do a lot of code review just to begin commenting.
Most of us won't have the attention span for that. I personally get
distracted by the coding style anyway. ;)

The reason I ask is that after last week's discussion of search in MT
I started reading over my existing code and writing notes that lead to
writing up docs for "the way it should be" if I were (almost) starting
over. I'm wondering what the best (right?) next step now.

Thoughts?

<tim/>