Hey everyone,
In light of the awesome news above, I wanted to get everyone up to speed on the plan forward. There’s a bit of work to do in the near term to get ready for open source contributors.
How Issues Works
All bug reports, sync issues, feature suggestions, and packaging/distribution issues for Mailsync should be reported here on Discourse, the same as you would Mailspring issues. This is helpful because, often, there’s a fair bit of overlap between the two projects, and we don’t want to have to move things around.
GitHub Issues is strictly for our contributors, and will only contain vetted issues which are on the short-term roadmap. This way, problems can be discussed in detail on Discourse, and only the immediately relevant information moved to GitHub Issues.
Building Mailsync
We need to iron out a few wrinkles with Mailsync’s build scripts. Do NOT open issues about building Mailsync! We’ll be creating a place for build-related discussions later, separate from the issue reporting.
Building Mailspring
By default, the Mailspring repository actually relies on a compiled binary of Mailsync. This won’t be changing, as it mitigates a lot of issues regarding building and versions and whatnot. Folks who want to work on Mailspring should not have to muck around with Mailsync.
Of course, we’ll have instructions for changing what version of Mailsync you’re using, for testing purposes. Documentation forthcoming on that. Speaking of which…
Documentation, Standards, and Cleanup
Our first priority was just to get Mailsync GPL’d. There’s still a lot of work to do!
- Documentation needs to be written.
- Coding standards for Mailsync need to be formally nailed down.
- The code needs to be tidied up in places.
- The PR workflow needs to be set up.
In other words, please pardon our dust.