# 2022-12-18 Weekly Meeting

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

[Link to last week's minutes](https://hackmd.io/@veloren/rkMh99Xdj)

### Topics:

#### TWiV

- Angel isn't finding time to work on it
- Changing to a month cadence?
- Christof is happy to keep working on them for the time being
- The cadence will be one to maximum three weeks depending on the amount of content to cover

#### Benefits of TWiV/Reading Club

- Brings in new developers
- TWiV
- Seeing 100 devblogs gains a lot of trust
- There was a podcast that was very impressed by this
- Players see it a lot as the "heartbeat" of the game
- People will look at the lack of blog updates as the blog being "dead"
- This is fair, since we don't have any other periodic outreach for the project otherwise
- Bless the people who wrote a lot of content :pray:
- Gives the devs a platform
- For new contributors, it can allow them to share what they've done, even if it isn't a massive essay about a core part of the game
- For devs, it's a way to write something that could go back to later
- We should announce blog content request in new-contributors as well
- Anecdotally
- People have become developers from the posts in the Rust Gamedev Newsletter
- From the perspective of players
- There are very few oppertunities to see into Veloren's progress outside of blogs
- Can see the updates from Airshipper
- YouTube/Streamed content
- Dev videos
- Are approachable for people who don't know much about the code base
- Lets people see the developers making mistakes, and thinking through problems
- When we see features in the blog, they're completed, and retrospective on the topics, rather than breaking it down in realtime
- Arewevelorenyet
- A way for people to learn about specific systems at great detail
- Links to sections of previous blog posts
- Also contains sections about core game systems

#### Backing up the Discord

- Will Discord ever make a way to back up a server? Unsure
- There's probably a bot for this

From @aweinstock
> if we could get chat history as a git repo, with like one markdown file per day and a section per channel or something, it'd be more convenient to link discussions from issues/rfcs

### Code reading club

## Next week leads

Lead: @xMAC94x
Call for Review!:
Issues (limit 7):
Minutes:

### Todo agenda:

- Release preparation