Date
1 - 3 of 3
OpenMAMA End of Support for Avis
Frank Quinn <fquinn.ni@...>
Hi Folks,
I'd like too propose that we stop maintaining the avis bridge for OpenMAMA and that the release which just went out (2.4.1) is the last to support avis, which may then be removed from the code base.
This has already been agreed by the Steering Committee, but I want to put it out there to the users and dev mailing lists to see if there are any further objections, or if anyone would like to step up and take ownership of the bridge (e.g. split out an external OpenMAMA-avis project).
There are several reasons for wanting to retire support for avis:
1. To the best of my knowledge, nobody is using it (we never hear of it on the mailing list any more).
2. Avis itself hasn't been updated in 7 years
3. It's a resource drain on any new functionality we may add for zero return.
4. Even today, doesn't pass all unit tests because the payload doesn't support all OpenMAMA functionality.
It's all about focus - I want to make sure that we spend time focusing on what people are actively using.
If anyone has any sentimental attachment to the avis bridge, please speak up now.
We are currently scheduling the removal of avis from the codebase on 25th July.
Cheers,
Frank
I'd like too propose that we stop maintaining the avis bridge for OpenMAMA and that the release which just went out (2.4.1) is the last to support avis, which may then be removed from the code base.
This has already been agreed by the Steering Committee, but I want to put it out there to the users and dev mailing lists to see if there are any further objections, or if anyone would like to step up and take ownership of the bridge (e.g. split out an external OpenMAMA-avis project).
There are several reasons for wanting to retire support for avis:
1. To the best of my knowledge, nobody is using it (we never hear of it on the mailing list any more).
2. Avis itself hasn't been updated in 7 years
3. It's a resource drain on any new functionality we may add for zero return.
4. Even today, doesn't pass all unit tests because the payload doesn't support all OpenMAMA functionality.
It's all about focus - I want to make sure that we spend time focusing on what people are actively using.
If anyone has any sentimental attachment to the avis bridge, please speak up now.
We are currently scheduling the removal of avis from the codebase on 25th July.
Cheers,
Frank
Frank Quinn <fquinn.ni@...>
Hi Folks,
Last call on this - if I hear no word back, it's getting taken out on Monday.On Sat, Jul 16, 2016 at 7:18 PM, Frank Quinn <fquinn.ni@...> wrote:
Hi Folks,
I'd like too propose that we stop maintaining the avis bridge for OpenMAMA and that the release which just went out (2.4.1) is the last to support avis, which may then be removed from the code base.
This has already been agreed by the Steering Committee, but I want to put it out there to the users and dev mailing lists to see if there are any further objections, or if anyone would like to step up and take ownership of the bridge (e.g. split out an external OpenMAMA-avis project).
There are several reasons for wanting to retire support for avis:
1. To the best of my knowledge, nobody is using it (we never hear of it on the mailing list any more).
2. Avis itself hasn't been updated in 7 years
3. It's a resource drain on any new functionality we may add for zero return.
4. Even today, doesn't pass all unit tests because the payload doesn't support all OpenMAMA functionality.
It's all about focus - I want to make sure that we spend time focusing on what people are actively using.
If anyone has any sentimental attachment to the avis bridge, please speak up now.
We are currently scheduling the removal of avis from the codebase on 25th July.
Cheers,
Frank
Frank Quinn <fquinn.ni@...>
Cheers Damian,
With that in mind, I just created: https://github.com/OpenMAMA/OpenMAMA-avis including a README explaining the situation.
With that in mind, I just created: https://github.com/OpenMAMA/OpenMAMA-avis including a README explaining the situation.
As I have heard no objections, we'll be be removing avis from the core code and updating the documentation and website etc. over the next week or so.
Cheers,On Mon, Jul 25, 2016 at 10:19 AM, Damian Maguire <dmaguire@...> wrote:
For what it's worth, I'm fully supportive of this move, as was everyone I spoke to about it. I think Avis is a distraction for core OpenMAMA that we don't need - the CI work, build system changes, core code changes, unit tests etc all have additional costs when taking Avis into account, and I think it's actually very confusing for end users of the API.
I do wonder if it would be worth extracting the code to a separate repo anyway, with a deprecation notice - at least it remains visible and available to other users who are interested (and might be an opportunity to firm up the process/framework for non-core bridges).
Cheers,
D
DAMIAN MAGUIRE
Senior Sales Engineer
M. +44 783 584 4770
Adelaide Exchange Building, 2nd Floor, 24-26 Adelaide Street, Belfast, BT2 8GD
velatradingtech.com | @vela_tt
From: openmama-dev-bounces@... <openmama-dev-bounces@...> on behalf of Frank Quinn <fquinn.ni@...>
Sent: 22 July 2016 09:35:41
To: openmama-dev; openmama-users@...
Subject: Re: [Openmama-dev] OpenMAMA End of Support for AvisThe information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. Vela Trading Technologies LLCFrankCheers,Hi Folks,Last call on this - if I hear no word back, it's getting taken out on Monday.
On Sat, Jul 16, 2016 at 7:18 PM, Frank Quinn <fquinn.ni@...> wrote:
Hi Folks,
I'd like too propose that we stop maintaining the avis bridge for OpenMAMA and that the release which just went out (2.4.1) is the last to support avis, which may then be removed from the code base.
This has already been agreed by the Steering Committee, but I want to put it out there to the users and dev mailing lists to see if there are any further objections, or if anyone would like to step up and take ownership of the bridge (e.g. split out an external OpenMAMA-avis project).
There are several reasons for wanting to retire support for avis:
1. To the best of my knowledge, nobody is using it (we never hear of it on the mailing list any more).
2. Avis itself hasn't been updated in 7 years
3. It's a resource drain on any new functionality we may add for zero return.
4. Even today, doesn't pass all unit tests because the payload doesn't support all OpenMAMA functionality.
It's all about focus - I want to make sure that we spend time focusing on what people are actively using.
If anyone has any sentimental attachment to the avis bridge, please speak up now.
We are currently scheduling the removal of avis from the codebase on 25th July.
Cheers,
Frank
