-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resume-schema, version 1.0.0 #197
Comments
Thanks Chris. As we have done in the past, we should label issues with the pre-existing labels. Once consensus is reached, we should draw up a PR for it. Once a decent consensus is agreed upon for the PR, we can merge it in and then update the README change log. |
Okay, those could be an excellent starting point. Thanks, @stp-ip. If you're still around, it would be nice to look through the commits with you. |
Still around. stp on IRC. |
Okay! We've had a lot of good discussion, and I believe it's more than time to start committing stuff. We (the community) are more than in agreement on a lot of things, so let the pull requests commence. We'll start with the easy stuff, and move on to the big stuff in due time. When and if anybody pull requests, please includes tests for your additions to the schema! resume-cli is messed up in several places, but we should start by finalizing v1.0.0's schema first before touching the cli's codebase, or else we'll just be adding more unnecessary work if we change things. |
If I can help in any way, just mention me! |
Piggybacking off of #187 , I think resume-schema needs an new major version (that is, a version that breaks backwards compatibility with a new featureset).
Since @thomasdavis is super busy, I'll leave his issue, and open this one with a list of features already suggested that should be put into this new version.
I'll update this as I go through them.
The text was updated successfully, but these errors were encountered: