Core Coding Project: Difference between revisions
Jump to navigation
Jump to search
(De-cluttered page. Hopefully it's more readable with more call to action motivation) |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
===C++ & Qt4/5 Devs Welcome=== | |||
===C++ & Qt4 Devs Welcome=== | |||
This is the primary and arguably the most complex work that can be done to improve Scribus.<br /> | This is the primary and arguably the most complex work that can be done to improve Scribus.<br /> | ||
If you are knowledgeable or at least familiar with software engineering using C++ and [http://qt.nokia.com/ Qt4]<br /> | If you are knowledgeable or at least familiar with software engineering using C++ and [http://qt.nokia.com/ Qt4/5]<br /> | ||
the Scribus Team would welcome your contributions. | the Scribus Team would welcome your contributions. | ||
=== Some Ideas Where to Start === | === Some Ideas Where to Start === | ||
| Line 20: | Line 19: | ||
===Connect with Scribus Devs on IRC=== | ===Connect with Scribus Devs on IRC=== | ||
Join [ | Join [[Special:WebChat| #scribus]] or [irc://irc.libera.chat:6697/scribus #scribus] on Freenode and talk to the developers. <br /> | ||
Different team members are focusing on different areas, so if you are interested in a particular Scribus subsystem then you should get in touch with the respective developer.<br /> | Different team members are focusing on different areas, so if you are interested in a particular Scribus subsystem then you should get in touch with the respective developer.<br /> | ||
===Non-Core Devs=== | |||
[[How_to_code_new_features]] is a good place to offer your contributions. | |||
[[Category:Development]] | |||
Latest revision as of 16:51, 24 February 2022
C++ & Qt4/5 Devs Welcome
This is the primary and arguably the most complex work that can be done to improve Scribus.
If you are knowledgeable or at least familiar with software engineering using C++ and Qt4/5
the Scribus Team would welcome your contributions.
Some Ideas Where to Start
It is possible to start small and focus on incremental and very simple improvements such as:
- the removal of compiler warnings
- fixing trivial bugs
- fixing tweak bugs
- fixing minor bugs
- working through the roadmap
Other Ideas
- To get ideas for intermediate level projects with a 1-3 month timeframe you could take a look at our former GSoC projects.
- Scribus users provide a constant stream of feature requests in the BTS. These present an excellent opportunity for involvement and many of them are not difficult to implement.
- Look at the Main API to see examples of the Scribus classes.
Connect with Scribus Devs on IRC
Join #scribus or #scribus on Freenode and talk to the developers.
Different team members are focusing on different areas, so if you are interested in a particular Scribus subsystem then you should get in touch with the respective developer.
Non-Core Devs
How_to_code_new_features is a good place to offer your contributions.