> For the complete documentation index, see [llms.txt](https://community.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.theiofoundation.org/about-techup/stakeholders/communities/agreement.md).

# Community Partner Agreement

<div align="center"><img src="/files/q5MWkn7w7sVqHTdS9VJe" alt=""></div>

## About this Agreement

This Agreement is to be subscribed between

* The IO Foundation as the host of the TechUp initiative, *hereinafter* TechUp\
  and
* `Community Name` \
  *hereinafter* The Community

with official email `Community Email`\
signed on the `Signature Date`                            *hereinafter* The Date\
for the following seasons `List of Seasons` *hereinafter* The Seasons

**Signatures**

For the Community\
`Community Representative Name`\
`Community Representative Title`\
`Community Representative Signature`

For TechUp (The IO Foundation)\
`TechUp Representative Name`\
`TechUp Representative Title`\
`TechUp Representative Signature`

Both parties enter this Agreement with the intention of bringing The Community into TechUp, an initiative by The IO Foundation, to support The Community and the broader TechUp Community.

This Agreement will enter in effect immediately from The Date until the end of the last of The Seasons.\
This agreement can be made void by any of the parties with a prior notice of 2 months to be filed through the [Community Management Interface](https://TIOF.Click/TUTarianCommunityLifecycleManagement).

## Requirements

To qualify as a Community Partner, The Community must verify the following requirements (*hereinafter* The Requirements):

* You are a community of developers, designers, accountants or any other industry that wishes to create positive impact in technology
* You do not charge your members with a fee to be a part of your community\
  (If you do, you can still participate in TechUp as a [Sponsor Partner](/about-techup/stakeholders/sponsors.md))
* Abide by The IO Foundation’s [Code of Conduct](https://TIOF.Click/TIOFPolicyCoC)
* Attend at least 1 [orientation session](/about-techup/activities/learn/orientation-sessions.md)
* Provide the TechUp team with all the necessary on your side to run high quality activities

{% hint style="success" %}
By signing this Agreement The Community confirms to verify The Requirements.
{% endhint %}

{% hint style="success" %}
By signing this Agreement TechUp commits to not update The Requirements without prior notice. Any such updates would be reflected on a posterior Agreement.
{% endhint %}

## Benefits

By participating in TechUp as a Community Partner, The IO Foundation will ensure that you will be granted the following benefits (*hereinafter* The Benefits):

* Access to the TechUp Space\
  Your community members, as well as other people you may invite or attract, can access all [publicly accessible activities](/about-techup/about/hidden/terminology.md#publicly-accessible-activity) and engage with a global community of technologists.\
  See the full list here. [LEARN](/about-techup/activities/learn.md) [BUILD](/about-techup/activities/build.md) [CONNECT](/about-techup/activities/connect.md)
* Ability to run your own activities\
  This includes the possibility of broadcasting to your own media channels.
* 1 [virtual booth](/about-techup/techup-space/booths.md)\
  Allows you to showcase your community, run private activities and allow people to contact you.
* 1 optional [virtual booth](/about-techup/techup-space/booths.md) for specific a event you may organize.\
  Allows you to showcase and promote such event separately.
* Increased exposure
  * Customized promotion materials\
    This will allow you to promote your community and activities more easily.
  * Promotion of your community in TechUp's official channels\
    We will give exposure to your community, at least once per Season.
  * Possibility to run a session presenting your community\
    You will have the opportunity to showcase your community.
  * Possibility to have a segment presenting your community in our Codefield productions\
    You will have the opportunity to showcase your community and your work across TIOF's Codefield audience.
  * Global platform announcements\
    Presenting your community and encouraging participants to reach out to you
* Assistance before, during and after your activities from the TechUp crew\
  We provide a comprehensive help and provide regular updates with new features and activities.
* Statistics after each of your activities\
  So that you can analyze how did your activities perform.

**Platform updates**\
The platform used for the TechUp Space releases new features very often, of which TechUp will inform you regularly.

{% hint style="success" %}
By signing this Agreement The Community acknowledges The Benefits.
{% endhint %}

{% hint style="success" %}
By signing this Agreement TechUp commits to upholding The Benefits.
{% endhint %}

{% hint style="warning" %}
By signing this Agreement, The Community also acknowledges that while the platform used by TechUp may deploy new features, these will may not be immediately available.
{% endhint %}

## Commitments

By participating in TechUp as a Community Partner, and in order to maintain your status, The Community will need to make sure to comply with the following Commitments (hereinafter The Commitments):

* Abide by The IO Foundation’s [Code of Conduct](https://TIOF.Click/TIOFPolicyCoC) and the [Dhatham House Rule](broken://pages/L53VEfiE9P4qziNtn8yR) at all times and in all your activities
* Not charge your members, or anyone you invite to your activities, a fee to access TechUp\
  (If you do, you can still participate in TechUp as a [Sponsor Partner](/about-techup/stakeholders/sponsors.md))
* Organize at least 1 activity on each of The Seasons
* Provide TechUp with the necessary information about The Community

  such as Name, Description, Logo, etc.

  * At least 1 email address that will be associated with your booth(s)\
    (Provided in the signature of this Agreement)
  * The necessary to connect your broadcast channels, should you decide to do so
* [Dress up your booth](https://help.airmeet.com/support/solutions/articles/82000443874-how-to-setup-booths-in-airmeet) no later than 7 natural days after joining TechUp
* Promote TechUp and your activities among your own members and networks\
  (you can use your own collaterals or the customized ones TechUp will provide you)
* Coordinate with the TechUp team to ensure the best experience across your activities and the whole TechUp Space.

{% hint style="success" %}
By signing this Agreement The Community commits to abide by The Commitments.
{% endhint %}

{% hint style="danger" %}
Failure of compliance with The Commitments at any time during The Seasons will trigger a review of your TechUp Membership.
{% endhint %}

{% hint style="success" %}
By signing this Agreement TechUp commits to not update The Commitments without prior notice. Any such updates would be reflected on a posterior Agreement.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://community.theiofoundation.org/about-techup/stakeholders/communities/agreement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.