+1 to having a release from me. Having to build Tuscany themselves does put people off trying it - first installing maven and svn and downloading all the dependencies etc - having a binary download would help a lot. Not so much time to May 15th though, we need a release plan...
...ant On 3/22/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > > We have been having a series of discussions recently about project > structure, APIs, extensions, policies for plugins, distributions and so > on. I think this is a sign that we have started to move beyond the "code > the core like crazy" phase to a "how do people add stuff" phase. > > However, although we have made a lot of progress, I don't think we're > quite ready for them to do that yet. As can be seen from our > discussions, there are a couple of things that need to settle down from > both technical and social perspectives. > > We have two sessions at JavaOne: a panel on open source SOA and a BOF > specifically on Tuscany. I think these present a good opportunity to > meet with other like-minded people, show them what we have and encourage > them to come and participate. > > I think it would be good by then to actually have a binary release > available for anyone to download and use. That will lower the barrier to > entry and hopefully encourage people to contribute extensions, bindings, > and the like. I also think that working on a release would focus our > discussions both technical and social. > > JavaOne is early this year (May 15 IIRC) which is not far away. I'd like > to suggest we sort out the APIs we were discussing and get the project > structure set up. > > What do you think - is this the right time? Should we work toward such a > release? What else should be in it? > > -- > Jeremy >
