Deprecate or Revive stagnant packs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, azure, kafka
- Domain
- release
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.
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
- Dominant language
- Shell
- Stars
- 5
- Forks
- 18
- Avg merge
- 1m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from StackStorm-Exchange/ci
-
Remove FORCE_CHECK_ALL_FILES and always check all filesMay be free again @nmaludy claimed this 2257 days ago, and no pull request is open. Openenhancement help wanted
StackStorm-Exchange/ci#88 · 2 reactions · 1 assignee ·
-
Makeing it easier to test from a developer's laptopMay be free again @nmaludy claimed this 2257 days ago, and no pull request is open. Openenhancement
StackStorm-Exchange/ci#71 · 1 comment · 1 reaction · 1 assignee ·
All issues in StackStorm-Exchange/ci
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mattpocock/skills#1174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day