Difference between revisions of "Community Development"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 45: | Line 45: | ||
* Developer development | * Developer development | ||
** [https://www.amazon.com/Expert-proficient-programmer-learning-practices/dp/1838552650 Expert C++ (Grigoryan, Wu)] | ** [https://www.amazon.com/Expert-proficient-programmer-learning-practices/dp/1838552650 Expert C++ (Grigoryan, Wu)] | ||
** [https://www.amazon.com/C-17-Complete-Guide-First/dp/396730017X C++17 - The Complete Guide (Josuttis)] | ** [https://www.amazon.com/C-17-Complete-Guide-First/dp/396730017X C++17 - The Complete Guide (Josuttis)] | ||
| Line 52: | Line 53: | ||
** [https://www.amazon.com/Effective-Modern-Specific-Ways-Improve/dp/1491903996 Effective Modern C++ (Meyers)] | ** [https://www.amazon.com/Effective-Modern-Specific-Ways-Improve/dp/1491903996 Effective Modern C++ (Meyers)] | ||
** [https://www.amazon.com/Python-Crash-Course-2nd-Edition/dp/1593279280Python Crash Course (Matthes)] | ** [https://www.amazon.com/Python-Crash-Course-2nd-Edition/dp/1593279280Python Crash Course (Matthes)] | ||
** [http://practical%20svg https://abookapart.com/products/practical-svg] | |||
** ? | ** ? | ||
| Line 64: | Line 66: | ||
Ideas for topics: | Ideas for topics: | ||
* Warnings and Assertions best practices (Thomas) | * Warnings and Assertions best practices (Thomas, Dec 22, 2020) | ||
* std::move and other modern C++ features | * std::move and other modern C++ features | ||
* How does Inkscape's garbage collection work? | * How does Inkscape's garbage collection work? | ||
| Line 71: | Line 73: | ||
* What is a node observer? | * What is a node observer? | ||
* Text (Tav) | * Text (Tav) | ||
* Exceptions | |||
Latest revision as of 15:00, 24 May 2021
Draft
Book Campaign
In the past, the Inkscape board has allocated funds to buy books for active developers. We plan on doing another book campaign, but this time opening it up to all members of the Inkscape community. There are two conditions for receiving a book:
- You've been contributing to the Inkscape community for at least six months (and plan to continue!).
- The book will aid your contributions.
If you would like a book, please add your name to the following list:
| Name | Active since | Book |
|---|---|---|
| Tav | 2007 | C++17 (Josuttis) |
| You! | 201x | Making Inkscape Awesome! |
At a later point, we'll need your contact information to send you the book.
Suggested books:
- Community development
- Website development
- ?
- UX
- https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654
- Don't Make Me Think (Krug)
- https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/
- Gamestorming: A Playbook For Innovators, Rulebreakers, and Changemakers (Grey, Brown, Macanufo);
- Developer development
Developer Presentations
(Developer development)
Developers could share knowledge and experience with short presentations, followed by discussion. This could be incorporated in the weekly developer meeting, or scheduled as a separate event (TBD). If the presenter agrees, these presentations should be recorded.
Ideas for topics:
- Warnings and Assertions best practices (Thomas, Dec 22, 2020)
- std::move and other modern C++ features
- How does Inkscape's garbage collection work?
- How to properly use signals (libsigc++)
- Why is direct manipulation of the XML tree discouraged?
- What is a node observer?
- Text (Tav)
- Exceptions