Open justaugustus opened 3 years ago
I can write these up, as I already have done for some other projects like undici. What types of issue and pull request should these encompass?
As discussed at the last INI meeting, I agreed to do a first draft. Please take a look at https://github.com/richsalz/messing-around/issues/new/choose and play around. Put feedback here.
@richsalz the grammar on the website template is off and the second section should contain a description of the problem, not what should be done.
Fixed, thanks @Nytelife26 (guess that second shot this morning did have an affect :)
**If you know the URL, please paste it here**
If you don't know the URL, please describe the page so we can
find it.
**What is the issue?**
What did you find that was wrong?
A clear and concise description of what you want to happen.
**Do you have a suggestion on how to fix this?**
If so, please describe it here.
@richsalz Obviously this is not exactly required but I feel it would help to clarify the process for suggesting linguistic changes to INI documents. This is the template we use to get community translations for KCS projects:
Applied to the INI, this would look something like:
**The phrasing I found was:** "<the sentence you are suggesting a change for>"
**Which is located at:** <link to the page it is on, and preferably the section too>
**And my suggestion is:** <your suggested changes>
**Which resolves:** <the reasoning behind your changes>
I like that change (but I'd change "which resolves" to "reason for the suggestion") but which template where you thinking of? All?
but which template where you thinking of?
The one for linguistic changes, titled "Suggest wording changes".
The one for linguistic changes, titled "Suggest wording changes".
thanks, done!
We need issue and PR templates!