I agree with Rafi, we should make an effort to promote "proton" as an independent sub project of Qpid. There are many examples of such situations in the Apache community.
+1 for separate website, mailing list and bug tracking. Regards, Rajith P.S We should eventually do the same for QMF as well. On Fri, Jun 22, 2012 at 7:07 PM, Rafael Schloming <[email protected]> wrote: > Hi Everyone, > > As some of you may know I've been working on AMQP 1.0 support in the > form of the proton library. I've taken the liberty of putting up a draft > web site here: > > http://qpid.apache.org/proton/ > > It's very much in the spirit of having something to show is better than > nothing, so please review and comment with that in mind. > > The code is nearing the point where a first release is in sight, and > this does raise two infrastructure questions. > > 1) We'll need to do something for bug tracking. > 2) It would be extremely helpful to have an email list for proton users. > > For the moment I've created a proton component under the qpid project, > but as JIRA projects can only have one set of release numbers, I don't > think this will be workable as I would expect proton updates to be > initially much more frequent than qpid releases. I did a bit of research > and it looks like it's easy enough to request another JIRA sub project > from apache infra, so unless there are any objections, I propose we do > this. > > Regarding (2), I believe this would require an official vote, so I'd > like to throw it out there for discussion. Currently the need for such a > list is being filled with ad-hoc off-list emails. It would be very nice > to be able to give the people interested in proton a stepping stone into > the broader qpid community. > > --Rafael > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
