- identify potential fora for sharing Phlogiston work
- Easy tag and volunteer page on mediawiki
- identify Phlogiston tasks suitable for those fora
- tagged some Phlogiston tasks as Easy
- frame work appropriately for those fora
- didn't do anything to make them look shovel-ready
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T125583 [EPIC] Support teams using Phlogiston/Phragile Burnups in FY2016Q3 | |||
| Declined | None | T124090 Identify some candidate Phlogiston tasks for help | |||
| Resolved | None | T122608 Expose some Phlogiston work to community volunteers |
Event Timeline
Comment Actions
I don't understand what "fora" means in this context. Is this "mark some tasks as good first task" or what is the scope?
Comment Actions
I think it might just be marking some tasks easy, but I also wonder:
- where, if anywhere, else we should advertise these
- what we can do to make them more appealing and more do-able
- if anyone else is trying to solve the same problems of detailed Phabricator reporting and what we can learn from them.
Comment Actions
Feel very encouraged to add a section to https://www.mediawiki.org/wiki/Annoying_little_bugs :)
- what we can do to make them more appealing and more do-able
General: Dedicated instructions on https://www.mediawiki.org/wiki/Phlogiston how to get the code (there's a GitHub link listed at least), running it locally, creating/getting test data to play with it. For specific tasks: Clear problem definition, how to reproduce the problem, what is expected instead, pointers to related code areas (function names etc).
- if anyone else is trying to solve the same problems of detailed Phabricator reporting and what we can learn from them.
That venue might be https://secure.phabricator.com/T1562