It's currently set up so that only Phabricator administrators can create blogs. I think an admin should just create it for you instead of making you an administrator or fiddling with application policies.

Although what does 'internal' refer to in the task title?

1. Does that mean I have to have an admin post for me every time I want to write a post?

2. Internal means it's not an external-facing, promotional-type blog. The contents aren't supposed to be private - the intention is research visibility across the 3 Reading teams. It's going to have a lot of process/in-progress type stuff. I'd rather have a blog than spam people on various lists. This is the closest I can come to doing a blog that I have found that seems to adhere to our foundational principles.

Thanks!

In T134951#2283522, @pizzzacat wrote:

1. Does that mean I have to have an admin post for me every time I want to write a post?

No, creating posts in an existing blog and creating blogs should be entirely separate things... And if they're not let's open an upstream bug :)

In T134951#2283522, @pizzzacat wrote:

2. Internal means it's not an external-facing, promotional-type blog. The contents aren't supposed to be private

Okay.

No, creating posts in an existing blog and creating blogs should be entirely separate things... And if they're not let's open an upstream bug :)

Great. Things don't always make sense to me in Phab land so I never assume things will work the most obvious/desired way. :)

How do I get started?

We need an admin to be able to do anything

Who is the admin?

The list of admins is available at https://phabricator.wikimedia.org/people/query/zYtnRSCkBXQ./
People with operations access on the servers have access to the generic @admin account but should probably not really be using it for things like this

Ok, so I guess the question I have been trying this whole time to ask is, which actual person do I need to contact for "things like this"?

Thank you for your help!

The phabricator admins... You do not contact a specific individual.

gotcha. thanks!

I created the blog:

https://phabricator.wikimedia.org/phame/blog/view/6/

But @pizzzacat is not able to post. Perhaps this requires the creation of an `acl*' group, in which case it is above my paygrade, and should be referred to @Aklapper.

That blog's edit policy allows members of a publicly-joinable project access

For the time being, I've changed the Edit Policy to not include a project open for everybody. So currently it's only admins and @pizzzacat.

@pizzzacat: If you go to https://phabricator.wikimedia.org/phame/blog/ , is there a "New Post" button shown for "Reading UX Research"? Clicking that, you should get a "Create Post" page and a "Create New Post" button at the bottom. Can you describe at which point it fails and what the unexpected behavior is?

(I have not played yet with Phab blogs so I'm happy to learn with y'all.)

Thanks @Aklapper!

The point at which it fails is after clicking the "New Post" button. I get the following:

Meh, I'm puzzled. Maybe @mmodell has some ideas as policies on https://phabricator.wikimedia.org/phame/blog/edit/6/ look okay to me.

@Aklapper: fixed. The culprit was the policy on the 'create blog post' form, which is https://phabricator.wikimedia.org/transactions/editengine/phame.post/view/13/

I added @pizzzacat to that acl. We should probably make an acl*blogadmins or something like that at some point soon. I'll do that if anyone else requests a blog I guess.

@pizzzacat: can you confirm that you are able to create a post now?

@mmodell, apologies, was OOO, it's working now though. Thank you!