# 2022-08-14 weekly meeting

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

## Issues
- https://gitlab.com/veloren/veloren/-/issues/1622
- Solutions: constrain what values can be entered successfully. Or don't go backwards in time when command is entered.
- https://gitlab.com/veloren/veloren/-/issues/1627
- Imbris: this happens when it falls back to OpenGL. (either missing vulkan drivers, badly configured vulkan drivers, or no vulkan support) Just disable OpenGL in Airshipper for now?
- https://gitlab.com/veloren/veloren/-/issues/1568
- We're unsure what causes this bug. It's not just logging out. The normal timer doesn't kick in either.
- https://gitlab.com/veloren/veloren/-/issues/1553
- Can be fixed by changing the present mode setting. MR 3384 network fixes should address this. (or not - the issue might not have anything to do with physics, but just animation)
- https://gitlab.com/veloren/veloren/-/issues/1475
- https://gitlab.com/veloren/veloren/-/issues/328

## Sunday meeting improvements?

- Setup stage / vc where everyone can speak?
- Issues
- There are some that are mentioned as "this should be closed but it would be better if more people agreed"
- There are some that warrent a lot of discussion from the attendees
- zesterer: "I'm not even convinced that discussing issues is necessarily productive in a meeting, It ends up being 2 or 3 people with very specific knowledge of a system doing some sherlock holmes-ing of the issue, which doesn't really need to be done with 15 people watching"
- MRs
- The only reason that MRs are discussed at meetings is to bring attention to getting testing/code review done on them
- Should this be shifted away from a meeting?
- Maybe people could request that their MR is discussed if there is something that needs to be said about it?
- Leads
- Leads ten
- Talking in meetings
- One person tends to speak, while many others prefer to use chat
- Would threads for each issue/MR be a better way to handle things?
- This way items can stay focused
- A log can be uploaded to that issue/MR after the meeting
- Wants/Points
- DaforLynx: Miss our old game design meetings, even if not much got done in those, I just liked chatting about game design lol
- Christof: But bringing [issues/MRs] back into memory once a week feels a good idea.
- zesterer: Yeah, I think I'd like to see more collaborative user-facing meetings again where we discuss upcoming changes and community events rather than specific technical stuff
- Hannibal: Talking about what we are currently working on could be cool too, like progress discussion
- zesterer: I wonder whether a good way to resolve issues might be to have an 'issue of the day' bot that posts in new-contributors with the issue and people that want to pick it up or resolve it can discuss it there?
- Ideas
- Issue of the day
- Random issue is chosen, people who opt in are pinged
- A thread is created for this issue, the goal is to add more info about the issue, get it solved, get it tagged, whatever
- This could also help with finding more issue that could be good beginner issues, but this might be better done with the bot giving 5 untagged issues at a time
- Tagging beginner issues
- How do we know that somethign is beginner
- It's easy for us to tag things, but we should also work to add some hints on how to start
- Should this just be places in code, or people/channels to talk to?
- New contributors
- We don't make it clear when a problem is easy to do
- Can we make specific places for new contributors to onboard, or get to know the core devs?
- zest: There are any enormous number of things that are really accessible in Veloren now because we've invested time in having stuff defined in manifests and simple, composable systems to implement stuff Creating items, abilities, crafting recipes, new worldgen spawns, worldgen spots, sprites, etc. all require exceedingly little or no code
- Blogs
- Making more sustainable
- Not as much content going in these days
- More people feeling like they aren't mentioned in the blog
- Separation to community posts as well
- RFCs
- MRs
- Better templates
- More push to update the book when needed

## MRs

- https://gitlab.com/veloren/veloren/-/merge_requests/3494
- https://gitlab.com/veloren/veloren/-/merge_requests/3502
- https://gitlab.com/veloren/veloren/-/merge_requests/3493
- https://gitlab.com/veloren/veloren/-/merge_requests/3498
- https://gitlab.com/veloren/veloren/-/merge_requests/3432
- https://gitlab.com/veloren/veloren/-/merge_requests/3527

## Next week leads
Lead: @christof