Difference between revisions of "GSOC how to begin"

From Scribus Wiki
Jump to navigation Jump to search
m (made some refinements and formatting changes)
Line 1: Line 1:
[[Category:GSOC]]
+
[[Category:GSOC]][[Category:GSOC 2014]][[Category:Development]]
 
+
{{Announcement|Welcome to Scribus, Welcome to the Google Summer of Code!!|Here is a short introduction on how to proceed toward a successful GSOC.}}
==== Wellcome to Scribus, wellcome to the GSOC !! ====
+
<center>__TOC__</center>
 
 
Here is a short introduction on how to proceed toward a successfull GSOC.
 
 
 
 
== Scribus is a DTP software ==
 
== Scribus is a DTP software ==
To begin with, you have to become familiar with scribus
+
To begin with, you have to become familiar with Scribus
 
 
 
* Read the wiki and documentation
 
* Read the wiki and documentation
* Use Scribus for basic uses, and for some more complex real world uses.
+
* Use Scribus for basic uses, and for some more complex real world uses. Check out [[Success_stories]]
* Note the strength and the weaknesses of the tool
+
* Note the strength and the weaknesses of the tool
  
 
== Scribus is a community ==
 
== Scribus is a community ==
Go on IRC, subscribe to the user and dev list, or to the forums.  
+
Scribus is an international community. The mailing list has users hail from all over the globe since 200x?<br />
 
+
# Ways to connect to the community are through:
Please use the same nickname on all various media
+
* IRC #scribus on freenode
(IRC, lists, forum, GSOC site, etc)
+
* [http://lists.scribus.net Mailing lists] Subscribe to the user and dev list  
 
+
* [http://forums.scribus.net Scribus forums]
Introduce yourself, your skills, your experience
 
  
Good communication is very important for the success of the GSOC :
+
'''Note:''' Please use the same nickname on all various media (IRC, lists, forum, GSOC site, etc)
We have to understand you and feel that you understand us
 
  
 
== Scribus is code ==
 
== Scribus is code ==
Line 29: Line 23:
 
Subscribe RSS to follow the bug tracker and the commits
 
Subscribe RSS to follow the bug tracker and the commits
 
Install svn and get a copy of the dev version's source
 
Install svn and get a copy of the dev version's source
Compile the dev version
+
Compile the dev version  
  
 
Look at the bug tracker and see if you could fix some bugs.
 
Look at the bug tracker and see if you could fix some bugs.
Line 35: Line 29:
 
but there are other possibly easy to fix bugs
 
but there are other possibly easy to fix bugs
 
</pre>
 
</pre>
See :
+
<big>'''See''':</big>
 
* http://bugs.scribus.net/search.php?tag_string=easyhack
 
* http://bugs.scribus.net/search.php?tag_string=easyhack
 
* [[Low Hanging Fruit‎]]
 
* [[Low Hanging Fruit‎]]
  
<pre>
+
== Strategies for Success ==
Open an account on the mantis bug tracker (request on irc).
+
# <big>Introduce yourself, your skills, your experience</big>
Study and fix a first bug
+
# <big>Good communication is very important for the success of the GSOC</big>
You can ask for help, and we'll be happy to help when possible,
+
# <big>We have to understand you and feel that you understand us</big>
but show that you can be autonomous and dont expect too much support :
 
the devs are busy.
 
Carefully test your fix :
 
it has to fix the issue and should not introduce any other issue.
 
When ready, upload your patch on the bug tracker
 
Explain the fix in your report
 
A good fix will be quickly merged in the trunk version
 
and you will know you are on the good track
 
  
Go on with a slightly more complex fix.
+
== Jump In ==
 
+
# Open an account on the mantis bug tracker (request on irc via Malex).
And so on.
+
# Study and fix a first bug
</pre>
+
# You can ask for help, and we'll be happy to help when possible
 +
# Howerver, show that you can be autonomous and don't expect too much support (currently all the devs are volunteering their precious time)
 +
# Carefully test your fix : it has to fix the issue and should not introduce any other issue.
 +
# When ready, upload your patch on the bug tracker
 +
# Explain the fix in your report
 +
# A good fix will be quickly merged in the trunk version
 +
# You will know you are on the good track
 +
# Go on with a slightly more complex fix.
 +
<big>Repeat</big>
  
 
== GSOC is a dynamic ==
 
== GSOC is a dynamic ==
 
+
<big>Taking part to the GSOC requires dedication and perseverance</big>
Taking part to the GSOC requires dedication.
+
When you enter this path, you will slowly discover the Scribus world and the the Scribus GSOC world too.
When you enter this path, you will slowly discover Scribus world
+
Simultaneously, the Scribus team members will slowly discover you too.
and the Scribus GSOC world too,
+
It's an organic process
and Scribus team members will slowly discover you too.
 
  
 
You will also discover possible Scribus GSOC projects  
 
You will also discover possible Scribus GSOC projects  
Line 69: Line 62:
 
Make propositions.
 
Make propositions.
 
Study the project.  
 
Study the project.  
Open a blog or a wiki for your project so as to show your progesses.
+
Start a blog or a wiki for your project so as to show your progress. This will also greatly benefit you.  
 
Draw diagrams or code charts, Imagine data structures.
 
Draw diagrams or code charts, Imagine data structures.
 
Make a proposal of UI. Build some real dialog window.
 
Make a proposal of UI. Build some real dialog window.
  
Those need not be perfect but will show  
+
They need not be perfect, their sole purpose is to show  
 
your understanding of the issue and of the project
 
your understanding of the issue and of the project
and your ability to organise and create solutions.
+
and your ability to brainstorm, organize, present, and persuade the team with your solutions.
 +
These are all very important skills that will serve you well from here on forward.
  
 
These steps will enable you to build a project proposal for the GSOC too.
 
These steps will enable you to build a project proposal for the GSOC too.
Line 82: Line 76:
 
how long time will each step require.
 
how long time will each step require.
  
Be ambitious, be realistic and thou shall succeed !
+
Be ambitious, be realistic (levelheaded) and thou shalt succeed !
  
When accepted, this project will be full time work for you
+
When accepted, this project will be full time job for you for the duration of 2 months. As per the GSOC agreement.
during 2 months.
 

Revision as of 03:24, 13 January 2014

Announcement: Welcome to Scribus, Welcome to the Google Summer of Code!!
Here is a short introduction on how to proceed toward a successful GSOC.

Scribus is a DTP software

To begin with, you have to become familiar with Scribus

  • Read the wiki and documentation
  • Use Scribus for basic uses, and for some more complex real world uses. Check out Success_stories
  • Note the strength and the weaknesses of the tool.

Scribus is a community

Scribus is an international community. The mailing list has users hail from all over the globe since 200x?

  1. Ways to connect to the community are through:

Note: Please use the same nickname on all various media (IRC, lists, forum, GSOC site, etc)

Scribus is code

You have to discover the code and the tools for coding

Subscribe RSS to follow the bug tracker and the commits
Install svn and get a copy of the dev version's source
Compile the dev version 

Look at the bug tracker and see if you could fix some bugs.
Some easy to fix bugs are marked with the "easyhack" tag
but there are other possibly easy to fix bugs

See:

Strategies for Success

  1. Introduce yourself, your skills, your experience
  2. Good communication is very important for the success of the GSOC
  3. We have to understand you and feel that you understand us

Jump In

  1. Open an account on the mantis bug tracker (request on irc via Malex).
  2. Study and fix a first bug
  3. You can ask for help, and we'll be happy to help when possible
  4. Howerver, show that you can be autonomous and don't expect too much support (currently all the devs are volunteering their precious time)
  5. Carefully test your fix : it has to fix the issue and should not introduce any other issue.
  6. When ready, upload your patch on the bug tracker
  7. Explain the fix in your report
  8. A good fix will be quickly merged in the trunk version
  9. You will know you are on the good track
  10. Go on with a slightly more complex fix.

Repeat

GSOC is a dynamic

Taking part to the GSOC requires dedication and perseverance When you enter this path, you will slowly discover the Scribus world and the the Scribus GSOC world too. Simultaneously, the Scribus team members will slowly discover you too. It's an organic process

You will also discover possible Scribus GSOC projects and the one you might work on.

Make propositions. Study the project. Start a blog or a wiki for your project so as to show your progress. This will also greatly benefit you. Draw diagrams or code charts, Imagine data structures. Make a proposal of UI. Build some real dialog window.

They need not be perfect, their sole purpose is to show your understanding of the issue and of the project and your ability to brainstorm, organize, present, and persuade the team with your solutions. These are all very important skills that will serve you well from here on forward.

These steps will enable you to build a project proposal for the GSOC too.

Define and plan the content of your future work : what shall you achieve, how long time will each step require.

Be ambitious, be realistic (levelheaded) and thou shalt succeed !

When accepted, this project will be full time job for you for the duration of 2 months. As per the GSOC agreement.