Integrated user management for a group of repositories
I just needed to post some comments on https://pikchr.org/home/forum and https://fossil-scm.org/forum/forum and noticed that sqlite.org do not have integrated user management between their projects. I know this is a fossil-scm issue but because I only have an account here I'm posting it here. How hard would be to have fossil-scm to manage/share user management between several repositories of the same organization ? It seems that it makes sense and provide a better user experience for it's users. Cheers !
Fossil already has integrated account management. It has had it for years. It's called login groups. It is just not turned on for self-registered accounts such as the one you are using to post the message above.
Thank you for reply ! But the point for my post was just that would be nice if I could use the same login in all public repositories for one organization like sqlite.org. Why not also have a group for self registered users ? Why a user need several accounts like one for sqlite other for fossil-scm other for pikchr.org, ... ?
How would you set up the dependency graph? In the SQLite spirit, let's first try the simplest thing that could possibly work:
box "Fossil forum" fit arrow 50% box "Fossil SCM" fit arrow 50% box "SQLite forum" fit arrow 50% box "SQLite proper" fit
That means sanctified entities like drh can log in anywhere with all capabilities because he has the all-powerful Setup capability on the
sqlite.org/src repo. It would also mean that lesser beings like you and I can log into the Fossil forum because we have a login here on this forum.
But hark! Now we have new problems:
Just because we have a login on the SQLite forum, we have rights on the Fossil SCM code repo? Really??
I have more rights on the Fossil SCM repo than here on this forum, and a different set of extended rights on the Fossil forum. I believe login groups allows user shadowing, so I could have independent logins with different capabilities while you get a single login everywhere, but it does at least go to show that we're not going to end up with "one login everywhere" regardless.
We have to fix problem #1, though. That one's fatal. Let's try again:
box "Fossil forum" fit arrow 50% box "SQLite forum" fit arrow 50% SP: box "SQLite proper" fit FS: box "Fossil SCM" fit at .5 above SP arrow from FS.s to SP.n
Now we're saying that the likes of drh get a login on the Fossil SCM repo and all the forums, but we've fixed problem #1 by requiring that those who have a login on the Fossil SCM repo but not on SQLite's own source repo (like me) must sign up separately there.
But hark! There's at least one new problem: why don't people like me get a login on the Fossil forum delegated from the Fossil SCM repo? It appears that the feature only allows you to set up a single delegation per repository; you can't make the Fossil forum repo delegate to both the SQLite forum and Fossil SCM source repos, so that members of either get a login on the Fossil forum repo as well.
…And I haven't even tried to figure out where the combined Pikchr source/forum repo fits into any of this. Which single delegation should it declare, and why?
(5) By Scott Robison (casaderobison) on 2021-07-03 00:08:24 in reply to 3 [source]
The ultimate reason is "no one has felt strongly enough about having this feature up to this point in time to contribute it."
By and large fossil is used by individual projects. Just because someone is interested in SQLite doesn't mean they are interested in fossil or pikchr, or any other combination.
What you are looking for is a first class citizen of github or chiselapp, and great for people who want to offload their project to a third party. For those who don't want to do that, there isn't such a feature yet.
Whether or not your questions motivate someone to create "social project functionality" above and beyond what fossil already has (which has apparently satisfied most people up to now) remains to be seen.