Gee Wiz hello I’m interested in partaking in this event jME seems like a very prominent engine and I would love to participate and become a student. Possibly I can work on a GameState system, a small game or motion blur.
i agree with zathras [link] though maybe the work can stand as a basis for later deployment after all isn’t GDE a series of plug-ins?
btw i understand you can assign more than on student to a single project. would it make sense for the game project proposal that, given enough participants, you kind of cluster them to a single game project to work together and create a small app based off of some pre-written ideas you or another senior programmer in the community has? such as a simple FPS which i personally think is the quickest way to show off the engines many talents and features without killing your students with an MMO btw murder by code is a crime in the US 
(hope you don't mind, I went in and actually added some punctuation to your last paragraph because I was having a hard time making sense of it without any)
Bonechilla said:That's an interesting point you raise there. Yes, it would be possible to have several people work together on the same project; after all that's what jME is already :) The difficult part is making the GSoC student's (or students') contribution clearly distinct from the rest, so Google may easily identify what work the student accomplished and whether or not it makes them eligible for the $5000 stipend. I don't know how big a say the mentors will have in this (the biggest one I'd assume) but it would be foolish to think that Google won't be involved in the final call at all.
btw i understand you can assign more than on student to a single project. would it make sense for the game project proposal that, given enough participants, you kind of cluster them to a single game project to work together and create a small app based off of some pre-written ideas you or another senior programmer in the community has? such as a simple FPS which i personally think is the quickest way to show off the engines many talents and features without killing your students with an MMO btw murder by code is a crime in the US ;)
It's definitely a suggestion worth considering. I'll edit the game-proposal section in the ideas page to appropriately convey the idea.
ahh yes erlend, racing for the train is no excuse for poor grammar :D
Maybe each GSoC student can be assigned to a specific task; ie one work on a character implementation, the other work on terrain implementation. The student who begins a given implementation or who arguably does the most work in a specific implementation gets the credit.
While we are on the subject, would it also make sense to add a tab to the top of the site to list all finished or noteworthy projects involving the engine?
Bonechilla said:That wouldn't work. The student(s) to receive (monetary-) credit is already determined in the student application process, at which point a mentor is assigned to that student. A student's approval is based on the validity and usefulness of whichever project that student applied for. It's not supposed to be a contest, just an educational and productive collaboration between likeminded developers.
Maybe each GSoC student can be assigned to a specific task; ie one work on a character implementation, the other work on terrain implementation. The student who begins a given implementation or who arguably does the most work in a specific implementation gets the credit.
Bonechilla wrote:
While we are on the subject, would it also make sense to add a tab to the top of the site to list all finished or noteworthy projects involving the engine?
Bonechilla said:
ahh yes erlend, racing for the train is no excuse for poor grammar :D
LOL, I've been having a hard time adjusting to the new schedules as well ^^
normen said:
Zathras, most of the things you describe could be built into the GDE. Especially deploying should imho not be included in any scripts provided with the core engine. Savvy programmers know how to deploy their apps and probably want to do it on their own. For GDE users, the integrated NetBeans deploying possibilities can be used/extended.
Cheers,
Normen
I tend to agree with this sentiment. What we do need though, is a bit of a jME oriented ANT - > Webstart tutorial because it can certainly be a tricky thing to do if you've never done it before no matter how savvy a programmer you are. I'll start laying out and authoring something like this would consist of but it basically comes down to build.xml (building the jar's, making the manifest, specifying libs, signing the jar's) and jnlp. With a smartly written ant script and a shell script to move the jar's, folks could have a continuous integration builder doing nightlies of their own project with very little effort and minimal maintenance :) I just went totally off topic, sorry!