Core Coding Project: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(Created page with "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 ...")
 
No edit summary
Line 1: Line 1:
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 [http://qt.nokia.com/ Qt4] the Scribus Team would welcome your contributions. It is possible to start small and focus on incremental improvements such as
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 [http://qt.nokia.com/ Qt4] the Scribus Team would welcome your contributions. It is possible to start small and focus on incremental and very simple improvements such as the removal of compiler warnings, fixing [http://bugs.scribus.net/permalink_page.php?url=http%3A%2F%2Fbugs.scribus.net%2Fsearch.php%3Fproject_id%3D1%26severity_id%3D20%26sticky_issues%3Don%26sortby%3Dlast_updated%26dir%3DDESC%26hide_status_id%3D90 trivial], [http://bugs.scribus.net/permalink_page.php?url=http%3A%2F%2Fbugs.scribus.net%2Fsearch.php%3Fproject_id%3D1%26severity_id%3D40%26sticky_issues%3Don%26sortby%3Dlast_updated%26dir%3DDESC%26hide_status_id%3D90 tweak], and [http://bugs.scribus.net/permalink_page.php?url=http%3A%2F%2Fbugs.scribus.net%2Fsearch.php%3Fproject_id%3D1%26severity_id%3D50%26sticky_issues%3Don%26sortby%3Dlast_updated%26dir%3DDESC%26hide_status_id%3D90 minor] bugs, working through the [http://wiki.scribus.net/canvas/1.5.x_Roadmap roadmap]. These are just some ideas. Please come into #scribus or #scribus-dev on the freenode.net 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.
 
To get ideas for intermediate level projects with a 1-3 month timeframe you could take a look at our former [http://wiki.scribus.net/canvas/Category:GSOC GSoC projects].
 
Scribus users provide a constant stream of [http://bugs.scribus.net/permalink_page.php?url=http%3A%2F%2Fbugs.scribus.net%2Fsearch.php%3Fproject_id%3D1%26severity_id%3D10%26sticky_issues%3Don%26sortby%3Dlast_updated%26dir%3DDESC%26hide_status_id%3D90 feature requests] in the BTS. These present an excellent opportunity for involvement and many of them are not difficult to implement.

Revision as of 05:00, 31 December 2010

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 the Scribus Team would welcome your contributions. It is possible to start small and focus on incremental and very simple improvements such as the removal of compiler warnings, fixing trivial, tweak, and minor bugs, working through the roadmap. These are just some ideas. Please come into #scribus or #scribus-dev on the freenode.net 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.

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.