So, this thread seemed to stop without us ever actually taking a concrete action to create a mailing list :-)
I know there were a couple of conversations off-list that happened after this to try to articulate more clearly what we thought the target audience of the list was, and how that was different to the scope of the current lists. I'm sure others will correct me here, but I *think* that it can be summarized as the need for a list to * Discuss how to use/integrate the AMQP 1.0 libraries that we are developing * Discuss with "users" of these libraries any issues they are having / requirements they may have * Discuss issues end users may be having getting the libraries to work with other AMQP 1.0 implementations In general the idea is that the list would be community facing and a place where we would discuss AMQP 1.0 support and interoperability rather than how to deploy and manage the Qpid "brokers" (users of other brokers should feel equally at home on the proposed list as those who are using the brokers that we maintain). Developer discussion amongst committers would remain on dev (where, separately, we definitely need to ensure we have more discussion of our roadmap as was already pointed out). There was previously some questioning whether "proton" would be an appropriate name for this list, since the scope would clearly include the Messaging API when has AMQP 1.0 capabilities. I also question whether using proton as the name may be sub-optimal as it will not be obvious to those who don't already know what Qpid Proton is. As such I would propose that [email protected] might be a better name for the mailing list (where implicitly AMQP means AMQP 1.0). What are people's thoughts? Would people be happy with this suggestion? Should I open a vote? -- Rob On 27 June 2012 15:37, Rafael Schloming <[email protected]> wrote: > On Tue, 2012-06-26 at 16:48 +0100, Gordon Sim wrote: >> On 06/25/2012 11:55 PM, Rafael Schloming wrote: >> > It makes sense that the people who are interested in using proton also >> > want to see a simplified API to get their users started with AMQP 1.0. >> > It really gives them an immediate ROI for integrating the engine. They >> > give their users very simple and easy access from the very broad variety >> > of languages, platforms, and environments that the messenger API can >> > support. >> >> What about the existing messaging API; does it not make sense for them >> to consider that also for some cases? > > Yes, assuming it supports 1.0. > > However there is really a lot of demand for, and good synergy when > proton is sold with something very simplified. Something more > scripting/web/mobile oriented where literally only one or two lines of > code is enough to send or receive a message. One of the places where > AMQP 1.0 shines is the cloudy/mobiley/web enabled scenarios, and in that > space people expect to see something akin to a pub nub type API. > >> On 06/25/2012 06:30 PM, Rafael Schloming wrote: >> > The fundamental issue here is that Qpid now needs to serve two >> > audiences. A very horizontal audience made up of pretty much anything >> > that might ever want to speak AMQP, and a more specialized, vertical >> > audience of people interested in a particular message broker. >> >> I certainly accept that distinction, but are you saying that the first >> audience would/should only be interested in proton rather than the full >> range of APIs on offer? > > No, I think there's more that we can and should offer, but I do think > there needs to be a serious and real effort around interoperability with > stuff outside of qpid for anything that we offer to that audience, and > right now proton is ahead of the curve on that front as it was > designed/developed with that in mind and has been tested from the > beginning against external 1.0 implementations. > > I've also found that proton and messenger together make a very > compelling story and are easy to promote and sell together and could be > a very powerful tool for bootstrapping the AMQP 1.0 ecosystem, something > at the core of the Qpid mission. It was with this in mind that I put > together the proton site. I wanted to keep the story simple, so it > doesn't go into all of the other 0-X qpid offerings, but I would hope as > more and more stuff both inside and outside of qpid speaks AMQP 1.0 > (either via proton or in general) we would link to them from the proton > site as they are all things you could speak to if you integrate proton, > and all part of the value you get from doing so. > > --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]
