Changes between Initial Version and Version 1 of pds-2010-04

Show
Ignore:
Timestamp:
04/12/10 20:20:19 (4 years ago)
Author:
particle
Comment:

notes from the parrot developer summit meeting

Legend:

Unmodified
Added
Removed
Modified
  • pds-2010-04

    v1 v1  
     1parrot virtual developer summit: 11 april 2010 
     2 
     3* review of the 2.3 release 
     4 
     5  * deprecation policy is better than before. some would prefer opt-in to opt-out 
     6  * need better testing of packages before supported releases 
     7 
     8 
     9* process questions 
     10 
     11good: 
     12  * shorter deprecation policy. 
     13  * new weekly status meeting time works well. 
     14  * gsoc works well for getting new parrot contributors. 
     15  * weekly roadmap review is helpful, keep it going. 
     16 
     17bad: we set too many weekly priorities. 
     18fix: 
     19  * make weekly priorities specific tasks 
     20  * completable by 1-2 people in a week 
     21  * one won't be set unless 2+ people have volunteered to work on it 
     22  * know this fix works if we complete a higher percentage of our weekly priorities 
     23 
     24bad: milestone priorities are hard to manage far out in time 
     25fix: 
     26  * stop the busy work of maintaining longer-term roadmap items 
     27  * use a long-term roadmap for big plans, not small tasks. 
     28  * every week, review weekly, monthly, and quarterly priorities. 
     29  * schedule people on weekly priorities. 
     30  * know this fix works if we complete a higher percentage of our weekly priorities, and spend less time maintaining roadmap items 
     31 
     32the team has committed to these fixes for the 2.6 quarterly cycle. 
     33 
     34bad: stale tickets in trac 
     35fix: 
     36  * reduce ticket count by periodic focused triage/fix sessions 
     37  * use ticket system only for bugs, put wishlist items on wiki 
     38  * open separate tickets for testing bugs and their fixes, close original bug report with pointer to new ticket 
     39  * put wishlist items on wiki page 
     40  * define stale tickets as 'no comments in 6 months', make trac report available 
     41{LOST THE THREAD HERE, NEED BETTER SUMMARY OF FIX AND SUCCESS CRITERIA} 
     42 
     43 
     44* error reporting (line numbers) 
     45 
     46  * high priority for rakudo 
     47  * testing framework needed 
     48  * in progress: cotto, chromatic, tene have worked or will work on this 
     49 
     50 
     51* block exit handlers, TT#1523 
     52 
     53  * need more info from rakudo team 
     54  * may require pdd/spec work 
     55  * in progress: allison, whiteknight working on it, will contact jnthn 
     56 
     57 
     58* lexical implementation 
     59 
     60  * need requirements from rakudo 
     61 
     62 
     63* performance/memory usage in general 
     64 
     65  * list of possible performance improvements at 
     66  http://trac.parrot.org/parrot/wiki/PerformanceImprovements 
     67  * fixing vtable overrides and sweep free gc are monthly-branch-sized tasks 
     68  to be scheduled in future parrot weekly meetings 
     69 
     70 
     71* plumage (project priority, how to boost resources, how far along is it? what does it need?) 
     72 
     73  * project priority for parrot 
     74  * not enough developers working on it 
     75  * will not add to parrot core, will keep as separate project 
     76  * fix: seek out funders, which may unblock developers 
     77 
     78 
     79* NFG strings 
     80 
     81  * gsoc proposal in 
     82  * hope it's funded, discuss later if not 
     83 
     84 
     85* concurrency 
     86 
     87  * gsoc proposal in 
     88  * threads currently work, but are limited 
     89  * not a pre-rakudo * priority 
     90  * will focus on this after gc has been addressed 
     91 
     92 
     93* prototype-based OO 
     94 
     95  * PMC and Class unification will not be extensive 
     96  * other class models will not be excluded 
     97  * PMCProxy will go away 
     98  * will add Prototype PMC to parrot core and notify rakudo team 
     99 
     100 
     101* HLL interop, TT#556, TT#557, TT#558 
     102 
     103  * sorear working on an implementation 
     104  * may require spec changes based on work in progress 
     105  * meeting with stakeholders (sorear, tene, pmichaud, japhb) would be beneficial 
     106 
     107 
     108* moving the build system off Perl5 
     109 
     110  * not urgent, just general long-term direction 
     111  * need smaller tasks, wiki page seems a good place 
     112 
     113 
     114* chmod files 
     115* tar library 
     116* zlib library 
     117 
     118  * good features, add to wishlist 
     119 
     120 
     121* git conversion 
     122 
     123  * not planned during this quarter 
     124  * revisit at next quarterly meeting 
     125 
     126 
     127* security subsystem 
     128 
     129  * parrot priority, largest blocker for PL/Parrot 
     130  * not before 2.9 
     131  * specific tasks can be completed sooner 
     132  * coordinate with PL/Parrot team 
     133 
     134 
     135* runcore support, can we trim the list? 
     136 
     137  * discuss in upcoming weekly status meeting, to be deprecated at 2.3 
     138 
     139 
     140* next big task: GC/Concurrency/Lorito/? 
     141 
     142  * garbage collection is the next big task 
     143  * possibly followed by: concurrency, lorito, jit 
     144 
     145 
     146* make sure gsoc students aren't blocked 
     147  * use weekly tasks to support them 
     148  * have them attend weekly status meeting 
     149