Regarding the docs, I think I will move it to github wiki. Also break tutorials into several small projects that do just one thing. It was in Google code at the time. We have to move on with new technologies like everyone else, its a new decade now 
3 Likes
@The_Leo @Darkchaos @sgold Can you guys please polish the ideas so we can submit our application. The deadline for GSoC application is Feb 5th 13:00 Central Time.
Also, someone needs to register our organization(jMonkeyEngine) for GSoC at at : https://summerofcode.withgoogle.com/get-started/ before we start the application process. Probably it should to be done by someone from the core team. I do not think if I can do it since I am trying to participate as a student.
We should post a blog post or a github document page with the ideas or anything else which is more accessible then google doc. I vote for github document page. Here is an example of R language GSoC 2019 project idea list: table of proposed coding projects · rstats-gsoc/gsoc2019 Wiki · GitHub
I guess we can still keep updating the idea page after Feb 5th. This is current idea pages for R language for 2020, and its mostly empty : table of proposed coding projects · rstats-gsoc/gsoc2020 Wiki · GitHub Every year they have around 20+ ideas and for each ideas they have 4-5 applicants. They usually want the applicants to complete certain tasks before applying.
2 Likes
Also if you are a student who is already working on jME for a while is also eligible to participate as a student. Here is a section from GSoC FAQ,
Source: Frequently Asked Questions | Google Summer of Code | Google Developers
1 Like
My idea is about as polished as it’s going to get.
I’d feel uncomfortable representing JMonkeyEngine in that capacity. Perhaps @jayfella would be a better option.
I’ve started the application. It’s not short and I have an important meeting today, but I’ll get it finished before the deadline. This is going to be tight…
6 Likes
I’ve finished polishing the idea. Take a look, in case you spot some problems.
PS: also when submitting the idea list for GSoC. Wouldn’t it be better to submit an uneditable document, cus anyone can edit the current one.
2 Likes
Yeah truth be told this is an extremely tight deadline. I’m going to need all the help I can get to push this through on time. Please do as much as you can - every little helps 
3 Likes
I was thinking we can convert the idea list to a github wiki page with only the new ideas for GSoC 2020. That way we do not send them a google doc link - instead a link to the github wiki page. Also that way we can keep the github pages updating. I believe many organization do that.
Do you guys want me to send a pull request at GitHub - jMonkeyEngine/jmonkeyengine: A complete 3D game development suite written purely in Java. or GitHub - jMonkeyEngine/wiki: The official wiki for jMonkeyEngine.?
Or we could share a read only link to the google doc since we are short in time.
Or a separate repo jmonkeyengine/gsoc-2020 where we could also host the modules when we’re done or at least all the documents that we’d gather during the process
@Darkchaos I don’t think I have permission to create a new repo. Can you please create it then I can send pull request.
I don’t have the permission either.
Maybe @sgold can help, because jayfella is too busy with the application itself etc?
Ricardo can too. I’ll make it.
1 Like
Can’t seem to fork it since it’s empty. Here is what I am seeing,
Can you please create a basic readme.md file?
1 Like
Sorry about that. Done.
2 Likes
I’ve made a pull request. I’ve copied all content from the google drive and split it up in 2 pages. 2020 idea page and 2014 idea page.
1 Like
I tried to integrate the PR and discovered I don’t have write access to the repo.
1 Like
@sgold @The_Leo @Darkchaos The GSoC 2020 Idea page is up now at https://github.com/jMonkeyEngine/GSoC_2020 Also please add and remove ideas as necessary. There are some last minute additions, i.e. Mobile Game example idea.
I’ve broken down each idea into subsections. Some section needs more work. I’ve marked them // todo
There is a new section in each idea labeledTests (Students will do one or more of the following tests before contacting the mentors). In some other organizations they want the students to complete some task before/during contacting the mentor.
Please go though it one final time before we submit our application tomorrow (Feb 5th 13:00 Central Time).
@jayfella Are we just submitting just the link or the github page?
1 Like
there is typo(missing word) in Here you and find more about our team.
Regarding Further Reading (links to code, docs and conversations) section: is it necessary atm? Because I think it will be hardly filled up right now and it would probably be better not be there atm than be empty.
Regarding Tests (Students will do one or more of the following tests before contacting the mentors) sections:
I can see the benefit of having a small test to make sure ppl are at least somewhat familiar with jME. On the other hand, designing a separate test for each idea is. in my opinion, redundant. If we’d like to just make sure the applicants got some familiarity with jME, a single general test should suffice.
Then the question is who would make it, what should it contain, and till when? (well i think there is time for this, since its not like we need it for the ideas list atm)
4 Likes
I agree. We can have general tests students take before the contact mentor. But it’s not necessary like you said. We can remove them.
It may be nice to include bug fixing in the list of proposals as well. So anyone interested can take an existing issue from Issues · jMonkeyEngine/jmonkeyengine · GitHub and submit a PR.