StackStorm-Exchange / StackStorm-Exchange/ci
Deprecate or Revive stagnant packs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 18
- Avg merge
- 1m
- Merged PRs (30d)
- 8
Description
Background
Following the work performed in https://github.com/StackStorm-Exchange/ci/issues/153 some packs were identified as being so stagnant that the effort required to bring them up to a healthy state may be too much. This issue is to open a discussion as to the decision to deprecate or revive the pack.
Stagnant Packs
The below packs have been identified for review.
- stackstorm-aws - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-openstack - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-kafka - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-rackspace - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-azure - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-telegram - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
- stackstorm-tesla - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675331186
- stackstorm-qualys - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675464257
- stackstorm-phantomjs - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2669666678
- stackstorm-mssql - reference https://github.com/StackStorm-Exchange/ci/issues/153#issuecomment-2675209244
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue 153 and its referenced comments, then review the linked repositories for the listed stagnant packs. The work needs a decision for each pack—deprecate or revive—and is complete when those decisions and their follow-up actions are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, kafka
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100