https://phabricator.wikimedia.org/project/profile/1686/ is a non-public project which is against the guidelines.
Description
Related Objects
- Mentioned Here
- T103700: LOG: Phabricator project creation
Event Timeline
sudo ./bin/policy show PHID-PROJ-7jvft7t6ifzte5tcz5yg
sudo ./bin/policy unlock PHID-PROJ-7jvft7t6ifzte5tcz5yg
Hi, we want to use this project to coordinate activities like administration of Wikimedia Ukraine's server.
At least for some tasks we do not want them to be public, but available only to several people appointed by Wikimedia Ukraine's board
Other tasks can be public
I do not yet understand how to do this in phabricator.
You have to change the policy of each task (maybe you need rights for this, that's the thing of @Aklapper), but if you make a project private, the task are NOT private, and at the other direction: Private tasks don't need a private project. Every project should be public, this don't affect tasks...
Appears to be fixed, there is a recent log entry.
intracer changed the visibility from "Custom Policy" to "Public (No Login Required)".
I will close this.
@intracer: See https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects and https://www.mediawiki.org/wiki/Phabricator/Project_management (and their discussion pages).
@Krenair: Why do you see sense in making each chapter list every software project they start (under their very own prefix)?
That's the status quo, for most project types anyway. I'm asking you to justify making a special exception for chapter projects.
Justification: Because documenting a chapter-only project feels heavy-weight for no good reason.
Are there any other types of projects that you think also shouldn't need to be documented?
Added a comment T103700#1924135
It's not difficult for me comment creation of new projects for WMUA. I'd respect any decision you may come to in your discussion. Sorry for late reply due to holidays and waiting till you come to some decision