changeset: 229:2ef36103abe0
tag: tip
user: Matthias-Christian Ott <ott_AT_mirix.org>
date: Fri Mar 06 15:32:35 2009 +0100
files: gsoc.md
description:
improve gsoc application
diff -r f0abdb78a409 -r 2ef36103abe0 gsoc.md
--- a/gsoc.md Fri Mar 06 13:44:26 2009 +0100
+++ b/gsoc.md Fri Mar 06 15:32:35 2009 +0100
_AT_@ -1,118 +1,125 @@
Google Summer of Code 2009
==========================
-We are applying as a mentoring organization for GSoC 2009.
+Suckless.org is applying as a mentoring organization for [Google Summer of
+Code 2009][1].
-We are home of quality software such as dwm, dmenu, libixp, and wmii, with
-a focus on simplicity, clarity and frugality. Our [philosophy](/common/) is
-about keeping things simple, small and elitist. We believe that this philosophy
-should be the mainstream philosophy in the IT world. Unfortunately the tendency
-to complex, error-prone and slow software seems to be the major driver in
-todays IT world. We aim to proof the opposite with our software projects.
+We are home of quality software such as dwm, dmenu, libixp, and wmii, with a
+focus on simplicity, clarity and frugality. Our [philosophy](/common/) is about
+keeping things simple, minimal and elitist. We believe that this philosophy
+should be the mainstream philosophy in the IT sector. Unfortunately the
+tendency to complex, error-prone and slow software seems to be predominanat
+in present-day software industry. We aim to proof the opposite with our
+software projects.
Our project scopes focus on advanced and experienced computer users. In
-contrast to the usual commercial software world or many mainstream Free
-Software projects, who focus more on average and normal end users, we believe
-that experienced users are pretty much ignored in most software projects. This
+contrast to the usual proprietary software world or many mainstream Free
+Software projects who focus more on average and normal end users we think
+that experienced users are pretty much ignored by software projects. This
is particularly true for user interfaces, such as graphical environments on
-the desktop, on mobiles, and in so-called Web applications. We believe that
-the market of experienced users is growing continously, because every computer
-user advances during the time and looks for more appropriate solutions for
-his work style from time to time.
+desktop computers, on mobile devices, and in so-called Web applications. We
+believe that the market of experienced users is growing continously, because
+every computer user advances during the time and looks for more appropriate
+solutions for his work style from time to time.
-Our philosophy makes us an ideal mentoring organization for GSoC, because our
-focus on the essential details is much more likely to deliver great achievable
-results in the limited period of time for students, than big projects with more
-likely flaky and unfinished results of other mentoring organizations.
+Our philosophy makes us an ideal mentoring organization for Google Summer
+of Code, because our focus on the essential details is much more likely to
+deliver great achievable results in the limited period of time for students,
+than big projects with more likely flaky and unfinished results of other
+mentoring organizations.
-In contrast to most projects in the Free Software world we focus on strong
-leadership. We usually have a single project leader who maintains the
-mainstream code repository and a bigger crowd of reviewers and contributors
-discussing the future improvements on the dedicated project mailing lists and
-on IRC.
+In contrast to most Free Software projects we focus on strong leadership. We
+usually have a single project leader who maintains the mainstream code
+repository and a bigger crowd of reviewers and contributors discussing
+the future improvements on the [dedicated project mailing lists and on
+IRC](/common/community.html).
We intend that each student will be the project leader of his/her
-particular project and the only individual with the privilege to commit to this
-repository. There will be one project mentor for each project and the existing
-suckless community as more rigid external reviewers of the progress of the
-student, and also of the mentor.
+particular project and the only individual with the privilege to commit to
+this repository. There will be one project mentor for each project and the
+existing suckless community as more rigid external reviewers of the progress
+of the student, and also of the mentor.
We offer at least one backup mentor for each student from our community.
-Our project ideas for GSoC 2009 are intended to focus on:
+Our project ideas for Google Summer of Code 2009 are intended to focus on:
-* Graphical user interfaces for expert users (such as more advanced concepts for mail clients, messaging clients, music players, text editors)
+* Graphical user interfaces for expert users (such as more advanced
+ concepts for mail clients, messaging clients, music players, text editors)
* Web applications for expert users collaborating the GUI concepts
* Mobile applications for expert user collaborating the GUI concepts
-* General Unix/Linux userland enhancements
+* General userland enhancements Unix-like operating systems, in particular
+ GNU/Linux
* Audio applications
* Image/Streaming/Gallery desktop and web applications
-* Foundations of a new windowing system for Unix/Linux (based on xorg drivers, but no X11- or XServer-dependency)
+* Foundations of a new windowing system for Unix-like operating systems
+ (based on xorg drivers, but no X11- or XServer-dependency)
* Improvements of our existing software projects
-Ideas
------
-Post your ideas for students projects during [Google's Summer of Code
-2009][1] here. See the [FAQ entry][2] on the ideas list for further details.
+Mentors
+-------
+The following persons have volunteered to serve as mentor during Google
+Summer of Code 2009:
+
+* Anselm R. Garbe <garbeam_AT_gmail.com>
+
+If you want to act as a mentor as well, please contact Anselm before you
+add yourself to the list.
+
+Conrete ideas
+-------------
+Post your ideas for students projects during Google Summer of Code 2009
+here. See the [FAQ entry][2] on the ideas list for further details.
The listed ideas generally require good knowledge in C and experience with
Unix-like operating systems. Their severity ranges from low to medium.
An academical background in computer science is usually not required.
-Students with very low severity projects are encouraged to work at
-least on two projects in order to stay fair to other students with more
-difficult and labour-intensive projects, although this seems to be not
-required by Google.
-
-Please consider to contact us first if you want to apply for a project,
-so we can discuss the ideas at first and avoid misunderstandings in the
-first place.
+Please consider to contact us first if you want to apply for a project, so we
+can discuss the ideas at first and avoid misunderstandings in the first place.
### Unix utilities
Although there have been several attempts to replace GNU coretutils on
GNU/Linux by smaller counterparts, no suckless collection POSIX-compliant
-utilities exits. Existing solutions could be evaluated and reused if
-possible.
+utilities exits. Existing solutions could be evaluated and reused if possible.
### Port dwm to Microsoft Windows
-Many dwm users who have to use Microsoft Windows regularly have proposed
-to port dwm to Microsoft Windows. There are several tiling window managers
-but unfortunately the majority are proprietary software.
+Many dwm users who have to use Microsoft Windows regularly have proposed to
+port dwm to Microsoft Windows. There are several tiling window managers but
+unfortunately the majority are proprietary software.
### ddm
-At the moment there is no suckless display manager for X11 thus a new
-dynamic display manager (ddm) should designed and implemented.
+At the moment there is no suckless display manager for X11 thus a new dynamic
+display manager (ddm) should designed and implemented.
### Comprehensive code audit
-All software hosted at suckless.org should undergo a comprehensive
-code audit. This includes search for vulnerabilities, verification of
-all algorithms, proof-reading of the documentation and possibly code
-clean-up. The result should be a report on all found errors and maybe
-some advice for the project maintainers. This task requires experience
-in this field.
+All software hosted at suckless.org should undergo a comprehensive code
+audit. This includes search for vulnerabilities, verification of all
+algorithms, proof-reading of the documentation and possibly code clean-up. The
+result should be a report on all found errors and maybe some advice for the
+project maintainers. This task requires experience in this field.
### stm
-There seems to be a need for a suckless ticket management system,
-as this is a common task in today's daily activity in businesses
-and in private time management. This task would include the design
-and implementation of a suckless system that solves the problem
-of TTS, ARS and TRS all together.
+There seems to be a need for a suckless ticket management system, as this
+is a common task in today's daily activity in businesses and in private
+time management. This task would include the design and implementation of
+a suckless system that solves the problem of TTS, ARS and TRS all together.
### Suckless programming language
-Although sufficient, C is not a perfect programming language. It suffers
-from legacy syntax and semantics and lacks features that make designing
-libraries and developing abstractions much easier. To address the
-shortcomings the student should survey its problems, evaluate possible
-solutions and enhance the language.
+Although sufficient, C is not a perfect programming language. It suffers from
+legacy syntax and semantics and lacks features that make designing libraries
+and developing abstractions much easier. To address the shortcomings the
+student should survey its problems, evaluate possible solutions and enhance
+the language.
-This is perhaps a bit utopian but still worth considering. Anyhow,
-it should be possible to build a working prototype by reusing existing
-solutions for parsing and code generation.
+This is perhaps a bit utopian but still worth considering. Anyhow, it should
+be possible to build a working prototype by reusing existing solutions for
+parsing and code generation.
[1]:
http://code.google.com/soc/
[2]:
http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_ideas_5167658354380897_772
Received on Fri Mar 06 2009 - 15:32:41 CET