Ticket #1642 (closed story: fixed)

Opened 11 years ago

Last modified 11 years ago

Two editing modes- collaborative editing and branching

Reported by: hans Owned by: hans
Priority: blocker Milestone: 2.5
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by hans) (diff)

In Estonia I have at least one upcoming project where school textbook will be published in LeMill. In this project authors are sceptical about other people editing their book. I agree with them that something like a school textbook is good in stable state where anybody is not able to modify that. The authors feel totally fine about Creative Commons Attribution-ShareAlike? license.

One solution to this kind of situations is to have two editing modes:

  • collaborative editing (exactly as we have it now)
  • branching (copy and edit feature that we had for some time in the beginning)

The first author should be able to choose the editing mode for her learning resources. These radio buttons should be in the About-page for learning resources (web pages, presentations, exercises, PILOT's).

See the UI prototype screenshot: http://lemill.org/trac/attachment/ticket/1642/editing_settings.png

Text used in the UI:

Editing settings
You can choose how other people can edit this learning resource and if the draft version is hidden from others.

    Anybody can edit this learning resource
    Other users can only edit a copy of this learning resource

    Draft version is hidden from other users

The same settings are used in #1726

If resource has been already edited by several people (for example http://lemill.net/content/overview-of-lemill/view) then the first author (Tarmo) has a possibility to change the editing mode. It means that Hans, Jukka and Teemu can't edit that resource anymore and have to make a copy.

Attachments

editing_settings.png (55.7 KB) - added by hans 11 years ago.

Change History

comment:1 Changed 11 years ago by hans

  • Type changed from defect to story

comment:2 Changed 11 years ago by hans

  • Owner changed from anonymous to hans
  • Priority changed from major to blocker
  • Status changed from new to assigned
  • Milestone set to 2.5

I will make a decision about the open questions and create an enhancement ticket for the developers.

comment:3 Changed 11 years ago by hans

The following version of the story is going to be edited:

In Estonia I have at least one upcoming project where school textbook will be published in LeMill. In this project authors are sceptical about other people editing their book. I agree with them that something like a school textbook is good in stable state where anybody is not able to modify that. The authors feel totally fine about Creative Commons Attribution-ShareAlike? license.

One possible solution to this kind of situations is to have two editing modes:

  • collaborative editing (exactly as we have it now)
  • branching (copy and edit feature that we had for some time in the beginning)

I think that the first author should be able to choose the editing mode for her learning resources. These radio buttons could be in the additional information page.

There are also some our learning resources that would benefit from that:

I have a lot of open questions with this story:

  • How should we call these things? We need name for the title of this selection ("Editing mode" or "Collaboration mode"?) and both options ("Collaborative editing", "Collaborative authoring", "Collaboration"; "Branching", "Adapting", ...?)
  • What will happen if editing mode is changed for a resource that has already several authors?
  • Is there a flexible way to allow editing for a small group of authors but not for all users?

Changed 11 years ago by hans

comment:4 Changed 11 years ago by hans

  • Description modified (diff)

comment:5 Changed 11 years ago by hans

  • Description modified (diff)

comment:6 Changed 11 years ago by hans

  • Description modified (diff)

This story is agreed by Hans and Tarmo

comment:7 Changed 11 years ago by hans

  • Description modified (diff)

comment:8 Changed 11 years ago by hans

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.