GSoC 2008 Application - Revision history

ArneBab at 07:46, 11 March 2008

2008-03-11T07:46:53Z

←Older revision		Revision as of 07:46, 11 March 2008


	Phex also has a history of being utilized in academic studies to test p2p networks, and the current API changes aim to build on that history by making it even easier to utilize the Phex code in new ways.		Phex also has a history of being utilized in academic studies to test p2p networks, and the current API changes aim to build on that history by making it even easier to utilize the Phex code in new ways.
		+
		+	We believe that the Gnutella protocol is the best (most efficient for users) way to do keyword based searches, so we concentrate on optimizing it for that purpose.


	4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?		4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?

-	We are a very small team and are looking for more developers that enjoy working on an open source project and bring new ideas into the project.	+	We are a very small team and are looking for more developers that enjoy working on an open source project and bring new ideas into the project.
		+
		+	We want to push the limits of p2p filesharing even faster, and our wiki contains numerous ideas which can further revolutionize the way in which internet users experience data and culture, and we want to realize these ideas along with new ones which go beyond our current imagination.

ArneBab at 07:36, 11 March 2008

2008-03-11T07:36:28Z

←Older revision		Revision as of 07:36, 11 March 2008

	3. Describe your organization.		3. Describe your organization.

-	Phex is an open source project developing a popular and free Gnutella client since 2001.	+	Phex is an open source project developing a popular and free Gnutella client since 2001. Phex was one of the first Gnutella clients, and it still takes an active role in pushing the limits of Gnutella, while keeping its CPU load low, so even people with old computers can use it.
		+
		+	Phex also has a history of being utilized in academic studies to test p2p networks, and the current API changes aim to build on that history by making it even easier to utilize the Phex code in new ways.

ArneBab at 07:27, 11 March 2008

2008-03-11T07:27:27Z

←Older revision		Revision as of 07:27, 11 March 2008


	* gregor?		* gregor?
		+

	==About The Program==		==About The Program==

	1. What is your plan for dealing with disappearing students?		1. What is your plan for dealing with disappearing students?

-	~~They should work inside our main svn tree~~, so even if a student disappears, the code ~~still stays with Phex~~.	+	We will make sure, that even an unfinished contribution will help the project by working with a clear roadmap with major milestones.
		+
		+	If a student disappears, we can not reach him/her, but we can take steps to minimize the chance that the student disappears in the first place.
		+
		+	For this, the student must report to the community on a weekly base, so he/she directly experiences the feedback.
		+
		+	Also the student must write well commented code, so even unfinished code can be completed by other members. Automatic testing will be done using the tools from Ohloh, backed by manual overview by the existing members of our project.

	Features should be merged into trunk as soon as reasonably possible.		Features should be merged into trunk as soon as reasonably possible.
		+
		+	And additionally to reports to the community, our mentors will be in contact with them before the student starts coding, during the project and hopefully also thereafter.
		+

	2. What is your plan for dealing with disappearing mentors?		2. What is your plan for dealing with disappearing mentors?

-	We have a backup mentor for each mentor. Also we chose ~~longactive~~ contributors to minimize the chance of a disappearing mentor.	+	We have a backup mentor for each mentor. Also we chose contributors who have been active for a long time to minimize the chance of a disappearing mentor.
		+
		+	Also mentors must regularly report to the community, too, so that their work can be carried on easily.
		+

	3. What steps will you take to encourage students to interact with your project's community before, during and after the program?		3. What steps will you take to encourage students to interact with your project's community before, during and after the program?

-	We want them to report ~~on their activity inside~~ the community ~~forums~~, so they ~~interact with other contributors and see~~ the ~~effects of their changes~~.	+	As for reducing the chance for disappearance, we want them to report to the community on a weekly basis, so they directly experience the feedback and fun free software development brings with it.
		+

	4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?		4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
		+
		+	We will include them as full members in our planning, so that they can take an active role in the future of our project, so that they can feel a sense of ownership about the parts they contribute themselves.
		+

	Thanks!		Thanks!

ArneBab at 07:18, 11 March 2008

2008-03-11T07:18:56Z

←Older revision		Revision as of 07:18, 11 March 2008

	11. Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)		11. Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)

-	~~'''We be good if we could create one in the Wiki~~.~~'''~~	+	http://www.phex.org/wiki/index.php/GSoC-2008_Student-Template

ArneBab: typo

2008-03-09T22:11:44Z

typo

←Older revision		Revision as of 22:11, 9 March 2008

	1. What is your plan for dealing with disappearing students?		1. What is your plan for dealing with disappearing students?

-	They should work inside ~~out~~ main svn tree, so even if a student disappears, the code still stays with Phex.	+	They should work inside our main svn tree, so even if a student disappears, the code still stays with Phex.

	Features should be merged into trunk as soon as reasonably possible.		Features should be merged into trunk as soon as reasonably possible.

ArneBab: /* About The Program */

2008-03-07T12:39:02Z

About The Program

←Older revision		Revision as of 12:39, 7 March 2008

	2. What is your plan for dealing with disappearing mentors?		2. What is your plan for dealing with disappearing mentors?

-	~~Have~~ a backup mentor.	+	We have a backup mentor for each mentor. Also we chose longactive contributors to minimize the chance of a disappearing mentor.

	3. What steps will you take to encourage students to interact with your project's community before, during and after the program?		3. What steps will you take to encourage students to interact with your project's community before, during and after the program?

ArneBab at 12:35, 7 March 2008

2008-03-07T12:35:57Z

←Older revision		Revision as of 12:35, 7 March 2008



-	arne_bab Ã¤t web.de	+	* arne_bab Ã¤t web.de
		+
		+

	==About Your Mentors==		==About Your Mentors==

	1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.		1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
		+
		+	We chose longstanding and active members, who know where the project is heading.
		+

	2. Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)		2. Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)
		+
		+	* gregor?

	==About The Program==		==About The Program==

ArneBab: /* About Your Organization */

2008-03-07T12:32:27Z

About Your Organization

←Older revision		Revision as of 12:32, 7 March 2008

	3. Describe your organization.		3. Describe your organization.

-	Phex is a open source project developing a popular and free Gnutella client since 2001.	+	Phex is an open source project developing a popular and free Gnutella client since 2001.


	4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?		4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?

-	We are a very small team and are looking for more developers that enjoy working on a open source project and bring new ideas into the project.	+	We are a very small team and are looking for more developers that enjoy working on an open source project and bring new ideas into the project.




	12. Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)		12. Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)
		+
		+
		+	arne_bab Ã¤t web.de

	==About Your Mentors==		==About Your Mentors==

ArneBab at 12:30, 7 March 2008

2008-03-07T12:30:53Z

←Older revision		Revision as of 12:30, 7 March 2008

	7. What license does your project use?		7. What license does your project use?

-	GPL	+	GPL-2 or later.


	8. URL for your ideas page		8. URL for your ideas page

-	~~'''We need to work out a Wiki page here'''~~	+	http://www.phex.org/wiki/index.php/GSoC-2008-Ideas




	1. What is your plan for dealing with disappearing students?		1. What is your plan for dealing with disappearing students?
		+
		+	They should work inside out main svn tree, so even if a student disappears, the code still stays with Phex.
		+
		+	Features should be merged into trunk as soon as reasonably possible.

	2. What is your plan for dealing with disappearing mentors?		2. What is your plan for dealing with disappearing mentors?
		+
		+	Have a backup mentor.

	3. What steps will you take to encourage students to interact with your project's community before, during and after the program?		3. What steps will you take to encourage students to interact with your project's community before, during and after the program?
		+
		+	We want them to report on their activity inside the community forums, so they interact with other contributors and see the effects of their changes.

	4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?		4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?

	Thanks!		Thanks!

GregorK at 09:54, 7 March 2008

2008-03-07T09:54:42Z

New page

== About Your Organization ==

1. What is your Organization's Name?

Phex

2. What is your Organization's Homepage?

http://phex.org

3. Describe your organization.

Phex is a open source project developing a popular and free Gnutella client since 2001.

4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?

We are a very small team and are looking for more developers that enjoy working on a open source project and bring new ideas into the project.

5. Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)

No

6. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)

No

7. What license does your project use?

GPL

8. URL for your ideas page

'''We need to work out a Wiki page here'''

9. What is the main development mailing list for your organization?

phex-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phex-developers
or Forum:
http://www.gnutellaforums.com/development-coding/

10. Where is the main IRC channel for your organization?

#phex on freenode.net

11. Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)

'''We be good if we could create one in the Wiki.'''

12. Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)

==About Your Mentors==

1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.

2. Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)

==About The Program==

1. What is your plan for dealing with disappearing students?

2. What is your plan for dealing with disappearing mentors?

3. What steps will you take to encourage students to interact with your project's community before, during and after the program?

4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?

Thanks!