FAQ ideas
by Karsten Wade
Throw out some ideas, or make some edits:
https://fedoraproject.org/wiki/Summer_Coding_FAQ
I want to put a bit more there before telling
e.g. summer-coding-discuss. Maybe give us 24 hours to throw out some
ideas?
Make sections of questions and leave them blank or incomplete if you
aren't sure what the answer is. :)
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
13 years, 11 months
Question about Summer Coding
by 杨杰
Hi, everyone!
I am Yang Jie, a MSc student from China. I found Fedora-SIG some days
ago and feel quite interested in this activity. I browsed the ideas
but didn't find a proper idea, so I want to propose for a file sharing
administration tool of Samba & NFS based on Gnome for fedora, but
found it not in the idea list. I wonder could a student create an idea
and propose for it?
Description of the project:
Name: File Sharing Administration Tool for Gnome
KDE has taken an advance on file sharing which is Kcm-filesharing by
allowing the user list all samba/nfs shares and allow the user to
configure the shares centrally and graphically, while which is
required but not supplied by Gnome.
The proposed project aims to create a utility that should provide a
graphical administration tool to configure both samba system shares
and nfs shares. It is able to manage the file sharing management,
authentication, and other most worthy configurations of samba and nfs.
Its main page is
https://fedoraproject.org/w/index.php?title=Summer_Coding_2010_ideas_-_Gn....
Please check it! Any advice is welcome!
Thank you & Best wishes!
--
Yang Jie（杨杰）
hi.baidu.com/thinkdifferent
Group of CLOUD, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
PHONE: 86 1346888 3723
TEL: 86 29 82665263 EXT. 608
MSN: xtyangjie2004(a)yahoo.com.cn
once i didn't know software is not free; then i knew it days later;
now i find it indeed free.
14 years
full and half projects
by Karsten Wade
Swiping an idea from Ruby SOC, what do you all think about having 1/2
projects that are smaller in scope, designed to run in 1/2 the time of
a full project, and have 1/2 of the stipend?
== full project ==
* ~10 weeks
* Full scope
* $5000
== half project ==
* ~5 weeks
* Smaller scope
* $2500
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years
Coding test
by Mel Chua
https://fedoraproject.org/wiki/GSoC_2010_plan#Workflow_plan mentions a
coding test that students have to pass - where do we find out more about
the test, how to administer it, how it's designed, etc? (I can
understand the test itself being non-public so students will take it on
even footing.)
I've been searching but unable to find stuff, so if it's simply that I'm
missing something, just let me know. ;)
--Mel
14 years
Re: Fedora Summer Coding 2010 : Copr
by Toshio Kuratomi
On Wed, Apr 21, 2010 at 04:43:43PM +0530, shan chak wrote:
> Hi
> My name is Shankhoneer Chakrovarty and I am a final year student pursuing
> B.Tech from Indian Institute Of Information Technology.
> One of my professors introduced me to FOSS ideologies and encouraged me to take
> up FOSS development. I completed building up of Tibetan OCR ( Tibet is a
> province of China near India China border ) which was released under GPLv2.
> My skillset includes working in C,C++ and Python. I mostly work in Linux (
> Ubuntu is my favourite ) but I have dual boot system with windows as well.
> I read the Copr information page.It seems to be interesting as well as long.
> Are you planning to complete whole corp during this summer?
> Can you include me with your project please? If there is any work on corp to
> show, please tell me.Where is the codebase?
> I also read the application procedure for FSoC2010 and I am really interested
> in it.Can you please provide me some guidance regarding the same?
>
Let me fill you and any other potential students in on what the status of
Copr is. Copr is a new project to implement an old idea. The idea is to
make it easy for Fedora packagers to make third party repositories. The
repositories can be used for a variety of purposes:
* Updates to new, incompatible versions of software within a Fedora release
* Packages that are not yet in Fedora
* Packages that don't yet follow Fedora's Guidelines but are legal for
distribution using Fedora services
* Rebuilds of Fedora packages with different buid time options enabled
* Other use cases that packagers will come up with once the service is
deployed.
We are working on three pieces of software to enable this:
* mock-vm builds packages inside of a virtual machine. skvidal has this
well under control and we likely are not looking for summer coding help to
do this.
* Headhunter allocates jobs to be performed on other computers. This is
a generic service that could be used by system admins and application
developers for other things besides a buildsystem. It uses func
(https://fedorahosted.org/func) to have Headhunter communicate with the
computers that will run the tasks. Summer coding work on this would include:
+ writing modules to perform tasks we need: building packages in mock,
creating new repositories, updating web pages with the lists of
available repositories, etc.
+ deciding how to deploy func, headhunter, how to share the package
information, etc in order to build.
+ porting func and headhunter to use amqp/qmf for communication.
* The Copr buildsystem is the front end to this. It needs to provide a web
interface to view builder state and a command line client to manage
repositories and build packages for those repos. Other pieces that could
be written are an interface for users to search and browse the
repositories. We'll be implementing this as a TurboGears2 project.
Copr is a very new project and as such, there isn't much code to start out
with. This makes working on Copr for the summer both exciting for you and
risky for us: You get a chance to help design how the system works since
many of the decisions of how to implement this have not been made. It's
risky for us since we'll need to maintain and build on the code you write
after the summer whether or not you stick around to help :-) Because of the
risk, here's some of the things we're looking for in a student:
* Willingness to jump on IRC and start talking with us.
* Willing to start talking in public about things (#fedora-summer-coding and
#fedora-admin are appropriate channels.)
* We communicate with each other well -- since we're working on basics of
how the system will look, we'll need to mesh well as a team... which may
have nohting to do with what your skills are, just how well we end up
working together.
* Able to formulate ideas, discuss them, modify or discard them, and
implement them. Since this is new software, we're going to be bouncing
implementation ideas off of each other constantly that may be good, maybe
bad, or might need to be shelved in the short term to get something that
minimally works for people to use.
* A Fedora packager -- you don't need to be part of Fedora already but if
you are and you think you can keep maintaining pieces of Copr that you've
worked on over the summer (or new pieces of the project) that is a bonus
for us as we know you have a vested interest in seeing that the Copr
repositories are running.
* Experience with the relevant pieces of technology. If you're planning on
working on the web front end, having some experience with TurboGears2 is
good. If you want to work on the amqp communication, some experience
setting up or programming for qpid or another amqp broker is good.
Experience with python is likely to be a hard prerequisite whereas the
other pieces of technology can be picked up while on the job if necessary.
-Toshio
14 years
a 30-day bumped schedule looks like ...
by Karsten Wade
... this:
https://fedoraproject.org/wiki/Summer_Coding_2010_schedule_-_proposed_cha...
(Pasted below, with monthly calendars.)
We had 3 weeks slack in May already, so I moved the project start date
up to 1 June and we gained 4 weeks without touching the end of the
schedule.
Put in an admonition that final student _project_ schedule was part of
the proposal, to be debated then accepted/rejected like any other part
of the proposal. As long as it's all done in time for the end date,
of course.
## Proposed schedule
* April
7 April - Students can begin submitting applications
* May
Whole month - students, mentors, and sub-projects get to
know each other
13 May - Mentors need to finish idea pages
20 May - Students applications + proposals need to be in
21 May - Sponsors must pledge funding by this point
24 May - Organizers finalize how many applications will be
accepted
27 May - Mentors + admins finalize rank-ordered list
28 May - Students informed yes/no about application
* June
01 June - Project begins (depending on proposal)
Proposals may have a modified schedule included.
* Whole month - code, interact
* July
5 July - Midterm evaluations period begins
12 July - Midterm evaluations due
* August
09 August - Project coding completes
16 August - Students final report, code snapshot, and
evaluations due
20 August - Mentor evaluations due for students
23 August - Final evaluations due back to students
25 August - Mentor, sub-project evaluations due
* September
01 September - Sponsors receive report from organizers
06 September - Sponsors release and deliver funds (proposed
date)
April 2010 May 2010 June 2010
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
1 2 3 1 1 2 3 4 5
4 5 6 7 8 9 10 2 3 4 5 6 7 8 6 7 8 9 10 11 12
11 12 13 14 15 16 17 9 10 11 12 13 14 15 13 14 15 16 17 18 19
18 19 20 21 22 23 24 16 17 18 19 20 21 22 20 21 22 23 24 25 26
25 26 27 28 29 30 23 24 25 26 27 28 29 27 28 29 30 ags
30 31
July 2010 August 2010 September 2010
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
1 2 3 1 2 3 4 5 6 7 1 2 3 4
4 5 6 7 8 9 10 8 9 10 11 12 13 14 5 6 7 8 9 10 11
11 12 13 14 15 16 17 15 16 17 18 19 20 21 12 13 14 15 16 17 18
18 19 20 21 22 23 24 22 23 24 25 26 27 28 19 20 21 22 23 24 25
25 26 27 28 29 30 31 29 30 31 26 27 28 29 30
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years
