Remove core ppl from lead contributors

2 files changed, 0 insertions, 99 deletions

diff --git a/railties/doc/guides/html/2_3_release_notes.html b/railties/doc/guides/html/2_3_release_notes.html
index 07e825ca99..29157d0154 100644
--- a/railties/doc/guides/html/2_3_release_notes.html
+++ b/railties/doc/guides/html/2_3_release_notes.html
@@ -281,13 +281,6 @@ Using the <tt>ParamsParser</tt> middleware preprocesses any XML, JSON, or YAML r
 </ul></div>

 <h3 id="_renewed_support_for_rails_engines">1.2. Renewed Support for Rails Engines</h3>

 <div class="paragraph"><p>After some versions without an upgrade, Rails 2.3 offers some new features for Rails Engines (Rails applications that can be embedded within other applications). First, routing files in engines are automatically loaded and reloaded now, just like your <tt>routes.rb</tt> file (this also applies to routing files in other plugins). Second, if your plugin has an app folder, then app/[models|controllers|helpers] will automatically be added to the Rails load path. Engines also support adding view paths now.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-</ul></div>

 </div>

 <h2 id="_documentation">2. Documentation</h2>

 <div class="sectionbody">

@@ -476,23 +469,11 @@ render <span style="color: #FF0000">'other_controller/action'</span>
 render <span style="color: #FF0000">'show'</span>

 render <span style="color: #990000">:</span>show</tt></pre></div></div>

 <div class="paragraph"><p>Rails chooses between file, template, and action depending on whether there is a leading slash, an embedded slash, or no slash at all in what&#8217;s to be rendered. Note that you can also use a symbol instead of a string when rendering an action. Other rendering styles (<tt>:inline, :text, :update, :nothing, :json, :xml, :js</tt>) still require an explicit option.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://m.onkey.org/">Pratik Naik</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_application_controller_renamed">4.2. Application Controller Renamed</h3>

 <div class="paragraph"><p>If you&#8217;re one of the people who has always been bothered by the special-case naming of <tt>application.rb</tt>, rejoice! It&#8217;s been reworked to be application_controller.rb in Rails 2.3. In addition, there&#8217;s a new rake task, <tt>rake rails:update:application_controller</tt> to do this automatically for you - and it will be run as part of the normal <tt>rake rails:update</tt> process.</p></div>

 <div class="ulist"><ul>

 <li>

 <p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-<li>

-<p>

 More Information:

 </p>

 <div class="ulist"><ul>

@@ -514,13 +495,6 @@ More Information:
 <div class="paragraph"><p>Lead Contributors: <a href="http://blog.hungrymachine.com/">Aaron Batalion</a> and <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a></p></div>

 <h3 id="_rack_based_lazy_loaded_sessions">4.4. Rack-based Lazy-loaded Sessions</h3>

 <div class="paragraph"><p>A big change pushed the underpinnings of Action Controller session storage down to the Rack level. This involved a good deal of work in the code, though it should be completely transparent to your Rails applications (as a bonus, some icky patches around the old CGI session handler got removed). It&#8217;s still significant, though, for one simple reason: non-Rails Rack applications have access to the same session storage handlers (and therefore the same session) as your Rails applications. In addition, sessions are now lazy-loaded (in line with the loading improvements to the rest of the framework). This means that you no longer need to explicitly disable sessions if you don&#8217;t want them; just don&#8217;t refer to them and they won&#8217;t load.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://joshpeek.com/">Josh Peek</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_mime_type_handling_changes">4.5. MIME Type Handling Changes</h3>

 <div class="paragraph"><p>There are a couple of changes to the code for handling MIME types in Rails. First, <tt>MIME::Type</tt> now implements the <tt>=~</tt> operator, making things much cleaner when you need to check for the presence of a type that has synonyms:</p></div>

 <div class="listingblock">

@@ -538,13 +512,6 @@ Mime<span style="color: #990000">::</span>JS <span style="color: #990000">=~</sp
 <div class="paragraph"><p>Lead Contributor: <a href="http://www.workingwithrails.com/person/5510-seth-fitzsimmons">Seth Fitzsimmons</a></p></div>

 <h3 id="_optimization_of_tt_respond_to_tt">4.6. Optimization of <tt>respond_to</tt></h3>

 <div class="paragraph"><p>In some of the first fruits of the Rails-Merb team merger, Rails 2.3 includes some optimizations for the <tt>respond_to</tt> method, which is of course heavily used in many Rails applications to allow your controller to format results differently based on the MIME type of the incoming request. After eliminating a call to <tt>method_missing</tt> and some profiling and tweaking, we&#8217;re seeing an 8% improvement in the number of requests per second served with a simple <tt>respond_to</tt> that switches between three formats. The best part? No change at all required to the code of your application to take advantage of this speedup.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://yehudakatz.com/">Yehuda Katz</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_improved_caching_performance">4.7. Improved Caching Performance</h3>

 <div class="paragraph"><p>Rails now keeps a per-request local cache of requests, cutting down on unnecessary reads and leading to better site performance. While this work was originally limited to <tt>MemCacheStore</tt>, it is available to any remote store than implements the required methods.</p></div>

 <div class="ulist"><ul>

@@ -598,11 +565,6 @@ http://www.gnu.org/software/src-highlite -->
 <div class="ulist"><ul>

 <li>

 <p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-<li>

-<p>

 More Information: <a href="http://ryandaigle.com/articles/2008/11/20/what-s-new-in-edge-rails-render-stops-being-high-maintenance">What&#8217;s New in Edge Rails: render Stops Being High-Maintenance</a>

 </p>

 </li>

@@ -625,23 +587,11 @@ select_datetime<span style="color: #990000">(</span>DateTime<span style="color:
 <div class="paragraph"><p>Lead Contributor: <a href="http://samoliver.com/">Sam Oliver</a></p></div>

 <h3 id="_assettag_timestamp_caching">5.3. AssetTag Timestamp Caching</h3>

 <div class="paragraph"><p>You&#8217;re likely familiar with Rails' practice of adding timestamps to static asset paths as a "cache buster." This helps ensure that stale copies of things like images and stylesheets don&#8217;t get served out of the user&#8217;s browser cache when you change them on the server. You can now modify this behavior with the <tt>cache_asset_timestamps</tt> configuration option for Action View. If you enable the cache, then Rails will calculate the timestamp once when it first serves an asset, and save that value. This means fewer (expensive) file system calls to serve static assets - but it also means that you can&#8217;t modify any of the assets while the server is running and expect the changes to get picked up by clients.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://joshpeek.com/">Josh Peek</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_asset_hosts_as_objects">5.4. Asset Hosts as Objects</h3>

 <div class="paragraph"><p>Asset hosts get more flexible in edge Rails with the ability to declare an asset host as a specific object that responds to a call. This allows you to to implement any complex logic you need in your asset hosting.</p></div>

 <div class="ulist"><ul>

 <li>

 <p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-<li>

-<p>

 More Information: <a href="http://github.com/dhh/asset-hosting-with-minimum-ssl/tree/master">asset-hosting-with-minimum-ssl</a>

 </p>

 </li>

@@ -673,18 +623,12 @@ The <tt>autolink</tt> helper has been refactored to make it a bit less messy and
 <div class="ulist"><ul>

 <li>

 <p>

-Lead Contributor: <a href="http://m.onkey.org/">Pratik Naik</a>

-</p>

-</li>

-<li>

-<p>

 More Information: <a href="http://ozmm.org/posts/try.html">try()</a>.

 </p>

 </li>

 </ul></div>

 <h3 id="_object_tap_backport">6.2. Object#tap Backport</h3>

 <div class="paragraph"><p><tt>Object#tap</tt> is an addition to "Ruby 1.9":http://www.ruby-doc.org/core-1.9/classes/Object.html#M000309 and 1.8.7 that is similar to the <tt>returning</tt> method that Rails has had for a while: it yields to a block, and then returns the object that was yielded. Rails now includes code to make this available under older versions of Ruby as well.</p></div>

-<div class="paragraph"><p>Lead Contributor: <a href="http://bitsweat.net/">Jeremy Kemper</a></p></div>

 <h3 id="_fractional_seconds_for_timewithzone">6.3. Fractional seconds for TimeWithZone</h3>

 <div class="paragraph"><p>The <tt>Time</tt> and <tt>TimeWithZone</tt> classes include an <tt>xmlschema</tt> method to return the time in an XML-friendly string. As of Rails 2.3, <tt>TimeWithZone</tt> supports the same argument for specifying the number of digits in the fractional second part of the returned string that <tt>Time</tt> does:</p></div>

 <div class="listingblock">

@@ -697,7 +641,6 @@ http://www.gnu.org/software/src-highlite -->
 <div class="paragraph"><p>Lead Contributor: <a href="http://www.workingwithrails.com/person/13536-nicholas-dainty">Nicholas Dainty</a></p></div>

 <h3 id="_json_key_quoting">6.4. JSON Key Quoting</h3>

 <div class="paragraph"><p>If you look up the spec on the "json.org" site, you&#8217;ll discover that all keys in a JSON structure must be strings, and they must be quoted with double quotes. Starting with Rails 2.3, we doe the right thing here, even with numeric keys.</p></div>

-<div class="paragraph"><p>Lead Contributor: <a href="http://www.koziarski.net/">Michael Koziarski</a></p></div>

 <h3 id="_other_active_support_changes">6.5. Other Active Support Changes</h3>

 <div class="ulist"><ul>

 <li>

@@ -735,11 +678,6 @@ Active Support&#8217;s <tt>from_xml</tt> no longer depends on XmlSimple. Instead
 <div class="ulist"><ul>

 <li>

 <p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-<li>

-<p>

 More Information:

 </p>

 <div class="ulist"><ul>

@@ -789,23 +727,9 @@ More Info:<a href="http://m.onkey.org/2008/12/4/rails-templates">Rails templates
 </ul></div>

 <h3 id="_quieter_backtraces">7.3. Quieter Backtraces</h3>

 <div class="paragraph"><p>Building on Thoughtbot&#8217;s "Quiet Backtrace":http://www.thoughtbot.com/projects/quietbacktrace plugin, which allows you to selectively remove lines from Test::Unit backtraces, Rails 2.3 implements <tt>ActiveSupport::BacktraceCleaner</tt> and <tt>Rails::BacktraceCleaner</tt> in core. This supports both filters (to perform regex-based substitutions on backtrace lines) and silencers (to remove backtrace lines entirely). Rails automatically adds silencers to get rid of the most common noise in a new application, and builds a <tt>config/backtrace_silencers.rb</tt> file to hold your own additions. This feature also enables prettier printing from any gem in the backtrace.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributor: <a href="http://www.loudthinking.com/">David Heinemeier Hansson</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_faster_boot_time_in_development_mode_with_lazy_loading_autoload">7.4. Faster Boot Time in Development Mode with Lazy Loading/Autoload</h3>

 <div class="paragraph"><p>Quite a bit of work was done to make sure that bits of Rails (and its dependencies) are only brought into memory when they&#8217;re actually needed. The core frameworks - Active Support, Active Record, Action Controller, Action Mailer and Action View - are now using <tt>autoload</tt> to lazy-load their individual classes. This work should help keep the memory footprint down and improve overall Rails performance.</p></div>

 <div class="paragraph"><p>You can also specify (by using the new <tt>preload_frameworks</tt> option) whether the core libraries should be autoloaded at startup. This defaults to <tt>false</tt> so that Rails autoloads itself piece-by-piece, but there are some circumstances where you still need to bring in everything at once - Passenger and JRuby both want to see all of Rails loaded together.</p></div>

-<div class="ulist"><ul>

-<li>

-<p>

-Lead Contributors: <a href="http://bitsweat.net/">Jeremy Kemper</a> and <a href="http://joshpeek.com/">Josh Peek</a>

-</p>

-</li>

-</ul></div>

 <h3 id="_other_railties_changes">7.5. Other Railties Changes</h3>

 <div class="ulist"><ul>

 <li>

diff --git a/railties/doc/guides/source/2_3_release_notes.txt b/railties/doc/guides/source/2_3_release_notes.txt
index 08d591d149..035f28bca0 100644
--- a/railties/doc/guides/source/2_3_release_notes.txt
+++ b/railties/doc/guides/source/2_3_release_notes.txt
@@ -43,8 +43,6 @@ Here's a summary of the rack-related changes:
 
 After some versions without an upgrade, Rails 2.3 offers some new features for Rails Engines (Rails applications that can be embedded within other applications). First, routing files in engines are automatically loaded and reloaded now, just like your +routes.rb+ file (this also applies to routing files in other plugins). Second, if your plugin has an app folder, then app/[models|controllers|helpers] will automatically be added to the Rails load path. Engines also support adding view paths now.
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson] 
-
 == Documentation
 
 The link:http://guides.rubyonrails.org/[Ruby on Rails guides] project has published several additional guides for Rails 2.3. In addition, a link:http://guides.rails.info/[separate site] maintains updated copies of the Guides for Edge Rails. Other documentation efforts include a relaunch of the link:http://newwiki.rubyonrails.org/[Rails wiki] and early planning for a Rails Book.
@@ -172,13 +170,10 @@ render :show
 -------------------------------------------------------
 Rails chooses between file, template, and action depending on whether there is a leading slash, an embedded slash, or no slash at all in what's to be rendered. Note that you can also use a symbol instead of a string when rendering an action. Other rendering styles (+:inline, :text, :update, :nothing, :json, :xml, :js+) still require an explicit option.
 
-* Lead Contributor: link:http://m.onkey.org/[Pratik Naik]
-
 === Application Controller Renamed
 
 If you're one of the people who has always been bothered by the special-case naming of +application.rb+, rejoice! It's been reworked to be application_controller.rb in Rails 2.3. In addition, there's a new rake task, +rake rails:update:application_controller+ to do this automatically for you - and it will be run as part of the normal +rake rails:update+ process. 
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson]
 * More Information:
  - link:http://afreshcup.com/2008/11/17/rails-2x-the-death-of-applicationrb/[The Death of Application.rb]    
  - link:http://ryandaigle.com/articles/2008/11/19/what-s-new-in-edge-rails-application-rb-duality-is-no-more[What's New in Edge Rails: Application.rb Duality is no More]
@@ -193,8 +188,6 @@ Lead Contributors: link:http://blog.hungrymachine.com/[Aaron Batalion] and link:
 
 A big change pushed the underpinnings of Action Controller session storage down to the Rack level. This involved a good deal of work in the code, though it should be completely transparent to your Rails applications (as a bonus, some icky patches around the old CGI session handler got removed). It's still significant, though, for one simple reason: non-Rails Rack applications have access to the same session storage handlers (and therefore the same session) as your Rails applications. In addition, sessions are now lazy-loaded (in line with the loading improvements to the rest of the framework). This means that you no longer need to explicitly disable sessions if you don't want them; just don't refer to them and they won't load.
 
-* Lead Contributor: link:http://joshpeek.com/[Josh Peek]
-
 === MIME Type Handling Changes
 
 There are a couple of changes to the code for handling MIME types in Rails. First, +MIME::Type+ now implements the +=~+ operator, making things much cleaner when you need to check for the presence of a type that has synonyms:
@@ -217,8 +210,6 @@ Lead Contributor: link:http://www.workingwithrails.com/person/5510-seth-fitzsimm
 
 In some of the first fruits of the Rails-Merb team merger, Rails 2.3 includes some optimizations for the +respond_to+ method, which is of course heavily used in many Rails applications to allow your controller to format results differently based on the MIME type of the incoming request. After eliminating a call to +method_missing+ and some profiling and tweaking, we're seeing an 8% improvement in the number of requests per second served with a simple +respond_to+ that switches between three formats. The best part? No change at all required to the code of your application to take advantage of this speedup.
 
-* Lead Contributor: link:http://yehudakatz.com/[Yehuda Katz]
-
 === Improved Caching Performance
 
 Rails now keeps a per-request local cache of requests, cutting down on unnecessary reads and leading to better site performance. While this work was originally limited to +MemCacheStore+, it is available to any remote store than implements the required methods.
@@ -247,7 +238,6 @@ The render method has been getting smarter over the years, and it's even smarter
 <% render @articles %>
 -------------------------------------------------------
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson]
 * More Information: link:http://ryandaigle.com/articles/2008/11/20/what-s-new-in-edge-rails-render-stops-being-high-maintenance[What's New in Edge Rails: render Stops Being High-Maintenance]
 
 === Prompts for Date Select Helpers
@@ -272,13 +262,10 @@ Lead Contributor: link:http://samoliver.com/[Sam Oliver]
 
 You're likely familiar with Rails' practice of adding timestamps to static asset paths as a "cache buster." This helps ensure that stale copies of things like images and stylesheets don't get served out of the user's browser cache when you change them on the server. You can now modify this behavior with the +cache_asset_timestamps+ configuration option for Action View. If you enable the cache, then Rails will calculate the timestamp once when it first serves an asset, and save that value. This means fewer (expensive) file system calls to serve static assets - but it also means that you can't modify any of the assets while the server is running and expect the changes to get picked up by clients.
 
-* Lead Contributor: link:http://joshpeek.com/[Josh Peek]
-
 === Asset Hosts as Objects
 
 Asset hosts get more flexible in edge Rails with the ability to declare an asset host as a specific object that responds to a call. This allows you to to implement any complex logic you need in your asset hosting.
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson]
 * More Information: link:http://github.com/dhh/asset-hosting-with-minimum-ssl/tree/master[asset-hosting-with-minimum-ssl]
 
 === Other Action View Changes
@@ -295,15 +282,12 @@ Active Support has a few interesting changes, including the introduction of +Obj
 
 A lot of folks have adopted the notion of using try() to attempt operations on objects - It's especially helpful in views where you can avoid nil-checking by writing code like +<%= @person.try(:name) %>+. Well, now it's baked right into Rails. As implemented in Rails, it raises +NoMethodError+ on private methods and always returns +nil+ if the object is nil.
 
-* Lead Contributor: link:http://m.onkey.org/[Pratik Naik]
 * More Information: link:http://ozmm.org/posts/try.html[try()]. 
 
 === Object#tap Backport
 
 +Object#tap+ is an addition to "Ruby 1.9":http://www.ruby-doc.org/core-1.9/classes/Object.html#M000309 and 1.8.7 that is similar to the +returning+ method that Rails has had for a while: it yields to a block, and then returns the object that was yielded. Rails now includes code to make this available under older versions of Ruby as well.
 
-Lead Contributor: link:http://bitsweat.net/[Jeremy Kemper]
-
 === Fractional seconds for TimeWithZone
 
 The +Time+ and +TimeWithZone+ classes include an +xmlschema+ method to return the time in an XML-friendly string. As of Rails 2.3, +TimeWithZone+ supports the same argument for specifying the number of digits in the fractional second part of the returned string that +Time+ does:
@@ -320,8 +304,6 @@ Lead Contributor: link:http://www.workingwithrails.com/person/13536-nicholas-dai
 
 If you look up the spec on the "json.org" site, you'll discover that all keys in a JSON structure must be strings, and they must be quoted with double quotes. Starting with Rails 2.3, we doe the right thing here, even with numeric keys.
 
-Lead Contributor: link:http://www.koziarski.net/[Michael Koziarski]
-
 === Other Active Support Changes
 
 * You can use +Enumerable#none?+ to check that none of the elements match the supplied block.
@@ -338,7 +320,6 @@ In addition to the Rack changes covered above, Railties (the core code of Rails
 
 Rails Metal is a new mechanism that provides superfast endpoints inside of your Rails applications. Metal classes bypass routing and Action Controller to give you raw speed (at the cost of all the things in Action Controller, of course). This builds on all of the recent foundation work to make Rails a Rack application with an exposed middleware stack. 
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson]
 * More Information:
  - link:http://weblog.rubyonrails.org/2008/12/17/introducing-rails-metal[Introducing Rails Metal]
  - link:http://soylentfoo.jnewland.com/articles/2008/12/16/rails-metal-a-micro-framework-with-the-power-of-rails-m[Rails Metal: a micro-framework with the power of Rails]
@@ -363,16 +344,12 @@ This will layer the changes from the template on top of whatever code the projec
 
 Building on Thoughtbot's "Quiet Backtrace":http://www.thoughtbot.com/projects/quietbacktrace plugin, which allows you to selectively remove lines from Test::Unit backtraces, Rails 2.3 implements +ActiveSupport::BacktraceCleaner+ and +Rails::BacktraceCleaner+ in core. This supports both filters (to perform regex-based substitutions on backtrace lines) and silencers (to remove backtrace lines entirely). Rails automatically adds silencers to get rid of the most common noise in a new application, and builds a +config/backtrace_silencers.rb+ file to hold your own additions. This feature also enables prettier printing from any gem in the backtrace.
 
-* Lead Contributor: link:http://www.loudthinking.com/[David Heinemeier Hansson]
-
 === Faster Boot Time in Development Mode with Lazy Loading/Autoload
 
 Quite a bit of work was done to make sure that bits of Rails (and its dependencies) are only brought into memory when they're actually needed. The core frameworks - Active Support, Active Record, Action Controller, Action Mailer and Action View - are now using +autoload+ to lazy-load their individual classes. This work should help keep the memory footprint down and improve overall Rails performance. 
 
 You can also specify (by using the new +preload_frameworks+ option) whether the core libraries should be autoloaded at startup. This defaults to +false+ so that Rails autoloads itself piece-by-piece, but there are some circumstances where you still need to bring in everything at once - Passenger and JRuby both want to see all of Rails loaded together.
 
-* Lead Contributors: link:http://bitsweat.net/[Jeremy Kemper] and link:http://joshpeek.com/[Josh Peek]
-
 === Other Railties Changes
 
 * The instructions for updating a CI server to build Rails have been updated and expanded.