Somewhat short answers below (running low on email time). On 10/29/07, Bill Venners <[EMAIL PROTECTED]> wrote: > Hello, > > I just now joined this list to ask a question. I apologize to the > extent it is off-topic, but I didn't know how else to reach someone > involved with Apache Commons who would know the answer. > > When someone proposes a new API for Apache Commons, what are the > rules about acceptance and package naming? <snip/>
The base package name is listed on the proposal to establish a new component. We sometimes debate it later (such as at graduation from sandbox, though I think we're better off spending that time at proposal stage). > It looks like APIs in the > sandbox are allowed to have the package names that you'd want them to > ultimately have if they are approved. Is that correct? <snap/> Yes. > If so, doesn't > that mean the package name is burned forever if it ends up getting > moved to dormant and abandoned? <snip/> That hasn't caused any major problems so far. Note that sandbox components have no releases, so as far as Commons is concerned, the package name is not "public" (and thereby, may be reassigned if deemed fit etc.). > > Also, I would assume that APIs in sandbox are allowed to make > breaking changes from release to release, as the APIs there are being > "tried out." <snap/> No releases out of sandbox. APIs potentially volatile. > Once they are promoted to commons proper, you would try > very hard maintain backwards compatibility from release to release? > Is that correct? <snip/> Yes. > I couldn't find anything to that effect on the web > site. > > Lastly, what is the process for letting something into the sandbox in > the first place? > <snap/> Component needs to be proposed by an existing (ASF) committer. -Rahul > The reason I ask this is there's a nascent project in the Scala > community that is very similar to Apache Commons. And they are > debating how to manage it. I figured it would help them to understand > how other similar projects were managed, to learn from your experience. > > I appreciate any insights you may have to offer. Feel free to email > me privately or on this list. > > Thanks. > > Bill > ---- > Bill Venners > President > Artima, Inc. > http://www.artima.com > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
