pear:pear2:migration

Differences

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

Link to this comparison view

Next revision		Previous revision
pear:pear2:migration [2011/05/02 23:28] – created clockwerxpear:pear2:migration [2017/09/22 13:28] (current) – external edit 127.0.0.1
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.
 +  * Change of focus - pear channel index
  
 +===== Sudden cutover =====
 +==== Benefits ====
 +  * Immediately achieves PEAR2 launch
  
-===== Phased: Timeline & Tasks ===== +==== Sequence/Tasks ====
-  * 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)). +
-  * Tweak PEPR to be a new package process for pear2 +
-  * Enable both the PEAR and pyrus installer to understand "I have migrated to another channel" +
-    * Kill old packages from pear.php.net. With fire. Put them in an archive channel or other location+
  
 +  * Move pear.php.net to old.pear.php.net
 +  * Replace pear.php.net with pear2.php.net
 +  * Create rewrite rules for old content to direct inbound traffic from 404 pages on pear.php.net to old.pear.php.net
 +  * Add a prominent link to the old site in the header
  
 +==== Risks ====
 +
 +  * Represents a fork - potential for high attrition rate of developers
 +  * 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
 +
 +==== People/Roles  ====
 +See https://github.com/pear2
 +  * Michael Gauthier - Design, Project Sponsor
 +  * Brett Bieber - Developer (pear2 site), stakeholder
 +  * Helgi Þormar Þorbjörnsson - Developer pear1 site, rewrite rules, stakeholder
 +  * Community - UAT
 +
 +===== Phased migration =====
 +==== Benefits ==== 
 +  * Achieves PEAR2 launch
 +  * Lower risk than sudden cutover
 +
 +==== 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: Tweak PEPR to be a new package process for pear2
 +  * June: Enable both the PEAR and pyrus installer to understand "I have migrated to another channel"
 +    * July: Kill old packages from pear.php.net. With fire. Put them in an archive channel or other location
 +  * August: Improve the awareness of pyrus - from screencasts to tutorials to shiny visual lures.
 +
 +==== 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.
 +
 +==== People/Roles ====
 +  * Daniel O'Connor, sponsor, developer pear1 site, pepr; archive
 +  * Helgi Þormar Þorbjörnsson, PEAR/Pyrus channel migration functionality
 +  * Michael Gauthier - Design, pyrus awareness
 +  * Brett Bieber - pyrus awareness
 +  * Community - UAT
 +
 +
 +===== PEAR channel aggregator =====
 +==== Benefits  ====
 +  * Cleanly separates 'channel technology' from 'packages repository'
 +  * Integrates with the wider community
 +
 +==== 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
 +  * Make pear2 a prominent channel in the aggregator
 +  * Make pear1 an archive channel in the aggregator
 +  * Update the pear installer to be aware of the channel aggregator by default, rather than pear.php.net
 +
 +==== Risks ====
 +  * Relies on external parties
 +
 +==== People/Roles ====
 +  * Stuart Herbert - project sponsor, implementor pear channel aggregator
 +  * ???
pear/pear2/migration.1304378891.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools