1.0 Roadmap [WIP] - Githubissues

evanplaice commented 4 years ago

[ ] switch to ajv #371
[x] add certificates section #341
[ ] make all properties optional? #373
[ ] typescript support? #327
[x] change education.gpa -> education.grade #146 #286 #288 #328

Ecosystem

[x] When a theme fails on registry, show a message that there is a new schema and link to it
[x] When a CLI tool fails, notify that there is v1 and link to it
[ ] Update homepage where required
[ ] Maybe post on all themes that v1 is released now and everyone should move to it
[x] create an issue on all popular official repos about the v1 repo and potential breakages.

Note from Thomas: Don't think we will support anything pre v1, this will be a mandatory shift to v1. Going to be a bit of a mess, but should sort itself quick enough.

None of this is final, suggestions welcome :+1:

stp-ip commented 4 years ago

education.grade -> education.score

The rest I agree with or have no clear stance on.

fballiano commented 4 years ago

I understand that gpa is not exactly correct and grade would be better but if possible I'd not introduce breaking changes.

thomasdavis commented 4 years ago

I do believe I really messed up the gpa addition, no idea what my reasoning was. (everything in retrospect is obvious) (https://github.com/jsonresume/resume-schema/issues/7)

I think we should definitely change it, and I will work overtime to try fix any breaking changes in the ecosystem due to the gpa

fballiano commented 4 years ago

@thomasdavis I was referring to breaking changes in json-resumes that were already created by people and that can't be fixed unless they change them

augustobmoura commented 4 years ago

It's #256 planned to 1.0? I'm still seeking for education.description. We can go for smaller coverage area just adding it instead of adding to all sections like is proposed in the issue

chadidi commented 4 years ago

Can we add this to the roadmap https://github.com/jsonresume/resume-schema/pull/150#issuecomment-709342857, this is really important!

thomasdavis commented 4 years ago

Just added some extra bullet points.

I will be pushing to release v1 by Saturday.

thomasdavis commented 4 years ago

Merged v1 into master, and set master back to default.

Consider it just a soft release. (the cli or registry won't point at v1 just yet)

Adding the new semver github action approach.

When writing PR titles use the following

"fix: added something" - will bump the patch version "feat: added something" - will bump the minor version "perf: added something" - will bump the major version

After a PR is merged, it will auto bump and publish to NPM.

thomasdavis commented 4 years ago

Okay v1 is released guys, again, amazing job!

I'm not going to update the ecosystem until the weekend.

So we can still bring in new changes as minors/patches and fix anything I may have broke in this process.

thomasdavis commented 4 years ago

Updated current check list.

v1 is going into action.

Looking forward to breakages.

formlesstree4 commented 3 years ago

Giving a date string of "Present", empty string, or NULL for End Date will not render the resume. I don't want to put an end date for a job I currently have.

My apologies if this isn't the right spot for this information!

SethFalco commented 3 years ago

Giving a date string of "Present", empty string, or NULL for End Date will not render the resume

I believe that depends on the theme / service in use. Implementations should treat it as an optional field, if not, I think it's worth sending a bug report or feature request where the issue is occurring.

make all properties optional

All properties are already optional. additionalProperties is for allowing custom properties on top of things defined in the schema already.

Nezteb commented 1 year ago

Is there anything an external contributor can do to help move the roadmap along? 😄 Although, the 1.0.0 release was made in November of 2020 (which was after this issue was created), so maybe this can/should be closed? I don't know what the status of the spec itself is.

cc @evanplaice @thomasdavis @SethFalco

eerison commented 1 year ago

I guess this repo was abandoned :'(

eerison commented 1 year ago

Is there anything an external contributor can do to help move the roadmap along? 😄 Although, the 1.0.0 release was made in November of 2020 (which was after this issue was created), so maybe this can/should be closed? I don't know what the status of the spec itself is.

cc @evanplaice @thomasdavis @SethFalco

most of resume repo was abandoned :'(, I started this one few weeks ago, maybe it can help you somehow :)

https://github.com/shield-wall/myprofile

SethFalco commented 1 year ago

I guess this repo was abandoned :'(

It wasn't abandoned exactly, but most of the maintainers are too busy to keep up with it, unfortunately.

I occasionally try to help with tooling/ecosystem, i.e. I'd like to clean up the repos and get themes up-to-date or backward compatible with different versions of the spec. But I don't review or modify the spec itself.

I'll try to find time to review the road map and either handle or scrap tasks.

In any case, I wouldn't consider the individual tasks listed in the roadmap a roadmap. There is no defined timeline associated with it, so they're basically just ordinary tasks.

jsonresume / resume-schema

1.0 Roadmap [WIP] #372