Changes between Version 1 and Version 2 of Fellowship2013/Priorities


Ignore:
Timestamp:
03/25/2013 07:37:20 AM (3 years ago)
Author:
exarkun
Comment:

if these are numbered, then put what seems to be a priority at the top

Legend:

Unmodified
Added
Removed
Modified
  • Fellowship2013/Priorities

    v1 v2  
    1   1. Tickets already in review before
    2     * Many tickets have had some work done on them but have not yet been completed.  These tickets represent a large amount of invested effort that has yet not yielded any benefits.
    3     * As such, completing them may result in proportionally more return for effort.
    4     * Some judgement needs to be applied in selecting tickets from this category.  Just because effort has been invested does not necessarily mean the tickets are particularly valuable to resolve.
    5     * Some tickets are stalled or abandoned because they are really, really hard (and so probably require lots and lots more effort)
    6     * A trac report will produce a list of tickets in this category - https://twistedmatrix.com/trac/report/16
    7   1. Deferred cancellation
    8     * Ultimately the vast majority of Twisted-provided APIs that return a `Deferred` should implement cancellation logic rather than relying on the fallback behavior provided by `Deferred` itself.
    9     * This is a very large number of ''mostly'' small, self-contained tasks.
    10     * Potentially a GSoC project or OPW project instead of a Fellowship project (lends itself well to beginners)
    11     * Most tickets for this work have not yet been created
    121  1. Deploy to new tummy machine (ASAP)
    132    * Cube (hosting most current infrastructure) will be desupported in the immediate future.
     
    2211       * user accounts
    2312       * dns
     13  1. Tickets already in review before
     14    * Many tickets have had some work done on them but have not yet been completed.  These tickets represent a large amount of invested effort that has yet not yielded any benefits.
     15    * As such, completing them may result in proportionally more return for effort.
     16    * Some judgement needs to be applied in selecting tickets from this category.  Just because effort has been invested does not necessarily mean the tickets are particularly valuable to resolve.
     17    * Some tickets are stalled or abandoned because they are really, really hard (and so probably require lots and lots more effort)
     18    * A trac report will produce a list of tickets in this category - https://twistedmatrix.com/trac/report/16
     19  1. Deferred cancellation
     20    * Ultimately the vast majority of Twisted-provided APIs that return a `Deferred` should implement cancellation logic rather than relying on the fallback behavior provided by `Deferred` itself.
     21    * This is a very large number of ''mostly'' small, self-contained tasks.
     22    * Potentially a GSoC project or OPW project instead of a Fellowship project (lends itself well to beginners)
     23    * Most tickets for this work have not yet been created
    2424  1. Attempt trac upgrade in a way that allows switching back to current version
    2525    * Basically, set up a testing deployment/environment where trac changes can be tested before going live