Community-Driven Development -The Change Review Board

1. Community-Driven Development -The Change Review Board Climate Data Assimilation Weather Robert Ferraro ESMF Community Meeting May 23, 2006 Robert.Ferraro@JPL.NASA.GOV

2. Outline • What is the ESMF Change Review Board? • How does it function? • How can you contribute?

3. ESMF Change Review Board • Established to provide user community guidance to the continuing development of ESMF functionality • Sets the schedule and expectations for future functionality enhancements in ESMF internal and public distributions • Based on user community and stakeholder input • Constrained by available developer resources • Updated quarterly to reflect current realities • Reviews and approves internal releases to assure that adequate alpha testing has been completed • Reviews and approves public releases to assure that adequate beta testing has been completed

4. The Change Review Board Process • Gather community and stakeholder input • Special joint CRB/JST telecon prior to each CRB meeting • Ad-hoc consultation by CRB members with their respective communities and stakeholders • Meet quarterly to review and update the development schedule • Review and approve (sometimes with adjustments) the next internal release • Review community inputs, and add development tasks to the schedule based on this input • Adjust the future release schedule based on current realities and changing priorities • Publish the updated schedule on the ESMF CRB web page • http://www.esmf.ucar.edu/main_site/esmf_crb.html • OrNavigate from the ESMF main page via the “Management” sidebar link

5. The Development Schedule • This is the list of all tasks that the CRB tracks and schedules • The Schedule plans 3 internal releases into the future May not be stable Beta testers are invited to hammer away! Tasks scheduled for this release The release will be delayed if this task is not completed This is the stable, beta tested release It includes all prior internally released and beta tested functionality If this task is not done in time, it will be deferred to the next release This functionality is being contributed by someone outside of the core development team It may or may not get done in time for the scheduled release

6. Scheduling Tasks • Why are there “unscheduled” tasks on the schedule? • The CRB defines development tasks for every suggested enhancement to the ESMF implementation • The core development team estimates the resources required to accomplish each task • The CRB places tasks into the next 3 internal releases based on priorities determined by the CRB, and the available developer resources • The lower priority tasks that don’t fit are carried as “unscheduled”

7. The CRB Membership Robert Ferraro, ChairNASA Jet Propulsion Laboratoryrobert.ferraro@jpl.nasa.govMark IredellNOAA National Centers for Environmental Predictionmark.iredell@noaa.govAlan WallcraftNaval Research Laboratorybei_chief_scientist@nrlssc.navy.milThomas CluneNASA Goddard Space Flight Centerthomas.l.clune@nasa.govChris HillMassachusetts Institute of Technologycnh@plume.mit.eduMariana VertensteinNational Center for Atmospheric Researchmvertens@ucar.eduAtanas TrayanovNASA Goddard Space Flight Centertrayanov@janus.gsfc.nasa.govCecelia DeLuca, ex officioNational Center for Atmospheric Researchcdeluca@ucar.edu • Members are appointed by the ESMF Execute Board to 1 year renewable terms • Members represent the user community, not just their own institutions or agencies

8. How You Can Influence The Process • Join a joint CRB/JST Telecon • The telecon is announced on the JST email loop • CRB members attend to listen to users’ input • User priorities • Suggestions for new or modified functionality • Contact a CRB member directly