Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: core-commits@hadoop.apache.org
Date: Fri, 21 Aug 2009 10:58:31 -0000
Message-ID: <20090821105831.11383.51101@eos.apache.org>
Subject: [Hadoop Wiki] Update of "BristolHadoopWorkshop" by SteveLoughran

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by SteveLoughran:
http://wiki.apache.org/hadoop/BristolHadoopWorkshop

The comment on the change is:
wrap up

------------------------------------------------------------------------------
  = Bristol Hadoop Workshop, University of Bristol, August 10, 2009 =
  
  This was a little local workshop put together by Simon Metson of Bristol University, and Steve Loughran of HP, to get some of the local Hadoop users in a room and talk about our ongoing work.
+ 
+ == Acknowledgements ==
+ 
+ # Bristol Centre for Nanoscience and Quantum Information [http://www.bristol.ac.uk/nsqi-centre/ NSQI] for the room and other facilities
+ # University of Bristol Particle Physicics group for hosting the workshop
+ # HP Laboratories for the food and coffee
+ # Cloudera for supplying beer at the Highbury Vaults.
+ 
+ == Presentation == 
  
  These presentations were intended to start discussion and thought
  
@@ -271, +280 @@

   # Less testing, reduced quality
  Apparently under [http://community.cloudera.com] - number of messages/JIRA and infer activity, such as [http://community.cloudera.com/reports/47/contributors/ contributors] and [http://community.cloudera.com/reports/47/issues/ popular issues]
   
+ With Yahoo! outsourcing searching to MS, it means that MS can take on a big project that -even if it isn't profitable to MS, can be subsidised by other parts of their business. It ensures Yahoo! continuing survival as an independent company, which is the best state for Hadoop development. It also frees up some Yahoo! datacentres for other projects. Those big datacentres are large, slowly-depreciating assets, and by offloading the indexing to someone else, there is now spare datacentre capacity for Yahoo! to use for other uses, uses that are highly likely to use Hadoop at the back end -because what else would they build a datacentre-scale application on? 
+ 
  At the same time, there are opportunities for people outside Yahoo!
   * more agile deployments
   * more open to contributions from other people, universities etc.
  Of course, this could impact release schedule/quality; needs to be managed well.
- Clearly for Cloudera, this gives them a greater opportunity to position themselves as "the owners of Hadoop", especially if they get more of the core Hadoop people on board. However, Apache do try to add their own management layer to stop handing off full  
+ Clearly for Cloudera, this gives them a greater opportunity to position themselves as "the owners of Hadoop", especially if they get more of the core Hadoop people on board. However, Apache do try to add their own management layer to stop handing off full ownership of a project to outside companies. But the reality is whoever provides the engineering effort owns the project, so any organisation that can provide FTEs can dominate.
  
  What are the increased responsibilities for everyone else involved with Hadoop?
   * Everyone has to test on larger cluster. EC2 may get tested, but it's not enough as it is virtual, and only represents one single site/network config.