@Jcross: Why is this task not in scope for Security-Team? Which other project tag should be assigned to this task?

@Aklapper - This was a task where the priority changed around quarterly goals. At the moment, it's kind of floating in the aether, but will most likely become an upcoming quarterly goal for me. If it makes sense to decline it or mark it invalid for now, we can do that.

@sbassett: Ah, thanks. If this is still "on a list" and not forgotten that's fine. :)
(Wondering though what's the sense of restricting the visibility of the project tag currently associated to this task.)

@Aklapper - Do you mean user-sbassett? I'm not sure, I don't believe I created that project, I just requested it be created. I forget who actually created it for me and why they might have restricted it.

Yes. I wonder what @chasemp's exact intention was behind restricting that

@Aklapper - not really sure. Maybe just default protecting the work of a Security-Team member? Though obviously any security-protected task I'd be working on wouldn't be visible to people without security access. I'll plan to ask @chasemp when he gets back.

In T227008#5531607, @Aklapper wrote:

Yes. I wonder what @chasemp's exact intention was behind restricting that

I can't recall but I think scott did the sane thing and fixed it