Deck branching when forking a deck

Background

At the moment, when a user clicks on the Fork button, a new deck revision is created. The new deck revision is owned by the user who forked the original deck. However, the creator of the deck remains the same.

In the December release, we have the following options:

• use this functionality (i.e., forking creates a new revision), this entails the following changes in the platform:
  • extend the myDecks view and add revisions owned by a user to his/her myDecks view (now it only shows the decks the creator of which is the user), 
  • show creator as well as revision owner in the Deck view (now it only shows the original creator of the deck)
     
• perform branching explicitly, by creating a new deck (with new ID). This entails one of the following:
  • copying/replicating (with new IDs) all of its slides and sub-decks in the newly branched deck. The newly created items will start at revision 1, and will be owned by the user who did the branching
  • adding the contents (slides and sub-decks) as they are. The newly created branched deck will contain the same slides/sub-decks at the revisions they were in the branched deck. This means that even though the user branched a deck, he/she would have to share the same contents with the rest of the decks that use them, as they will have the same ID and therefore the same revision history.

Action items