Thunderbird/2020 Virtual Summit Talk Ideas: Difference between revisions
Ryanleesipes (talk | contribs) (Thunderbird in 2020 added.) |
Ryanleesipes (talk | contribs) (Moved How to Improve Thunderbird Documentation) |
||
| Line 1: | Line 1: | ||
This page is intended as a space to collect ideas for presentation and discussion for the Thunderbird Virtual Summit, taking place in 2020. | This page is intended as a space to collect ideas for presentation and discussion for the Thunderbird Virtual Summit, taking place in 2020. | ||
== Submissions == | == Submissions == | ||
| Line 75: | Line 65: | ||
A little journey on how we can drastically improve the usability of Thunderbird by carefully implementing empty spaces. | A little journey on how we can drastically improve the usability of Thunderbird by carefully implementing empty spaces. | ||
== '''How to Improve Thunderbird Documentation''' == | |||
Type: Discussion | |||
Host/Speaker: [mailto:ryan@thunderbird.net Ryan Sipes [:ryanleesipes<nowiki>]</nowiki>] | |||
This discussion would cover how we might improve developer and enterprise user documentation. Would also like to touch on how to make the developer documentation easier to find for new contributors. | |||
Revision as of 17:03, 28 April 2020
This page is intended as a space to collect ideas for presentation and discussion for the Thunderbird Virtual Summit, taking place in 2020.
Submissions
Thunderbird in 2020
Type: Presentation
Host/Speaker: Ryan Sipes [:ryanleesipes]
This presentation covers the changes Thunderbird underwent in 2019 and early 2020 as an organization, and our plans to make 2020 the best year for Thunderbird yet.
How to begin with Thunderbird Development: A guide for University students and Junior Developers
Type: Presentation & Discussion
Host/Speaker: Khushil Mistry [:khushil324]
This presentation and discussion would cover my journey as a GSoC student and Thunderbird Intern. I will talk about the difficulties I faced and how university students and junior developers can start their contribution with Thunderbird.
Why we might want to start type checking our JavaScript and how that could even work
Type: Presentation & Discussion
Host/Speaker: Paul Morris [:pmorris]
JavaScript is a dynamically typed language, but now TypeScript's tooling can be used to statically type check plain vanilla JavaScript files (with some help from JSDoc). Type checking offers various benefits that include catching certain classes of bugs sooner (before they get to users) and making code easier to understand. Tools like ESLint and Prettier have improved Thunderbird's JavaScript code and developer experience. Would type checking be a good next step and how might that work?
Developing integrated OpenPGP support
Type: Presentation & Discussion
Host/Speaker: Kai Engert [:kaie]
An update will be given on the progress of the ongoing effort to add integrated OpenPGP support to Thunderbird, about the work that is still ahead of us, and we'll discuss your questions.
Thunderbird 78 Overview
Type: Presentation & Discussion
Host/Speaker: Magnus Melin [:mkmelin]
Thunderbird 78 is coming up in mid 2020. Overview of what we can expect to see in that.
Taking care of the tree
Type: Presentation & Discussion
Host/Speaker: Magnus Melin [:mkmelin]?
Short presentation of how Treeherder works, how to star failures, file bugs and such.
Hey, we got designers!
Type: Presentation & Discussion
Host/Speaker: Alessandro Castellani [:aleca]
How we're working towards a consistent visual identity and improving usability through design iterations, and how we're trying to do it without upsetting you too much.
The importance of white space, a UI experiment
Type: Presentation & Discussion
Host/Speaker: Alessandro Castellani [:aleca]
A little journey on how we can drastically improve the usability of Thunderbird by carefully implementing empty spaces.
How to Improve Thunderbird Documentation
Type: Discussion
Host/Speaker: Ryan Sipes [:ryanleesipes]
This discussion would cover how we might improve developer and enterprise user documentation. Would also like to touch on how to make the developer documentation easier to find for new contributors.