You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.
pyvideo is currently maintained by people who have admin status and that's it. That's problematic when growing the site and growing a community of people to maintain the site.
I want to build a system that scales to like 50 active contributors tops. If we get beyond that, we should switch to a new system.
I'm thinking we should create a django group and then make sure we have a way to manage the people in that group. Then we'll give that group permission to edit video data and change the edit links on the site so that this group can edit video data.
This issue covers:
creating that group
creating the permission for editing video data (which covers the Video and RelatedUrl models (and maybe others--I forget))
making sure we have some good way for adding/removing people from that group and seeing status of people in the group
maybe some things I'm not thinking about
The text was updated successfully, but these errors were encountered:
This would also be very useful for associating slides with videos. I manually associate slides with videos when bookmarking talks. Storing this data with the video would be useful.
pyvideo is currently maintained by people who have admin status and that's it. That's problematic when growing the site and growing a community of people to maintain the site.
I want to build a system that scales to like 50 active contributors tops. If we get beyond that, we should switch to a new system.
I'm thinking we should create a django group and then make sure we have a way to manage the people in that group. Then we'll give that group permission to edit video data and change the edit links on the site so that this group can edit video data.
This issue covers:
The text was updated successfully, but these errors were encountered: