There are a lot of working collaborative models out there, with more or less top control: my best examples are stackoverflow and wikipedia. There are disadvantages in their solution but it works.
I know source code is not as granular as a wikipedia article, or a stackoverflow question. But you can already see in stackoverflow that if a person asks an alredy asked question his question is kind of 'rejected' (unvoted, marked as duplicate or unanswered). So people are aware and fight dependencies in a quite less firmly tighted platform than our target (in source code you can see dependencies a lot better than in a question forum) Even Google organizes the Google summer of Code where students contribute to different open source projects, but at the same time in an centrally organized manner (so good profiles can be detected and given wider responsibilities)... the same could apply for this fork -- 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/0993daeb-4c30-44c4-8fdf-701413d9b058%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
