Separate SSL code into own project
Open
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 162
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
More of a request than a bug...
I am in need of SSL routines for a project, but having to build or coerce aws into providing it seems excessive.
Should the SSL code, given how small, self-contained and valid for a lot more than just aws & web traffic, not be moved into its own repository?
Contributor guide
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
Review the existing SSL routines and how they are coupled to the AWS framework. Determine the scope and boundaries of a separate repository, then confirm whether the project should be moved. Done would require an agreed repository structure and migration plan.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100