Hi, I had the experience of wanting to contribute to GWT with a new feature<https://code.google.com/p/google-web-toolkit/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Stars&groupby=&sort=&id=8727>, but I received kind of a rigid answer: "we won't adopt that, it was designed otherwise".
So I'm wondering "who decides on the design", since this if decisions are rigid there is a risk that the community will fork GWT and have different variants (which is naturally bad in essence because the energy will be split on the different projects). I think this is an important questions to solve: "who decides on priorities?" For my concrete example: there's no "standard" solution for authorizations in GWT, addressing the problem is definitely a subject that interests the whole community. I proposed a "draft" solution that is born dead. So - where can we discuss the design of a solution to be adopted? - do we really have to wait until there are thousands of favorites on a bug to start thinking about it - other platforms adopted solutions for (logging, aop, security, code organisation, ect...) if something exists and works on other platforms, isn't that an additional indicator that the feature is valuable and that it should be addressed in GWT too? Your comments are welcome :) -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/ba191aeb-9c88-4fcb-a1a3-dae0d2963ac0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
