pear:group:meetingagenda:20090906
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| pear:group:meetingagenda:20090906 [2009/09/06 07:25] – shupp | pear:group:meetingagenda:20090906 [2009/09/08 13:21] – add link to last meeting gauthierm | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| * Long term | * Long term | ||
| * get active maintainers of quality PEAR1 packages to port them to PEAR2 | * get active maintainers of quality PEAR1 packages to port them to PEAR2 | ||
| + | |||
| + | |||
| ===== Minutes ===== | ===== Minutes ===== | ||
| - | === Unresolved Issues from Last Year === | ||
| - | * Three outstanding RFC's are awaiting Group voting | ||
| - | === Testing and Continuous Integration Server | + | ==== Attendees |
| + | * Brett Bieber ([[saltybeagle]]) | ||
| + | * Mike Gauthier ([[gauthierm]]) | ||
| + | * Chuck Burges ([[ashnazg]]) | ||
| + | * Bill Shupp ([[shupp]]) | ||
| + | * Ken Guest ([[radagast]]) | ||
| + | Chuck called the meeting to order shortly after 14:00 UTC.\\ | ||
| + | Bill logged the IRC content for absent members.\\ | ||
| + | Mike compiled minutes.\\ | ||
| + | |||
| + | ==== Followup from Last Meeting on 2009-08-16 ==== | ||
| + | * See the [[pear: | ||
| + | * Bill got the ' | ||
| + | * Bill created a cron job that puts PEAR package releases on Twitter | ||
| + | * Cron job is in the pearweb/ | ||
| + | * Cron is currently on Bill's laptop | ||
| + | * Bill reports that Digg does not have spare design resources to give to PEAR. | ||
| + | * Chuck reports that Travis granted access for Chuck to the pear account on Github. | ||
| + | * Action Items: | ||
| + | * Bill will check with Brett and/or Christian to see about getting the Twitter cron running on a PEAR server. | ||
| - | * agenda item was mostly skipped as Christian and Daniel are not present | + | ==== Topics ==== |
| - | * QA needs to be emphasized for PEAR | + | |
| - | * phpUnderControl is planned for sg1 for testing with multiple PHP versions | + | |
| - | === Attracting New Developers | + | === SVN Avail === |
| + | * PEAR Group needs to be added to pear in the global_avail file so they can give SVN access to new PEAR developers | ||
| + | * The old PEAR Group and PEAR president currently have access | ||
| + | * Action items: | ||
| + | * Bill will ask Andrei to update the pear line in global_avail to include the group and president | ||
| + | * Chuck sent a patch to pear-group on September 1st to do this, patch just needs committing. | ||
| - | * Community outreach via blogs, social networks, etc was suggested | + | === PEAR Test Server (sg1) === |
| - | * PEAR needs mention on Facebook, Twitter, etc. | + | * The goals for sg1 are at http://wiki.php.net/ |
| - | * Group members' | + | * The new PEAR group has been successfully testing pearweb improvements on test.pear.php.net |
| - | * Group members should post PEAR-related posts to the shared PEAR blog. | + | |
| - | * this will include meeting minutes, vote outcomes, security notices, etc. | + | |
| - | * The website was mentioned as a place where PEAR could improve its appearance to attract new developers. It was suggested that the website should include tutorials and screen-casts for new developers. | + | * Tests will run under separate PHP versions |
| - | * The members of the PEAR group should all use Pyrus and promote | + | * Christian is setting up a phpfarm script |
| - | its use to other developers. | + | * At some point, this will integrate with pUC |
| - | * High-quality packages with active developers will encourage other developers | + | * Daniel' |
| - | * Being friendly, timely and helpful to new developers | + | * Once set up, developers can opt-in to phpUnderControl notifications |
| - | * Being quick to respond to new accounts | + | * Action |
| - | * IRC support is being handled pretty well. | + | * Chuck will start setting up phpUnderControl |
| - | * Action | + | * Mike and Bill will assist Chuck where possible |
| - | * Bill will look into wrangling control of the pear and pear2 Twitter accounts. | + | * Mike will send a message |
| - | * Bill will set up a Twitter account for pearphp | + | |
| - | * Bill will ask if Digg has any design resources | + | |
| - | * David will make sure Group will be given accounts on the PEAR blog | + | |
| - | * Group members will start using Pyrus and tell their developer friends how cool it is. | + | |
| - | === PEAR2 === | + | === Goals for 2009-2010 |
| + | * Attracting new developers is going well | ||
| + | * We have Spreadsheet_Excell_Writer maintainers now! | ||
| + | * New developers need more mentoring to ensure they' | ||
| + | * Action Items: | ||
| + | * Ken will start a wiki page outlining areas where the QA-Group can improve mentoring - " | ||
| + | * Bill will put the PEAR Group goals on a separate page in the wiki | ||
| + | * Mike will review docbook styles for pearweb | ||
| - | * Brett and Greg (cellog) are the only two developers working on PEAR2--they may need some help. | + | === Fakemail === |
| - | * website needs assistance in terms of development and design | + | * PEAR Group unanimously approves its use |
| - | * PEAR2 cannot launch until at least PHP 5.3.1, but the website and bug-tracking infrastructure likely won't be ready by then anyway. | + | * Unit tests should skip if Fakemail is not present |
| - | * Marketing | + | * Action Items: |
| - | * Teaser posts on Pyrus features will increase interest in PEAR2. | + | * Ken will install Fakemail on sg1 |
| - | * Major marketing will be withheld until the stable launch of Pyrus. | + | * Ken will check with Christian to get sg1 shell access |
| - | * Bug Manager | + | |
| - | * a functioning bug tracker is needed before PEAR2 can launch | + | |
| - | * some PHP internals developers want a global bug tracker for all PHP projects | + | |
| - | * PEAR2 developers want to build a stand-alone bug tracking package that could be used for PEAR2 and for other projects. (Bug Manager) | + | |
| - | * either of these goals will take some time | + | |
| - | * Action items | + | |
| - | * Bill will look into assisting Greg with the Bug Manager package | + | |
| - | * Christian | + | |
| - | === Next Meeting | + | === RFCs === |
| + | * Two RFC's were discussed, [[pear: | ||
| + | * Several of the more controversial RFCs are becoming dependencies of the policy and standards RFCs | ||
| + | * The abandoned-alpha-package period is a bit too long (one year). Six months was suggested. | ||
| + | * Group agrees that power to delete an abandoned package should rest with the Group only. | ||
| + | * Mike had several minor comments and fixes which were emailed to pear-group for group review | ||
| + | * Brett was added as a sponsor to the PEAR2 policy so that a current PEAR Group member is a sponsor | ||
| + | * PEAR2 policy regarding including alpha packages in the channel has been superseded by Greg's RFC on versioning | ||
| + | * Group voted to reaffirm the PEAR2 Policies RFC until 45 days following the next Group elections. Votes were +5, 0, 0 | ||
| + | * Group voted to reaffirm the PEAR2 Standards RFC until 45 days following the next Group elections. Votes were +5, 0, 0 | ||
| - | * 2009-09-06 at 14:00 UTC | + | === Next Meeting ==== |
| - | * Action items | + | * PEAR Group is going to meet in two weeks to talk about only RFCs |
| - | * Brett will post to pear-group with a potential new time. Possibly 2-3 hours earlier as Bill doesn' | + | * Next meeting |
pear/group/meetingagenda/20090906.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1