I’ve seen it on so many idea list that I feel its a necessity. It might point the students towards other resources that dive deep into the idea that is not possible to include in the short description.
Yes, that is always expected in GSoC project. But I think this gives serious students a direction to start.
A pending pull request from DarkChaos shows an example.
A list of bug fixes does not require in depth knowledge of the engine…maybe we can list them as a prerequisite tasks when they apply.
Can you please send a pull request?
@jayfella Is there anything we can do to help you in the application process?
If so, you can take an example at my projects, I’ve designed the tests so that students are forced to understand/work towards using JME. Once they’ve solved the tests, they are basically all set up to start developing.
Thank you for applying to be a Google Summer of Code 2020 mentor organization. Sadly, we were unable to accept jMonkeyEngine this year. We had many more applications than available slots. We hope you will apply again in the future!
I didn’t post here yet, because I planned to write something along the lines of “at least speaking of me as Mentor, we can still do any of these project ideas, as some of them are very relevant for the near future of jme, so if someone is up for a bigger project, just hit me up”.
It is unfortunate that they are not providing any details. The idea page was lacking?
Or something else…
From GSoC documentation the most important criteria for selection is the idea page. But our idea page is far better then many that were selected for GSoC 2020.
For example, CircuitVerse got selected when they have only 4 big ideas(where 1 of them is bring your own idea) with little no details and only 2 mentors. Here is their idea page:
CircuitVerse GSoC 2020 idea page