Relevant milestones: Phabricator (2016-06-15), Phabricator (2016-06-29)

Here's my draft of a post about the sponsored improvements that have landed in recent weeks:
{P3436}

@mmodell: Thanks for working on this. Very appreciated!

Some quick'n'dirty blunt feedback:

• s/Phacility/Phacility (the company developing Phabricator)/ ?
• s/reaping/seeing/ ? (might be clearer for non-native speaker audience). Also... "laundry list"? (I just put stuff into my washing machine.) :)
• s/Wikimedia's production Phabricator instance/phabricator.wikimedia.org/ ? (Not sure people need to know production vs test instance. )
• Link "RFC" to https://www.mediawiki.org/wiki/Requests_for_comment ? Dunno
• "on a VM Instance" - maybe drop that technical detail? "test instance running on WMF Labs" might be sufficient?
• s/Unfinished/Work in Progress/ ? Sounds better. :)

Again, thanks!

I asked @mmodell last night if I could make an etherpad to do some light copy/editing. I go distracted (it was almost 11pm) and didn't, but now.... https://etherpad.wikimedia.org/p/phabricatorphacilityworkblogpost :) (and of course I forgot the c/e things I saw last night, will read/review later)

I basically just edited the etherpad to included @Aklapper's suggestions.

There's also now a section on milestone and calendar changes and the new task graph (in the etherpad), if anyone wants to read/review. I just re-wrote it to be more simple/straight-forward, but left the original. Up to Mukunda.

@greg: I'm sure your rewrite is an improvement... I was having trouble expressing that part clearly, it started sounding like an incident report timeline which wasn't my intention for the blog post ;)

In T137727#2473968, @mmodell wrote:

@greg: I'm sure your rewrite is an improvement... I was having trouble expressing that part clearly, it started sounding like an incident report timeline which wasn't my intention for the blog post ;)

:) Good habit anyways.

I took the liberty to remove the incident report version and left mine and added a nice "Here's to yet more fruitful collaborations with upstream Phabricator!" to close it out. Other than that I think all we need to decide is timing.

@mmodell / @Aklapper: Were we going to do this on the main Wikimedia Blog or just in Phab? If on the main blog, we'll need a couple weeks (I assume) for turn around with Communications copy editing this :)

See: https://meta.wikimedia.org/wiki/Wikimedia_Blog/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts

I wasn't planning to go for anything as high-profile as the wikimedia blog, especially if it's gonna take weeks... I was thinking Phabricator blog post + email to wikitech-l

Hey, do Phabricator blog posts have RSS feeds? We could add that to planet.wikimedia.org. Gets you a bit more views at almost no cost.

Why not put it on the Wikimedia blog? It's a pretty cool thing that should be shared more widely IMO :)

In T137727#2476716, @Dzahn wrote:

Hey, do Phabricator blog posts have RSS feeds? We could add that to planet.wikimedia.org. Gets you a bit more views at almost no cost.

Only reference upstream I found was https://secure.phabricator.com/T2272 which is closed and has an associated commit, but, my RSS feed reader (NewsBlur) can't find it (the atom feed).

https://phabricator.wikimedia.org/phame/blog/feed/1/

It doesn't seem to be referenced in the html header so I guess you just have to know that it exists?

:) ->> https://gerrit.wikimedia.org/r/#/c/299867/1/modules/planet/templates/feeds/en_config.erb

In T137727#2476444, @greg wrote:

@mmodell / @Aklapper: Were we going to do this on the main Wikimedia Blog or just in Phab?

IMO I'd be happy to see this on the WM Blog. If things take a bit longer, post it $somewhere_else first (like on Phab)...

@Aklapper: That sounds good to me, let's put it on phab first and then get the ball rolling on a WM Blog post with same/similar content.

Are we happy with the current version? The formatting looks good in phabricator. I don't anticipate deploying new upstream work this week so we won't have any further updates to the fixed tasks to announce for a while.

In T137727#2481194, @mmodell wrote:

Are we happy with the current version? The formatting looks good in phabricator. I don't anticipate deploying new upstream work this week so we won't have any further updates to the fixed tasks to announce for a while.

+1, I'm good. We can publish on the RelEng phame blog whenever and then get in touch with Communications about the Wikimedia Blog post (I can do that reaching out). Thanks!

Etherpad LGTM. (I'd only remove one of the two "helpful"s about the task dependency graphs.)
Again thanks for working on this. <3!

OK I've published Blog Post: Sponsored Phabricator Improvements