Move it to be a sub-project of Phlog?

@JAufrecht: Any comment?

sounds reasonable to me. Would it have to be both sub-projected and re-named to fully prevent conflict? Something like:

"Phlogiston" → "Phab-Category"
"Phlogiston" → "task-category"
"Phlogiston" → "tracking-category"
"Phlogiston" → "Phlogiston-category"

?

In my understanding, Subproject would mean when searching for Phlogiston tasks you'd also get everything currently under #category which has nothing to do with the Phlogiston codebase itself. So I'd go for #Phlogiston-category, without creating a subproject.