> If a feature is not wanted by the 'main' project, but might be useful > to others, then forking and making it public provides the feature to > others who might be interested
If a proposed feature is truly useful to others, then I'd say that it should be considered for inclusion in the main project, not implemented in a forked, potentially incompatible, side project. It is up to the PMC to decide what constitutes a valuable feature. > If the project clearly states its purposes and intentions, especially > if it is an experimental feature which is not intended to be merged > back into the original source tree, then its use is a free choice for > someone to make. They can be made aware if there is no intention of > maintaining ongoing compatibility, or furthering development past a > certain point. I agree with this. If something is clearly marked as experimental then there is most likely no harm in making it public. G
