[cairo-commit] [cairo-www] src/summerofcode

Carl Worth cworth at freedesktop.org
Tue Mar 18 09:36:33 PDT 2008


 src/summerofcode/ideas.mdwn |   78 ++++++++++++++++++++++++++++----------------
 1 file changed, 50 insertions(+), 28 deletions(-)

New commits:
commit 8bb5deb22cd1d067f299748a2e5f8efa8905f085
Author: Carl Worth <cworth at cworth.org>
Date:   Tue Mar 18 09:36:15 2008 -0700

    Link from Summer of Code ideas page to Summer of Code announcement
    
    Also, while we're here, reflow some paragraphs and do some minor
    edits to the text.

diff --git a/src/summerofcode/ideas.mdwn b/src/summerofcode/ideas.mdwn
index 67f80a7..eae0a53 100644
--- a/src/summerofcode/ideas.mdwn
+++ b/src/summerofcode/ideas.mdwn
@@ -1,35 +1,57 @@
 [[meta title="Cairo's Summer of Code Pool of Ideas"]]
 
-Intro on Cairo coolness
+The cairo project is glad to be participating in [Google Summer of
+Code 2008](http://code.google.com/soc/2008/). See the [cairo
+announcement](http://cairographics.org/news/2008/03/17/cairo_summer_of_code/)
+for an overview of the process to be followed by students, then come
+back here for a list of potential project ideas.
+
+Why cairo is cool
+=================
+
+Cairo has a great community of users and developers. We use a single
+mailing list for both user questions and development discussions.
+This has proved to be a very effective way of helping users become
+developers gradually. It all starts by submitting that small first
+patch. The same thing applies to our IRC channel. Please feel free to
+join and watch for a few days, to get the hang of it. We never say
+"this is not the right list/channel for this question/discussion".
+Mailing list and IRC information can be found on the [cairo contact
+page](http://cairographics.org/contact/).
+
+Overview of the library
 =======================
 
-We also have a great community of users and developers, and use the same mailing
-list for both user questions and development discussions.  This has proved to
-be a very effective way of helping users become developers gradually.  It all
-starts by submitting that small first patch.  Same thing about our IRC channel.
-Feel free to join and watch for a few days, to get the hang of it.  We never
-say "this is not the right list/channel for this question/discussion".
-Mailing list and IRC information can be found on the [cairo contact page](http://cairographics.org/contact/).
-
-
-Library improvements
-====================
-
-Cairo is a library written in C.  Its main external dependency is a library
-called Pixman, that does the software rendering for cairo.  Most of the ideas
-below do not touch on Pixman though.  See [here](http://cairographics.org/download/)
-for instructions on how to get cairo.
-
-Cairo has a very clean code base that is a pleasure to read.  We believe that
-source code should be written with being read by humans as a primary goal.
-The file names are very clean and instantly give an easily understandable map
-of the code base.  For example, the cairo xlib surface backend is implemented
-in src/cairo-xlib-surface.c.  All the other xlib-specific code is under
-src/cairo-xlib-*.c names too.  The code itself is fairly well documented with
-comments and documentation blocks for all public symbols.  The best way to start
-seeing how things work, after you have checked the [documentation](http://cairographics.org/documentation/)
-and know how to _use_ cairo, is to start skimming through src/cairo.c and
-checking out other source files from there.
+Cairo is a library written in the C programming language.  Its main
+external dependency is a library called pixman that does the software
+rendering for cairo.  Most of the ideas below do not touch on Pixman
+though.  See [cairo download](http://cairographics.org/download/) for
+instructions on how to obtain the cairo source code.
+
+Cairo has a very clean code base that is a pleasure to read.  We
+believe that source code should be written with a primary goal to make
+it easy to be read by humans.  The file names are very clean and
+instantly give an easily understandable map of the code base.  For
+example, the cairo xlib surface backend is implemented in
+src/cairo-xlib-surface.c.  All the other xlib-specific code is under
+src/cairo-xlib-*.c names too.  The code itself is fairly well
+documented with comments and documentation blocks for all public
+symbols.  The best way to start seeing how things work, after you have
+checked the [documentation](http://cairographics.org/documentation/)
+and know how to _use_ cairo, is to start skimming through src/cairo.c
+and checking out other source files from there.
+
+Summer of Code Project Ideas
+============================
+
+Each idea below is given a difficulty estimate, (Easy, Medium, or
+Hard), determined by one of the potential mentors. Please use these
+ratings to help choose an appropriate project. If a project
+description uses terms you've never heard of and is also rated Hard,
+then you can know that that's a project that will provide plenty of
+learning experiences for you. If a project is rated as Easy, then
+maybe it won't keep your interest and give you the intellectual
+challenge you're looking for.
 
   * [Medium] Implement a faster lookup-table-based rasterizer
 


More information about the cairo-commit mailing list