Workspaces Terms?
-
Is there a specific Terms of Service with regards to Workspaces, specifically paid-for Private Workspaces? I've been trying to find such, and have seen mentioned that private projects are very private, but the existing ToS wouldn't seem to accommodate that. Regarding thus, would it also render a private Workspace public if the creator's Pro subscription expired or was canceled? Or would they just be unable to add apps to the project until renewing?
-
Is there a specific Terms of Service with regards to Workspaces, specifically paid-for Private Workspaces? I've been trying to find such, and have seen mentioned that private projects are very private, but the existing ToS wouldn't seem to accommodate that. Regarding thus, would it also render a private Workspace public if the creator's Pro subscription expired or was canceled? Or would they just be unable to add apps to the project until renewing?
At this moment we do not have ::Workspaces-specific terms of service yet, general CodeProject terms do apply. However, we are working on getting document like that. Your private content will never become public without your approval. If your premium subscription expires, the private workspaces will be locked down and you will not be able to access them. If you renew the subscription, the lock will be lifted. After subscription expires nothing is deleted, just rights of access do change.
-
At this moment we do not have ::Workspaces-specific terms of service yet, general CodeProject terms do apply. However, we are working on getting document like that. Your private content will never become public without your approval. If your premium subscription expires, the private workspaces will be locked down and you will not be able to access them. If you renew the subscription, the lock will be lifted. After subscription expires nothing is deleted, just rights of access do change.
Excellent! That brings up another question, though, regarding Privatization - is there any way to mix and match privitization of apps and projects? Say I create a library I'd like to keep private, but release an API, would there be a way to publicly display the API Wiki (and thus the project itself so people can access said Wiki), but keep the Repo itself and an internal Wiki private?
-
Excellent! That brings up another question, though, regarding Privatization - is there any way to mix and match privitization of apps and projects? Say I create a library I'd like to keep private, but release an API, would there be a way to publicly display the API Wiki (and thus the project itself so people can access said Wiki), but keep the Repo itself and an internal Wiki private?
Currently the public/private switch is attached to each workspace. We do not plan to change it anytime soon, though I can imagine scenarios where half of workspace would be desired to be public and half private. So, there is a chance that we will implement such feature in (probably distant) future. In meantime, the suggested way to handle this would be to created 2 workspaces, one public and one private.
-
Currently the public/private switch is attached to each workspace. We do not plan to change it anytime soon, though I can imagine scenarios where half of workspace would be desired to be public and half private. So, there is a chance that we will implement such feature in (probably distant) future. In meantime, the suggested way to handle this would be to created 2 workspaces, one public and one private.
While inelegant, sounds like a workable solution. I'll make sure to post the idea for mixed permissions to the feature requests when I get the chance. Thanks for the answers!
-
While inelegant, sounds like a workable solution. I'll make sure to post the idea for mixed permissions to the feature requests when I get the chance. Thanks for the answers!
Great, thanks.
-
Currently the public/private switch is attached to each workspace. We do not plan to change it anytime soon, though I can imagine scenarios where half of workspace would be desired to be public and half private. So, there is a chance that we will implement such feature in (probably distant) future. In meantime, the suggested way to handle this would be to created 2 workspaces, one public and one private.
I can imagine the scenario as well, but I would want to carefully weigh the ease of management that would afford with the potential for accidentally releasing private info to the public. I think it would be better to err on the side of security here and make it less likely for someone to accidentally publicize something. One more thing to debate! yay!