Hi Trond, Unless there are any objections from anyone on the list, I think we can go ahead and set this up. More inline below....
Trond Norbye wrote: (snip...) > > Our schedule is not 100% fixed yet, but one of the things we have in > our roadmap is to look into the scalability on multicore computers. We > will try to push our modifications upstream to the Memcached > community, but we need a place for the members of the team to store > our changes (and share with the team) before they are accepted into > the community version. This is also the version we are going to > integrate into Solaris. > I think officially speaking, what is going into OpenSolaris would become part of the sfwnv consolidation like the rest of the Web Stack work. There are only a few high-level consolidations the work could become part of if it were to be part of OpenSolaris itself, instead of unbundled. It's obviously not ON or Gnome/X11 or others. Having said that, I understand you need a place to work before putback to sfwnv and it'd be good to be able to easily get others on this list (and over in memcached) to see what all you're working on. Longer term, if the sources end up being pretty much the same, and if the sfwnv consolidation gets to be more open, we may want to fold this in. The difficulty here is maintaining the history, but I don't want to get so stuck in analysis that we just don't do anything. One other thing to consider here is issue tracking. We can leverage the existing opensolaris.org stuff (warts and all) but should document it. What were your thoughts on that? Is there an existing bugster category we should expose and then document on the project pages? - Matt -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron at sun.com Phone: 310-242-6439
