Page MenuHomePhabricator

New project: APG-FDC
Closed, ResolvedPublic

Description

I am looking at trying out Phabricator to manage the Annual Plan Grants FDC process. For this, I need a new project. I suggest calling it APG-FDC (there are two parts to the Annual Plan Grants (APG) process, the FDC - Funds Dissemination Committee- and the simple APG process). At this stage, this is to be a pilot in trying out Phabricator as an effective way of running this project. Thanks.

Event Timeline

Project description: This is a project that will outline the process, tasks and milestones associated with the Annual Plan Grants FDC Process. More information about Annual Plan Grants/ Funds Dissemination Committee can be found on the relevant page on meta. The most important milestones are outlined on the APG Calendar.

The APG-FDC process consists of recurring rounds (2 rounds per fiscal year), which are usually referred to as Round 1 - YYYY-YY+1 and Round 2 YYYY-Y+1. Possible names for this project are AnnualPlanGrants-FDC for better readability or APG-FDC (a bit jargony).

I would also assume type is "default" unless there is a specific not-software-related type :)

Additional question: Once the project is created, can I add sub-projects/milestones myself? Thanks.

I don't think the proposed name conforms with our best practices on naming projects.

Can you be a bit more specific? Would Annual-Plan-Grants-FDC work? (Adding the full Funds Dissemination Committee bit is over the top I think). We could also stick with Annual-Plan-Grants and I'd have to have a specific FDC tag or a sub project Annual-Plan-Grants-FDC to make sure we don't phagocyte the Annual-Plan-Grants process altogether. Thanks.

If I understand correctly APG and FDC are different things. Since Tasks can have from 0 to infinite projects added, would it be a good idea to have one project called #Annual-Plan-Grants and another one called #Funds-Dissemination-Committee? Of course APG and FDC could be set as project aliases afterwards if needed. Regards.

Hello. APG and FDC are different things, but APG is the "umbrella" project. the FDC is a committee that makes decisions for part of the Annual Plan Grants process, the other part are simple Annual Plan Grants (yeah, I know, naming is a Wikimedia plague ;)). In any case. There is little "project material" thing to the FDC, since it's a committee. In my case, its name is used to differentiate two processes, one that has the FDC as deciding committee, the other one that has a simple APG committee as the deciding committee So to be super accurate, we'd need to have the following:
#Annual-Plan-Grants, #Funds-Dissemination-Committee (this would have the only project elements pertaining to the FDC, such as (s)election milestones etc. which might be a good idea anyway). #simple-Annual-Plan-Grants-committee
As a sub-project of #Annual-Plan-Grants, you'd have Annual-Plan-Grants-FDC and #Annual-Plan-Grants-simple for example. At this stage, I am only responsible for the FDC bit of that process, so I don't need anything pertaining to simple. Also, a lot of the milestones/tasks pertaining to the Annual-Plan-Grants-FDC process would not pertain to the project #Funds-Dissemination-Committee, since they do not involve the committee at all. Does that make sense?

So to summarize, what would work would be:
#Annual-Plan-Grants (tag APG for short)
and a sub-project Annual-Plan-Grants-FDC (tag APG-FDC for short)
nice to have would be #Funds-Dissemination-Committee. (tag FDC for short) but it's not my priority for now.

We can leave the simple bit out for now.

Aklapper triaged this task as Medium priority.

So to summarize, what would work would be:
#Annual-Plan-Grants (tag APG for short)
and a sub-project Annual-Plan-Grants-FDC (tag APG-FDC for short)
nice to have would be #Funds-Dissemination-Committee. (tag FDC for short) but it's not my priority for now.

We can leave the simple bit out for now.

I'm not sure I can still follow. :-/

Does that mean there would be

  • tasks that are under a #Annual-Plan-Grants (top-level) project
  • and other tasks that would be under an #FDC subproject (#Annual-Plan-Grants being its parent project)
  • and other tasks that would be under a #Funds-Dissemination-Committee (top-level) project

? (Also note that subprojects can only have one parent project.)
If we'd want to have two or three [sub]projects, they'd also need to have project descriptions.

Almost. This is a bit complicated because of stupid naming issues. [edit: stupid naming issues on our part, ie. we have no good names for these processes]
#Annual-Plan-Grants is a top level project
Annual-Plan-Grants-FDC is a subproject of #Annual-Plan-Grants

At this stage, all I need is Annual-Plan-Grants-FDC with the project description I gave above:

Annual-Plan-Grants-FDC is a project that will outline the process, tasks and milestones associated with the Annual Plan Grants FDC Process. More information about Annual Plan Grants and the Funds Dissemination Committee can be found on the relevant page on meta. The most important milestones are outlined on the APG Calendar.

I don't want to take #Annual-Plan-Grants because one day maybe, we might need it for a top level project name that includes BOTH the "APG FDC process" and the "simple APG process". I also don't want to take Funds-Dissemination-Committee because that's just the committe, not the process and it can be a top level project of its own (because it also has a timeline and deadlines etc.). Does this help? Thanks!

one day maybe

For the records, we cannot "easily" convert a (default, top-level) project into a sub-level project but it *is* possible.

Thanks everybody for the patience and for clarifying!

Requested project Annual-Plan-Grants-FDC (you can also enter #APG-FDC in any project tag field) has been created: https://phabricator.wikimedia.org/project/view/2665/

Please encourage interested people to visit the project and to join the project as members, and to watch the project in order to receive updates!

Recommended practices for project and workboard management in Phabricator are available.

And if for some reason you ever want to rename the project, please check the guidelines first.

Enjoy!