Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Factorize configuration files across projects #412

Open
AntoineRondelet opened this issue Oct 29, 2021 · 1 comment
Open

Factorize configuration files across projects #412

AntoineRondelet opened this issue Oct 29, 2021 · 1 comment
Assignees
Labels
build Task related to the compilation and execution of the project tooling Task related to the tooling used in the repository

Comments

@AntoineRondelet
Copy link
Contributor

AntoineRondelet commented Oct 29, 2021

This issue is not directly related to Zeth, but rather concerns:

  • Zecale
  • Libsnark/ff
  • Zeth

These projects use cmake and hold rather similar versions of files in the cmake directory. While there is value to have these files replicated in each projects (each project has its own configuration), in many cases the files in cmake/ remain untouched and are project independent. Duplicating these files is increasing the chances of inconsistencies across projects (e.g. a make target is renamed on zeth but the content of cmake/ isn't updated on the other repos). There may be value to try to factorize these config files in one location that is shared across all repos. Let's think about that.

@AntoineRondelet AntoineRondelet added build Task related to the compilation and execution of the project tooling Task related to the tooling used in the repository labels Oct 29, 2021
@AntoineRondelet AntoineRondelet self-assigned this Oct 29, 2021
@AntoineRondelet
Copy link
Contributor Author

Similar thing for files like CODING_STANDARDS.md, CODE_OF_CONDUCT.md, and CONTRIBUTING.md. These could be hosted on a Github repo to which we link in the individual's README's to avoid duplication of these files and keep them consistent. These files can act as "parent/default" files and can be overwritten on a case by case basis in the specific repos, as needed, as we do in Zecale for instance: https://github.com/clearmatics/zecale/blob/master/CODING_STANDARDS.md#coding-standards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Task related to the compilation and execution of the project tooling Task related to the tooling used in the repository
Projects
None yet
Development

No branches or pull requests

1 participant