Difference between revisions of "Core Coding Project"

From Scribus Wiki
Jump to: navigation, search
m (added ===Non-Core Devs=== link)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Development]]
+
__NOTOC__
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.
+
===C++ & Qt4/5 Devs Welcome===
 +
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/5]<br />
 +
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 [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] bugs
 +
* fixing [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] bugs 
 +
* fixing [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]
 +
 
 +
===Other Ideas===
 +
* 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.<br />
 +
* Look at the [http://docs.scribus.net/index.php?lang=en&page=devel/index Main API] to see examples of the Scribus classes.
  
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].
+
===Connect with Scribus Devs on IRC===
 +
Join [[Special:WebChat| #scribus]] or [irc://irc.freenode.net:6667/scribus-dev #scribus-dev] 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 />
  
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.
+
===Non-Core Devs===
 +
[[How_to_code_new_features]] is a good place to offer your contributions.  
  
Look at the [http://docs.scribus.net/index.php?lang=en&page=devel/index Main API] to see examples of the Scribus classes.
+
[[Category:Development]]

Latest revision as of 06:38, 22 November 2013

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:

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-dev 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.