My user story:
As a manager, I would like to see my team's work in one board, so that I can keep a broad view on the tasks that my team is specifically either assigned to or considering as part of the workload.
I know several tickets have multiple tags, but I wanted to express that <:) I believe we'll be formalizing that in the near future, but examples of best practices also welcome :)
So that mean the Reading board is illicit? :)
That may be a problem: as CLs, we need a more flexibility. We don't only have a task-to-task view, but a global one. Sometimes we need to schedule announcements on products which are related but lot directly linked. At the moment, we don't have a tool to do that and a board is, fur us, the best solution.
I haven't think any moment that I will not use the CL board too :)
This Collab CL board will be useful for the Collab team too: whey will have a look on CL actions without all CL actions we can have on our board.
Yes! But Community-Relations-Support (and any team project with a decent amount of activity) just becomes too big to be the main tracker. Sprints are the default way for teams to track the work that is currently going on, i.e. DevRel-December-2015.
I want to propose monthly sprints for CL (starting as a test in January, ideally) as part of T116025: Goal: Align Community Liaison and Developer Relations project management practices. This would allow i.e. Trizek (or @Moushira, who long ago requested Readers-Community-Engagement) to have all the flexibility they need to manage their projects, while i.e. Rach (or anybody else interested in CL's current work wherever it happens) can track it by watching a single project (the current monthly sprint).
Not sure what "the Reading board" is - if you refer to the link you put into this task's desc, it is simply the board of the existing project Readers-Community-Engagement.
I was merely pointing out that when you ask for creating some board, in fact you ask for creation of a project (cf. project request guidelines; project management recommendations).
My attempt to make a joke was not a success :)
My request is to create a project Collaboration-Community-Engagement in order to facilitate CL job for Quiddity and I, mainly by having a Kanban board.
Yes. I confused the two terms., sorry.
- Name: Collaboration-Community-Engagement (to have something similar to Reading's CL board)
- Description: Board for organizing work around Community Engagement tasks related to Collaboration-Team-Triage (Notifications, StructuredDiscussions, and more)
- Fully open project
- Community-Relations-Support subproject
@Quiddity, what do you think about all this?
Can this be Collaboration-Community-Liaison instead of Collaboration-Community-Liaising to stay consistent with Community-Liaison?
Also, technically, subprojects don't exist (info would only be part of the project desc).
Requested project Collaboration-Community-Engagement has been created: https://phabricator.wikimedia.org/project/profile/1691/
Please encourage interested people to visit the project and to join the project as members, and to subscribe themselves to the project in order to receive updates!