On 3/6/06, Simon Kitching <[EMAIL PROTECTED]> wrote: <snip/> > > Regarding sandboxes, the issue is really where the commit mails will go. > An experimental project that hopes to be promoted to community X really > should have its commit messages go to the mailing list for that > community. Other than that, what *is* a "sandbox" exactly? > <snap/>
IMO, this is a good point. Its like going to grad school, if you expect to graduate, at some point you must declare a major (sorry about the analogy, I'm aware they rarely work ;-). So unclear how this will play out in a Jakarta sandbox. Concretely speaking, if we mix the Commons and Taglibs sandboxes today, and assume that the groupings mentioned in this thread already exist -- some commits need to go the JWC, some to JLC and some to "Commons - JLC" (whatever that is). > In general, though, the split-off of Jakarta Language Components seems > wise. Commons email traffic is a pretty hefty burden, so halving it for > people only interested in one of the two new commons pieces is good. I > believe there are enough people interested in each community to allow > the separate pieces to thrive. Of course people should be encouraged to > subscribe to both where possible - and general always! > <snip/> +1 -- its time to establish that there are two equally useful pieces here, with differing API styles, differing thresholds for involvement and therefore, potentially attracting differing audiences (at the user and developer level). The more shared developers we can retain the better, ofcourse its understood that individual interests will trump utopian views in this regard. -Rahul > Cheers, > > Simon > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
