Flesh out the community profile

[Nerdpie]

Under 'Insights' (probably only visible to contributors for any given project...), one tab is 'Community', which shows the Community Profile. This includes several items:

• Description
• README
• Code of conduct
• Contributing - provided reference
• License - Choosing a license
• Issue templates - Reference
• Pull request templates

While several of these are a bit superfluous for this repo, I want to set them up as practice. My notes/thoughts on the topic:

• The description, while a bit... 'meh' does its job.
• The README isn't ideal, but it needs to stay this way for the site itself to render properly.
• Pretty sure I said as much in the 'contributing' file, but I don't expect many contributions to the repo; those that I may get are likely to be from friends, so I'm not too concerned about conduct.
• I really don't know what license to use; my first thought is that this is for MY site, so 'All Rights Reserved', but if someone like a feature that I add later or something, why shouldn't they be able to use the code?
• The main issues that I anticipate getting would be related to my streams, e.g. "try this mod" or "your mic sux!!1" (That last one would likely be flagged as not constructive, by the way...) Thoughts on the templates?

[raeselkie]

I think I did the license thing right so that you can see everything. Let me know if you can't.

For issue templates, I'd recommend "stream suggestions", "code suggestions", and "bug reports".

[Nerdpie]

The license file was on your fork; normally, you would want to open a PR to my repo, but we'll get there. Also, you typically want to make changes on a branch, rather than directly on the master. Lotsa details. The Git Book may help. I'm also going to see what access I can give you for the repo.

Edit: You're now a collaborator, so you should be able to directly tweak the repo. For more in-depth examples of issue templates, this project has some fairly nice ones.

Also, I'm currently using the Jekyll backend for the GitHub Page, which primarily uses Markdown for the markup language (there's a joke there somewhere...), but I can tune it to use HTML or something else if desired.

[raeselkie]

You're lucky I could even find the stuff with how my brain is going today, lol. =P I'll look through the Book thing--it's slow and if anyone looks over my shoulder, it will appear to be work. This is where the fact that I am very firmly not a programmer shows up--I have literally never needed to look at Github for anything other than "oh, that's how that works" before.

…

On Fri, Apr 5, 2019 at 1:51 PM Nerdpie ***@***.***> wrote: The license file was on your fork; normally, you would want to open a PR to my repo, but we'll get there. Also, you typically want to make changes on a branch, rather than directly on the master. Lotsa details. The Git Book <https://git-scm.com/book/en/v2> may help. I'm also going to see what access I can give you for the repo. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AvCNb_hhGJmWbUmCMdEcCUSjChLXScQhks5vd40PgaJpZM4b3ROo> .

[Nerdpie]

I've used the web UI to create some generic issue templates, but they clearly need tuned for our use.