@Milimetric Can you please link the list thread? And possibly (if not mentioned in thread) list some examples of tasks (either existing or artificial)? Thank you.

@Danny_B: See https://office.wikimedia.org/wiki/Internal_tech_group for what we're thinking about. I don't have a link to the thread handy, but would like to include it on that page at some point.

In T139994#2449454, @ksmith wrote:

@Danny_B: See https://office.wikimedia.org/wiki/Internal_tech_group

Errm, that's some internal WMF page that only WMF folks can access?

"improve internal technology and processes" sounds a bit vague - how to differentiate from e.g. WMF's Office IT department or Team-Practices?

Sorry about the internal-ness. Yes, that's a staff-only wiki.

This a volunteer working group, who hopes to streamline WMF internal staff processes, either via improved documentation/templates, or automation. An example is that filling out an expense report is currently awkward and time-consuming.

The wiki page is on office because we will be dealing with finance and HR-related processes, and didn't want to risk something inappropriate leaking out. We're not actually working on anything top secret. Just mundane.

@Danny_B / @Aklapper: I've updated the description based on comments, thanks for the feedback. Let me know if anything else is unclear.

@Milimetric You request component, but the description states "This a volunteer working group..." Shouldn't that rather be team (violet) instead then?

Also, if you work on partially non-public things, you probably would you need private space for that to prevent any accidental leakage.

BTW: The list also seems to be private.

Ok, Team works for us, I'll update the description. You're also right that we might need some tickets to be private, I don't know how to specify that officially but I'll say so in the description. Anything else left to clarify?

Team is fine too I think, if Phab allows to create team query/workboard (which I think it does), it's fine. I also assume we can make some tasks private for team members only?

In T139994#2477120, @Smalyshev wrote:

Team is fine too I think, if Phab allows to create team query/workboard (which I think it does), it's fine. I also assume we can make some tasks private for team members only?

You could either fiddle with manually editing each task's policies, or request a Space in addition to the project if you can define Space members.

This feels stuck, is there anything left to address?

@Milimetric I can create the tag, that's no issue with that. But that won't guarantee you the privacy yet. So I thought having the space set prior the tag would be better. However, spaces can be set only by Phabricator members.

Let me know if you would like the tag to be created regardless the existence of the space.

I think it would be useful to have the tag created first. We can just refrain from discussing anything sensitive until we have the space. But it would be nice to get ourselves organized as right now the tasks are floating around random other projects.

@Milimetric : Is this project still active / are its 4 open tasks still something to follow up on at some point?
Asking as https://phabricator.wikimedia.org/project/profile/2146/ lists the last activity in 2016...

@Milimetric : Is this project still active / are its 4 open tasks still something to follow up on at some point?
Asking as https://phabricator.wikimedia.org/project/profile/2146/ lists the last activity in 2016...

@Aklapper it's failed as far as I'm concerned. Two of the people that were originally interested are not at the foundation and I'm too busy to do anything with it. I think in general it's an idea we need to prioritize, so I wouldn't delete the tag. But if the open tasks bother you I can decline them.

FYI I have archived the project tag WMF-Internal-Tech as it seems to be unused.