*IMHO it is totally irrelevant if a package is named internal or not. If the API in that package is public then its public and if that API is useful it will be used no matter what. *
I don't agree with you on this point: when the team designs a solution, they know if it's a solid architecture or if they didn't have time to think about it and there a re big chances these APIs will change drastically in future versions. Sometimes it is also because they're applying a new idea and they don't know how it will evolve (which axis will be the leading axis). So naming packages that are well designed the same way as packages that aren't is a "loss of information". User developers will feel they have been betrayed if they build a big solution on an API that disappears on the next release or completely mutates in a way that they have to rewrite their soft from ground. So unless all GWT packages are well and maturely thought an no package is done only to solve a problem very specifically then taken the time to rethink (which I doubt). Loosing this information (or not communicating it is definitely a risky choice) *Actually I think the best way to let people try features that are not in GWT trunk is to create a GWT fork at Github and let people know about it. * Ok, but you know humans: each person will want himself to be glorified, and a person wouldn't like his efforts to be "stolen" and attributed to another person who just forked GWT. That's why, unless the GWT team says: here's an "official" Github fork to post your ideas (the part of: let people know about it). The GWT team might specify it's a fork made by the community for the community : the fact it is somehow certified as the "official" GWT fork changes a lot of things in comparison to if I said to everyone: it's "My Fork" come and put your effort in it, I will be rewarded for your efforts. As I started this discussion by saying that if everybody starts forking GWT we will loose the synergy, and proposed to brainstorm on "the procedure" to avoid that, it's no surprise that when you argue that "everyone should fork GWT and make people know about it" I will not agree :) -- 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/d612fdc0-dde1-4796-83e6-fb8d7103cc18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
