The terms might not be perfect but sometimes you have to be able to say no.
Not because it's not possible or because it might not help a small subset of users but because it would alter how the product would "look" and "feel" out of the box. Meaning you have a resemblance of a goal for what you are trying to accomplish and reject contributions because they change your course. This is getting a bit abstract though, let's wait for the patches to keep rushing in before thinking about how to stop the fire hose. --emi Pe 20 iun. 2017, la 13:30, Bertrand Delacretaz <[email protected]> a scris: >> On Tue, Jun 20, 2017 at 12:21 PM, Emilian Bold <[email protected]> >> wrote: >> ...It's also unclear to me how "product management" and "user experience >> design" would work under Apache.... > > The (P)PMC drives the project and can setup those things however it > wants (although hearing of "product management" here gives me the > corporate shivers ;-) > > UI and UX are in my experience very hard to get right in open source > projects as it's quite easy to get into bikeshedding about minor > things. > > I don't know how NetBeans does that but I suppose supporting themes > that are independent from the code helps - people can then contribute > their own themes inside or outside of Apache NetBeans. There might > even be a business in creating commercial themes, as getting those > right requires a lot of effort and focus that can be hard to find in a > participative project - and Apache loves to enable businesses > (although they don't have a voice inside our projects). > > -Bertrand
