SummerOfCodeGreywhind - Revision history

Esr: Hide historical instance of "SVN" from mediawiki search to avoid false positives.

2013-03-21T00:59:17Z

Hide historical instance of "SVN" from mediawiki search to avoid false positives.

Greywhind: Last year's mentor info.

2010-04-18T20:36:41Z

Last year's mentor info.

Greywhind: Updates based on discussion with noy.

2010-04-12T02:34:32Z

Updates based on discussion with noy.

Crab: /* SoC Application */

2010-04-09T22:09:12Z

‎SoC Application

Crab: /* SoC Application */

2010-04-09T21:15:50Z

‎SoC Application

Greywhind: Initial expansions of proposal.

2010-04-09T19:35:25Z

Initial expansions of proposal.

Show changes

Ivanovic: add link to SoC application

2010-04-09T08:39:42Z

add link to SoC application

Crab at 19:25, 8 April 2010

2010-04-08T19:25:11Z

Greywhind: Minor edit to section 2.4

2010-03-30T04:18:43Z

Minor edit to section 2.4

Greywhind: Minor grammar fix.

2010-03-30T04:14:25Z

Minor grammar fix.

@@ Line 189: / Line 189: @@
 We do not plan to favor Wesnoth players as such, but some particular projects require a good feeling for the game which is hard to get without having played intensively.
-.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.
+.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.
 I have not yet contributed any patches. I will try to submit at least one patch within the next two weeks, so that you can see some of my code and I can start to learn the project's code.
@@ Line 240: / Line 240: @@
 .1) Are you familiar with any of the following tools or languages?
-     * Subversion (used for all commits)
+     * Sub&shy;&shy;version (used for all commits)
-Yes. I have worked with Subversion for Leges Motus.
+Yes. I have worked with Subv&shy;&shy;ersion for Leges Motus.
      * C++ (language used for all the normal source code)

← Older revision		Revision as of 20:36, 18 April 2010
Line 152:		Line 152:

	I have been both a mentor and a student for the Google Summer of Code before, both times for the Thousand Parsec project.		I have been both a mentor and a student for the Google Summer of Code before, both times for the Thousand Parsec project.
		+
		+	My previous mentor was Tim Ansell (mithro_AT_mithis.com).

	I was a mentor first, because I was not yet 18 and thus could not be paid by Google for work. I provided advice and guidance for and evaluated the successful completion of jmtan's 2008 project to create a 3D client for Thousand Parsec. He was a very self-sufficient student, and I was quite pleased with his work.		I was a mentor first, because I was not yet 18 and thus could not be paid by Google for work. I provided advice and guidance for and evaluated the successful completion of jmtan's 2008 project to create a 3D client for Thousand Parsec. He was a very self-sufficient student, and I was quite pleased with his work.

@@ Line 25: / Line 25: @@
   * share_victory - if we win, does the other player win automatically as well?
   * team - this will be a shortcut to set all the other parameters at once - if both players have "team" selected for the other, they will show with the same team label.
 I would also like to try to make the visual indications of these things obvious and useful. For instance, units that cannot be attacked due to alliance settings will have a tooltip to indicate this. Ally-controlled villages will similarly be marked. Additionally, the scenario creator will be able to specify whether the settings chosen by a given player should be visible to the rest of the players. Secret alliances can be quite fun.
 Finally, I would really like to consider adding a textual treaty feature (for multiplayer only), where two players (or perhaps even a group) could set up a written agreement that would allow even more interesting interactions. These written treaties would have no coded enforcement - it would be up to the participants to follow or break them as they please.
@@ Line 44: / Line 48: @@
 *June 13: This week will involve beginning the GUI setup for the basic ally parameters. I will have a basic user interface (simple checkboxes, probably) in place by this date. The parameters will not have a gameplay effect at this point.
-*June 20: I will add written treaty support, if that feature is thought valuable by other developers. This will extend the original basic preferences in the back end. If this feature is not going to happen, I will instead polish the GUI and give players visual feedback on how to use it.
+*June 20: I will add written treaty support, if that feature is thought valuable by other developers. This will extend the original basic preferences in the back end. If this feature is not going to happen, I will instead polish the GUI and give players visual feedback on how to use it. At this time, it looks like the latter case is more likely.
 *June 27: The written treaty support will be available through the GUI and in WML. If this feature is not going in, I will instead implement secret/public status for the other settings.

@@ Line 10: / Line 10: @@
 =SoC Application=
-[http://socghop.appspot.com/gsoc/student_proposal/review/google/gsoc2010/npartlan/t127077146530 t127077146530]
+[http://socghop.appspot.com/gsoc/student_proposal/review/google/gsoc2010/npartlan/t127077146530 Greywhind's Improved Alliance System, with Configuration Options and Textual Treaties]
 =Proposal=

@@ Line 10: / Line 10: @@
 =SoC Application=
-[http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/npartlan/t127077146530 t127077146530]
+[http://socghop.appspot.com/gsoc/student_proposal/review/google/gsoc2010/npartlan/t127077146530 t127077146530]
 =Proposal=

@@ Line 8: / Line 8: @@
 =IRC=
 Greywhind
 =Questionnaire=

← Older revision		Revision as of 19:25, 8 April 2010
Line 1:		Line 1:
−	{{~~SoC2010Student~~}}	+	{{SoC2010Student_2\|greywhind\|SoC Ideas New Alliance System}}
	[[Category:SoC Ideas New Alliance System]]		[[Category:SoC Ideas New Alliance System]]

@@ Line 64: / Line 64: @@
 .4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
-I am currently involved in the Leges Motus project, although the other two developers have very little time to devote to the project at the moment, so it is usually moving slowly and taking up little of my time.
+I am currently involved in the Leges Motus project, although the other two developers have very little time to devote to the project at the moment, so it is moving slowly and taking up little of my time.
 .5) Gaming experience - Are you a gamer?

@@ Line 48: / Line 48: @@
 I am also one of the founding designers and lead gameplay programmer for the open-source team-based zero-gravity shooter [http://legesmotus.cs.brown.edu Leges Motus]. With two other students, I have enjoyed creating a truly unique zero-gravity top-down view shooter, with highly extensible and customizable maps and weaponry. We are nearly prepared to release our third open beta, with the new support for multiple weapons, among other improvements.
-For classes, I have completed various less significant programming assignments, involving various tasks from using C to re-implement the "lsof" command (searching through raw information about open files and sockets) to attempting to automatically piece together arbitrary jigsaw puzzles using Java to managing the storage and failure-tolerant access to data across a distributed system of computers.
+For classes, I have completed various less significant programming assignments, involving various tasks, from using C to re-implement the "lsof" command (searching through raw information about open files and sockets), to attempting to automatically piece together arbitrary jigsaw puzzles using Java, to managing the storage and failure-tolerant access to data across a distributed system of computers.
 .2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)