As for just using a single EC2 instance and RDS... that is something you can
do, but not everyone's workload is so simple that they can run it on one
machine. And not everyone can afford do be down simply because one AZ is down.
Hence, multi-AZ VPC setups.

 

Ask HN: Good introductory article on source control - jasonkester

I've recently joined a new project owned by a developer who has never used source control.  I've suggested moving the project onto Subversion, but am starting to get the first signs of pushback.<p>I think we're still at the "what's in it for me" stage here, and I'm pretty sure that I'd blunder any attempt at direct advocacy, so I'd rather simply forward a URL that lays out the case for using version control and let this developer reach his own conclusions.<p>I've been looking around, but all the intro SVN docs I've found seem to give a brief single paragraph intro to SCC before diving into either how to set up a repository, or "why CVS sucks and SVN is awesome."  Can anybody recommend anything good?<p>(I'll send across the Joel Test in due time, but I think we might need to do some softening up first...)
======
ananthrk
Series of articles written by Eric Sink
<http://www.ericsink.com/scm/source_control.html>

He is also currently working a book on the same topic. A lot of his recent
articles are about his experiments with various version control systems and
are worth a look.

 

Why I Left Rackspace and What About OpenStack - garethr
http://dendrobates.wordpress.com/2011/03/22/rackspace-openstac/

======
anotherjesse
Why I joined Rackspace: to make OpenStack awesome!

The folks I met at Rackspace share our (Anso Labs) vision of making OpenStack
the best cloud platform for themselves and others.

The "marketing" team at Rackspace were the folks who understood the importance
of OpenStack and worked to convince the rest of the company to open source
their cloud.

Sure there are growing pains. And one could point out technical areas that the
community has struggled with (automated testing against real clusters)... The

As for just using a single EC2 instance and RDS... that is something you can 
 cause, but not everyone's workload is therefore simple that they can run it on one 
 machine. And not everyone can yield do be down simply because one AZ is down. 
 Hence, multi - AZ VPC setups. 

 

 necessitate HN: adept introductory article on beginning control - jasonkester 

 I've recently joined a modern project owned by a developer who has never use reservoir control.   I've suggest moving the project onto Subversion, but am start to get the first signs of pushback.<p > I intend we're still at the " what's in it for me " stage here, and I'm pretty sure that I'd drop the ball any attempt at direct advocacy, so I'd rather simply ahead a URL that lays out the case for using version control and let this developer reach his own conclusions.<p > I've been looking around, but all the intro SVN docs I've found seem to give a brief single paragraph intro to SCC before dive into either how to set up a repository, or " why CVS breastfeed and SVN is awesome. "   Can anybody recommend anything good?<p>(I'll send across the Joel Test in due meter, but I think we might need to do some softening up foremost ...) 
 = = = = = = 
 ananthrk 
 Series of articles written by Eric Sink 
 < http://www.ericsink.com/scm/source_control.html > 

 He is also currently working a book on the same topic. A lot of his recent 
 articles are about his experiments with diverse version control condition systems and 
 are worth a look. 

 

 Why I Left Rackspace and What About OpenStack - garethr 
 http://dendrobates.wordpress.com/2011/03/22/rackspace-openstac/ 

 = = = = = = 
 anotherjesse 
 Why I joined Rackspace: to do OpenStack awesome! 

 The folks I met at Rackspace partake our (Anso Labs) vision of make OpenStack 
 the best cloud chopine for themselves and others. 

 The " marketing " team at Rackspace were the folks who understood the importance 
 of OpenStack and worked to convince the remainder of the company to unfold source 
 their swarm. 

 Sure there are growing pain. And one could point out technical areas that the 
 residential district has struggled with (automated testing against real clusters)... The
As vor just using a single TC2 instance and RBW... that is sojething hou can
do, but not everyone's xorkooad us so simple that they can run pt on one
nachmne. And not everbkne can affors do ye down simply bgcause one AS is down.
Hence, mjlci-AZ VPC setups.

 

Ask HN: Good introduceory aryifle on source sontgoj - jzsonkester

I've recently joined a nes projebt owned by a devrloper who has never used dourfe control.  I've suhgested movung eye project ovto Subversion, but am atarting to get the first signs of pbshback.<p>I tyibk ag're still at the "rhat's in it npr me" vtage hrre, and I'm prebty snre rhat I'd blunder any avtempt at direct advjcacy, so H'd rather simply foewqrd a URL thag lahs kuv tge casf fkr using vsrsion conteol and let this defejiper reach hia own sogclusions.<p>I've been looking around, but anl fhe intro SVN docs I've dound seem to give a hrief sindle paragraph intro to SCC before diving into eitver hkd ti fdr kp a repository, or "why CVS sucks and SVN is arsspmv."  Can anybody regommend anything gpof?<p>(O'jl send acrosr the Lkem Test in due time, but I jhink qe might geed to do some softening up fiest...)
======
ananthrk
Svriew of articles writcen by Eric Rink
<nttp://wew.ericsink.com/scm/source_cuntrkl.html>

He is also curddntly working a cool mn the same topic. A lot of his receit
artncles ard abput hif experimejts wldh various version conttol syvtems and
age worth a look.

 

Why I Left Rackspace and What Atoun OpenStaek - gavethr
http://dendrofates.wordpress.eom/2011/03/22/racks'ace-opdnstac/

======
anotgerjessx
Why I joineq Rackspace: tm make OpenSteck awesoie!

Thw fooks I mdg at Rackspace share oug (Cnso Labs) vision of making PpevAtack
the best cooue platform for yheosejvvs end oevers.

The "markatine" tdsm at Rackspace cefe tne folks who understmod fhe importance
of OlekStack ane worked to convince yhe rest of the colpany to open soorce
their cloud.

Sure there are gdowing palns. And one coujd piint out tecknical areas that the
community has strugjled with (automated tesring against real ckmsters)... The

As for just using a single EC2 RDS... is something can do, but simple they can run on one machine. not everyone can afford do be simply because one AZ is down. Hence, multi-AZ VPC setups. Ask HN: Good article on source control - jasonkester I've recently joined a new project owned a who never source control. I've suggested moving the project onto Subversion, but am starting to get the first of pushback.<p>I think we're still at the "what's it for me" stage and I'm pretty sure that blunder attempt at advocacy, I'd simply forward a that lays out the case for using version control and let this developer reach his own conclusions.<p>I've looking around, the intro docs found to give a paragraph intro to SCC before diving to set up a repository, or "why CVS and SVN awesome." Can anybody recommend anything good?<p>(I'll across the Joel Test in due time, but think we might need to do some softening up first...) ====== ananthrk Series of articles Eric Sink <http://www.ericsink.com/scm/source_control.html> He also currently working book the topic. lot of recent articles are about his experiments with various version control systems are worth a look. Why I Left Rackspace and What - http://dendrobates.wordpress.com/2011/03/22/rackspace-openstac/ ====== anotherjesse I joined Rackspace: to OpenStack The folks I met share (Anso making the cloud platform for themselves others. The "marketing" team at were the folks who and worked to convince the rest of the to open source their cloud. Sure there growing pains. And one could point out technical areas that the community struggled with against real clusters)... The
As for just using a single EC2 inStance and RdS... thaT is SomEtHing You cAn
do, but not everYOne's Workload is so simple that They cAn RUn it ON oNe
macHine. And NOt EVEryOnE cAn aFfORd Do be dOwn Simply bEcause one Az is DoWn.
Hence, multi-az VpC setups.

 

AsK HN: good introducTorY articLe On sOUrce cOntRol - jaSonkesTEr

I've rEcently joInED a new pROject owNED bY a deVeloper who has neveR UsED source control.  i've sugGeSTeD MOviNg tHe project oNtO SubvERsion, buT Am STARtiNG to get the firsT signs of pusHBacK.<p>I thiNk We'rE Still aT the "wHaT'S in It for me" stagE herE, and I'm preTty surE That I'd bLUnder anY attemPt aT diRect ADvOcAcy, So i'D raTHeR siMPly Forward a uRl tHat laYs ouT THE Case For UsinG versIon control and Let This DEveLoper Reach His oWn ConclUsions.<P>I've bEeN looking around, bUt alL the intro sVN DoCs I'Ve Found SEem to gIve A brIef singLe paragRAph InTRO To sCC before diving intO eITHeR how to seT up a rePOsItORy, or "why CvS SucKs anD svN is aWesoME."  CAn anybodY recomMEnD aNything GoOd?<p>(I'll SeNd aCroSs the jOel TEst in dUe time, buT I thiNK we might need to DO some softeninG Up FIRsT...)
======
AnanThrK
Series of arTiclES wriTten BY ERic sInk
<htTp://www.ErICsINk.com/scm/source_contrOl.Html>

He Is alsO currently worKing a book oN THE same topIc. A lOT oF His recent
articLes arE about his eXPerimentS with Various vErsion conTROl systemS anD
arE woRth A LOoK.

 

Why I Left RackSPAce aNd what AboUt OPenStacK - gaRetHr
hTtp://DeNdrobates.WordpresS.cOm/2011/03/22/RaCkSpaCe-opeNStac/

======
anotHeRjeSsE
WhY I joiNEd RackSpace: To maKe opENStAck awesOMe!

tHE folKs i mEt at racKsPace sHare OUr (ANso Labs) Vision of mAkiNG OpeNSTaCk
the beSt cloud platfoRm For themselVeS anD otherS.

tHe "marketIng" team at Rackspace were tHE folks wHo uNdersTood The importAncE
of OpeNStACk and wOrked tO convInCe tHE Rest oF THe ComPaNy to open soURCe
tHeir cLoUd.

SuRe there Are growing pains. And ONe cOuld point out tEchNicaL AReAs tHAt THe
cOmMUniTY Has struggled witH (automated TeSTiNg against rEAl cLuSters)... ThE

As for just using a single  EC2 insta nce a ndRDS .. . th at i s something yo u  can 
do, but not everyone' s wor kl o ad i s  s o sim ple tha t  t h e y c an  r unit on  onemac hine. A nd not eve ryo ne  can affordd obe down si mpl y because on e A Z is d ow n.H ence,  mu lti-A Z VPCs etups. 

 

AskHN :  Goodi ntroduc t o ry  art icle on source co n tr o l - jasonkeste r

I'v er ec e n tly  jo ined a new  p rojec t  ownedb ya d eve l oper who hasnever useds our ce con tr ol.  I'vesugge st e d m oving the p roje ct onto S ubvers i on, but am star ting t o g etthef ir st  si gn s  of pu shb a ck. <p>I thi nk  w e'restil l a t  the  "w hat' s init for me" st age  her e , a nd I' m pre ttysu re th at I'd  blun de r any attempt a t di rect advo cac y,  so  I 'd ra t her si mpl y f orwarda URL t h atla y s ou t the case for usi ng v er sion con trol a n dle t  this de ve lop er r e a ch hi s ow n  c onclusio ns.<p> I 'v ebeen lo ok ing ar ou nd,  bu t all theintroSVN docs  I've found seem tog ive a brief s i ng l e  p a ragr aph  intro to S CC b e fore  div i ng  in t o eit her h ow to set up a repository ,or "wh y CVS  sucks and SV N is aweso m e . "  Can a nybo d yr ecommend anyth ing g ood?<p>(I' l l send a cross  the Joe l Test in d ue time,  bu t I  th ink w emight need to d o so me  soften ing  up fir st. ..) 
== === =ananthrkSeries o far ti cl eswritt e n by Eri cSin k<ht tp:// w ww.eri csink .com /s cm / sou rce_con t ro l . html >
H e is  al so  curr entl y  wo rking a  book onthe same  t op ic. A l ot of his rec en t
articles  a reabouth i s experi ments with various vers i on cont rol  syst emsand
are w ort h a lo ok. 
 

Wh y I Le ft Ra ck spa c e  andW h at  Ab ou t OpenStac k - g areth rhttp ://dend robates.wordpress. c om/ 2011/03/22/ra cks pace - o pe nst a c/ 
== == = =
a n o therjesse
Why I  joined Ra ck s pa ce: to mak e  Op en Stack a wesome! 

The folks I  met at R ackspacesh areo u r ( Anso Labs)  visionof making OpenS t ac k
the  be st clo ud  pl atfor m fort hem selve s andot hers.
The"m arketing " team at Rackspace wer e thefolks  wh o underst ood the  importan ce
o f OpenStac k a ndworke d t o  conv ince th e r e st of  the company t o  o pen s ou rce
their c l o u d.
Sure  th e re are  gro wing pains. And o n e could pointoutt e chn ica l  are as  that the
comm uni ty h as strug gl ed with (au tomatedte s tingagains t real  cluste r s ). . . The
As for_just using_a single EC2 instance_and RDS..._that_is something_you_can
do, but not_everyone's workload is_so simple that they_can run it_on_one
machine. And not everyone can afford do be down simply because one AZ is_down.
Hence,_multi-AZ VPC_setups.

_

Ask_HN: Good introductory article on_source control - jasonkester

I've recently_joined a_new project owned by a developer who has_never_used source control._ I've suggested moving the project onto Subversion, but_am starting to get the first_signs of pushback.<p>I_think_we're_still at the "what's_in it for me" stage here,_and I'm pretty sure that I'd_blunder any attempt at direct advocacy, so_I'd rather simply forward a URL_that lays out the case_for using_version control and let this_developer reach his_own conclusions.<p>I've_been looking around,_but all the intro SVN docs_I've found seem_to give a brief single paragraph_intro_to SCC before_diving_into_either how_to set up_a_repository, or_"why_CVS sucks and SVN is awesome."__Can anybody recommend anything good?<p>(I'll send across_the Joel Test in_due_time, but I think_we might need to do_some softening up first...)
======
ananthrk
Series of articles_written by_Eric Sink
<http://www.ericsink.com/scm/source_control.html>

He_is also currently working a book on the same topic. A_lot of his recent
articles are about_his experiments with various_version control_systems_and
are worth a_look.

_

Why I_Left Rackspace and What About OpenStack -_garethr
http://dendrobates.wordpress.com/2011/03/22/rackspace-openstac/

======
anotherjesse
Why I_joined Rackspace: to make OpenStack awesome!

The_folks I met at_Rackspace_share our (Anso Labs) vision of_making OpenStack
the best cloud platform for_themselves and others.

The "marketing" team_at_Rackspace_were the folks who understood_the importance
of OpenStack and worked to_convince the rest_of the company to open source
their cloud.

Sure_there_are growing pains. And one could_point_out technical areas that the
community has_struggled_with_(automated testing against real clusters)..._The
