> For the complete documentation index, see [llms.txt](https://docs.catalystcontributors.org/contributor-infrastructure-analysis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalystcontributors.org/contributor-infrastructure-analysis/discussions-and-meetings/kick-off-meeting.md).

# Kick Off Meeting

Initial chat going over intentions of the contributor infrastructure analysis proposal and discussion around the scope

### **Meeting Recording**

{% embed url="<https://www.youtube.com/watch?v=wJHiMnupjhU>" %}

### **Agenda**

**Proposal:** [**https://cardano.ideascale.com/c/idea/403621**](https://cardano.ideascale.com/c/idea/403621)

**Meeting:** Catalyst After Town Hall, Wednesday 13th April 2022

**Catalyst Town Hall Zoom Link**: <https://zoom.us/w/95015698561?tk=a5HYFnHz5KUrUyb-8pYHpdUxnFA5fw7ue797fQE7zoE.DQMAAAAWH2CAgRZHYlZHZUdrRFJSNm9hNy1PR001MHpRAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA&pwd=KytXalE1TkNJbnRmSWVEV3hnRE1Ddz09#success>

**Overview**

Both Catalyst and Cardano contributors need an initial setup for the tools and processes to use from day one. Our job is to research, analyse, decide and setup the main core parts of that infrastructure before contributors get started.

Contributors will take ownership of this infrastructure and own the decisions around tools and processes from the first day of being onboarded.&#x20;

This analysis focuses on ensuring contributors are functional and can begin contributing from day one.

**Proposal Tasks**

* Research
* Requirements & priorities
* Solution selection
* Future considerations
* Setup

Note - Sharing and discussion at every stage

**Main focus areas**

![](https://198384149-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBy3Yz8H6Fhw92cUOLCNP%2Fuploads%2FlpIDWnHZoD8qZHKdIphI%2Finfrastructure-analysis-areas.png?alt=media\&token=a708eadc-eca0-4389-a68e-014750806f05)

The main core parts that need to be researched, analysed and decided on are the following areas:

* **Communication**
  * Examples - Chat, Video meetings.
  * Used for - Organisation, social, community, collaboration
* **Long form content**
  * Examples - Documents, posts, forums.
  * Used for - Debate, collaboration, information collation
* **Governance**
  * Examples - Contributor votes, community votes
  * Used for - Funding distribution decisions, product decisions, community decisions
* **Treasury management**
  * Examples - Multi sigs, Treasury tools (e.g. Gnosis safe as Ethereum example)
  * Used for - Funding distribution, software and subscription payments
* **Product development workflow**
  * Examples - Task management, workflow integrations
  * Used for - Problem sensing, problem prioritisation, task tracking, accountability, task distribution

**Other areas for consideration**

These areas can be ignored for the short term and researched and decided by the contributors once they start:

* Design tools - Leave decision to be guided by design contributors
* Software tools - E.g. repository management. Leave decision to be guided by development contributors
* Software libraries and SDKs - Leave decision to be guided by development contributors
* Calendar - Organising contributor internal events, community events

**Notes**

* There may be other core areas to consider and add to this list in the near future.
* We are not looking to create new infrastructure for this initial setup work.
* The analysis should be useful for providing guidance on where future development effort could be highly impactful. For instance by finding where is most lacking in terms of functionality and completeness out of the tools and process that are selected from this research.