Julia and Github

[yuyichao]

@mohamed82008

I noticed almost all modules have a certain file organisation, e.g. src, docs, examples and test folders. Is there any assumption Pkg makes about the file structure when cloning it from Github, or when testing it? And how do the using and import commands deal with such a structure for local/private modules?

Please read the document https://docs.julialang.org/en/latest/manual/modules/#Modules-and-files-1

@mohamed82008

What is the purpose of the .travis.yml, appveyor.yml and .codecov.yml files?

http://lmgtfy.com/?q=travis.yml

@mohamed82008

I noticed most modules have a LICENSE file that does not really limit any action, which begs the question, why have a license file if you are not going to use it to sue anybody!?

You don’t choose a license because you want to sue somebody. In fact, if you don’t put a license than you can. Licenses – Open Source Initiative

@mohamed82008

Some modules have a different number of green, yellow and red indicators on their Github page for coverage, build, documentation, etc. How are these evaluated exactly?

Same as 2 and you should click on them to find out.

@mohamed82008

I find .gitignore, NEWS.md, README.md, and REQUIRE self-explanatory but if you want to say a word about them for sake of completion, please feel free.

.gitignore is documented in git and is googleable, REQUIRE is documented in our doc and is searchable. Others are generally googleable.

Please make some simple attempt to find out things (doc search + google search) before asking.