-
Notifications
You must be signed in to change notification settings - Fork 36
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
"How To" on using github to help with SSVC #401
Comments
I agree that GitHub specific 'how to' topics should be directed to the GitHub site. SSVC specific topics would be more effectively handled in the SSVC Wiki page. |
One question is whether there are how-to's that are targeted at folks who are not SW developers. GitHub how-to's tend to assume a baseline amount of knowledge of a SW developer. Since we are working with a fair amount of plain text, and want to solicit feedback from folks who may not be SW devs, are we aware of any existing videos or resources that are a sort of how to orient into the github docs, maybe with a focus on the github web GUI? Also not clear whether github desktop would be useful for folks https://docs.github.com/en/desktop/overview/about-github-desktop ? Obviously we should not try to solve the whole "non-developers using github" training problem. But maybe we can try to find resources we could point folks towards. My cursory 20 minute search did not turn up anything that was obviously a good option, though. |
I agree that the videos and GItHub documentation assumes that the user will have some SW programming familiarity. My question is what level of proficiency should we assume in documenting how to use and contribute to the SSVC GitHub project? Levels of familiarity with the concepts behind how to write and version SW should be accounted for but how much of that is any one given project's responsibility? Also, do we want folks who aren't familiar with how coding works (as evidenced in the videos and help files) actively contributing. We do want the ideas they bring for sure but shouldn't the burden be on the contributor to learn? |
Can we add a "suggestion box" link to the front of the website that is just a link to the "create a new issue" link? https://github.com/CERTCC/SSVC/issues/new/choose |
This comment is now the subject of: |
With #468 done, would it be enough to add a list of links to help resources about GitHub (the links in the first comment here) and provide a pointer to that list of links? Assuming the links go on the wiki, we may want to point people from the website to there from the links. Does that pointer just get added to the bottom of the box of contributing options created for #468? |
I just created https://github.com/CERTCC/SSVC/wiki/Github-Tips-for-SSVC-contributors |
It came up in conversation that folks might be hesitant to contribute because Github use can be intimidating. So the goal here is to make it easier for folks to contribute.
Some initial thoughts on approach to resolution:
/docs
), orI think they belong in the wiki, with maybe a pointer from https://certcc.github.io/SSVC-staging/about/contributing/ to that.
Starting on a list of extant resources:
I'm not sure what other content we might want to include. Comments welcome.
The text was updated successfully, but these errors were encountered: