There are two reasons why I think amqp-libraries@ is strictly superior to proton@.
Firstly, while you may consider "proton" as a distinct stream of work, I'm not sure how that works with something like the messaging API which fits in with your "quadrant" of APIs, but is clearly not part of Proton as we know it today. Secondly, as I previously stated, I think that for a new user searching for information on AMQP libraries, the obvious list to look for would be "amqp-libraries". The name proton is pretty meaningless unless you already know it. (There is also perhaps some general value for us in having the association between "qpid", "amqp" and "library" become more obvious to search engines). In any case I'm not sure that "stream of work" is the right way to define mailing lists for the user community. Stream of work is a concept that is meaningful to us, the committers, but a user will be looking for functionality - which is a more natural definition of a mailing list. The way that we choose to divide and sub-divide our work would seem subject to change, what is part of the current "Proton" stream may not always be so in the future. -- Rob On 12 July 2012 22:53, Rafael Schloming <[email protected]> wrote: > On Thu, 2012-07-12 at 18:10 +0200, Rob Godfrey wrote: >> > To me, proton is very clearly a distinct stream of work. While > [email protected] is probably better than using the current > user list, I feel like the obvious list to create is > [email protected]. I think there is a good chance that an > amqp-libraries list will just end up being an oddly named list for the > proton sub-project anyways. Any additional separate streams of work that > come along will probably want their own list for the same reasons as > proton. > > --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]
