Re-Sharing Behavior Update

[MTRichards]

In a future ownCloud release (8?).

As an ownCloud user, I want people with reshare privileges on a file or folder that I have shared with them to be able to reshare that with other users, and I want those "reshared" recipients to appear in my shared to list, so that myself - and everyone that the file is shared with - knows who has access to the file.

This means two things have to happen:

1. Every user that is a share recipient of a file or folder can see a list of who else has access to the file or folder (which will need to be a setting that can be disabled in the config file for some security related reasons)
   and
2. That the sharing behavior moves from the current ad hoc re-share chain (which is difficult to search and understand programmatically or as a user) to a scenario where a reshared file or folder recipient is just added to the file or folder owner's "shared with" list.

In short, rather than creating an ad-hoc share using reshare, the user would be adding another person(s) to the file or folder owner's list of "shared with".

This will make it much easier to report on sharing, much faster for the API to allow mobile and desktop (in the future) to make changes to the shares, and makes it much easier on the admin and end user to understand.

[karlitschek]

yes. good point,

[PVince81]

As discussed 👍

[PVince81]

If I remember well we identified some potential difficulties but can't remember right now.
This needs to be thought through, including how the old reshares will be migrated.

[schiessle]

Absolutely, we discussed this already in Stuttgart and I'm in favour of it! This would also make a lot of other stuff much easier! I will put this on my ToDo List 😄

[nickvergessen]

Just came across this while trying to add acitivities for "Resharing".
Will put them on the oC8 list, so I do not have to implement them twice.

[PVince81]

Any update when we want this ?

[PVince81]

Note: if we still don't want to schedule this, there's a bunch of permission propagation issues that will need to be solved then, like #13201
and these fixes will likely to be thrown away afterwards.

[michaelstingl]

00002404

[MorrisJobke]

cc @craigpg FYI ... @michaelstingl has a request for this feature.

[cdamken]

@MorrisJobke @MTRichards Is it possible to put it in a milestone? When is planned?

[DeepDiver1975]

Is it possible to put it in a milestone? When is planned?

I don't see this happen before 8.2 @MTRichards FYI

[MTRichards]

No sooner than 8.2, agreed.

[nickvergessen]

so we need a new milestone me hides 🙊

[MTRichards]

Now it is an official user request.

[bboule]

@MTRichards did this make 9 or should we be setting a different expectation?

[MTRichards]

Should be in 9.0. We are reworking sharing, thus this should be reflected in it.

[DeepDiver1975]

@schiesbn let's chat soon-ish about the migration path - THX

[DeepDiver1975]

@MTRichards do we have any reference database dump to 'play' with? Or at least an understanding how the most complex and biggest installations out there look like - with respect to resharing? THX

[MTRichards]

@bboule is your link to our running systems.
@bboule do you have any access to the data?
or @MorrisJobke perhaps there is something from our work with [customer you spent a while on]?

[caratsch]

@DeepDiver1975 & @MorrisJobke I can provide/send you an actual dump if you want

[rullzer]

With #20773 in shares created via the OCS endpoint (so soon all shares!) will have the new sharing behaviour. So they are actually shares of the file owner but have the user that shares them as initiator.

[MorrisJobke]

@MTRichards do we have any reference database dump to 'play' with? Or at least an understanding how the most complex and biggest installations out there look like - with respect to resharing? THX

I can check with @caratsch - what do we want to know?

• shares vs reshares - original folder vs subfolder
• external shares
• self-mounted external shares

Anything else?

[PVince81]

Missing pieces to finish this:

• make share GUI / files app use the OCS endpoints to be able to create such shares: Web interface should use the OCS Share API #21554
• migration of old shares: upgrade to sharing 2.0, remove hierarchical re-shares #21660
• some OCS API modifications (minimal) ([Share 2.0] Add share owner information to OCS Share API #21754)

[rullzer]

some OCS API modifications (minimal)

This is basically just adding information about who owns the files. The info is already there in the share object. I just did not yet expose it to the outside world.

[rullzer]

PR for extending the API #21754

[PVince81]

@rullzer anything left for "re-sharing" behavior update on the code side ?

• QA
  • flat reshares testing: Create test plan for resharing behavior update QA#94
  • reshare migration: Migration testing of reshares QA#92
• documentation: @carlaschroder @jospoortvliet

[rullzer]

• Properly fix displaying the new resharing behaviour...

[PVince81]

Properly fix displaying the new resharing behaviour...

@rullzer what about this ?

[rullzer]

@PVince81 ah crap forgot about that one... let me see what I can do :)

[PVince81]

@rullzer what's left to fix ? I thought it was that tooltip about the initiator but it got shot down.

[rullzer]

Yes lets close this. This is basically done. The multiple link shares (#22327) that are needed to have this resharing behaviour also for link shares is raised separatly,

Other stuff that comes up now are either bug or new features :)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.