So ideally each project would be very specifically scoped and not super broad - the editor engagement project is already problematic in that that team has morphed so much that there are a lot of instances with unclear use or ownership. I'm highly inclined to decline this and have you guys request more specifically scoped projects. If you feel like this can create undue burden, we can expand the number of people who can create projects - I think @bd808 in the reading team already can.

Also I'm inclined to decline this because sprints named YOLO deserve to get projects declined :p

https://phabricator.wikimedia.org/T104994 is much better scoped imo

In T105045#1435080, @yuvipanda wrote:

we can expand the number of people who can create projects - I think @bd808 in the reading team already can.

I think I do have the wikitech mojo to do that but nobody has ever showed me how to use these powers. I suppose I should get a tutorial (or pointed at the fine documentation).

@yuvipanda, could you please identify the appropriate place for us to create our instances?

@bd808 how about I write up guidelines and instructions later today?

After discussing in IRC @yuvipanda I now understand that the intention is to have more projects that are more tightly scoped. I think we agreed on reading-smoketest

The scope of this project is to run automated tests on Reading projects. Name accordingly.