diff options
Diffstat (limited to 'community')
| -rw-r--r-- | community/gsoc/organization_application.mdwn | 164 | ||||
| -rw-r--r-- | community/gsoc/project_ideas.mdwn | 1 | ||||
| -rw-r--r-- | community/gsoc/project_ideas/driver_glue_code.mdwn | 2 | ||||
| -rw-r--r-- | community/gsoc/student_application_form.mdwn | 50 |
4 files changed, 108 insertions, 109 deletions
diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn index 9fe3a420..ee8259b2 100644 --- a/community/gsoc/organization_application.mdwn +++ b/community/gsoc/organization_application.mdwn @@ -8,27 +8,16 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -* Link ID: - -hurd - -* Group Name: +* Organization Name: GNU Hurd -* Home Page URL: - -http://hurd.gnu.org - -* Public Email: - -bug-hurd@gnu.org - * Description: -The Hurd project is a loose community of people sharing a common interest in -developing the Hurd kernel, which is the official kernel of the [GNU operating -system](http://gnu.org). +The mission of the Hurd project is to create a general-purpose kernel suitable +for the [GNU operating system](http://gnu.org), which is viable for everyday +use, and gives users and programs as much control over their computing +environment as possible. When the Hurd was originally started in 1990, it was the last missing major component for a complete GNU system. Today Linux and other free kernels are @@ -57,8 +46,8 @@ approach. To offer these possibilities, the Hurd uses a true multiserver microkernel architecture. That makes it quite unique: The Hurd is the only general-purpose multiserver microkernel system in development today that is nearly ready for -everyday use, and offering almost perfect UNIX compatibility. (More than half -of the packages in the Debian repository are available for the Hurd.) All other +everyday use, and offering almost perfect UNIX compatibility. (Almost 65% +of all packages in the Debian repository are available for the Hurd.) All other existing true microkernel systems are either research projects not nearly complete enough for actual use, or limited to embedded systems and other special purposes, or both. @@ -71,7 +60,15 @@ contact with the most distinguished researchers in that field from the microkernel operating system groups, and have written a couple of [research papers](http://walfield.org/). -* Why is your group applying to participate? What do you hope to gain by participating? +* Home Page: + +http://hurd.gnu.org + +* Main Organization License: + +GNU General Public License (GPL) + +* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? The primary goal of course is to find and introduce new long-term contributors to the project. @@ -80,93 +77,78 @@ Aside from that, it is a way to make progress with tasks that require an amount focused work, that is hard to do for volunteers working in their spare time only. -Also it is a good possibility to get valuable input from new people, as well as +Also it is a good opportunity to get valuable input from new people, as well as spreading technical and other knowledge about the Hurd among actual and -potential contributors. More generally, participation should help raising -awareness among people who might know about the existence of the Hurd, but -otherwise having very little idea what the project is all about, and how its -progress is. +potential contributors. Last but not least, we hope the participation will have a positive effect on our community -- new impulses, increased communication etc. -* What is the main public mailing list for your group? - -bug-hurd@gnu.org, see http://lists.gnu.org/mailman/listinfo/bug-hurd - -* Where is the main IRC channel for your group? - -\#hurd on freenode.net - -* What criteria do you use to select the members of your group? Please be as specific as possible. - -The most important criterium is that the person is involved in the project for -some time, knowing the ways; so he can actually instruct the student; and if -there are tough technical questions he can't answer himself, he knows whom to -ask. - -It's also important that the mentors are reliable and helpful, so the students -won't be left on their own with any problems they face. - -* Has your group participated previously? If so, please summarize your involvement and any past successes and failures. +* Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. In 2006 and 2007, we participated under the umbrella of the GNU project, getting one slot each year. -The 2006 participation was mostly a failure. After some intitial work -(available in CVS), the student disappeared -- moving to another country and -other personal issues from what we heard. +In 2008 we participated as an organisation on our own for the first time. This +turned out extremely beneficial: With the better visibility, we get a lot +more applications (more than 20), mostly of good or excellent quality. -The 2007 participation was a considerable success. The student was very bright -and dedicated. We got some code, as well as a lot of ideas, which we continued -discussing after the end of GSoC, and he intends to put into code as well in -the future. +In 2009, we were rejected as an organisation, so we participated under the GNU +umbrella again. -In 2008 we participated as an organisation on our own for the first time. This -turned out extremely beneficial: Not only did it give us much better -possibilities to find and select good students, as we hoped. We also get a lot -more applications, mostly of good or excellent quality. +While the 2006 student disappeared midway, in all the later years all of our +students were successful -- including even one who worked on his project in +spite of not getting a slot. Half of them are regular Hurd contributors now. -We ended up with four slots. (We didn't request more, because we were not sure -whether we would be able to mentor them properly, and generally didn't want to -overdo it on our first "full" participation.) There was also a fifth student, -who worked on his project in spite of not getting a slot. +Selecting the most promising students, as well as suitable mentors, turned out +to be the most tricky part of GSoC participation -- but we learned our lesson +after the first failure: We didn't have any students that didn't meet our +expectations since then, and we also believe our mentoring is exceptionally +good now -- one project that was in serious trouble, turned out well after all, +due to effective mentor intervention. -All five students were pretty successful, most of them completing or almost -completing the original goals -- some even exceeding them. Even our weakest -student, after serious struggling in the beginning, did quite well in the end. +* If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. -Two students are still regularily working on the Hurd -- not as much as we -hoped of course, but probably as much as can be realistically expected... +2008: 4/4 -All in all, the participation was a considerable amount of work, but it was -definitely worth it :-) +(+1 inofficial in 2008) +(under GNU umbrella: 2006: 0/1; 2007: 1/1; 2009: 1/1) -* If your group has not previously participated, have you applied in the past? If so, for what sort of participation? +* If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? -- -* What license does your organization use? +* What is the URL for your ideas page? -GNU General Public License (GPL) +http://www.gnu.org/software/hurd/community/gsoc/project_ideas.html -* What is the URL to the ideas list of your organization? +* What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use. -http://www.gnu.org/software/hurd/community/gsoc/project_ideas.html +bug-hurd@gnu.org ( http://lists.gnu.org/mailman/listinfo/bug-hurd ) -* What is the main development mailing list for your group? +* What is the main IRC channel for your organization? -bug-hurd@gnu.org, see http://lists.gnu.org/mailman/listinfo/bug-hurd +\#hurd on freenode.net -* What is the application template you would like contributors to your organization to use. +* Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site. [[student_application_form]] -* What is your plan for dealing with disappearing contributors? +* What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible: -The plan is mostly to avoid that happening in the first place. For that, we -will be particularily careful with the selection of the students: Making sure +The most important criterium is that the person is involved in the project for +some time, knowing the ways; so he can actually instruct the student; and if +there are tough technical questions he can't answer himself, he knows whom to +ask. + +It's also important that the mentors are reliable and helpful, so the students +won't be left on their own with any problems they face. + +* What is your plan for dealing with disappearing students? + +The plan is mostly to avoid that happening in the first place. To this end, we +are particularily careful with selection of students: Making sure that they have no other obligations during that time; that they are motivated enough; that they actually have the necessary skills to complete the task; that they fit in our community. @@ -183,7 +165,7 @@ state where it is useful even if not finished. We will also try to limit damage by insisting that students regularily check in their work, so that we get partial results at least if someone disappears. -* What is your plan for dealing with disappearing members? +* What is your plan for dealing with disappearing mentors? As our mentors all have been with the project for some time, the risk of them disappearing is not too big. If one of them disappears nevertheless, it's not a @@ -193,32 +175,36 @@ We will encourage the students to keep discussions public as much as possible, keeping private conversations with the mentors to a minimum, so the transition should go smoothly. -* What steps will you take to encourage contributors to interact with your community before, during, and after the program? +* What steps will you take to encourage students to interact with your project's community before, during and after the program? We try to make it very clear that we expect the students to get into regular contact with us before the end of the student selection process, and won't consider their applications otherwise. This way we know that the students are able and willing to communicate with us in the first place. -After the selection, the regular contact will be kept up: We require the -students to participate in weekly IRC meetings, where we ask the students +After selection, the regular contact is kept up: We require the +students to participate in IRC meetings up to twice a week, where we ask the students actively about the work they do, problems they face, decisions they take etc. -Furthermore, we will ask them to hang around on IRC most of the time while +Furthermore, we ask them to hang out on IRC most of the time while working on their projects, so we keep in close contact. We also require the students to join our main development mailing list, so any -design questions etc. can be discussed there. We will encourage them to take +design questions etc. can be discussed there. We encourage them to take part in other conversations, not directly related to their projects, as well. -After the program we continue the regular meetings, still discussing the -projects: The application of the code created, future directions etc. +After the program we continue the regular meetings, discussing the further +development of their original projects; as well as new projects, after the +original ones are done. -* What will you do to ensure that your accepted contributors stick with the project after the program concludes? +* What will you do to ensure that your accepted students stick with the project after GSoC concludes? -We will try to invite all participating students to a conference afterwards, -where we will discuss the projects, as well as other Hurd-related topics. We -hope this will motivate them to follow up on the work they have done during the +In addition to keeping up the regular IRC meetings, +we try to invite all participating students to meet us at conferences afterwards, +where we discuss the projects, as well as other Hurd-related topics. This should +keep them motivated to follow up on the work they have done during the program, and generally help keeping them involved. -* Please select your backup group administrator. +* Is there anything else you would like to tell the Google Summer of Code program administration team? : + +* Backup Admin (Link ID): diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn index aaaa68c3..96d93869 100644 --- a/community/gsoc/project_ideas.mdwn +++ b/community/gsoc/project_ideas.mdwn @@ -78,7 +78,6 @@ See also the list of [Hurd-related X.org project ideas](http://wiki.x.org/wiki/H [[!inline pages="community/gsoc/project_ideas/language_bindings" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/virtualization" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/file_locking" show=0 feeds=no actions=yes]] -[[!inline pages="community/gsoc/project_ideas/driver_glue_code" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/server_overriding" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/tcp_ip_stack" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/nfs" show=0 feeds=no actions=yes]] diff --git a/community/gsoc/project_ideas/driver_glue_code.mdwn b/community/gsoc/project_ideas/driver_glue_code.mdwn index e1b8d22e..a4462133 100644 --- a/community/gsoc/project_ideas/driver_glue_code.mdwn +++ b/community/gsoc/project_ideas/driver_glue_code.mdwn @@ -44,3 +44,5 @@ ethernet) from a recent system, and try to port it to run in the existing driver framework in GNU Mach. Completing the port might be too involved for the exercise; but it's pretty likely that you will find something else to improve in the glue code while working on this... + +*Status*: Zheng Da is working on DDE, and has mostly completed the initial port. diff --git a/community/gsoc/student_application_form.mdwn b/community/gsoc/student_application_form.mdwn index 84070cbf..dcf9909c 100644 --- a/community/gsoc/student_application_form.mdwn +++ b/community/gsoc/student_application_form.mdwn @@ -21,7 +21,8 @@ title yourself of course -- but surely this isn't hard, if you were able to come up with your own project idea :-) Submitting the application form is only part of the deal: we expect a few other -things on top of that. Lacking these, the application is not complete, and we +things on top of that, as explained below. This is important, so please take +it seriously -- without these things, the application is not complete, and we won't consider it. One of the things we expect is that you contact us directly as soon as possible @@ -30,41 +31,44 @@ One of the things we expect is that you contact us directly as soon as possible in particular allows for very informal conversations. (Note though that we are not all in the same time zone, and people generally -don't stare at the IRC screen all the time -- it can take quite a long time -until somebody replies: even several hours. Don't get discouraged by that: Just +don't stare at the IRC screen all the time: it can take quite a long time +until somebody replies -- even several hours. Don't get discouraged by that. Just be patient and hang on, or try again later.) Contacting us as soon as possible is crucial, as regular communication is the single most important factor for a successful GSoC project. We need to see that -you are able and willing to talk to us regularily. Also it allows us getting to -know you much better than the application form alone could. +you are able and willing to talk to us regularily. Also, we get to +know you much better this way than what the application form alone would allow us to. -You shouldn't be at a loss for reason to contact us. You ought to discuss your -project and application with us for exmple: You will gain a much better idea -about the project, our expectations etc. -- in short, you will be able to +You shouldn't be at a loss for reasons to contact us. You ought to discuss your +project and application with us for exmple -- you will gain a much better idea +about the project, our expectations etc. In short, you will be able to submit a better application right from the beginnig, saving both yourself and us some tedious roundtrips :-) Also, if you really want to get involved with the Hurd project, there are -surely many things you will want to know :-) All in all, you should have ample +surely many things you will want to know -- after all, it's a fascinating +project, with a fascinating architecture etc., right? :-) + +All in all, you should have ample causes to get in touch during the application period. Bonus points if you also participate in discussions not directly related to your project. The other thing necessary to complete your application is making a change to -some part of the Hurd code, and submitting a patch with the change. (If you are +some part of the Hurd code, and submitting a patch implementing that change. (If you are not sure what that means, ask us!) This is important, as it shows that you have everything set up to start hacking -on the project (source code, tool chain, testing environment etc.), and that -you have all kinds of qualifications necessary to successfully finish the -project: general programming abilities; working in the Hurd environment; +on the project (source code, tool chain, testing environment etc.); and that +you have all kinds of qualifications necessary to successfully finish your +project: general programming skills; working in the Hurd environment; submitting patches and reacting to feedback; finding and/or asking for any information you need; and so on. Don't get us wrong: We absolutely do *not* demand that you have and know all this up front. After all, the idea of GSoC is to *introduce* you to free software development in general, and to our project specifically :-) We are -willing to help you with anything you will need to create the patch -- you just +eager to help you with anything you will need to create the patch -- you just need to ask! We actively encourage you to contact us whenever you have any doubts. Don't be @@ -72,7 +76,7 @@ afraid that we will think worse of you when you ask too much. On the contrary: this is an occasion for you to show us that whenever there is something you don't know yet, you are able to learn quickly, and know how to ask for help :-) -As for the kind of change we want: Ideally, it would be some real improvement +As for the kind of change we want: ideally, it would be some real improvement (bug fix or new feature) in a part of the Hurd related to the specific project you want to work on. (This is not always possible though -- in that case, a useful change to some unrelated part of the Hurd would also do, or perhaps some @@ -101,9 +105,17 @@ you are unsure about something. And now that you are prepared to face the enemy, here we go :-) +* Please supply your contact information here: full name, email address, IRC +nick, Jabber ID, phone number, etc. -- anything we might need to recognize you +and to keep in touch. + +* Introduce yourself: who are you, where are you from, what do you do, how did +you get here... Don't write a long essay here -- just a bunch of basic facts +you think we should know, so we get some idea whom we are talking to :-) + * Please describe the task of the project you want to work on, in your own words. Be as specific as possible. It's not sufficient to rephrase the -description from the project ideas page; show us that you actually understand +description from the project ideas page -- show us that you actually understand what this task involves! Read the available documentation (and possibly code) if necessary. And don't hesitate to ask us if you have any doubts :-) @@ -116,7 +128,7 @@ ready to be merged to mainline. Experience shows that adding the "final touches" necessary for that, tends to take up quite a lot of time -- there are always some bugs here and there, some misunderstandings about how things are supposed to work, build system issues, missing documentation, forgotten bits, -and so on. Thus, the schedule should suppose that a larger part of the main +and so on. Thus, the schedule should assume that a larger part of the main implementation work will be done by midterm! Also note that by the beginning of the summer session, you need to be able to @@ -190,8 +202,8 @@ intend to make sure you will be able to dedicate sufficient time to your project nevertheless? Please be open about this, and also mention things you are not yet sure about. -We can be flexible about time arrangements; but we need to know about any -possible obstacles up front. +We can be flexible about time arrangements; but we absolutely need to know about any +possible obstacles up front. Surprises on that score are not acceptable. * How do you intend to make sure that your code will keep on being maintained and supported properly after the end of the GSoC program? |