Page MenuHomePhabricator

Fix restricted project "WMUA-Tech"
Closed, ResolvedPublic

Event Timeline

Krenair raised the priority of this task from to Needs Triage.
Krenair updated the task description. (Show Details)
Krenair added subscribers: Krenair, demon, 20after4.

PHID-PROJ-7jvft7t6ifzte5tcz5yg

sudo ./bin/policy show PHID-PROJ-7jvft7t6ifzte5tcz5yg

sudo ./bin/policy unlock PHID-PROJ-7jvft7t6ifzte5tcz5yg

Aklapper updated the task description. (Show Details)
Aklapper set Security to None.

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...

Matthewrbowker subscribed.

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: Please fix the Join Policy of WMUA-Tech which is against the guidelines. Reopening this task.

Aklapper renamed this task from Fix a 'Restricted project' to Fix restricted project "WMUA-Tech".Dec 25 2015, 8:20 PM
Aklapper reopened this task as Open.

All policys are at setting "all users" (visibilty is public)

It also needs to be documented at T103700: LOG: Phabricator project creation.

We should exclude Wikimedia chapter projects from that - I don't see much sense.

It also needs to be documented at T103700: LOG: Phabricator project creation.

We should exclude Wikimedia chapter projects from that - I don't see much sense.

Why Wikimedia chapter projects specifically?

@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