Changes

Jump to navigation Jump to search
Typos
Line 329: Line 329:  
=== It is 'suggested' one creates a task/issue? how do I do that ? ===
 
=== 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"
+
  "It's a good habit to create a task/issue associated with more relevant changes"
   −
Goto the zynthian issue tracker github page...
+
You will need a GitHub account to report issues. This is so that we know who reported it and can engage with them in its progress.
 +
 
 +
The best way to report a bug is to use the "Report Issue" button in the webconf. This creates a new issue in GitHub issue tracker, from a template with some data populated that is useful to the developers.
 +
 
 +
If you want to to this manually then, go to the zynthian issue tracker GitHub page...
    
[[File:Zynthian-issue-tracker-page.png|600px|thumb|center]]
 
[[File:Zynthian-issue-tracker-page.png|600px|thumb|center]]
Line 344: Line 348:     
==== So what have we gained here ? ====
 
==== 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. You also get a unique identity number that goes into the Zynthian event queue. #941 in this case. This is an identifier you can add into a connect with Pull requests so the call for work and the doing of work can be related, tracked and pull requested, accepted tested and completed.
+
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. You also get a unique identity number that goes into the zynthian event queue. #941 in this case. This is an identifier you can add into a comment with Pull requests so the call for work and the doing of work can be related, tracked and pull requested, accepted tested and completed.
   −
This sort of structure within a project like Zynthian is a very good thing. And if precisely scratching your name into a spaceship excites you, then take this as an early buzz.
+
This sort of structure within a project like zynthian is a very good thing. And if precisely scratching your name into a spaceship excites you, then take this as an early buzz.
    
[[File:Zynthian Issues page.png|600px|center]]
 
[[File:Zynthian Issues page.png|600px|center]]
 
<br clear=all>
 
<br clear=all>
   −
Because an event 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"
+
An issue 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. . .
+
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>
   −
==== How Do I fork the Zynthian github repository? ====
+
==== How Do I fork the zynthian GitHub repository? ====
 
+
[https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo The GitHub write up is here...] But in summary it's done from the appropriate zynthian page end of the process.
[https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo The github write up is here...] But in summary it's done from the appropriate zynthian page end of the process.
+
[[File:Zynthian-ui fork page.png|600px|thumb|center|Zynthian page at GitHub]]
[[File:Zynthian-ui fork page.png|600px|thumb|center|Zynthian page at Github]]
      
<br clear=all>  
 
<br clear=all>  
Line 370: Line 373:  
<br clear=all>
 
<br clear=all>
   −
Here is the confirmation in my personal github space.
+
Here is the confirmation in my personal GitHub space.
    
[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]
 
[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]
Line 376: Line 379:  
<br clear=all>
 
<br clear=all>
   −
==== Can I view files on my Zynthian-ui github repository? ====
+
==== Can I view files on my zynthian-ui GitHub repository? ====
 
[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]
 
[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]
   −
In fact there is a very useful github element that allows you to view code on gihub within a browser based tool that is nothing more or less than VSC.
+
In fact there is a very useful GitHub element that allows you to view code on gihub within a browser based tool that is nothing more or less than VSC.
   −
It's no coincidence Microsoft bought github...
+
It's no coincidence Microsoft bought GitHub...
    
To operate this feature simple select the appropriate repository home page... https://github.com/wyleu/zynthian-ui/
 
To operate this feature simple select the appropriate repository home page... https://github.com/wyleu/zynthian-ui/
Line 393: Line 396:  
<br clear=all>
 
<br clear=all>
   −
 
+
and here in VSC in GitHub showing a ctldev file ready to be examined.  
and here in VSC in github showing a ctldev file ready to be examined.  
      
[[File:Github-vsc-editing-zynthian-ui-testing-ctrldev file.png|600px|thumb|center]]
 
[[File:Github-vsc-editing-zynthian-ui-testing-ctrldev file.png|600px|thumb|center]]
511

edits

Navigation menu