Skip to content

Commit 1980e0e

Browse files
pzainopzaino
authored
Merge pull request #14 from RISC-OS-Community/develop
cumulative merge of changes from Develop to Main repo
2 parents 534eb06 + 1827d95 commit 1980e0e

File tree

5 files changed

+142
-3
lines changed

5 files changed

+142
-3
lines changed

‎.gitattributes‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ tests/**/Hdr/** gitlab-language=armasm linguist-language=assembly linguist-detec
1616
tests/**/s/** gitlab-language=armasm linguist-language=assembly linguist-detectable=true
1717
tests/**/fth/** gitlab-language=forth linguist-language=forth linguist-detectable=true
1818
tests/**/p/** gitlab-language=prolog linguist-language=prolog linguist-detectable=true
19-
**,fe1 gitlab-language=make linguist-language=makefile
20-
**,fff gitlab-language=text linguist-language=text
21-
VersionNum gitlab-language=c linguist-language=c
19+
**,fe1 gitlab-language=make linguist-language=makefile linguist-detectable=true
20+
**,fff gitlab-language=text linguist-language=text linguist-detectable=true
21+
**,ffb gitlab-language=bbcbasic linguist-language=bbcbasic linguist-detectable=true
22+
VersionNum gitlab-language=c linguist-language=c
23+

‎.github/ISSUE_TEMPLATE/question.yaml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
name: Question
2+
description: Ask us a question for this repository/project
3+
title: "[Question]: "
4+
labels: [question]
5+
assignees:
6+
- code-reviews-team
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to ask us your question, we'll answer as soon as we have a chance.
12+
- type: input
13+
id: contact
14+
attributes:
15+
label: Contact Details (optional)
16+
description: How can we get in touch with you if we need more info?
17+
placeholder: ex. [email protected]
18+
validations:
19+
required: false
20+
- type: textarea
21+
id: question
22+
attributes:
23+
label: What would you like to ask?
24+
description: type your question in the box below
25+
placeholder: I would like to ask...
26+
value: "I would like to ask..."
27+
validations:
28+
required: true
29+
- type: checkboxes
30+
id: terms
31+
attributes:
32+
label: Code of Conduct
33+
description: By submitting this issue, you agree to follow our [Code of Conduct](./CODE_OF_CONDUCT.md)
34+
options:
35+
- label: I agree to follow this project's Code of Conduct
36+
required: true

‎.github/ISSUE_TEMPLATE/requirement.yaml‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
name: Requirement Report
2+
description: File a requirement report
3+
title: "[Requirement]: "
4+
labels: [requirement, enhancement, feature]
5+
assignees:
6+
- code-reviews-team
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this requirement report!
12+
- type: input
13+
id: contact
14+
attributes:
15+
label: Contact Details (optional)
16+
description: How can we get in touch with you if we need more info?
17+
placeholder: ex. [email protected]
18+
validations:
19+
required: false
20+
- type: textarea
21+
id: user
22+
attributes:
23+
label: As a RISC OS User I would like to
24+
description: Tell us about your requirement from a general user point of view
25+
placeholder: I would like that...
26+
value: "a new feature would be added that does x and y"
27+
validations:
28+
required: false
29+
- type: textarea
30+
id: developer
31+
attributes:
32+
label: As a RISC OS Software Developer I would like to
33+
description: Tell us about your requirement from a software developer point of view
34+
placeholder: I would like that...
35+
value: "a new feature would be added that does x and y"
36+
validations:
37+
required: false
38+
- type: textarea
39+
id: vendor
40+
attributes:
41+
label: As a RISC OS Vendor/Hardware designer I would like to
42+
description: Tell us about your requirement from a vendor point of view
43+
placeholder: I would like that...
44+
value: "a new feature would be added that does x and y"
45+
validations:
46+
required: false
47+
- type: checkboxes
48+
id: terms
49+
attributes:
50+
label: Code of Conduct
51+
description: By submitting this issue, you agree to follow our [Code of Conduct](./CODE_OF_CONDUCT.md)
52+
options:
53+
- label: I agree to follow this project's Code of Conduct
54+
required: true

‎.github/ISSUE_TEMPLATE/tasks.yaml‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
name: Tasks Report
2+
description: File a tasks report
3+
title: "[Tasks]: "
4+
labels: [enhancement]
5+
assignees:
6+
- code-reviews-team
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this tasks report!
12+
- type: input
13+
id: contact
14+
attributes:
15+
label: Contact Details (optional)
16+
description: How can we get in touch with you if we need more info?
17+
placeholder: ex. [email protected]
18+
validations:
19+
required: false
20+
- type: textarea
21+
id: background
22+
attributes:
23+
label: Background
24+
description: Provide some context for the tasks list
25+
placeholder: Ipsum lorem...
26+
value: "Ipsum lorem..."
27+
validations:
28+
required: true
29+
- type: textarea
30+
id: task-list
31+
attributes:
32+
label: Definition of Done
33+
description: Provide an easy to understand definition of done for each task
34+
placeholder: "- [ ] A"
35+
value: "- [ ] Task A is done when..."
36+
validations:
37+
required: false
38+
- type: checkboxes
39+
id: terms
40+
attributes:
41+
label: Code of Conduct
42+
description: By submitting this issue, you agree to follow our [Code of Conduct](./CODE_OF_CONDUCT.md)
43+
options:
44+
- label: I agree to follow this project's Code of Conduct
45+
required: true

‎CONTRIBUTING.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,8 @@ In general you'd want to:
125125

126126
One of the best and most complete C Coding style guide is the Linux Kernel C Coding Style Guide. So, for all general C related coding you should follow such set of rules (learning it can also help you a lot in your Software Engineering career), here is the Linux Coding Style guide for you: [Linux Coding Style Guide](https://www.kernel.org/doc/html/v5.10/process/coding-style.html).
127127

128+
If you are not an experienced C developer and need an easier to read coding manual before getting into the Linux coding style, we recommend to get copy of "The Elements Of C Programming Style" by Jay Ranade and Alan Nash, it's a very good introduction to good C coding style practices and goes from zero to competent C developer on the matter of coding style elements (it doesn't teach you C!).
129+
128130
Given that RISC OS is not linux and has its own ToolBox you shall consider all colliding rules to be superseded by the corresponding rule in the RISC OS Style Guide, here is a link to how to obtain it: [RISC OS Style Guide](https://www.riscosopen.org/wiki/documentation/show/Style%20Guide)
129131

130132
Also please have a look at the Programming Conventions hosted on RISCOS.info, [click here to read them](http://www.riscos.info/index.php/Programming_Conventions)

0 commit comments

Comments
 (0)