It could be hard to communicate and set expectations with a live work-in-progress gwt-project repository and via publishing on maven central. I agree with Jens on first setting up a foundation, rules and also maturing what GWT3 is; and in the meantime let people iterate in their own repos which will set expectation accordingly.
On Wed, Nov 15, 2017 at 9:31 AM, Jens <[email protected]> wrote: > Oh and if its just about making these small projects more discoverable > then one could also create a single project, e.g. gwtproject/gwt3-migration > and use the wiki for documentation and/or git submodules to link in all > these small projects as well. > > -- J. > > -- > 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/ee2066ec-2b18- > 4921-8476-6a2195cffecc%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/ee2066ec-2b18-4921-8476-6a2195cffecc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAN%3DyUA1v4ZO8f0QRTok-g0vfSWDr_2v-8W%3D8Qc7hg4SOOAT4Mw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
