Can we just call this project 'Fundraising' ?

@chasemp Yes, that's great. Thanks!

https://phabricator.wikimedia.org/tag/fundraising/

Fundraising-Backlog

editable by you, joinable by all for now. unsure what you want. have fun.

Remember that

Visible To All Users

must be Visible To Public

ah yes thanks

chasemp changed the edit policy of this Project from "All Users" to "Custom Policy".

In other words, I can't change the policies for Visible even after joining the team. I guess only @atgo can now?

In T682#11645, @Qgil wrote:

In other words, I can't change the policies for Visible even after joining the team. I guess only @atgo can now?

and administrators. (click on "custom policy")

In T682#11648, @jeremyb wrote:

In T682#11645, @Qgil wrote:

In other words, I can't change the policies for Visible even after joining the team. I guess only @atgo can now?

and administrators. (click on "custom policy")

This is true, I don't know what they need so I figured let @atgo decide

I can! That is interesting that you can't. I don't see you as a member,
@chasemp

The current defaults (totally negotiable) are defined at https://www.mediawiki.org/wiki/Phabricator/Help#Requesting_a_new_project

If a team needs something different, then they should specify it when requesting the project. Note that, specially now that we are starting, most teams will not know what they need or want. For instance, we have seen how many new project owners think that defining a project "visible only to team members" will make the related tasks visible only to them, which is not true.

We are creating more teams, and this is just the beginning. From now on, let's stick to the process (including myself, who not always has followed it), and let's improve it if needed.

Note: https://bugzilla.wikimedia.org/describecomponents.cgi?product=Wikimedia lists a "Fundraising" component with 11 open tickets: https://bugzilla.wikimedia.org/buglist.cgi?component=Fundraising&product=Wikimedia&resolution=---

That stuff should probably be moved / projects on those tasks re-adjusted after importing Bugzilla tickets.

OK, good catch. I don't think this is a duplication beyond the name of the project/component, because this project here is to organize the work of the team in Mingle, and the Bugzilla component is something different. The new project created during the Bugzilla will be called Wikimedia-Fundraising, and yes, some polish will need to be done when those bugs land here.

By the way, proof: https://bugzillapreview.wmflabs.org/tag/wikimedia-fundraising/

14 open tasks under "Wikimedia-Fundraising" (imported from Bugzilla): https://phabricator.wikimedia.org/maniphest/query/bSyzmb9u7iGe/#R

@atgo: Any plans to (re)triage them?

@Aklapper thanks for bringing this to my attention. I'll look into this as we go here.

@atgo: If I can help with cleaning up the now 17 tasks under Wikimedia-Fundraising (and archive that project afterwards? Don't know), let me know how.

@Aklapper I sort of want to keep that project for the community to submit issues that we can triage into our workflow, but will try to work through the tasks open over there coming up.

@atgo, please consider having a single project where all tasks land, and then create sprint projects where you cherry-pick the tasks for the next weeks. Having to monitor one space than having to monitor two spaces. Besides, I guess the traffic of new community tasks is not that big?