qgil wrote on 2014-09-04 15:20:02 (UTC)

Hi @Rdicerb, several things.

In T613#1, @Rdicerb wrote:

Or, rather, a project page where we can post tasks...

Note that you can edit the task description, amending mistakes and adding more details.

According to https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project, if you belong to a team that will manage several projects, then the first step is to create a project for your team. It is probably a good idea to create first the Community-Engagement project (public), since I guess by default your tasks will be public. What do you think?

I'm not even sure we can support real private projects in this instance. Maybe this has to wait to have Wikimedia Phabricator in production (coming soon). CCing @Rush and @mmodell.

Rush wrote on 2014-09-04 17:17:09 (UTC)

we couldn't confidently provide any real security here, i wouldn't put anything in this instance that can't be public knowledge. we could however provide a example of how things will work?

rdicerb wrote on 2014-09-05 00:49:56 (UTC)

OK, this makes sense. I've updated the task. Can I update my request for a Community Engagement (Product) project (public is OK) :)

qgil wrote on 2014-09-05 16:36:30 (UTC)

Done: #community-engagement. Have fun!

I have skipped "(Product)" because we prefer to avoid parentheses in project names, because we think that shorter is better, and because there is no confusion with another Community Engagement team here. I hope this works for you, otherwise projects can be renamed.

@Rdicerb, currently you are the only member of the team, and we have configured this WMF team project so only members can bring new members on board. See the "Edit members" tab in the project page.

importing issue status

Maybe I'm missing something here, but where was the justification for this being a restricted project?

Mmm... I don't recall exactly. At that time we still didn't have clear guidelines for project policies. #Community-Engagement was among the first team projects created, and back then the main reference was the Phabricator team, which was/is restricted (for a good ACL reason).

I guess they can be just set to All Users now?

@Rdicerb: "Joinable By: Community-Engagement (Project)." - is there a reason for this? See last comments here.

Not really, this was just a page that we requested when we were first coming into Phabricator

Can it be opened to all users then?

I had locked it, because we were planning on putting all our tasks on here, including details about work that wasn't public yet. I was under the impression that Herald was going to solve the "inability to watch a project I can't formally join", but the ETA of that is unclear, and we don't have anything private in here yet, so I'll open it back up.

As weird as this might sound, project policies do not condition task policies. Public tasks will be just as public when associating them to a restricted project. Tasks can be associated to multiple projects, and therefore it is not possible to set an infallible 1:1 mapping.