584
edits
Changes
Jump to navigation
Jump to search
Line 56:
Line 56: − === It is 'suggested' one creates a task/issue? how do I do that ? === − − "it's a good habit to create a task/issue associated with more relevant changes" − − Goto the zynthian issue tracker github page... − − [[File:Zynthian-issue-tracker-page.png|600px|thumb|center]] − − <br clear=all> − − Then fill out something relevant − − [[File:Duo-piano feature request.png|600px|thumb|center]] − − <br clear=all> − − ==== So what have we gained here ? ==== − Well, the communal Zynthian entity gains an area of interest. Even if the task, dies on the vine, and nothing more gets done, there is a possible development signposted. Because these could be allocated to somebody else at some later time which means the code magically appears from someone you probably would never have met. Of course if you go ahead yourself and write it then so much the better. You move that one step closer to the "Had An Open Source PR accepted" − − The github environment allows these relationships to be managed and the more structured this stuff is the less intimidating it becomes. . . − − <br clear=all> Line 208:
Line 186: + + + + + + + + + + + + + + + + + + + + + +
Contributing to Zynthian Development (view source)
Revision as of 12:54, 21 January 2024
, 21 Januaryno edit summary
No. Your code will be checked by people who control access to the core repository that you get your code from. They will not allow anything into the code base that they don't trust or that doesn't meet house rules about how stuff is written and presented.
No. Your code will be checked by people who control access to the core repository that you get your code from. They will not allow anything into the code base that they don't trust or that doesn't meet house rules about how stuff is written and presented.
=== How is code of the zynthian maintained? ===
=== How is code of the zynthian maintained? ===
So we better write some code.
So we better write some code.
<br clear=all>
=== It is 'suggested' one creates a task/issue? how do I do that ? ===
"it's a good habit to create a task/issue associated with more relevant changes"
Goto the zynthian issue tracker github page...
[[File:Zynthian-issue-tracker-page.png|600px|thumb|center]]
<br clear=all>
Then fill out something relevant
[[File:Duo-piano feature request.png|600px|thumb|center]]
<br clear=all>
==== So what have we gained here ? ====
Well, the communal Zynthian entity gains an area of interest. Even if the task, dies on the vine, and nothing more gets done, there is a possible development signposted. Because these could be allocated to somebody else at some later time which means the code magically appears from someone you probably would never have met. Of course if you go ahead yourself and write it then so much the better. You move that one step closer to the "Had An Open Source PR accepted"
The github environment allows these relationships to be managed and the more structured this stuff is the less intimidating it becomes. . .
<br clear=all>
<br clear=all>