Multi-user writing

elegaanz commented

2020-05-23 16:05:59 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.

Currently, an account can own many blogs, but each blog can only have one author. Articles are limited to one author too.

However, in some cases, it is useful to have many authors on the same blog (for a project made by different people for example).

The code currently allows that, but the UI doesn't. So we "just" have to adapt the UI.

Describe the solution you'd like

Here is a more detailed list of things to do:

Add people to a blog:
- Owners of a blog should have a way to "invite" someone to the blog (by entering their @ for instance)
- A notification and/or an email should then be sent to this person, with "Accept"/"Decline" options
- If they accept, they are added to the list of authors of the blog, and they can write articles in this blog.
Manage authors
- Owners of a blog should have access to a list of authors in the blog (other people may see it too, but without the possibility to interact). This list should contain:
  - The name/@/avatar of the author
  - It's role in the blog: owner (can change the settings of the blog) or regular author (can only write articles)
  - Buttons to change the role and remove someone from this list
- As an author in a blog, you should have an option to leave by yourself as well
Articles should show all of the authors at the bottom of the page (or maybe just the name of the blog instead, so that an article written by a lot of people doesn't eat all the screen just to show the list of authors)
When publishing an article, there should be a warning if you submit a new version while someone already submitted one in the meantime, to avoid overwriting other people's work.

And all of that should be federated, so we need to discuss which AP verbs to use in which cases too.

Describe alternatives you've considered

Not allowing that at all, and letting people collaborate outside of Plume (with some kind of shared pad/document). But that would be a "waste" of the potential of AP I think, since it could enable some new kind of collaboration.

~~Additional context~~

This is a quite big issue and I should maybe split it in smaller ones?

**Is your feature request related to a problem? Please describe.** Currently, an account can own many blogs, but each blog can only have one author. Articles are limited to one author too. However, in some cases, it is useful to have many authors on the same blog (for a project made by different people for example). The code currently allows that, but the UI doesn't. So we "just" have to adapt the UI. **Describe the solution you'd like** Here is a more detailed list of things to do: - [ ] Add people to a blog: - [ ] Owners of a blog should have a way to "invite" someone to the blog (by entering their @ for instance) - [ ] A notification and/or an email should then be sent to this person, with "Accept"/"Decline" options - [ ] If they accept, they are added to the list of authors of the blog, and they can write articles in this blog. - [ ] Manage authors - [ ] Owners of a blog should have access to a list of authors in the blog (other people may see it too, but without the possibility to interact). This list should contain: - The name/@/avatar of the author - It's role in the blog: owner (can change the settings of the blog) or regular author (can only write articles) - Buttons to change the role and remove someone from this list - [ ] As an author in a blog, you should have an option to leave by yourself as well - [ ] Articles should show all of the authors at the bottom of the page (or maybe just the name of the blog instead, so that an article written by a lot of people doesn't eat all the screen just to show the list of authors) - [ ] When publishing an article, there should be a warning if you submit a new version while someone already submitted one in the meantime, to avoid overwriting other people's work. And all of that should be federated, so we need to discuss which AP verbs to use in which cases too. **Describe alternatives you've considered** Not allowing that at all, and letting people collaborate outside of Plume (with some kind of shared pad/document). But that would be a "waste" of the potential of AP I think, since it could enable some new kind of collaboration. **~~Additional context~~** --- *This is a quite big issue and I should maybe split it in smaller ones?*

👍 4

KitaitiMakoto referenced this issue

2021-01-06 11:02:21 +00:00

Follow blogs instead of users? #869

KitaitiMakoto modified the milestone from 1.0 to 0.7.0

2021-01-16 07:22:15 +00:00

pwFoo commented

2021-02-14 19:19:41 +00:00

Please add the feature to follow a blog instead just users. User(name) I think more as login name and optional author name, but blog should the important thing to read and follow.
Author of the blog could be public or private / hidden. No need to know authors name or which blogs belong to the same author / group of users.

Please add the feature to follow a blog instead just users. User(name) I think more as login name and optional author name, but blog should the important thing to read and follow. Author of the blog could be public or private / hidden. No need to know authors name or which blogs belong to the same author / group of users.

pwFoo referenced this issue

2021-02-14 19:20:11 +00:00

Follow blogs instead of users? #869

pwFoo referenced this issue

2021-02-14 19:26:16 +00:00

Per blog tag lists/feeds #736

KitaitiMakoto modified the milestone from 0.7.0 to 0.8.0

2021-04-11 03:07:26 +00:00

KitaitiMakoto commented

2021-04-11 03:07:31 +00:00

Owner

Pushing this to v0.8.0.

bushgrad commented

2022-02-13 23:54:03 +00:00

Where multi-authors exist at a blog, any of the multiple authors should have access to the posting (publish) tool on that blog. Ony the 'owner' has access to the configuring tool of the blog.

Posting: If multi, a check list appears comprising the registered authors on the blog. The posting (editing and markup of the article) can appear after registering the Single or Multi authors. Posting of article should be performed by the one author that registered the multiple authors. After editing, it can then go to draft (waiting for publish; with possibly a time-limit set). Other authors must then authorise the publication (without having editing access at this stage). Published article is then 'authored' by 'blog name' and co-authors then appear as a reference note at the bottom.

For real time multi-author drafting, I suggest that authors use cryptpad, as this is already a feature in cryptpad.

Where multi-authors exist at a blog, any of the multiple authors should have access to the posting (publish) tool on that blog. Ony the 'owner' has access to the configuring tool of the blog. Posting: If multi, a check list appears comprising the registered authors on the blog. The posting (editing and markup of the article) can appear after registering the Single or Multi authors. Posting of article should be performed by the one author that registered the multiple authors. After editing, it can then go to draft (waiting for publish; with possibly a time-limit set). Other authors must then authorise the publication (without having editing access at this stage). Published article is then 'authored' by 'blog name' and co-authors then appear as a reference note at the bottom. For real time multi-author drafting, I suggest that authors use cryptpad, as this is already a feature in cryptpad.

👍 1

Rows
Columns

Multi-user writing #774