You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a open-ended issue which deals with the long term plan for this repo. I'll try to outline the way I see the current situation and make suggestions for moving forward, and then I hope that we can have a fruitful discussion to establish a way forward which will work for all stakeholders.
I will ping this issue to people who I think have an interest to partake in this discussion. If you feel that you are not interested, sorry for the trouble.
Current Situation
The current arteria-packs repo is a mainly populated with things that are used at the SNP&SEQ Technology Platform in Uppsala, however there is also code that can be of general interest. The repo also suffers from being a little bit disorganized, this is an effect of it having grown organically together with st2 from the early days of that project when things were not as clear as they are today.
Suggestions for the future
I think that we should rebuild this repo from the ground up, adding to it actions/workflows/sensors/etc that we think will be of general interest. To complement this each organization would have their own pack repo which can then use this repo as a "library". This should hopefully mean that we can use this as a basis for collaboration, while still adapting to each organizations specific needs.
Do you think that sounds reasonable?
My TODO list would then look something like this:
Finish the upgrade to st2 2.4.1 which is being addressed in St2 2 4 1 #86
Move to a Docker-based test environment
Prune the repo of SNP&SEQ specific things (moving them into a repo of their own)
That sounds very reasonable and it's exactly how it's progressing and how it should ideally be in the future.
Right now we are looking at having an AWS-backed CD environment so that we can deploy our docker-compose repo that is currently under CI, using docker too: https://travis-ci.org/umccr/st2-arteria-docker.
We'll continue on that line, it would be awesome if we could start seeing some of the arteria packs cleaned up and uploaded to the StackStorm exchange, really like that point since it would give Arteria a strong "maturity stamp" as a project if you will :)
This is a open-ended issue which deals with the long term plan for this repo. I'll try to outline the way I see the current situation and make suggestions for moving forward, and then I hope that we can have a fruitful discussion to establish a way forward which will work for all stakeholders.
I will ping this issue to people who I think have an interest to partake in this discussion. If you feel that you are not interested, sorry for the trouble.
@johanherman @Smeds @reisingerf @brainstorm
Current Situation
The current arteria-packs repo is a mainly populated with things that are used at the SNP&SEQ Technology Platform in Uppsala, however there is also code that can be of general interest. The repo also suffers from being a little bit disorganized, this is an effect of it having grown organically together with st2 from the early days of that project when things were not as clear as they are today.
Suggestions for the future
I think that we should rebuild this repo from the ground up, adding to it actions/workflows/sensors/etc that we think will be of general interest. To complement this each organization would have their own pack repo which can then use this repo as a "library". This should hopefully mean that we can use this as a basis for collaboration, while still adapting to each organizations specific needs.
Do you think that sounds reasonable?
My TODO list would then look something like this:
Anything you'd like to add to this list?
The text was updated successfully, but these errors were encountered: