Skip to content

Contributing_overview

Carolina Fernández edited this page Sep 25, 2015 · 4 revisions

Home > Contributing > Overview


Have you found that FELIX is a project you would like to contribute to? Fantastic! Here are some ways in which you could collaborate with us:

  • Test modules
  • ... And report issues
  • ... And fix bugs on them
  • ... And extend them
  • Develop new RMs to manage different resources
  • Improve documentation
  • User documentation (GitHub)
  • Technical documentation (software docs)
  • Spreading the word in the community
  • ... Another preferred way? Contact us

How to collaborate

Contributing to the project can be done in multiple ways:

  • Reporting issues:
  • Opening issues through the GitHub issue tracker
  • E-mail developer(s) in the corresponding development teams
  • Committing bug fixes or extensions on existing code
  • Fork the repository into your GitHub account, add your contributions and send a pull request
  • Clone the repository, push your contributions to a public repository and perform a git request-pull; then send the generated content through e-mail
  • Clone the repository, modify locally and generate some patch(es) through git format-patch push your contributions to a public repository and do a Git pull request; then send the generated content through e-mail or use git send-email
  • Adding a new module (e.g. a Resource Manager)
  • If you are interested in adding a different type of resources within the FELIX stack or adding capabilities through new modules, please add a new issue (with enhancement label) or contact the RO development team in advance.

Check the procedure page for detailed information on how to collaborate.

Contact

Development teams

  • Resource Orchestrator (RO):

[email protected]

[email protected]

  • Stitching Entity (SERM):

[email protected]

  • Transport Network (TNRM):

[email protected]

[email protected]

  • Computing (CRM), OpenFlow (SDNRM) and Expedient:

[email protected]

[email protected]

  • Monitoring System (MS):

[email protected]

  • Certificate-based Clearinghouse (C-BAS):

[email protected]

Documentation

  • User documentation Please refer to the history of the GitHub wiki page you would like to edit in order to identify the main contributor, then send an e-mail to that person. If there is no direct contact, contact [email protected].

  • Technical documentation Same as in development teams.

Clone this wiki locally