Request for Feedback: Collective Changes
As I've mentioned before, VideoSift 3.0 is coming. One of the major focuses for changes in the new version of VideoSift will be Collectives. We are thrilled with the way Collectives are going so far, and want to empower Sifters to create real sub-communities. There are a few areas that we haven't made decisions on, and at the risk of lifting the veil on our new release too much - we need your help.
We want to make Collectives viable sub-communities that are run by the Collective admin. To that end, The collective will resemble a complete VideoSift with its own Sift Talk area and Queue. We're considering giving collective admins the ability to control the collective queue release level. That means as a collective admin, I might choose to have videos publish to 80s.videosift.com at 4 votes, while they are still in the primary queue, yet to publish. This is tied in to how we will manage queue expiry - which I won't go into now, but it will work, trust me.
We would also like for Collectives to have their own Sift Talk, where posts can be made locally to the collective, or (with a tick box) published to the main Sift Talk as well.
With all of these changes, Collectives and Channels are looking very similar. Our plan then, is to turn Channels into collectives, appointing admins where required - or folding them into existing collectives (arts).
Collective admins will have a customizable area at the top of the sidebar of their collective which can be used for putting notices up, or even ads :0.
We're debating what to do about invites. With the merging of channels and collectives There may be a few "public" collectives which everyone is a member of. We could allow Collective admins to designate their collective as public, so no invites are required. We need input on this.
The new collectives would be completely CSS customizable. The downside is that current collective CSS would need to be rejiggered.
This is a pretty big change, I know. And I also know that sometimes communities can be change averse - but mull it over and give it your consideration. Some of the earlier changes were not well received, but have become integral to the site. The *dead invocation springs to mind.
We want to make Collectives viable sub-communities that are run by the Collective admin. To that end, The collective will resemble a complete VideoSift with its own Sift Talk area and Queue. We're considering giving collective admins the ability to control the collective queue release level. That means as a collective admin, I might choose to have videos publish to 80s.videosift.com at 4 votes, while they are still in the primary queue, yet to publish. This is tied in to how we will manage queue expiry - which I won't go into now, but it will work, trust me.
We would also like for Collectives to have their own Sift Talk, where posts can be made locally to the collective, or (with a tick box) published to the main Sift Talk as well.
With all of these changes, Collectives and Channels are looking very similar. Our plan then, is to turn Channels into collectives, appointing admins where required - or folding them into existing collectives (arts).
Collective admins will have a customizable area at the top of the sidebar of their collective which can be used for putting notices up, or even ads :0.
We're debating what to do about invites. With the merging of channels and collectives There may be a few "public" collectives which everyone is a member of. We could allow Collective admins to designate their collective as public, so no invites are required. We need input on this.
The new collectives would be completely CSS customizable. The downside is that current collective CSS would need to be rejiggered.
This is a pretty big change, I know. And I also know that sometimes communities can be change averse - but mull it over and give it your consideration. Some of the earlier changes were not well received, but have become integral to the site. The *dead invocation springs to mind.
Load Comments...
Discuss...
Enable JavaScript to submit a comment.