github.com/argoproj/argo-events@v1.9.1/docs/CONTRIBUTING.md (about)

     1  # Contributing
     2  
     3  ## How To Provide Feedback
     4  
     5  Please [raise an issue in Github](https://github.com/argoproj/argo-events/issues).
     6  
     7  ## Code of Conduct
     8  
     9  See [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
    10  
    11  ## Contributor Meetings
    12  
    13  A weekly opportunity for committers and maintainers of Workflows, Events, and Dataflow to discuss their current work and
    14  talk about what’s next. Feel free to join us! For Contributor Meeting information, minutes and recordings
    15  please [see here](https://bit.ly/argo-data-weekly).
    16  
    17  ## How To Contribute
    18  
    19  We're always looking for contributors.
    20  
    21  - Documentation - something missing or unclear? Please submit a pull request!
    22  - Code contribution - investigate
    23    a [good first issue](https://github.com/argoproj/argo-events/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
    24    , or anything not assigned.
    25  - Join the `#argo-contributors` channel on [our Slack](https://argoproj.github.io/community/join-slack).
    26  
    27  ### Running Locally
    28  
    29  To run Argo Events locally for development: [developer guide](developer_guide.md).
    30  
    31  ### Dependencies
    32  
    33  Dependencies increase the risk of security issues and have on-going maintenance costs.
    34  
    35  The dependency must pass these test:
    36  
    37  - A strong use case.
    38  - It has an acceptable license (e.g. MIT).
    39  - It is actively maintained.
    40  - It has no security issues.
    41  
    42  Example, should we add `fasttemplate`
    43  , [view the Snyk report](https://snyk.io/advisor/golang/github.com/valyala/fasttemplate):
    44  
    45  | Test                                    | Outcome                              |
    46  | --------------------------------------- | ------------------------------------ |
    47  | A strong use case.                      | ❌ Fail. We can use `text/template`. |
    48  | It has an acceptable license (e.g. MIT) | ✅ Pass. MIT license.                |
    49  | It is actively maintained.              | ❌ Fail. Project is inactive.        |
    50  | It has no security issues.              | ✅ Pass. No known security issues.   |
    51  
    52  No, we should not add that dependency.
    53  
    54  ### Contributor Workshop
    55  
    56  We have a [90m video on YouTube](https://youtu.be/zZv0lNCDG9w) show you have to get hands-on contributing.