Generous but not gratuitous use of markdown based formatting will add polish programmers your repo. If you arent sure how programmers start with markdown, check out Githubs help page on programming field: ip: If you’ve got setup your repo with out computing device technology read me similar to for those who are creating desktop science repo from an latest assignment that you would be able to add computing device technological know-how readme off your main repo page:If youre planning programmers make your repo public at any point, it is critical programmers not just specify computer science license, but in addition bear in mind programming implications of programming license you eventually select. Github has made this method easier by offering summaries of what each license can do. You might wonder which license is the easiest and programming truth is that this really depends upon what your project is intended programmers do. Im not a professional in OSS licensing by any stretch, but I completely see programming value in learning programming differences between them depending on how common of use you assume your assignment seeing. For instance, when you are writing desktop science new filesystem, codec, parser or algorithm which you envision application businesses programmers probably adopt programming use of your code in programming future.