---
# System prepended metadata

title: Solidity Retro 2021-02-03

---

# Solidity Retro 2021-02-03

***Post 0.8.1 edition***

Previous retrospective: https://hackmd.io/zyOFaQQ4QbWZmqNi_1MEtw
Next retrospective: TBD

## What was good?

Community
- Survey was awesome
- Communications with the community increased, probably leading to more felt transparency?
- We are mentioned in Week in Ethereum (and other newsletters) almost every week
- Forum launched.
- We did have some users contributing some (small) improvements/features/docs.

SMTChecker
- A lot of SMTChecker progress
- More people are aware/using SMTChecker
- More people contributing to the SMTChecker

SolYul
- significant amount of progress on the IR

Team
- cooperation despite remote work
- team communication on telegram and matrix.

Reviews
- Significantly more reviewing is going on.

Productivity
- we took some time to tackle complicated problems
- solc-bin cleaned up

Release
- 0.8. released 
- 0.8 was really well received


## What can be improved?

Blog [HM FH ĐM CR LA] - 5
- More technical content on blog (all the unreleased blog post topics in the issues), not a single one :(
- Technical blog posts didn't happen

Docs [BS MB KŚ] - 3
- Documentation is the primary learning resource for many people and it should be clearer in some places.

PRs [DK LA BS HM ĐM AA KŚ CR] - 8
- Too many open PRs/drafts.
- Many half abandoned PRs.
- More reviews.
- We settled for 2 pages of PRs

Planning and Discussion [DK][AB][AB] - 3
- Some planned issues tend to end up in limbo (where are templates or enum datatypes?)
- Discussions about complex issues can get a bit circular and excessive; maybe need more structure/explicit time allocation/calls/whatever
- Some complex issues are getting stuck
- Not focused enough

Breaking? [DK CP HM KŚ] - 4
- no work on breaking features yet

Team [ĐM MB CP BS CP cr FH AA][LA][AB] - 10
- Team interactions in a "remote only" world
- Design calls tend to have limited number of voices (I meant from the team -- alex)

Community [FH] - 1
- More people contributing code/docs.

## Action Items

- [ ] Revive conversation with tooling group (with the goal of selecting one feature which we will work on first)
- [ ] Read more Solidity code ([projects using Solidity list](https://docs.google.com/spreadsheets/d/1Y8Pjh7pt1HqmJ0u6N96-zT-z6Dt8rftMOGUNp8WPtDs/edit))
- [ ] Keep on fixing bugs with higher priority
- [ ] Standard library!
- [ ] Live or asynchronus Ask the Team Anything event
- [ ] In Monday meeting, collect issues to be discussed on Wednesdays so that more people can actively participate in the discussion rounds
- [ ] More ad-hoc calls between author and reviewer for PR reviews
- [ ] Actively take over abandonned PRs
- [ ] Optional: When PRs too many get stuck, have "theme weeks" for focusing on PRs on a certain topic

**Remote team interaction ideas:**
- Have "office hours" to cowork in Discord voice channel, maybe have a team voice channel? (check with Hudson which room to use best)
- See each other more often with camera on (e.g. during normal team meetings)