Phorge is meant to be a community project. Ensuring the public has access to what's going on in there easily would reduce the barrier to entry into the project.
Access could be granted to diffusion, maniphest, the repositories and their respective audits, paste, etc...
If this is generally agreed upon, I'll proceed with the config.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | Matthew | T15003 Configure default dashboards / sidebars / favourites | ||
| Resolved | Matthew | T15007 Extends access to part of phorge to logged out users |
So I edited policy.allow-public and set it to true in the DB.
And then proceeded to update the policies of various apps so that they can be accesses without login. Participating still require to be logged in.
Changes:
I haven't touched other app, because I'm not sure what we want to do with them. these were fairly obvious IMO, so I went for it.
It's on a subdomain that isn't listed anywhere and registration require approval, so that shouldn't be a problem.
Also, S1 isn't public, contrary to what the name says, so this effectively just changes the error message at the moment.
S1 has been adjusted (the option didn't exist until the switch you flipped was active). I've also adjusted all tasks (per-object policies) and the dashboard panels. I will make a pass at the subprojects unless you want to go for it.
Sorry about the spam... I've gone ahead and made all the component projects of Phorge public. Is there anything else we need to do here?