Aight, I´m just gonna keep coming back anyways, I´ll stop saying good bye...
Hope you have no place to be, sambwise, I do feel like frodo alot now, I don´t know what I´d do without you...
Some more considerations...
Staying inside the perforce free tier limit, I have 5 users and 20 Workspaces.
Considering how this project went before moving to unreal, I don´t think I´ll need more users anytime soon.
A lot of the artists collaborating will never touch unreal and just provide source assets that will be handled outside of perforce.
But the users that WILL use unreal and need to be connected to source control, will regularily change.
They might leave the project without notice (happens all the time), they might have to work on other stuff for a while, but come back etc.
So I´m wondering what the best way to deal with this situation would be.
I could of course just create a new user with specific name and delete an old one, thats no longer needed.
The simplest solution:
1. Modeller BillyK joins the project. I create user "BillyK" for him, he creates his own workspace.
After a while he ghosts me and I delete his user profile and his workspace (using p4 client).
Modeller HarryP joins the Project, I create user "HarryP" for him and he creates his own workspace.
After a while, he needs to take a 2 month break, so I delete his profile, in order to not block one of my 5 free user profiles.
I´m not sure if I also need to delete his workspace.
After two months, he wants to come back to the project. As I still have a free spot, I create user "HarryP" again, and he...creates a new workspace and resyncs all the files he needs?
Or could he reconnect his old worspace?
If he has to create a new workspace, I need to remove his workspace after he leaves AND tell him to also delete his local workspace folders. Otherwise he might end up with a mess on his side
2. I´m also thinking about another solution, where I only create a few users based on their task, BUT have them use different workspaces.
So I´d have usernames like:
ModellingA-> For Modeller A
ModellingB->For Modeller B
Director->For me, serving as superuser
The workspaces would follow a certain naming convention, for example:
The idea would be, that anytime a user leaves the project, I could just assign the next user for the same task to the same user profile.
In this scenario I´d only have to deal with deleting the workspace for the user that left.
I´d do this using the commandline like this:
p4 client -d AwsomeShort_ModA_BillyK_Home
I´m not sure this workflow really makes sense though.
I might end up in a situation, where I have 4 Modellers, but no Programmer.
So now I´d have to delete the "Programming" and "Lighting" userprofiles and create new userprofiles "ModellingC" etc., which kind of ruins the purpose of reusing the same users over and over.
3. In theory I could just have two "Modelling" users, but more "Modelling" workspaces.
So, Modeller BillyK would use:
Modeller TimmyD would use:
Modeller JoeyB would use:
and Modeller HarryT would use:
I´m not trying to work around the restrictions here, I also get that only one user per profile could log in at all times anyways, even if they are using different workspaces.
But imagine this scenario:
Modeller BillyK lets me know he´ll be away from the project for the next two months, as he has other projects to work on.
During that time, Modeller AliB joins the project.
I assign him the same profile as BillyK, he uses that with his own workspace for the next two months, working on different things than BillyK, OR even on the things BillyK worked on.
Once BillyK is back, AliB leaves the project or gets assigned another open user profile, while BillyK can pick up the work where AliB left it at, using his old workspace.
Either way...whenever I´d have a user leave, I´d need to delete his workspace, in order to not go over the 20 workspace limit.
I´d do this using:
Which gives me a list of all workspaces created by all users.
And then delete them using
p4 client -d workspacename