[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Alioth → Salsa

On Mon 2018-01-29 18:08:47 +0100, gregor herrmann wrote:
> - sharing and unsharing is terribly slow (several seconds before the
>   call returns), in the back of my head I saw busy tiny persons
>   running through a PostgreSQL database and adding/removing all the
>   IDs ...
> - sharing/unsharing also has a delay, I had to wait for about a
>   minute until project_users showed the correct output
> - sharing/unsharing are not idempotent, i.e. sharing fails when the
>   project is already shared, unsharing fails if the project is not
>   shared. That's not insane per se, but there doesn't seem to be a
>   method to list current shares. In dpt-salsa I now check if the user
>   with id 1 (that's the salsa administrator) is a project user
>   *cough*

[ ... ]

> AFAICS, access level "manager" is needed in a subgroup to allow the
> members to add new projects, i.e. push new repos, which is what we
> want. -- This seems to have the interesting side effect that all those
> "managers" get all "join requests" (in the To: header) :/ It sounds a
> bit unfortunate to send them to (in the future) 100 people.

[ ... ]

> Given the issue mentioned above (recipients) and the unhelpful mails
> generated by GitLab (user can't add a message to their request; no
> info who actually requests access in From or Subject; no possibility
> to reply or to find out user's email address; broken signature
> delimiter -- ok, that's just aesthetic), I'm wondering if we should
> turn off the join request feature and just point to the mailing list
> and/or homepage (like other teams already do).

this seems like you've identified at least 5 issues or potential feature
requests in gitlab.  have these been reported anywhere?

thanks for doing this work for the perl team, Gregor!


Reply to: