You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common complaint is: I want to try creating a package, but I don't have any ideas for what it should be about.
I think providing a list of ideas would help a lot of women take the next step toward becoming a package maintainer, especially if they don't want to go the traditional route of working their way up a FOSS project with patches/PRs and convincing the project leads that they should be considered for the core dev team.
This list could include ideas like:
Create a library that wraps the subprocess module and makes it more usable.
Write a pure Python YAML parser. Since the YAML spec is huge, consider implementing a defined subset of YAML like eYAML or cYAML
and other interesting unsolved or partially-solved problems that would make for great packages.
@willingc do you think this list would fit in anywhere in this project, or should it be something separate?
The text was updated successfully, but these errors were encountered:
@audreyr Totally what I have in mind to fit in this project. As far as I'm concerned this repo is a blank canvas. Push to it as you would like. I'll likely make a CPython folder in it for CPython specific stuff but I'm very excited about the maintainer side of things.
A common complaint is: I want to try creating a package, but I don't have any ideas for what it should be about.
I think providing a list of ideas would help a lot of women take the next step toward becoming a package maintainer, especially if they don't want to go the traditional route of working their way up a FOSS project with patches/PRs and convincing the project leads that they should be considered for the core dev team.
This list could include ideas like:
subprocess
module and makes it more usable.and other interesting unsolved or partially-solved problems that would make for great packages.
@willingc do you think this list would fit in anywhere in this project, or should it be something separate?
The text was updated successfully, but these errors were encountered: