forked from alicevision/AliceVision
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New AliceVision introduction files: README, CONTRIBUTING, logo, etc.
- Loading branch information
Showing
15 changed files
with
3,361 additions
and
3,099 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,74 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, gender identity and expression, level of experience, | ||
nationality, personal appearance, race, religion, or sexual identity and | ||
orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behavior and are expected to take appropriate and fair corrective action in | ||
response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
representing a project or community include using an official project e-mail | ||
address, posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team privately at alicevision-team@googlegroups.com. All | ||
complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good | ||
faith may face temporary or permanent repercussions as determined by other | ||
members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/ | ||
|
||
[homepage]: https://www.contributor-covenant.org | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
Contributing to AliceVision | ||
=========================== | ||
|
||
Alice Vision relies on a friendly and community-driven effort to create an open source photogrammetry solution. | ||
In order to foster a friendly atmosphere where technical collaboration can flourish, | ||
we recommend you to read the [code of conduct](CODE_OF_CONDUCT.md). | ||
|
||
|
||
Contributing Workflow | ||
--------------------- | ||
|
||
The contributing workflow relies on [Github Pull Requests](https://help.github.com/articles/using-pull-requests/). | ||
|
||
1. If it is an important change, we recommend you to discuss it on the mailing-list | ||
before starting implementation. This ensure that the development is aligned with other | ||
developpements already started and will be efficiently integrated. | ||
|
||
2. Create the corresponding issues. | ||
|
||
3. Create a branch and start a PR starting by [WIP], like "[WIP] My new feature" so everyone can follow the development. | ||
Explain the implementation in the PR description with links to issues. | ||
|
||
4. Implement the new feature(s). Add unit test if needed. | ||
One feature per PR is ideal for review, but linked features can be part of the same PR. | ||
|
||
5. When it is ready for review, remove "WIP" from the PR name. | ||
|
||
6. The reviewers will look over the code and ask for changes, explain problems they found, | ||
congratulate the author, etc. using the github comments. | ||
|
||
7. After approval, one of the developers with commit approval to the official main repository | ||
will merge your fixes into the "develop" branch. | ||
|
||
8. If not already the case, your name will be added to the [contributors list](CONTRIBUTORS.md). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
AliceVision Contributors | ||
======================== | ||
|
||
[libmv](https://github.com/libmv/libmv) has been an important source of inspiration for the design of openMVG and part of the code from the "multiview" and "robust_estimation" modules are based on libmv code, see [CONTRIBUTORS-libmv.md](CONTRIBUTORS-libmv.md). | ||
[openMVG](https://github.com/openMVG/openMVG) and [CMPMVS](http://ptak.felk.cvut.cz/sfmservice/websfm.pl?menu=cmpmvs) have been the first steps to build AliceVision. | ||
|
||
|
||
Individuals | ||
----------- | ||
|
||
anhtuann | ||
Bruno Duisit | ||
Carsten Griwodz | ||
Clement Aymard | ||
Clement Debize | ||
Cyril Pichard | ||
Fabien Castan | ||
Gregoire De Lillo | ||
Havard Espeland | ||
Iivari Aikas | ||
Jean Melou | ||
Lilian Calvet | ||
luxigo | ||
Michael Holroyd | ||
Michal Polic | ||
Nicolas Rondaud | ||
Pascal Monasse | ||
Pierre Gurdjos | ||
Pierre Moulon | ||
Renaud Marlet | ||
rhiestan | ||
Romain Janvier | ||
Romuald Perrot | ||
Rory McCann | ||
Sergi Pujades-Rocamora | ||
Simone Gasparini | ||
Stephane Flotron | ||
Tomas Pajdla | ||
vincentweb | ||
Yann Lanthony | ||
Yohann Salaun | ||
Zeljko Vrba | ||
|
||
|
||
Institutions | ||
------------ | ||
|
||
Czech Technical University (CTU) in Prague, Czech Republic | ||
http://cmp.felk.cvut.cz | ||
|
||
IMAGINE from the Universite Paris Est, LIGM Gaspard-Monge, France | ||
http://imagine.enpc.fr | ||
|
||
Institut National Polytechnique de Toulouse (INPT), France | ||
http://www.inp-toulouse.fr | ||
|
||
Mikros Image, Post-Production Company in Paris, France | ||
http://www.mikrosimage.com | ||
|
||
Simula Research Laboratory AS in Oslo, Norway | ||
https://www.simula.no | ||
|
||
Quine in Oslo, Norway | ||
http://www.quine.no | ||
|
||
This project has received funding from the European Union’s Horizon 2020 research and innovation programme, see [POPART](http://www.popartproject.eu) and [LADIO](http://www.ladioproject.eu). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.