language agnostic - Structure of open source project's repository -


I am at the beginning of starting a small open source project when the main repository is cloning, with all the editions all official The complete building environment is created with all the libraries and all the tools needed to create the installer file.

I like the fact that anyone who wants to contribute, clone the repository and start whatever you want. But I am thinking that it makes it easy for bad people to make malicious installers and leave them in the wild.

How should it be structured? What do you suggest included in the repository, keeping vs vs server?

What do you think is looking for a directory layout you have tagged your question language-agnostic , But it depends on the language (s) / framework / build tool you want to use.

  • And you can create a default layout for
  • You can give some examples
  • This evil People will not stop bad things, but it will help your potential contributors.


  • Comments

    Popular posts from this blog

    windows - Heroku throws SQLITE3 Read only exception -

    lex - Building a lexical Analyzer in Java -

    python - rename keys in a dictionary -