Thundermail Tailwind Launch
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We're organizing our launches into major release targets, the first of which was called Earlybird. The next big thing is called Tailwind. While features will be taking off on a regular basis, this helps us scope what's next into more manageable portions.
The main themes that we're aiming for are:
- Enable Thundermail as a Primary Inbox
Ensure that users can successfully adopt Thundermail as a reliable, daily email account. Focus on removing friction from onboarding, delivering consistent and timely email, and supporting natural day to day usage across devices. - Rapidly Improve Thunderbird Pro Based on Real Usage
Continuously identify, prioritize, and ship improvements that increase successful adoption of Thundermail as a primary inbox, based on real user behavior and feedback.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are identified. Start by reviewing the Tailwind launch themes and breaking them into concrete issues with code locations and acceptance criteria. The payload does not define a specific change or what completion would look like.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100