View source for Summer Coding 2010/zh-cn

Fedora 暑期代码大赛连接了学生、导师、子项目和赞助者，提供了在暑期练习编程的好机会。

该页面包含对所有人都有用的信息。([http://bit.ly/FSC-2010 Short URL.])

__TOC__

== 总则 ==

[[Summer Coding 2010 schedule]] 介绍了本次活动的时间表。

[[Summer Coding 2010]] （即本页）是查找本次活动信息的主要来源。

{{:Communication for Summer Coding 2010}}

== 如果你是学生 ==

该部分包含了愿意在 2010 Fedora 暑期代码大赛中为 Fedora Porject 或者 JBoss.org 做贡献的学生所需要的内容。

如果你有想法或者想要参与到 Fedora 或者 JBoss.org 中，你应该已经关注过社区和 [[Communicating and getting help|联系方式]].

=== 学生时间表 ===

{{:Summer Coding 2010 schedule}}

=== 学生参与步骤 ===

{{:Summer Coding 2010 step-by-step for students}}

=== 为什么在暑期参加自由开源软件？ ===

<fuzz>当你从事自由和开源软件工作的时候，你创建了一个将随你终身发展的工作。<fuzz>When you work in the open on free software, you create a body of work that follows you for the rest of your life.  相比于那些被数以千计学生做过的并且会在学期末被扔到抽屉最底层的编程作业来说，在自由开源软件工作是一个为活跃项目做贡献的机会。

在自由开源软件工作给你一个机会去：

* 和现实中的大型代码库协作。
* 和现实的工程师及其他专业人士协作。
* 在学习和<fuzz>获得学生价值<fuzz>的过程中为有意义的事情作贡献Contribute to something meaningful while learning and earning student value.
* 学习那些将要在毕业后的技术领域运用的工具和过程。
* 在全球领域结交朋友。
* 可能带来毕业后的实习或者工作机会。

=== 为什么在 Fedora 和 JBoss.org? 工作 ===

我们是一个庞大并且多元化的项目。我们对于和新贡献者合作以及帮助他们取得成功方面富有经验。

很多长期的贡献者继续为项目提供专业的知识和指导工作。那些和社区保持联系并取得成绩的人获得关注。他们会从中获得工作机会，包括被 Red Hat 雇用。[[GSoC report 2009|Past Google Summer of Code students were hired by Red Hat, as well as interns in various positions]].  这只是一个例子，表明在 JBoss.org 和 Fedora 项目社区的经历将从多方面影响你的职业生涯。

和许多长期的社区一样，你可以找到很多具有回报意义的子项目去从事。

你应该知道为自由和开源软件做贡献并不要求你具有超强的编程能力，或者其他的“超能力”。你只需要感兴趣并保有足够的好奇心，<fuzz>并且能接受“有价值的失败”<fuzz>。You just need be interested and curious enough, and be willing to become comfortable being ''productively lost''.  这是一个从发现和探索中学习的过程。

=== 你愿意从那些导师已有的提议开始么？ ===

导师们和子项目们已经设置好了暑期代码大赛的页面 [[Summer Coding 2010 ideas]] 。 在那里你可以找到：

* 你中意的完整的提议；
* 建议和使用个案来帮助你完成你自己的提议；
* 到子项目/上游项目的链接，让你了解更多。

举例来说，如果你对为 [http://rhq-project.org RHQ Project] 工作感兴趣，那里有一个连接指向他们网站上的提议页面以及他们的联系方式。如果你和他们联系，你可以了解到更多的提议，以及分享你的想法。

哪怕你觉得导师的提议启发了你，你也需要有对这个提议有自己的想法。

{{admon/note|Mentors have until 14 April to finish idea pages|Mentors are updating those pages up until then, so it crosses over with the student schedule.  If you see an idea you like, begin talking with the mentor immediately.  Check back with the [[Summer coding 2010 ideas|idea page]] regularly and put a ''watch'' on the page.}}

=== Do you have an idea you need a mentor for? ===

People can be most passionate about an idea that is their own.  That passion can be what helps you get through the hard part of the project.

Do you know what person or sub-project in JBoss or Fedora that might be the mentoring group for your idea?

You need to do these things:

# Contact the relevant sub-project for your idea or contact [http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss the discussion group].  
# Be prepared to explain your idea, receive input and criticism, and grow (or reduce) the idea so it has the best chance of being accepted for Fedora Summer Coding.
# Create an idea page, noting in the section for mentors that you are looking for a mentor.  Use [[How to create an idea page for Summer Coding]] to make the page.

=== 您已经在Fedora或JBoss社区做事了吗？ ===

我们“鼓励”Fedora及JBoss社区中的学生用户、参与者或贡献者加入进来。

您对想要在这次活动中看到什么有何想法？

你在这个项目的一个可能想要指导你进行2010暑期代码大赛的领域工作吗？例如，如果你为Fedora文档项目（Fedora Documentation Project）写了文档或者为Fedora的本地化项目（Fedora Localization Project）做了翻译，和你的群组讨论一下看看是否有一些想法可以做成一个学生计划，你可以请另一个子项目成员做指导（导师）。

=== What are my chances of having a proposal accepted? ===

This is the first year we are running a solo summer coding program, and many details are being finalized in parallel with taking and reviewing proposals.  For example, sponsors are still being sought, which affects the size of the funding pool.  We'll announce this information as it is known and decided; final funding-per-student may vary and is dependent on the quality of proposals as well as size of funding pool.

We may not be able to fund as many projects as we ran under the Google Summer of Code, but our goal is on quality and not quantity.

We intend to run Fedora Summer Coding in the future.  One idea is to run it for the summer in the Southern Hemisphere (Sep 2010 to Feb 2011).  If you don't get in this round, keep trying!  You are welcome to keep lurking and offering ways to help improve the program for future rounds.

== 如果您是导师 ==

想要成为导师是件好事情。加入 [http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss 讨论列表] 并做个自我介绍、说说您的项目构想等等。

您必须致力于与学生工作并要做为学生、分项目、上游以及整个项目(Fedora项目或JBoss.org)的联络人员。 您可以是Fedora分项目的人员、也可以是来自像JBoss.org项目的上游人员、也可以是大学资助学生的人员等等。

在Summer Coding 2010主列表讨论后，您将会受邀加入私有导师讨论列表 

=== 导师时间表 ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for mentors ===

{{:Summer Coding 2010 step-by-step for mentors}}

=== What to do with your ideas ===

Put them here on the [[:Category:Summer Coding 2010 ideas|Summer Coding ideas]] page.  Reference [[How to create an idea page for Summer Coding]] when creating your idea.

We are looking in to using [http://openhatch.org OpenHatch] for managing ideas.  If you are interested in learning more about that, join us on the [http://lists.fedoraproject.org/mailman/listinfo/summer-coding Summer Coding SIG mailing list].

=== 如何跟学生工作 ===

One way is to provide an idea for students to work on.  This idea might be very well planned out, in which case you may need a high-level of contact with the student to get it implemented correctly.

It is harder to find success where you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need. 

Where you can have looser ideas, you may be able to find a student who works as a sort-of intern who can implement a solution to a use case you have.  In past experiences, students going after a use case are more likely to get somewhere with self-direction.

You may also want to work with a student who brings an idea to your sub-project.  This requires a different level of communication throughout the project, but can be the most rewarding.

=== 导师职责 ===

You are an essential part of the student's success, the project's success, and the success for your overall organization (Fedora, JBoss.org, or another).

Your responsibilities include:

* Being an interface for an identified sub-project or SIG in Fedora or JBoss.org.
* Helping students communicate with the overall project and any upstreams.
* Be the final, accountable person for deciding if the student is successful or not, which affects payment. 

=== Are you committed to working with all parties? ===

You need to be committed to working on your part of the Fedora Summer Coding 2010 for it to be successful.  You may want to work with another mentor (''co-mentoring'') to ensure there is always someone available to work with the student and other project members.

=== How to comment on proposals ===

{{:How to comment on Summer Coding 2010 proposals}}

== You are a sub-project ==

Sub-projects are teams working on discrete parts of the Fedora Project or JBoss.org.  For example:

* Fedora Infrastructure
* RHQ
* Fedora Docs Team
* Drools
* Fedora Website Team

=== Timeline for sub-projects ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for sub-projects ===

{{:Summer Coding 2010 step-by-step for sub-projects}}

=== Working with students and the Summer Coding program ===

You can gain a lot of value from students working via the Summer Coding program in your sub-project area; read [[GSoC report 2009]] for examples.

Your sub-project may need to identify a single mentor to work with the student, if the mentor doesn't come from somewhere else in Fedora/JBoss.org.  In addition, you want a back-up mentor or, in some cases, co-mentors, to ensure continuity for the student and the rest of the sub-project.

If you have ideas/problems you want students to work on, they are best served to the students as use cases.  If you do have a strong plan for execution, make that clear in the idea so the student knows it is more of a guided project.

Some experience shows that student projects have a higher success rate for all involved when more of the initial idea is from the student.  Keep that in mind as you create ideas.

Ideas can be divided in to several parts for different students.  There are no explicit limitations on how students may interact on multiple parts of a project.  For example, two students could team build a new component instead of working on two discrete components separately. 

== You are a sponsoring organization ==

Fedora Summer Coding is about connecting sponsors (those with resources to share) with students (those with time, passion, and skills to share.) 

=== Timeline for sponsoring organizations ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for sponsors ===

{{:Summer Coding 2010 step-by-step for sponsors}}

=== Why you should be a sponsor? ===

What do you get out of it?

* Positively impact FOSS projects.
* Get your brand in front of smart students who want to work on FOSS.
* Work on a community program that demonstrates how open source business is done.
* See something you’d like coded be completed.
* Other positive brand associations. 

=== What you need to do ===

We need to start talking, soon.

* Open by default on the discuss list - http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss
* Private via direct email to project leadership - [[User:Quaid|Karsten Wade]], ...

What are the resources you can supply?

# Money to pay stipends to students for spending focused time on these FOSS projects. This is a cross between a summer job and an internship.
# Someone to help coordinate and to contribute as part of the Fedora Summer Coding special interest group (SIG).
# Mentors, especially if they work actively in sub-project or area the sponsor is supporting.

=== What does the Summer Coding program do? ===

The Fedora Summer Coding mentors sort the student ideas, generate the list of approved proposals, work with the students throughout the summer, and make sure you hear back about how things went. 

It’s not necessary as a sponsor to have ideas of how your resources should be used, that’s what the Fedora Project and JBoss.org mentors and sub-projects are prepared to do.

You can learn more about the model we are using in this blog post, [http://blog.melchua.com/2010/03/04/summer-of-code-swimchart-now-with-more-generic/ Summer Of Code Swimchart: Now With More Generic.] 

== You are an upstream ==

=== Timeline for upstreams ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for upstreams ===

{{:Summer Coding 2010 step-by-step for upstreams}}

=== Has a student brought a project idea to you? ===

Please join the [http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss discussion list] and talk with us about it.  We'll ask at least one member of your project to be on that list throughout the 2010 program.  It is not a requirement, and you can best work it out with the student's assigned mentor.

=== Do you have one or more ideas you want exposed to students? ===

As long as the idea is relevant for the Fedora Summer Coding program, you can put it on the [[Summer Coding 2010 ideas]] page.  Follow the process on that page.

As this is a program for the Fedora Project and JBoss.org, there must be some benefit to those projects for your upstream idea.  When you bring the topic to the discussion list, be prepared to talk about that.

There must be a demonstrable benefit to Fedora, even if it is only updated code in a package.  Another example is having a student do the work of getting your software packaged for Fedora.  All of your ideas and ramifications should be topics on the discussion mailing list.

=== Are you committed to working with all parties? ===

A project needs a mentor.  Throwing an idea over the wall on to the wiki page doesn't get it the attention it needs to be part of the Summer Coding program.  If you put an idea out there but do not have a mentor in mind for it, it is left open to the Summer Coding mentors and administators to sort out.

When considering a proposal, the mentors look at the amount of connection with upstream is required, and how strong the communication channels are.  A stronger connection means the proposal looks better.

== You are a Campus Ambassador ==

Campus Ambassadors should work to guide new interests through this process. They should work in both generating interest in Fedora Summer Coding within the Fedora Community and also generating interest in Fedora within student contributors.

Campus Ambassadors should then guide new contributors in helping them get set up with mentors and helping submit their Summer Coding proposal.
[edit] Campus Ambassadors - what

    * Students can have a quality intern-like experience working with Fedora/JBoss.org.
          o Money! Code! Fame! Success! Community! 
    * Sub-projects in JBoss.org and Fedora are ready to work with students.
    * This is right in your pocket, you can run with Summer Coding participation and make your school very successful.
    * You can make more students successful by being an additional mentor for students through the process.
    * Do you know someone at the university/college who wants to talk about partnering with Fedora Summer Coding? 

=== Timeline for Campus Ambassadors ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for Campus Ambassadors ===

{{:Summer Coding 2010 step-by-step for Campus Ambassadors}}

== You want to help organize ==

=== Timeline for organizers ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for organizers ===

{{:Summer Coding 2010 step-by-step for organizers}}

== You are a member of the Fedora Project community ==

=== Timeline for Fedora Project community ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for Fedora community ===

{{:Summer Coding 2010 step-by-step for Fedora community}}

== You are a member of the JBoss.org community ==

=== Timeline for JBoss.org community ===

{{:Summer Coding 2010 schedule}}

=== Step-by-step for JBoss.org community ===

{{:Summer Coding 2010 step-by-step for JBoss.org community}}


[[Category:Summer coding]]
[[Category:Summer Coding SIG]]
[[Category:Summer Coding 2010]]
[[Category:zh]]
[[Category:翻译]]