Open EloiStree opened 4 years ago
https://youtu.be/KD47s4uWAIw (Not the last version)
https://youtu.be/K0l-NOrVU0c
Downlaod the game:
https://eloistree.itch.io/magicdooratelierdegroupetechnocite
If you are workaholic and you work after work or the weekend. You can work on the code of your team as you don't have permission to do so. Your only option is to fork the code of your friend. Remove his package and add yours.... Or to wait patiently. That can quickly lead to problems.
Some participants did not understand that they could create dependency to paying asset on the store. Leading them to put some asset in the package that was public for the project. (We deleted the package immediately).
To reduce the time lost when you do the package or when you use the package, you need plenty fo tools. And that request a learning curved and some tools that don't bug. Else you start losing a lot lot lot of time.
More you use the package, more you start truning your project in a link of package that are linked to the small part that is creating your project.
But the weak point of that is that you start to transform everything you do as a package. Lot's of bad stuffs happens with that (Explain later). Main weakness of that is that when you want to update a small part of the game. It takes 2-4x more time that your team need you to do it.
Pierre Gueran gave a good tips & trick about that: "Don't do a package directly in the project. Start by doing the code for your team. Next project you required the package. Start to schedule to package it."
How and why you should use the power of Fork in the project.
During the weekend, the participant are not available. So if you want to change the code, you have only one option.
During the end of the project. I know it would not happens, but I was sitting on a new dilemma. "What would happen, if a student in the future set it project in private, move it, or remote it from the server ?" As soon as you update your project, you have error that would appear, the time you understand what is happening, you will probably lose the copy of the local code of the user and your project is screw...
So what do you do in this case ?
I suppose there are other solution. But for the moment it is all I have in head.
Group workspace: Google Sheet To be able to synchronized the group, we used a google sheet where people can comment the link of their assets. The project leader check some time to update the google sheet and refresh the page with comments.
Before we start, the workshop scheduling was not to teach only the package manager but the virtual reality to participant that don't own virtual reality.
You can find in the following part, the scheduling given to participant durant the workshop. In future version, more space should be given to design and coder. And the workshop should be shuffle and not split as we did if we want to have a game and not a portfolio application. ;). That my bad. The workshop what not plan as a workshop group work at it before COVID construction.
Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6
For three weeks, we did a workshop with the Belgian students of Technocité call Magic Doors.
The workshop was a success, I am planning to re-iterate the experiment. This post is a postmortem to make a review of how it happens. And how to improve the next workshop.