Open shigeya opened 3 years ago
We may want to update Code of Conduct with two items:
1) add website url e.g. near the top 2) change the phrase 'reception and dinners' to 'receptions and meals'
We may also want to add the Code of Conduct to the website documents area: https://bgin-global.org/docs
Looks like I can assign to you once you commented:D
Created pull request to add Repository for default files such as the Code of Conduct
Per the Github documentation: "Default files (in .github folder) will be used for any public repository owned by the account that does not contain its own file of that type."
@schwentker I understand. For a system other than Windows, it is not a good idea to have a folder with a name starting with a dot since file names starting with a dot are hidden unless specified. May we change the repository name to something such as group-repository-template
?
@shigeya the best functionality is achieved by putting the code of content in .github, the docs folder or in the repository root as follows:
GitHub will use and display default files for any public repository owned by the account that does not have its own file of that type in any of the following places:
For example, anyone who creates an issue or pull request in a public repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file.
How about we create a docs folder and put the Code of Conduct file in there?
Thanks for the explanation. I didn't know about this. Let me read through the doc
I understand, but the file name should be specific and in a specific format (refer to this section). I will follow-up in the PR, bgin-global/.github#1
created pull request to merge CODE_OF_CONDUCT.md in .github folder
is there anything else we need to do with this issue?
Thanks for the effort. I haven't noticed your PR to change PDF to Markdown. Since you merged the markdown version, I think we're done.
On how to let people know your proposal. Please understand how GitHub notify people. In this case, there are several ways to do so:
-f
option (do this carefully..)I think, I prefer to do 1+3 unless the purpose of the PR doesn't change.
Anyway, It is easier to understand and tweak the change while they're in PR form (before merge)
Please refer to Adding a code of conduct to your project to do.