User:Perennate - Revision history

Perennate: /* Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then". */

2013-05-22T03:43:07Z

‎Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".

Perennate: /* Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then". */

2013-05-22T03:40:30Z

‎Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".

Perennate: /* Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then". */

2013-05-20T21:31:24Z

‎Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".

Perennate: /* Description */

2013-05-04T20:52:30Z

‎Description

Perennate at 20:51, 4 May 2013

2013-05-04T20:51:51Z

Perennate: /* Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then". */

2013-04-30T21:46:02Z

‎Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".

Perennate: /* Write a small introduction to yourself. */

2013-04-30T21:45:39Z

‎Write a small introduction to yourself.

Perennate: /* Write a small introduction to yourself. */

2013-04-30T21:45:25Z

‎Write a small introduction to yourself.

Perennate: /* Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement. */

2013-04-30T21:42:09Z

‎Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.

Perennate: /* Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer. */

2013-04-30T21:41:26Z

‎Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.

@@ Line 220: / Line 220: @@
 |-
 | August || Fix any remaining bugs and update documentation that has not been added yet; continue working on remaining tasks or feature requests
 |}

@@ Line 194: / Line 194: @@
 * July 10 to July 15: update/implement command-line tools for add-on administration; update the static web page generator script listing add-ons
 * July 15 to end of July, and August: fix bugs, add documentation for add-on developers, finish any other remaining tasks.
 ==== Include as much technical detail about your implementation as you can ====

@@ Line 189: / Line 189: @@
 ==== Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then". ====
-* End of May to middle of June: get a working server running that supports the core features for the addon server with the existing client.
+* End of May to June 10: have add-on server and related client components support existing features, under an boost.asio structure; also use MySQL database for backend storage and handle maintaining versions on the server-side
-* Middle to end of June: add additional features above and any others that come up; update client to support these features.
+* June 10 to June 25: add support for automatic dependency resolution, integration with Wescamp for translation handling, and support for using forum accounts to push add-ons
-* July and August: fix bugs, add documentation for add-on developers, finish any other remaining tasks.
+* June 25 to July 10: add client-accessible functions such as searching add-ons written by a specific author, possibly add various add-on statistics add sort by, etc.
 ==== Include as much technical detail about your implementation as you can ====

@@ Line 13: / Line 13: @@
 * Forum accounts: give add-on authors the ability to publish using forum account(s) instead of the passphrase
 * Documentation: improve documentation of server configuration and guide on how to setup an addon server
 === Database ===

@@ Line 8: / Line 8: @@
 The revamped addon server/client will feature the following (mostly in addition to the existing capabilities):
-* Written in Python to more easily interact with the various tools, such interacting with WesCamp
+* Include integration with the various tools, such interacting with WesCamp
-* Better versioning handling: new versions will be recorded as separate entries in the database to track updates and file differences or git repository may be used
+* Better versioning handling: new versions will be recorded as separate entries in the database to track updates and file differences or git repository may be used; automatic update detection will be supported on the client side
 * Database: a MySQL database will be used to store information about add-ons
 * Forum accounts: give add-on authors the ability to publish using forum account(s) instead of the passphrase
 * Documentation: improve documentation of server configuration and guide on how to setup an addon server
@@ Line 26: / Line 25: @@
 CREATE TABLE translations (id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, addon_id INT, language_id INT, path VARCHAR(64))</pre>
-Functions such as searching all addons by a specific author will be supported through the web interface.
+Functions such as searching all addons by a specific author will be supported.
 === Versioning ===
@@ Line 36: / Line 35: @@
 The server will then respond with each file that the client either doesn't have or whose checksum+size combination don't match. Old files will also be deleted.
-When an add-on is being updated, the locked flag will be first set in the database and will wait for ongoing downloads to finish. locked flag is in the database because it can also be used for other reasons.
+When an add-on is being updated, the locked flag will be first set in the database and will wait for ongoing downloads to finish. locked flag is in the database because it can also be used for other reasons besides updates.
 === Dependencies ===

@@ Line 60: / Line 60: @@
 ==== Write a small introduction to yourself. ====
-Hi! I'm currently a first year student at the Massachusetts Institute of Technology; I've been interested in networking and games for a while, and worked on a game server for an RTS game before. I'm most experienced with Java and PHP, but also have worked with C++, Python, and a few other languages.
+Hi! I'm currently a first year student at the Massachusetts Institute of Technology; I've been interested in networking and games for a while, and worked on a game server for an RTS game before. I'm most experienced with Java and PHP, but also have worked with C++, Python, and a few other languages extensively.
 ==== State your preferred email address. ====

@@ Line 106: / Line 106: @@
 Yes, see above.
-GHost++: this is a game server for Warcraft III (reverse engineered), I added a few features and fixed a few security issues.
+* GHost++: this is a game server for Warcraft III (reverse engineered), I added a few features and fixed a few security issues.
-uxpanel: a game server control panel, something I developed.
+* uxpanel: a game server control panel, something I developed.
 ==== Gaming experience - Are you a gamer? ====

← Older revision		Revision as of 21:41, 30 April 2013
Line 133:		Line 133:

	I think only once before recently (this before time was a while ago), and I don't remember much. At the moment definitely single player.		I think only once before recently (this before time was a while ago), and I don't remember much. At the moment definitely single player.
−
−	~~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.~~

	==== 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 repository (during the evaluation period or earlier) please state so. ====		==== 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 repository (during the evaluation period or earlier) please state so. ====