Details
Working on setting up Phabricator, and trying to decide on a solution for this.
Basically, the Projects app is not fine grained enough for us. Our organization basically has two types of development teams that we would like to fit into the "Projects" app - Maintenance teams (permament teams handle the day to day administration, bug-handling, etc), and Project teams (temporary projects, that have a relatively short life-span).
For a user who is trying to browse the Projects app, it would be very useful to be able to distinguish the former from the latter. Presumably this could be done if {T390} was done, but since it isn't, we're left with having to think of some other way of handling this in the meantime. What do others do/suggest?
Additional questions:
- How difficult would it be to change the name of the Projects app (i.e., any unexpected side-effects)? A "Project" means something very specific in our organization which doesn't fit with how it is used in Phabricator. This has already caused confusion for us during presentations; renaming it to something like Teams or Groups would probably lessen confusion.
- Already asked this elsewhere, but would it be possible to reconfigure the default wiki space of projects to something else in a simple way? Would a hack/patch for this be accepted?
Answers
- Projects is expected to handle groups of all types (tags, teams, groups, policy groups, projects, sprints, etc), but we haven't come up with a better name for this. Some of these types need more work to work really well.
- There's no way to rename applications. If you go change the strings in the code that shouldn't break anything. However, all the URIs will still say "/projects/" and such, all the fields in other applications will still say "Projects", etc.
- We plan to let projects have more "type" information and expose it in more interfaces, although this will likely be a set of orthogonal options rather than major top-level types (per T390).
- We're removing the one-to-one wiki-to-project mapping and just exposing policies in Phriction. See T4029.