> On 1 Jul 2015, at 18:25, Jon Katz wrote:
>
> Wes noticed on Monday that, according to Google, they are unable to reach a
> growing number of our resources. [..]
>
> Screenshots below, followed by drill-down of specific resources.
>
> Today on https://en.wikipedia.org
>
> https://www.dropbo
As an outside observer, I'm a bit concerned about the deprecation of one of
the few tools used to give a "big picture" overview of what is coming, who
is scheduling what, and the ability to identify conflicting or competing
priorities. Engineering has done some outstanding work, but there have
als
Hi Gergo,
First: Thanks for your reply. I always appreciate your ability to point
out things people have missed/forgotten.
> I don't think all (or even the main) use cases of #roadmap are covered by
> the proposal.
>
> * #user-notice is much more noisy. A #roadmap task is "describing a
> signif
+teampractices
On Thu, Jul 2, 2015 at 4:17 PM, Greg Grossmeier wrote:
> Hello all,
>
> First, some history and context:
>
> The #roadmap project[0] in our Phabricator instance was set up by Erik M
> as a trial way of tracking upcoming releases, deployments, and generally
> "new things of note",
