summaryrefslogtreecommitdiff
path: root/community
AgeCommit message (Collapse)Author
2009-03-10Language bindings GSoC task: Rewrote note on previous Perl workantrik
Explicitely mention that the previous work can serve as a reference only -- most likely we can't use it directly because of missing copyright assignment. Probably it also uses a suboptimal technical approach. (Haven't checked.)
2009-03-10Language bindings GSoC task: Better starting point for Python bindingsantrik
2009-03-10Partial revert: Too much deleted while updating Lisp statusantrik
2009-03-09Mention cthread vs. pthread problem in language bindings GSoC taskantrik
2009-03-09Language bindings GSoC task: Lisp implemented last yearantrik
2009-03-09GSoC project ideas list: Inline each subpage individuallyantrik
This gives us better control -- in particular over the ordering. It will also allow easily disabling ideas without removing them alltogether, which I consider useful.
2009-03-09put myself as possible mentor, add comment on the pthread projectSamuel Thibault
2009-03-08Use actual URL instead of wiki link for project list in GSoC application formantrik
This way it can be pasted into the application form directly.
2009-03-07Update questions in GSoC application according to the actual formantrik
2009-03-07Rework introduction section in GSoC project ideas listantrik
Make it clear that we explicitely require the students to contact us, and to submit a patch as part of the application process. Most of this information is redundant with the introduction section of the student application form. This is not a problem: If they read it twice, there is a better chance that they will take it seriously...
2009-03-05community/gsoc/project_ideas: Split into subpages.Thomas Schwinge
2009-03-05Update copyright years.Thomas Schwinge
2009-03-05Add hook for additional information in GSoC student application formantrik
2009-03-05Add question about code maintainance after GSoC end to student application formantrik
The main purpose is to get a clear statement about whether the student intends to stick around after the end of GSoC...
2009-03-05Explain question about possible obstacles in GSoC student application formantrik
2009-03-05Explain question about time commitment in GSoC student application formantrik
2009-03-05Split time commitment and other activities questions in GSoC student ↵antrik
application form While these questions are related in establishing how much time the student will work on the project, they need to be handled (and explained) distinctly.
2009-03-05Reworked and explained vacations/exams question in GSoC student application formantrik
2009-03-05Merged and reworked IRC and time zone questions in GSoC student application formantrik
2009-03-05Reworked mailing list question in GSoC student application formantrik
Dropped bit about mailing list experience in general. It doesn't really mattter for our selection process. Also, make it explicit that this in not really a question, but rather a hint to subscribe ASAP.
2009-03-05Explain questions about Hurd in GSoC student application formantrik
2009-03-05Merge questions about Hurd project in GSoC student application formantrik
2009-03-05Drop questions about Hurd experience from GSoC student application formantrik
The purpose of these question was to encourage students to get some experience with using and developing Hurd during the application process. This indirect hint didn't really work anyways; and it's not necessary anymore, as we now explicitely require submitting a patch.
2009-03-05Drop question about how free software projects work from GSoC student ↵antrik
application form The students should have enough chance to get familiar with the process while creating/submitting a patch, required as part of the application process.
2009-03-05Punctuation fix in GSoC student application formantrik
2009-03-05Merge questions about Hurd involvement and free software involvment in GSoC ↵antrik
student application form
2009-03-05Explain question about learning in GSoC student application formantrik
2009-03-05State some expectations regarding the schedule in GSoC student application formantrik
2009-03-05Minor rewording is GSoC student application formantrik
2009-03-05Replaced introduction section of GSoC student application formantrik
Aside from rewording in general, we now explicitely demand that students contact us during the application period -- instead of just suggesting that they will really need to do so in order to properly answer the questions, and hoping that they take the hint... It is important that they contact us, and there is really no reason not to demand it explicitely. Also, introducing explicit patch requirement. (Instead of just asking for some "exercises" through the feedback form after they submit their applications...) Generally, we try to be much more clear about our expectations up front. This should make our work much easier when giving feedback for the applications. Also it should result in better applications -- and more happy students...
2009-03-05Drop note about size limit of GSoC student application formantrik
The FAQ for this year no longer explicitely mentions a limit -- although it still talks about external links... Let's assume there is no limit anymore.
2009-02-25GSoC application: Higher expectations regarding student communicationantrik
2009-02-24Don't have list of GSoC mentors for this year yet...antrik
2009-02-24Simplified answer to license question in GSoC applicationantrik
2009-02-24Describe 2008 GSoC participation in application formantrik
Also adapted question about no previous participation...
2009-02-24Mention getting long-term contributors as primary goal of GSoC participationantrik
This will probably make the Google folks happy, as this is officially the main purpose of the GSoC program... More importantly, past experience shows that even very skilled students are seldom able to leave a project in such a state that it is really useful for us without any followup work -- treating GSoC as a way to get code written by means of external sponsoring doesn't really work out. Finding long-term contributors is *much* more useful in the end.
2009-02-23Adapt questions in organization application according to list in 2009 FAQantrik
Note: Only the *questions* are adapted for now, not any answers...
2009-02-19Make it more obvious that these are not pure Hurd developer meetings.Thomas Schwinge
2009-02-03We still have the regular IRC meetings, this is no longer GSoC 2008 specific.Thomas Schwinge
2009-02-03Move GSoC 2008 into its own page. Add note about GSoC 2009.Thomas Schwinge
2008-12-28New homepagehttp://0xab.myopenid.com/
2008-12-15Contrary to what we said earlier, Neal and I won't be able to go to 25C3.Thomas Schwinge
2008-12-12Some tidy-up. No need to have lists of people that might show up somewhere ↵Thomas Schwinge
or rather not.
2008-12-12Initial page about the 25C3.Thomas Schwinge
2008-11-28Merge commit 'origin/master'Thomas Schwinge
2008-11-28EuroSys 2009: Neal, Samuel, Thomas intend to go.Thomas Schwinge
2008-11-27(no commit message)SamuelThibault
2008-11-28EuroSys 2009.Thomas Schwinge
2008-11-28FOSDEM 2009: no tschwinge this year. :-(Thomas Schwinge
2008-11-28FOSDEM 2009.Thomas Schwinge