Group owning of Scenes (and elements and dreams)
After creating DreamsFest with the team we did run into one slight issue and that is the person who owned a scene had to release it. With the team being spread out over various time zones with all their own life schedules it became a bit of a slow down if the owner could not update the scene when the other members needed it. I owned the 10 of the scenes. If someone in America needed it releasing they’d need to catch me before 12pm UK time otherwise they’d likely have to wait over 12 hours. Every time a bug is found or an anomaly is discovered the scene needs to be updated meaning the owner has to re-release it after it’s fixed.
My suggestion is to have an option for trusted collaborators to co-own a scene (dream or element). This would speed up group projects immensely whilst ensuring that if, for example, someone was to leave Dreams that you had a collaborative project with, you could still release the project without having to redo the work put in.
-
Totally agree. Co-ownership could solve a few issues.
-
I agree that would be nice to have. There could be an administrator system that would allow a few select team members to be able to publish. In real world working environments it's never all people in the team that can push requests to the master branch of a source controlled project. In such a system we could designate a few people that can publish and have access at all time to the whole project. There would still be one person that owns it but if we could promote some collaborators to admin levels they could publish as if the project was their own. My guess is that Mm is aware that some people could steal your project and publish without your consent. Communication is key and trust is earned.
It highly probable that the way Dreams ownership works links your content to your PSN account so it might be difficult for Mm to change it.
Accedi per aggiungere un commento.