we can punt to marketing. Lets take the word config out and just call them bundles internally for now.
On Aug 17, 2007, at 9:01 AM, Juris Galang wrote: > Why not let marketing come up with something snappy - just describe > what the thing does, and they could brainstorm :) > When/if it gets productised, we could potentially even have bundle- > packs (and that could use another name) > > Internally (for dev at least) I think 'config bundle' as opposed to > 'config module' is fine - if only to distinguish it from source > modules (or just modules) > > > > > On Aug 17, 2007, at 7:34 AM, Steven Harris wrote: > >> The problem is that "Config Bundles" are actually already called >> config modules. >> So you are voting for the rename to something else :-) >> >> On Aug 17, 2007, at 7:26 AM, Jason Voegele wrote: >> >>> On Friday 17 August 2007 10:22, Steven Harris wrote: >>>> How else is module used internally? >>> >>> We use module to refer to the directories under code/base that >>> contain all of >>> the source code, tests, etc. dso-l1, dso-l2, common, etc. etc. >>> >>> This is actually quite confusing in the build system, since it is >>> using the >>> word 'module' to refer to both the source code modules like dso-l2, >>> as well >>> as what we've been calling config bundles. For my own sanity, I >>> would like >>> to stay away from 'modules' being the replacement for 'config >>> bundles'. :-) >>> >>> -- >>> Jason Voegele >>> Running Windows on a Pentium is like having a brand new Porsche but >>> only >>> be able to drive backwards with the handbrake on. >>> (Unknown source) >>> _______________________________________________ >>> tc-dev mailing list >>> [email protected] >>> http://lists.terracotta.org/mailman/listinfo/tc-dev >> >> _______________________________________________ >> tc-dev mailing list >> [email protected] >> http://lists.terracotta.org/mailman/listinfo/tc-dev > _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
