Contributing » Guidelines

How Can I Contribute?

There are multiple ways in which you can contribute to Taskflow:

• Use it! Let us know what you think and how it helps your jobs!
• Catch a typo in documentation or want to make it better to understand? Edit the doc source and visit Build Documentation!
• Ask questions, request new features, and catch bugs? Report it at issue tracker!
• Know how to fix an issue, bug, or add new features? Make a pull request!
• Share Taskflow with others. The more people use it, the more solid Taskflow becomes!

Your contributions are always welcome. Every contribution regardless of its size is significant to keep Taskflow thrive.

How Can I Get Credit?

Your contribution is an undeniably important piece of the Taskflow project, and we want to make sure you always get credit for your work. Depending on the technical innovation and engineering effort, we credit your contributions as follows:

• We document your commit or pull request at the Contributors page
• We advertise your organization as either users or sponsors at the Project Website
• We highlight your names in our technical presentations (e.g., CppCon) from time to time
• We co-author you in our research publications if you introduce significant innovation (see References)

Your effort really matters to us and we are eater to acknowledge your contributions! As such, we would welcome any advice and recommendations that can improve our credit system. Please contact us.

How Can I Get Started?

There are no better ways other than trying out Taskflow before you want to contribute. We summarize a few steps below for you to follow.

#include <taskflow/taskflow.hpp>  // Taskflow is header-only

int main(){
  
  tf::Executor executor;
  tf::Taskflow taskflow;

  auto [A, B, C, D] = taskflow.emplace(
    [] () { std::cout << "TaskA\n"; },   //  task dependency graph
    [] () { std::cout << "TaskB\n"; },   // 
    [] () { std::cout << "TaskC\n"; },   //          +---+          
    [] () { std::cout << "TaskD\n"; }    //    +---->| B |-----+   
  );                                     //    |     +---+     |
                                         //  +---+           +-v-+ 
  A.precede(B);  // A runs before B      //  | A |           | D | 
  A.precede(C);  // A runs before C      //  +---+           +-^-+ 
  B.precede(D);  // B runs before D      //    |     +---+     |    
  C.precede(D);  // C runs before D      //    +---->| C |-----+    
                                         //          +---+          
  executor.run(taskflow).wait();

  return 0;
}

How Can I Report Issues?

Taskflow is in active development. We are not surprised that you encounter something that needs improvement or fixes to work for your use cases. Or you want to suggest something that can improve Taskflow's functionality. Please do not hesitate to share any of these issues with by by opening an post at our issue tracker!

Please make sure that you provide all the necessary information in the issue body to communicate your problem clearly so we can work on it efficiently.

How Can I Edit the Documentation?

Documentation is just as important as the codebase! There is always a scope of improvement in documentation to add some missing information or to make it easier to read. We use the famous Doxygen to compile our documentation. You can edit the documentation source which is stored as a text file in the doxygen directory of Taskflow. After editing the file locally, you can submit your changes to us by making a patch.

How Can I Submit a Patch?

To contribute your code to Taskflow, you need to make a pull request from your fork of Taskflow. GitHub makes the development flow of submitting pull requests extremely handy as long as you follow the standard fork process.

When you make a pull request, please provide all the necessary information requested by prompts in the pull request body. In addition, make sure the code you are submitting always accounts for the following three guidelines:

• Run the tests: You must pass through our unit tests (see Building and Installing) before submitting the pull request. Our unit tests have accumulated many corner cases over the past years that can detect defects in the newly developed features or bugs when changing the existing functionality.

• Profile the change: You must inspect any performance hit caused by your changes. There are multiple ways to profile Taskflow but we recommend you try to record the runtime of completing all unit tests before and after your changes.

• Document the code: You must document the code or provide a clear explanation about your pull request. You may also provide examples specific to your new changes and include them in our cmake script.

Please let us know all people who are involved in the pull request so that we can appropriately acknowledge everyone's effort at the Contributors page. If there are any issues that you would like to communicate offline, please contact us.

How Can I Lead a Project?

There are many on-going and future projects that interest us and the Taskflow community. Given the tremendous amount of work, we welcome organizations or individuals to take lead on these projects. The table below summarizes a list of projects that need you to either take lead or contribute:

If you have identified any other projects that can be included to the list, please make a post at our issue tracker or contact us.

Your Voice Matters!

If you find Taskflow helpful, please share it with your peers, colleagues, and anyone who can benefit from Taskflow. By telling other people about how Taskflow helped you, you will help us in turn and broaden our impact.

Thank you very much for contributing!