Hello everybody, A report for Stonehenge was due on the 10th of Nov. They are giving us an extension till today to file a report.
Given the options Kamal discussed below, I think its best we suspend the project. On our end we believe we have achieved great progress, and coupled with the recent end of WS-I work it seems a fitting time to tie a bow on this project and call it done (for now). We've discussed the idea of smaller samples, however we don't have any clear commitment from anyone to define or contribute to that. the area of cloud is looking more interesting, and I wouldn't rule our continuing Stonehenge in that context once its more clear. Please vote on whatever we should archive or continue Stonehenge. Continuing Stonehenge would require the community to continue work on it, we on the Microsoft side are currently evaluating cloud interop options. If I can persuade you to suspend Stonehenge, I will file a report with the incubation committee seeking so. Thanks, -----Original Message----- From: Scott Golightly [mailto:scott_goligh...@hotmail.com] Sent: Wednesday, October 20, 2010 12:55 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Ready to Graduate? I would like to see the project graduate and continue to provide samples to developers to understand how to do interoperability. I like the new direction of smaller samples that should make it easier to understand the key parts of creating interoperable web services. Having said that I would have to say that I probably won't have time to do anything until mid-November towards furthering that goal. Scott Golightly -----Original Message----- From: Kamaljit Bath [mailto:kamaljit.b...@microsoft.com] Sent: Wednesday, October 20, 2010 11:00 AM To: stonehenge-dev@incubator.apache.org Subject: FW: Ready to Graduate? Forwarding to the Stonehenge Developer mailing list. Folks, I think we are at a decision point on Stonehenge's current mission. We have achieved quite a bit together over the past 2 years and provided valuable evidence of interoperability based on WS-* specifications across multiple platforms. We have successfully released our code for 2 milestones and added important features - all of which provided important learnings for developers trying to do the same, which have been documented on our Wiki page. Moving forward, we need to decide if we should ask for graduation and understand what needs to be done to achieve that or decide to suspend the effort for now, archive all the current assets and then pick it up later, if needed for example to transition this work over for what makes sense for the new cloud computing environment. I will like to hear opinions from everyone first and then may be start a vote to decide the strategy. So please use this thread to state your thoughts on how we should move forward. Thanks, kamal -----Original Message----- From: Noel J. Bergman [mailto:n...@devtech.com] Sent: Monday, October 18, 2010 12:13 PM To: gene...@incubator.apache.org Subject: Ready to Graduate? Please evaluate the status of your project with respect to graduation. Why, for example, are Thrift and JSPWiki not yet ready to fly? What about Ace? Others? --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
