---
# System prepended metadata

title: 2022-01-09 Weekly Meeting
tags: [weekly-meeting]

---

# 2022-01-09 Weekly Meeting

###### tags: `weekly-meeting`

### Topics:

- Non-profit
- Thoughts on tagging issues
- MRs

## MRs

- https://gitlab.com/veloren/veloren/-/merge_requests/3075
 -> can we have review by combat
- https://gitlab.com/veloren/veloren/-/merge_requests/2904
 -> quite big change, is a new font okay ? If so we should ask  them for a merge conflic resolve
 - Need to ask for review by translators
- https://gitlab.com/veloren/veloren/-/merge_requests/3051
- https://gitlab.com/veloren/veloren/-/merge_requests/3049
 -> delete (2 thumbs down, no progress)
 
## To review

https://gitlab.com/veloren/veloren/-/merge_requests/3101

## Non-profit

- Remaining work
    - Figuring out who's on the board
        - Meeting with everyone here
    - Submitting forms of incorperation
- Unknowns to solve later
    - What tax exempt status looks like
    - How this would affect finances/Open Collective/money flow
    - What would the next steps be

## Tagging issues

- Big Cheung
- Issue tagging
    - Contributing in this domain
    - Why do issue tagging?
        - [External doc](https://docs.google.com/document/d/13NiiIrC3LxnjaItoclH0SKnILCLMo8nGSRtiSndbPR8/edit)
        - It's viewed as a tool to find what can be worked on
        - Allows people to explore problems better
        - Gives a better view of the heartbeat
    - Current state
        - Currently 100 untagged issues
        - Lots of resolved issues that aren't closed
    - Three main issue tags
        - Status tag
            - Gives context to the state of the issue
            - Needs discussion, ready, someone working on it...
        - Type tag
            - Bug, crash, feature, improvement
            - Helpful to organize
            - "Theme" of the issue
        - WG tag
            - Give the category of team that it pertains to
        - Each issue should have one of each
        - Beginner tags should be used to help onboard beginners
    - How to improve
        - Pre-existing issue formats
            - Auto-tag issues
        - Potentially use issue boards more
        - Actively
            - People should take time to add tags
        - Passivly
            - Improve the book
            - Help new contributors learn about this framework
        - Combing through old issues
            - Look for related MRs
            - Combing through active branches
            - On unknown issues, tag status/type/wg
            - If someone has tagged themselves as working on it, look into that
    - Questions
        - are we increasing the number of issues to be reviewed per meeting?
    - Comments
        - I feel like we could make more use of issue boards also
        - As another new contributor, I wholeheartedly agree that issue labels are important. It's amazing how much easier it is to dive into a project when there's more info on what needs to be done
        - Oh yeah templates are good
        - Potentially use the bot to dump informatino
        - Figure out how to integreate weights into the process
    - Action items
        - Figure out how to effectivly increatr thourhgput of meeting issue combing
        - Talk about whta the bot could to to help


## Next week

Lead: @Angel
Issues: @BigCheung
MRs: @xMAC94x