pear:pear2:migration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
pear:pear2:migration [2011/05/02 23:49] – clockwerxpear:pear2:migration [2011/05/02 23:52] – clockwerx
Line 6: Line 6:
  
 ===== How? ===== ===== How? =====
-Two options:+Multiple options:
   * Sudden cutover - redirect traffic to pear2.php.net; use the migration pain to inspire contributions and improved functionality.   * Sudden cutover - redirect traffic to pear2.php.net; use the migration pain to inspire contributions and improved functionality.
   * Phased migration - component by component swap processes such as PEPR over to feed into pear2; co-brand the pear.php.net front page experience; end of life unsupported packages.   * Phased migration - component by component swap processes such as PEPR over to feed into pear2; co-brand the pear.php.net front page experience; end of life unsupported packages.
Line 12: Line 12:
  
 ===== Sudden cutover ===== ===== Sudden cutover =====
-Benefits:+==== Benefits ====
   * Immediately achieves PEAR2 launch   * Immediately achieves PEAR2 launch
  
-Sequence/Tasks:+==== Sequence/Tasks ==== 
   * Move pear.php.net to old.pear.php.net   * Move pear.php.net to old.pear.php.net
   * Replace pear.php.net with pear2.php.net   * Replace pear.php.net with pear2.php.net
Line 21: Line 22:
   * Add a prominent link to the old site in the header   * Add a prominent link to the old site in the header
  
-Risks:+==== Risks ==== 
   * Represents a fork - potential for high attrition rate of developers   * Represents a fork - potential for high attrition rate of developers
   * Reduces capabilities (bug tracking, pepr)   * Reduces capabilities (bug tracking, pepr)
   * Requires high pressure/time critical investment to deal with any regression (broken main pear channel if not done right); coupled with existing community apathy   * Requires high pressure/time critical investment to deal with any regression (broken main pear channel if not done right); coupled with existing community apathy
  
-People/Roles - see https://github.com/pear2+==== People/Roles  ==== 
 +See https://github.com/pear2
   * Michael Gauthier - Design, Project Sponsor   * Michael Gauthier - Design, Project Sponsor
   * Brett Bieber - Developer (pear2 site), stakeholder   * Brett Bieber - Developer (pear2 site), stakeholder
Line 33: Line 36:
  
 ===== Phased migration ===== ===== Phased migration =====
-Benefits:+==== Benefits ==== 
   * Achieves PEAR2 launch   * Achieves PEAR2 launch
   * Lower risk than sudden cutover   * Lower risk than sudden cutover
  
-Sequence/Tasks:+==== Sequence/Tasks ====
   * May: Kill off news from pear.php.net((simple release of pear_index)); or replace it with a new pear blog((install wordpress on test.pear.php.net; update pear_index to point at new rss; and write content))   * May: Kill off news from pear.php.net((simple release of pear_index)); or replace it with a new pear blog((install wordpress on test.pear.php.net; update pear_index to point at new rss; and write content))
   * May: Tweak PEPR to be a new package process for pear2   * May: Tweak PEPR to be a new package process for pear2
Line 44: Line 47:
   * August: Improve the awareness of pyrus - from screencasts to tutorials to shiny visual lures.   * August: Improve the awareness of pyrus - from screencasts to tutorials to shiny visual lures.
  
-Risks:+==== Risks ====
   * We have declining interaction from contributors, this requires coordination of multiple senior pear developers with karma. Historically, we've tried parts of this but have not achieved consensus or consistent effort.   * We have declining interaction from contributors, this requires coordination of multiple senior pear developers with karma. Historically, we've tried parts of this but have not achieved consensus or consistent effort.
  
-People/Roles+==== People/Roles ====
   * Daniel O'Connor, sponsor, developer pear1 site, pepr; archive   * Daniel O'Connor, sponsor, developer pear1 site, pepr; archive
   * Helgi Þormar Þorbjörnsson, PEAR/Pyrus channel migration functionality   * Helgi Þormar Þorbjörnsson, PEAR/Pyrus channel migration functionality
Line 56: Line 59:
  
 ===== PEAR channel aggregator ===== ===== PEAR channel aggregator =====
-Benefits:+==== Benefits  ====
   * Cleanly separates 'channel technology' from 'packages repository'   * Cleanly separates 'channel technology' from 'packages repository'
   * Integrates with the wider community   * Integrates with the wider community
  
-Sequence/Tasks:+==== Sequence/Tasks ====
   * Write/Contribute to a [[http://blog.stuartherbert.com/php/2011/04/09/gathering-requirements-for-a-pear-channel-aggregator/|pear channel aggregator]] - possibly in progress   * Write/Contribute to a [[http://blog.stuartherbert.com/php/2011/04/09/gathering-requirements-for-a-pear-channel-aggregator/|pear channel aggregator]] - possibly in progress
   * Make pear2 a prominent channel in the aggregator   * Make pear2 a prominent channel in the aggregator
Line 66: Line 69:
   * Update the pear installer to be aware of the channel aggregator by default, rather than pear.php.net   * Update the pear installer to be aware of the channel aggregator by default, rather than pear.php.net
  
-Risks:+==== Risks ====
   * Relies on external parties   * Relies on external parties
  
-People/Roles+==== People/Roles ====
   * Stuart Herbert - project sponsor, implementor pear channel aggregator   * Stuart Herbert - project sponsor, implementor pear channel aggregator
   * ???   * ???
pear/pear2/migration.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools