Skip to content
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

Add "help wanted" instructions to site #180

Open
jordangov opened this issue Mar 19, 2018 · 10 comments
Open

Add "help wanted" instructions to site #180

jordangov opened this issue Mar 19, 2018 · 10 comments

Comments

@jordangov
Copy link
Contributor

Content

I would like the instructions on "how to open source" to include information on how to use the Code.gov "help wanted" labels so that GH issues can be displayed on the Code.gov site. Instructions for using these labels can be found on the "code-gov" repo.

Page(s) Affected

https://www.code.mil/how-to-open-source.html

But maybe also https://www.code.mil/frequently-asked-questions.html ?

@jotasprout
Copy link

I'd like to help here. I'd also like to mention that the site shows some closed issues under "Open Tasks."

@jordangov
Copy link
Contributor Author

Sounds great! I'm thinking that we may need a separate page for this. We have a "how to open source" which is more about the path to open sourcing a project. I foresee this (and other content) on a page about how to maintain an OSS project. Thoughts?

@jotasprout
Copy link

@jordangov That's what I thought the intent was. Not so much "how to open sources" as "How to contribute" -- like for Hacktoberfest (starting in a few days) participants. Basic instructions on forking, requirements, etc. -- am I correct?

Should we, along with this issue, open an issue to tag appropriate issues with "Hacktoberfest" as others do?

@jordangov
Copy link
Contributor Author

Sounds good. on the tagging, I don't think we'll be adding the Hacktoberfest labels. That would imply support of the event by the Federal Government, which I'm not ready to do. :)

@petercr
Copy link

petercr commented Oct 4, 2018

I would be glad to just on this one and help out 😎 👍

@jordangov
Copy link
Contributor Author

jordangov commented Oct 4, 2018

Thanks @petercr! PR review is always welcome (once we have a PR), and once we have a first pass, additions are always good.

@jotasprout
Copy link

Working on this and #240 today.

@jotasprout
Copy link

I am including screenshots. Should they be stored in /assets/images?

jotasprout added a commit to jotasprout/code.mil that referenced this issue Oct 8, 2018
Includes guidance for README and CONTRIBUTING pages, standards for Issues and Pull Requests, and instructions for applying and creating labels for issues.

Resolves: Code-dot-mil#180, Code-dot-mil#240
@jordangov
Copy link
Contributor Author

I think so, yes.

@GrooveCS
Copy link

GrooveCS commented Sep 1, 2020

Hello,

Is this still an open issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants