Thanks for your comments! It appears that the best way to go about my radical changes would be a dedicated fork of Weblocks, or a project that carries a new name and shares only its roots with Weblocks.
Some parts like a client-oriented test suite might be shared by both projects, but in general they should be separate. This is good for backwards compatibility as well, and the new project doesn't have to care about that so there's all the freedom that is needed to design and develop it. Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To view this discussion on the web visit https://groups.google.com/d/msg/weblocks/-/avYX902pfGcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
