Umbrella task for newsletters about Structured Data on Wikimedia Commons. https://commons.wikimedia.org/wiki/Commons:Structured_data/Newsletter_archive
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T170236 [Epic] Newsletters about Structured Data on Commons | |||
| Resolved | • SandraF_WMF | T170842 Send out Structured Data on Commons Newsletter - July 2017 edition | |||
| Resolved | • SandraF_WMF | T173840 Send out Structured Data on Commons Newsletter - The October 2017 Edition | |||
| Resolved | Keegan | T177204 Enable the Structured Commons newsletter via Extension:Newsletter as well | |||
| Resolved | • SandraF_WMF | T179328 Structured Commons newsletter - Nov-Dec 2017 edition | |||
| Resolved | Keegan | T186641 Structured Commons newsletter - Spring 2018 edition | |||
| Resolved | Keegan | T196652 Structured Data Newsletter - Summer edition |
Event Timeline
Comment Actions
See https://phabricator.wikimedia.org/T170126#3487371 - not sure "umbrella" tasks are really useful or necessary - they end up among your open tasks and they can't really be resolved... the child one instead is great!
Comment Actions
Arguments in favor of my choice to have umbrella tasks:
- Well, they are stuff I do continuously work on; some work just doesn't end :-)
- I like to make continuous tasks visible to anyone I work with ('see, this is stuff I have on my radar all the time')
- Allows me to structure my work better (tree structures help me getting insight). I do/did it for other private and work projects too.
- And I can link it from project pages on wiki, so that anyone who's interested can click on to the umbrella task and then see that I managed n newsletters in the past and have n planned for the future.
But if there are stronger arguments against (clogging up boards, adding confusion for others, problematic in terms of project and goals management) I'll be happy to stop doing this!
Comment Actions
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)