Luciano Resende wrote:
In this scenario, where we have a contrib folder at same level as
modules and it part of the main build, how can we two goals I
mentioned ?
The main goal for the clean up is to reduce amount of code users will
download and a step towards reducing our build time.
How about creating a branch, with the current trunk structure so we
have all modules archived and make some of these changes. Is this an
option that people would feel comfortable with?
I didn't think about it before, but now that you mention it, it's
probably better and easier to manage than having to move modules around
into a contrib directory (and I guess there's modules, samples, itests
etc. so not everything would fit in a single contrib dir).
+1
--
Jean-Sebastien
