diff --git a/community/index.html b/community/index.html index b30fd0d..a7fba88 100644 --- a/community/index.html +++ b/community/index.html @@ -50,6 +50,9 @@
  • Community
    • +
  • + Contributing +
  •  Documentation
  •  GitHub
    • @@ -63,25 +66,25 @@
    -

    Kuadrant Community

    +

    Kuadrant Community

    Welcome to the Kuadrant community, where we're working to bring together Gateway API and Open Cluster Management to help you manage, scale, load-balance and secure your Ingress Gateways as a key part of your application connectivity, in a single cluster or the multi-cluster Kubernetes environments.

    -

    Events and Meetings Calendar

    +

    Events and Meetings Calendar

    We hold community meetings periodically, the details of which can be viewed below:

    -

    Source Code

    +

    Source Code

    Kuadrant is an Open Source project, licensed under Apache License 2.0. Source can be found on the Kuadrant GitHub organisation.

    -

    Mailing List

    +

    Mailing List

    We use a mailing list hosted by Google Groups to communicate as a community, answer questions, exchange ideas and make announcements about the project. Once subscribed, you can email the mailing list by sending an email to kuadrant@googlegroups.com.

    To subscribe, send an email to kuadrant+subscribe@googlegroups.com
    To unsubscribe, send an email to kuadrant+unsubscribe@googlegroups.com

    -

    Issue Tracking & Bugs

    +

    Issue Tracking & Bugs

    We use GitHub to track project bugs, enhancement requests and to do feature planning.

    The Kuadrant project is made up of a range of components, each with their own issue trackers. You can find all of these by navigating to a specific component, and looking at its respective Issues.

    -

    Getting Involved

    +

    Getting Involved

    We welcome new contributors to the project, be you a seasoned multi-cluster networking expert, or someone new who is looking to improve some wonky documentation you come across. Many of our respositories include variants of a good-first-issue label for issues that might be good to start with.

    -

    Thinking about some initial contributions?

    +

    Thinking about some initial contributions?

    Consider fixing some bugs, trying Kuadrant and telling us about your experience or helping us hone our documentation.

    -

    Social Media

    +

    Social Media

    You can find us on:

    -

    Security Disclosures

    +

    Security Disclosures

    If you wish to make a responsible security disclosure, please email kuadrant-security@googlegroups.com.

    See also security.txt.

    diff --git a/contributing/index.html b/contributing/index.html new file mode 100644 index 0000000..55860e3 --- /dev/null +++ b/contributing/index.html @@ -0,0 +1,210 @@ + + + + + + + + + Contributing Guide + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + + + + + + + +
    +
    + +
    + + +
    +

    Contributors Guide

    + +

    Welcome to the Kuadrant contributors guide! We are delighted that you are interested in getting involved in our project 🎉

    +

    As you get started, you are in the best position to give us feedback on areas of our project that we need help with such as:

    + +

    If anything doesn't make sense, or doesn't work when you run it, please feel free to either open a Github issue against the relevant component repository or reach out to us directly on Slack or via the Kuadrant mailing list.

    +

    Ways to Contribute

    +

    We welcome many different types of contributions covering areas such as:

    +
      +
    • New features
      • +
    • Bug fixes
      • +
    • Documentation updates
      • +
    • Release management
      • +
    • Discussions, feedback and/or guidance on Slack/Mailing List
      • +
    +

    Community Calls

    +

    Each week we host a Kuadrant Community call which provides an open forum to discuss all things Kuadrant. Anyone is welcome to come along to this meeting to propose a topic, join in on discussions or just listen in to gain some context into what's going on in the project. For further details on how to join the call, see the Events and Meetings section on the website community page.

    +

    Missed a meeting? Don't worry! All of our Community calls are recorded and available from our YouTube channel.

    +

    Ask for Help

    +

    The best way to reach us with a question when contributing is to ask on:

    + +

    Reporting Issues

    +

    To report an issue in the Kuadrant project, you can create a Github issue in the relevant component repository e.g. Limitador, Kuadrant Operator, Authorino etc. If you are unsure of which component to log against, reach out via Slack or email. The more information you can provide the easier it will be to help resolve the issue, so please don't be shy on details.

    +

    Find an Issue

    +

    A list of good first issues can be found from the Kuadrant Github projects board. These issues are categorised per component. If you see an issue you're interested in progressing mark yourself as an assignee and update the issue status to In Progress

    +

    On the rare occasion that there are no good first issues available, that’s OK! There is likely still something for you to work on. If you want to contribute but you don’t know where to start or can't find a suitable issue, you can reach out via the Public Slack channel for suggestions and/or guidance.

    + +
    + + + + +
    + + + + +
    + + + + + + + + + + + + + + + + + diff --git a/index.html b/index.html index 472d36e..a4dc083 100644 --- a/index.html +++ b/index.html @@ -50,6 +50,9 @@
  • Community
    • +
  • + Contributing +
  •  Documentation
  •  GitHub