Fledging is the stage in a flying animal's life between hatching or birth and becoming capable of flight.
Fledger's goal is to use real world open source projects and open source standards / best practices to help software engineers with their general career. We hope as this helps you will learn, grow, and contribute to the community.
- Fledger provides a basic CLI to generate assessments and records.
- Industry Category Advisors provide summary best practices
- Open Source Partners help drive adoption of practice using open source.
"One of the best things you can do is to find something you're passionate about and contribute to it."
- Quality (Standards, Testing, Performance)
- Documentation (READMEs, Legal, Guides, CheatSheets)
- Release Notes
- Security
**For Job Seeks
Below are a number of categories, each category has an overview, interview guide, and how to work with partner teams in that category. The categories are basic prep, intended to be very light. Once you have tried it you can apply it for specific roles or companies you are interested in. You will have a better understanding to talk with a potential employer, an artifact that you went through, and it will set you up for you first 30-60-90 days as well as working with other teams.
Below are a set of Categories written in partnership with Industry experts, pick a category you are interested in to get started.
- [[SECURITY_CATEGORY]] - v1
- Usability - coming soon
- Accessibility - coming soon
- Quality - coming soon
For Internal Teams Fledger can be used to help onboard, train, and support team members. More to come. : )
Fledger commands are still a work in progress. This is a rough working doc with more details. [[BetaTesters]]
Fledger is licensed under the Apache-2.0 license.
Contributions are welcome! This community and project would not be what it is without the contributors. All contributions, from bug reports to new features, are welcome and encouraged. Please view the contribution guidelines before getting started.