chaoss
docs: update supported Python versions and add onboarding steps #3441 issue solved
Title / Commit: docs: update supported Python versions and add onboarding steps (#3441) — committed to the repo.
Files changed: README.md (path: README.md) Replaced the hard-coded "Python3.7 through Python3.11" text with guidance that Augur aims to support current officially-supported Python releases (centered on Python 3.11). Added cross-platform virtualenv examples (PowerShell for Windows and bash for macOS/Linux). Added an Onboarding for New Contributors section with steps: join Slack, read CONTRIBUTING.md, run Augur, find starter issues, and ask for help.
@MoralCode : I added a "discussion" label here because I'm not certain ... BUT, I think we have other open PR's that address the python versioning issues.
I think we have other open PR's that address the python versioning issues.
most likely - thats why i added the redundant tag
Title / Commit: docs: update supported Python versions and add onboarding steps (#3441) — committed to the repo.
Please make the titles of your Pull requests more descriptive of the actual issue being solved
Title / Commit: docs: update supported Python versions and add onboarding steps (#3441) — committed to the repo.
Please make the titles of your Pull requests more descriptive of the actual issue being solved
Problem 1: Outdated Python version documentation Issue: Hard-coded "Python3.7 through Python3.11" becomes outdated, and OSX-only examples don't help Windows/Linux users. Solution: Replaced with flexible language about supporting current Python versions (centered on 3.11) and added cross-platform virtual environment examples for Windows (PowerShell) and macOS/Linux. Impact: Documentation stays current longer and helps contributors on all platforms. Problem 2: Missing onboarding guidance Issue: New contributors lacked a clear starting point; onboarding info was scattered. Solution: Added an "Onboarding for New Contributors" section in README.md with steps: join Slack, read CONTRIBUTING.md, run Augur locally, find starter issues (first-timers-only or good first issue), and ask for help. Impact: Clear, visible path for newcomers to start contributing. Problem 3: Low discoverability Issue: Critical onboarding info was buried in docs. Solution: Placed onboarding steps directly in README.md for immediate visibility. Impact: Easier for new contributors to find and follow the process. Issues resolved: #3441, #3448