http://citconf.com/wiki/api.php?action=feedcontributions&user=Zsoldosp&feedformat=atomCitconWiki - User contributions [en]2024-03-28T09:44:46ZUser contributionsMediaWiki 1.35.11http://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=16636Peter Zsoldos2022-10-18T18:00:54Z<p>Zsoldosp: </p>
<hr />
<div>Experienced Software Developer among other things, with a passion for quality, education, community, and systems thinking. I also happen to believe in baby steps - a.k.a. the only way to run fast is to run slow. Also, I like finding solutions, not just executing/implementing ones from client - often the best solution doesn't even have to involve writing software!<br />
<br />
I've only missed two (2019, 2021) CITCON Europe events since 2010, and I was the organizer of the Budapest event<br />
<br />
<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi<br />
LinkedIn: http://www.linkedin.com/in/zsoldosp</div>Zsoldosphttp://citconf.com/wiki/index.php?title=MDD_Monitoring_Driven_Development&diff=16634MDD Monitoring Driven Development2022-10-17T18:12:58Z<p>Zsoldosp: </p>
<hr />
<div><br />
== From the Rubber Chicken to MDD ==<br />
<br />
@jtf's "presentation" <br />
<br />
# James Shore's Rubber Chicken <br />
** physical token you had to get to commit (push) to main (it was svn back then), and you ran the build/tests before commit<br />
** had to use a separate physical machine (solving the 'It works on my machine' problem)<br />
# CI<br />
** can run more stuff now (fast tests, slow tests) - but separate build for deploy<br />
# pipelines with artifact passing<br />
# promoting to test/prod<br />
# CD - blue green deploy - rolling back based on KPIs '''CI + monitoring now controls production'''<br />
** if any step fails, the change is automatically to be reverted<br />
** if it made to prod, but business metrics down<br />
*** not reverting code<br />
*** take out from production cluster to investigate<br />
<br />
== State of the monitoring (first) ==<br />
<br />
* metrics used in monitoring are not specific (high level business metric down, must have been this change)<br />
* just like adding tests after writing the code is hard, so is adding monitoring/metrics<br />
* who tried monitoring first?<br />
** zsoldosp - checklist item in issue template, but too many issues it didn't apply, so it kinda got ignored after on that project<br />
** PJ/intent media<br />
*** monitoring can stop deploy/rollout<br />
*** stopped doing acceptance tests in favor of monitoring<br />
** aparker / TIM - failure analyses: we built it, now that we know how it works, let's figure out <br />
*** how could it fail<br />
*** what impact it would have<br />
*** how would we know (from customers? )<br />
*** it it worth adding it? (metric, alert)<br />
<br />
== alerting ==<br />
<br />
* how many alerts should we create<br />
** high level? e.g.: number failed API requests?<br />
** more specific - e.g.: we know it after debugging that it failed 'coz the middleware failed. Should we monitor the middleware?<br />
* metrics vs. monitoring <br />
** monitoring triggers somene to look at it<br />
** metrics - kinda like classic OPs - collect data, don't attach metrics, just eyeball "looks to be an unusual shape, let's investigate"<br />
* who should we call (e.g.: if only high level metrics, who should the alerts wake up?)<br />
* (pagerduty.com)<br />
<br />
== "Failure Friday" practice ==<br />
* during work hours!<br />
* we think this should be redundant, so let's shut this off and see the team recover<br />
* important: do it when you expect the exercise to be successful<br />
<br />
<br />
== Feature validation / AB testing ==<br />
<br />
not the same as monitoring<br />
<br />
<br />
== Alert thresholds ==<br />
<br />
* it's not always binary (on/off) <br />
* normal is not the same as yesterday/last week / last year<br />
** seasonality - e.g.: black friday, but can be different for each industry. And you kinda know it "Mondays are usually about this many pageloads"<br />
** event driven - e.g.: if you publish tips, it depends on what happens in the world<br />
* factor into<br />
** what can we measure<br />
** what should be alert on (i.e.: wake people up). Some things can wait till next business days - use different channels<br />
<br />
== Improving Alerts ==<br />
<br />
* make them actionable<br />
** link to wiki of runbook how to fix<br />
** write it for your future self who alerted at 2am at a party, not with your present knowledge of the context of the feature you just implemented<br />
* metrics you don't use is inventory, thus not useful<br />
<br />
(question: any logging frameworks that would only flush logs on exceptions? but then on DEBUG level?)<br />
<br />
* should we alert on causes (disk full) or symptoms (user can't login) (symptoms more useful? some tools allow dependencies, i.e.: if this is down, these others will be down too, don't alert on those)<br />
<br />
== Workshop on MDD - 2 minutes to dropped jaws ==<br />
<br />
Story: Given that currently our support lines are overwhelmed, if we added an FAQ about it, support calls would drop back to managable levels<br />
<br />
what can we measure?<br />
<br />
* nr of FAQ views<br />
* # of calls<br />
* ask support reps to ask if caller read the FAQ & feed that back to the system?<br />
* instead of "was this helpful" "yes/no" maybe we could have "yes/Call support (link/phone number)" (talk to UX before doing this at home :-))<br />
<br />
=> the way you think of validation/measuring changes the product<br />
<br />
== Monitoring Embedded into Business ==<br />
<br />
* SRE handbook only focuses on the tech<br />
* if decision makers use monitoring data, it's important for the business, thus no need to justify why monitoring<br />
<br />
== Links ==<br />
<br />
* My Philosophy on Alerting (based my observations while I was a Site Reliability Engineer at Google) by Rob Ewaschuk: https://docs.google.com/document/d/199PqyG3UsyXlwieHaqbGiWVa8eMWi8zzAn0YfcApr8Q/edit<br />
* Patrick Debois: Codifying devops practices: https://jedi.be/blog/2012/05/12/codifying-devops-area-practices/<br />
<br />
== good questions to ask: ==<br />
* what does this data mean?<br />
* If we are not wachting it -> delete it? <br />
* Should we try "Failure Friday"?<br />
* Should we use "Daily Red"?<br />
* Is this indicator fast enough (leading or lagging indicator) to react?</div>Zsoldosphttp://citconf.com/wiki/index.php?title=MDD_Monitoring_Driven_Development&diff=16633MDD Monitoring Driven Development2022-10-17T18:09:33Z<p>Zsoldosp: zsoldosp notes typed up</p>
<hr />
<div><br />
== From the Rubber Chicken to MDD ==<br />
<br />
@jtf's "presentation" <br />
<br />
# James Shore's Rubber Chicken <br />
** physical token you had to get to commit (push) to main (it was svn back then), and you ran the build/tests before commit<br />
** had to use a separate physical machine (solving the 'It works on my machine' problem)<br />
# CI<br />
** can run more stuff now (fast tests, slow tests) - but separate build for deploy<br />
# pipelines with artifact passing<br />
# promoting to test/prod<br />
# CD - blue green deploy - rolling back based on KPIs '''CI + monitoring now controls production'''<br />
** if any step fails, the change is automatically to be reverted<br />
** if it made to prod, but business metrics down<br />
*** not reverting code<br />
*** take out from production cluster to investigate<br />
<br />
== State of the monitoring (first) ==<br />
<br />
* metrics used in monitoring are not specific (high level business metric down, must have been this change)<br />
* just like adding tests after writing the code is hard, so is adding monitoring/metrics<br />
* who tried monitoring first?<br />
** zsoldosp - checklist item in issue template, but too many issues it didn't apply, so it kinda got ignored after<br />
** PJ/intent media<br />
*** monitoring can stop deploy/rollout<br />
*** stopped doing acceptance tests in favor of monitoring<br />
** aparker / TIM - failure analyses: we built it, now that we know how it works, let's figure out <br />
*** how could it fail<br />
*** what impact it would have<br />
*** how would we know (from customers? )<br />
*** it it worth adding it? (metric, alert)<br />
<br />
== alerting ==<br />
<br />
* how many alerts should we create<br />
** high level? e.g.: number failed API requests?<br />
** more specific - e.g.: we know it after debugging that it failed 'coz the middleware failed. Should we monitor the middleware?<br />
* metrics vs. monitoring <br />
** monitoring triggers somene to look at it<br />
** metrics - kinda like classic OPs - collect data, don't attach metrics, just eyeball "looks to be an unusual shape, let's investigate"<br />
* who should we call (e.g.: if only high level metrics, who should the alerts wake up?)<br />
* (pagerduty.com)<br />
<br />
== "Failure Friday" practice ==<br />
* during work hours!<br />
* we think this should be redundant, so let's shut this off and see the team recover<br />
* important: do it when you expect the exercise to be successful<br />
<br />
<br />
== Feature validation / AB testing ==<br />
<br />
not the same as monitoring<br />
<br />
<br />
== Alert thresholds ==<br />
<br />
* it's not always binary (on/off) <br />
* normal is not the same as yesterday/last week / last year<br />
** seasonality - e.g.: black friday, but can be different for each industry. And you kinda know it "Mondays are usually about this many pageloads"<br />
** event driven - e.g.: if you publish tips, it depends on what happens in the world<br />
* factor into<br />
** what can we measure<br />
** what should be alert on (i.e.: wake people up). Some things can wait till next business days - use different channels<br />
<br />
== Improving Alerts ==<br />
<br />
* make them actionable<br />
** link to wiki of runbook how to fix<br />
** write it for your future self who alerted at 2am at a party, not with your present knowledge of the context of the feature you just implemented<br />
* metrics you don't use is inventory, thus not useful<br />
<br />
(question: any logging frameworks that would only flush logs on exceptions? but then on DEBUG level?)<br />
<br />
* should we alert on causes (disk full) or symptoms (user can't login) (symptoms more useful? some tools allow dependencies, i.e.: if this is down, these others will be down too, don't alert on those)<br />
<br />
== Workshop on MDD - 2 minutes to dropped jaws ==<br />
<br />
Story: Given that currently our support lines are overwhelmed, if we added an FAQ about it, support calls would drop back to managable levels<br />
<br />
what can we measure?<br />
<br />
* nr of FAQ views<br />
* # of calls<br />
* ask support reps to ask if caller read the FAQ & feed that back to the system?<br />
* instead of "was this helpful" "yes/no" maybe we could have "yes/Call support (link/phone number)" (talk to UX before doing this at home :-))<br />
<br />
=> the way you think of validation/measuring changes the product<br />
<br />
== Monitoring Embedded into Business ==<br />
<br />
* SRE handbook only focuses on the tech<br />
* if decision makers use monitoring data, it's important for the business, thus no need to justify why monitoring<br />
<br />
== Links ==<br />
<br />
* My Philosophy on Alerting (based my observations while I was a Site Reliability Engineer at Google) by Rob Ewaschuk: https://docs.google.com/document/d/199PqyG3UsyXlwieHaqbGiWVa8eMWi8zzAn0YfcApr8Q/edit<br />
* Patrick Debois: Codifying devops practices: https://jedi.be/blog/2012/05/12/codifying-devops-area-practices/<br />
<br />
== good questions to ask: ==<br />
* what does this data mean?<br />
* If we are not wachting it -> delete it? <br />
* Should we try "Failure Friday"?<br />
* Should we use "Daily Red"?<br />
* Is this indicator fast enough (leading or lagging indicator) to react?</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=16565Peter Zsoldos2020-05-30T11:02:29Z<p>Zsoldosp: </p>
<hr />
<div>Experienced Software Developer among other things, with a passion for quality, education, community, and systems thinking. I also happen to believe in baby steps - a.k.a. the only way to run fast is to run slow. Also, I like finding solutions, not just executing/implementing ones from client - often the best solution doesn't even have to involve writing software!<br />
<br />
I've so far been to almost all (2019 missed) CITCON Europe confs since 2010, and have organized the Budapest event<br />
<br />
<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi<br />
LinkedIn: http://www.linkedin.com/in/zsoldosp</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Monorepos&diff=16231Monorepos2016-04-21T06:32:25Z<p>Zsoldosp: /* Monorepos */ fix Ivan's name to link finally</p>
<hr />
<div>= Monorepos =<br />
<br />
According to [[Ivan Moore]], [http://danluu.com/monorepo/ danluu.com/monorepo] pretty much covers what was discussed, except it doesn't explain the problems of maven style dependency management as much as the session went into ([https://twitter.com/ivanrmoore/status/722897084429393921 tweet])</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Monorepos&diff=16230Monorepos2016-04-21T06:30:45Z<p>Zsoldosp: /* Monorepos */ change link to Ivan's name</p>
<hr />
<div>= Monorepos =<br />
<br />
According to [Ivan_Moore], [http://danluu.com/monorepo/ danluu.com/monorepo] pretty much covers what was discussed, except it doesn't explain the problems of maven style dependency management as much as the session went into ([https://twitter.com/ivanrmoore/status/722897084429393921 tweet])</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Monorepos&diff=16229Monorepos2016-04-21T06:30:11Z<p>Zsoldosp: Created page with "= Monorepos = According to [Ivan Moore], [http://danluu.com/monorepo/ danluu.com/monorepo] pretty much covers what was discussed, except it doesn't explain the problems of ma..."</p>
<hr />
<div>= Monorepos =<br />
<br />
According to [Ivan Moore], [http://danluu.com/monorepo/ danluu.com/monorepo] pretty much covers what was discussed, except it doesn't explain the problems of maven style dependency management as much as the session went into ([https://twitter.com/ivanrmoore/status/722897084429393921 tweet])</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2016Sessions&diff=16228CITCONEurope2016Sessions2016-04-21T06:24:12Z<p>Zsoldosp: creating page for Ivan Moore's monorepos session</p>
<hr />
<div><br />
Back to the [[Main Page]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
Back to the [[Main Page]]<br />
<br />
== 10:00 Topics ==<br />
<br />
# [[HowCanWeBecomeBetterTesters | How Can We Become Better Testers]]<br />
# [[self organizing teams]]<br />
# [[vm management solutions]]<br />
# [[status updates for automated tests to non-technical people]]<br />
# [[LearningMindset | Learning Mindset]]<br />
<br />
== 11:15 Topics ==<br />
<br />
# [[automated gui tests]]<br />
# [[security]]<br />
# [[test data generation]]<br />
# [[frustrated?]]<br />
# [[ask me anything Jenkins]]<br />
<br />
== Lunch Topics ==<br />
<br />
# [[]]<br />
# [[]]<br />
# [[Monorepos]]<br />
# [[]]<br />
# [[]]<br />
<br />
== 2:00 Topics ==<br />
<br />
# [[learn docker]]<br />
# [[tdd for people]]<br />
# [[how do you make CI more fun]]<br />
# [[continuously delivery side effects]]<br />
# [[selenium + JavaScript]]<br />
<br />
== 3:15 Topics ==<br />
<br />
# [[Testing your organization]]<br />
# [[]]<br />
# [[]]<br />
# [[]]<br />
# [[]]<br />
<br />
== 4:30 Topics ==<br />
<br />
# [[elephant carpachio]]<br />
# [[]]<br />
# [[]]<br />
# [[]]<br />
# [[]]<br />
<br />
== Closing Session ==<br />
<br />
[[CITCONEurope2016AhaMoments|A-Ha Moments]] <br />
<br />
== Table View ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Room name<br />
! 10:00<br />
! 11:15<br />
! 2:00<br />
! 3:15<br />
! 4:30<br />
|-<br />
| Room 1<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
|-<br />
| Room 2<br />
| [[]]<br />
| [[]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
|-<br />
| Room 3<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
|-<br />
| Lounge<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
|-<br />
| Far Corner<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
| [[...]]<br />
|}</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=16221Peter Zsoldos2016-04-19T14:02:21Z<p>Zsoldosp: </p>
<hr />
<div>Experienced Software Developer among other things, with a passion for quality, education, community, and systems thinking. I also happen to believe in baby steps - a.k.a. the only way to run fast is to run slow. Also, I like finding solutions, not just executing/implementing ones from client - often the best solution doesn't even have to involve writing software!<br />
<br />
I've so far been to all CITCON Europe confs since 2010, and have organized the Budapest event<br />
<br />
<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi<br />
LinkedIn: http://www.linkedin.com/in/zsoldosp</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=16220Peter Zsoldos2016-04-19T14:01:48Z<p>Zsoldosp: </p>
<hr />
<div>Experienced Software Developer among other things, with a passion for quality, education, community, and systems thinking. I also happen to believe in baby steps - a.k.a. the only way to run fast is to run slow. Also, I like finding solutions, not just executing/implementing ones from client - often the best solution doesn't even have to involve writing software!<br />
<br />
I've so far been to all CITCON Europe sessions since 2010, and have organized the Budapest event<br />
<br />
<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi<br />
LinkedIn: http://www.linkedin.com/in/zsoldosp</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=16219OnTheWeb2016-04-19T13:59:41Z<p>Zsoldosp: added my post about the Cluj conference</p>
<hr />
<div><br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
== CITCON Europe 2016 Cluj-Napoca ==<br />
<br />
[[Peter Zsoldos]] [http://blog.zsoldosp.eu/2016/04/18/citcon-cluj-2016/ conference notes]<br />
<br />
== CITCON North America 2015 Ann Arbor ==<br />
<br />
== CITCON Europe 2015 Helsinki ==<br />
<br />
[[Gojko Adzic]] [https://atlas.mindmup.com/gojkomonthly/testing_tools_the_next_generation/index.html Mind map from "Testing Tools: The next generation"]<br />
<br />
[[Tom Denley]] [https://vimeo.com/141771462 Lightning talk at TIM Group following Helsinki sharing thoughts on configuring CI through code]<br />
<br />
== CITCON Asia 2015 Hong Kong ==<br />
<br />
[http://leanarch.eu/2015/02/20/how-to-make-people-do-pair-programming/ How to make people do pair programming?]<br />
<br />
== CITCON North America 2014 Austin Texas ==<br />
<br />
[[Mitch Fincher]] [http://mitchfincher.blogspot.co.uk/2014/10/citcon-austin-2014.html shares his pictures and some jumbled notes]<br />
<br />
== CITCON Europe 2014 Zagreb ==<br />
[[Adina Moldovan]]: [http://altom.ro/blog/citcon-2014 http://altom.ro/blog/citcon-2014]<br />
<br />
[[Karlo Smid]] report: http://zagorskisoftwaretester.blogspot.com/2014/09/citcon-2014-zagreb-report.html<br />
<br />
uTest list of top tweets: https://blog.utest.com/2014/09/26/top-tweets-from-citcon-2014/<br />
<br />
== CITCON ANZ 2014 Auckland ==<br />
<br />
[[Katrina Clokie]] : [http://katrinatester.blogspot.co.nz/2014/02/non-functional-testing-in-continuous.html Non-functional testing in continuous delivery]<br />
<br />
== CITCON Europe 2013 Turin ==<br />
<br />
[[Peter Zsoldos]] : http://blog.zsoldosp.eu/2013/09/30/citcon-turin-2013/<br />
<br />
== CITCON North America 2013 Boston ==<br />
<br />
== CITCON ANZ 2013 Sydney ==<br />
<br />
https://twitter.com/search/realtime?q=citcon+sydney<br />
<br />
http://www.nztester.co.nz/oztester_files/OZTester01.pdf - Magazine with a write up on the conf (PDF)<br />
<br />
== CITCON Europe 2012 Budapest ==<br />
<br />
[[Attila Magyar]] : http://athos.blogs.balabit.com/2012/10/citcon-europe-2012-tdd-is-like-sex/<br />
<br />
[[Željko Filipin]] : http://filipin.eu/citcon-europe-2012-in-budapest/<br />
<br />
[[Viktor Sadovnikov]] http://prezi.com/uufxsflf00hf/citcon-2012/ - Prezi presentation of participation in CITCON<br />
<br />
== CITCON North America 2012 Portland Oregon ==<br />
<br />
== CITCON Asia 2012 Singapore ==<br />
<br />
[[Riju Kansal]] http://aaoblogkare.blogspot.co.uk/2012/04/citcon-cool-great-experience.html<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://blog.zsoldosp.eu/2011/11/citcon-london-2011.html<br />
<br />
Skillsmatter (the venue provider) put up the video recorded of the following sessions on their site at http://skillsmatter.com/event/agile-testing/citcon :<br />
<br />
* [[ To_Feature_Branch_Or_Not_To_Feature_Branch ]]<br />
* [[ Moving_an_Agile_Team_from_CI_to_CD ]]<br />
* [[ Configuration_Changes ]]<br />
* [[ Testing_for_Value ]]<br />
* [[ Radiators ]]<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://blog.zsoldosp.eu/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON ANZ 2010 Wellington New Zealand ==<br />
<br />
[[Manuel Kueblboeck]] [http://qualityswdev.com/2010/07/09/citcon-2010-wellington/ enjoyed his first open space and learned about different styles of pair programming]<br />
<br />
== CITCON North America 2010 Raleigh/Durham North Carolina ==<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America �07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=16130ConferencePlanning2015-11-09T13:05:21Z<p>Zsoldosp: expanded on security checklist</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Date & Location selection==<br />
<br />
* happens on the organization mailing lists<br />
* location requirements:<br />
** should have good (international) connections (airport, international railway stations, etc.)<br />
* date considerations<br />
** check for other conferences happening in the area - could hurt if there is a similar event just a week ago (or even on the same day), both when competing for sponsors & attendees. Impossible to achieve perfect schedule, but some places to check are<br />
*** meetup.com<br />
*** lanyard<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Physical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
* ask local commerce chambers and/or municipal/governmental Tourism, Events and Economic Development offices if they have any suggestions<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
===Once a venue has been confirmed===<br />
<br />
* establish a point of contact at the venue for logistics.<br />
* have local venue coordinator send and introductory email to the logistical point of contact and the sponsor@citconf.com mailing list, including the conference organizers. <br />
* conference organizers will send the following email to the logistical contact at the venue:<br />
<br />
Thanks for hosting CITCON (Year and City)! <br />
<br />
We are excited to work with you on this event. As a venue sponsor (Venue Name) receives all of the benefits of a full conference sponsor. <br />
<br />
Could you please send us both a web ready logo (jpeg, tif, or gif) and a print quality logo (eps or ai)? We will use these on the conference website, posters, and T- shirts. Also, can you please lets us know what web address you would like your logo to link to. <br />
<br />
Here are a few things we would like to check on to get started:<br />
<br />
1. Do you have any preferred catering vendors? <br />
<br />
2. Are you willing to receive delegate give away items from event sponsors and hold them until the event? (They wouldn't arrive until shortly before the day of the event.) If so, to what address and to whose attention should these item be sent?<br />
<br />
3. What items A/V and other items are available for conference use? i.e. projectors, microphone/sound system, white boards, ect. <br />
<br />
4. Is access to the building limited, is there security, will we need cards or pass codes? Is security aware that we are going be there (e.g.: if normally they don't provide weekend personnel, they might need to do so 'coz of the conf. See Helsinki)<br />
<br />
Thanks again for your help!<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
For examples, see [[Menu from CITCON Sydney 2013]] and [[Menu from CITCON Budapest 2012]].<br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** you'll finalize the order amounts one week prior to the event<br />
** ask for a complete breakdown of items included, have them specify any potential food allergy items i.e. shell fish, gluten free, peanuts, tree nuts, etc.<br />
* what we need the quote for<br />
** Friday evening reception (19:30-21:00)<br />
***delivery time 19:30<br />
*** i.e. finger-food, canapés, hors d'ourves, pizza <br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks, coffee, water<br />
**** cups and ice need to be included<br />
*** beers (and maybe some wine)<br />
**** glasses need to be provided<br />
** Saturday morning breakfast (9:00-10:00)<br />
*** delivery time 8:30<br />
*** i.e. danishes, croissants, muffins, fruit<br />
**** plates, napkins and utensils need to be included<br />
*** coffee, tea, juices, water <br />
**** cups and ice need to be included<br />
** Saturday beverage service - all day<br />
*** coffee and tea<br />
**** cups need to be included<br />
*** snacks are a plus but not required<br />
** Saturday lunch (12:30-14:00)<br />
*** delivery time 12:00<br />
*** i.e. sandwiches, pizza, full catering including hot food<br />
**** a full meal is required, i.e. chips/crisps or fruit should be included with sandwiches<br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks<br />
**** ice needs to be included<br />
<br />
===Invoices, Payment===<br />
<br />
* non-English invoices are fine<br />
* Invoices should be addressed to the OIF (Open Information Foundation, PO Box 1812, North Sioux City, SD 57049)<br />
* available payment options are credit card, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==Swag==<br />
<br />
* traditionally, there have only been T-shirts<br />
** taken care of by PJ/Amy<br />
** color voting happens on the organization mailing list (everyone on the list can vote, not just the current organizers)<br />
* stickers<br />
** from 2015 on<br />
** taken care of by PJ/Amy<br />
<br />
==During the event==<br />
<br />
===Tweetwall===<br />
<br />
In the main hall. Normally we use visible tweets, using the following link [http://visibletweets.com/#query=citcon&animation=1 http://visibletweets.com/#query=citcon&animation=1]<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=15875ConferencePlanning2015-06-23T18:36:48Z<p>Zsoldosp: added section about swag</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Date & Location selection==<br />
<br />
* happens on the organization mailing lists<br />
* location requirements:<br />
** should have good (international) connections (airport, international railway stations, etc.)<br />
* date considerations<br />
** check for other conferences happening in the area - could hurt if there is a similar event just a week ago (or even on the same day), both when competing for sponsors & attendees. Impossible to achieve perfect schedule, but some places to check are<br />
*** meetup.com<br />
*** lanyard<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Physical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
* ask local commerce chambers and/or municipal/governmental Tourism, Events and Economic Development offices if they have any suggestions<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
===Once a venue has been confirmed===<br />
<br />
* establish a point of contact at the venue for logistics.<br />
* have local venue coordinator send and introductory email to the logistical point of contact and the sponsor@citconf.com mailing list, including the conference organizers. <br />
* conference organizers will send the following email to the logistical contact at the venue:<br />
<br />
Thanks for hosting CITCON (Year and City)! <br />
<br />
We are excited to work with you on this event. As a venue sponsor (Venue Name) receives all of the benefits of a full conference sponsor. <br />
<br />
Could you please send us both a web ready logo (jpeg, tif, or gif) and a print quality logo (eps or ai)? We will use these on the conference website, posters, and T- shirts. Also, can you please lets us know what web address you would like your logo to link to. <br />
<br />
Here are a few things we would like to check on to get started:<br />
<br />
1. Do you have any preferred catering vendors? <br />
<br />
2. Are you willing to receive delegate give away items from event sponsors and hold them until the event? (They wouldn't arrive until shortly before the day of the event.) If so, to what address and to whose attention should these item be sent?<br />
<br />
3. What items A/V and other items are available for conference use? i.e. projectors, microphone/sound system, white boards, ect. <br />
<br />
4. Is access to the building limited, is there security, will we need cards or pass codes? <br />
<br />
Thanks again for your help!<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
For examples, see [[Menu from CITCON Sydney 2013]] and [[Menu from CITCON Budapest 2012]].<br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** you'll finalize the order amounts one week prior to the event<br />
** ask for a complete breakdown of items included, have them specify any potential food allergy items i.e. shell fish, gluten free, peanuts, tree nuts, etc.<br />
* what we need the quote for<br />
** Friday evening reception (19:30-21:00)<br />
***delivery time 19:30<br />
*** i.e. finger-food, canapés, hors d'ourves, pizza <br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks, coffee, water<br />
**** cups and ice need to be included<br />
*** beers (and maybe some wine)<br />
**** glasses need to be provided<br />
** Saturday morning breakfast (9:00-10:00)<br />
*** delivery time 8:30<br />
*** i.e. danishes, croissants, muffins, fruit<br />
**** plates, napkins and utensils need to be included<br />
*** coffee, tea, juices, water <br />
**** cups and ice need to be included<br />
** Saturday beverage service - all day<br />
*** coffee and tea<br />
**** cups need to be included<br />
*** snacks are a plus but not required<br />
** Saturday lunch (12:30-14:00)<br />
*** delivery time 12:00<br />
*** i.e. sandwiches, pizza, full catering including hot food<br />
**** a full meal is required, i.e. chips/crisps or fruit should be included with sandwiches<br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks<br />
**** ice needs to be included<br />
<br />
===Invoices, Payment===<br />
<br />
* non-English invoices are fine<br />
* Invoices should be addressed to the OIF (Open Information Foundation, PO Box 1812, North Sioux City, SD 57049)<br />
* available payment options are credit card, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==Swag==<br />
<br />
* traditionally, there have only been T-shirts<br />
** taken care of by PJ/Amy<br />
** color voting happens on the organization mailing list (everyone on the list can vote, not just the current organizers)<br />
* stickers<br />
** from 2015 on<br />
** taken care of by PJ/Amy<br />
<br />
==During the event==<br />
<br />
===Tweetwall===<br />
<br />
In the main hall. Normally we use visible tweets, using the following link [http://visibletweets.com/#query=citcon&animation=1 http://visibletweets.com/#query=citcon&animation=1]<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=15798ConferencePlanning2015-02-19T09:33:19Z<p>Zsoldosp: typos fixed + added section about tweet wall</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Date & Location selection==<br />
<br />
* happens on the organization mailing lists<br />
* location requirements:<br />
** should have good (international) connections (airport, international railway stations, etc.)<br />
* date considerations<br />
** check for other conferences happening in the area - could hurt if there is a similar event just a week ago (or even on the same day), both when competing for sponsors & attendees. Impossible to achieve perfect schedule, but some places to check are<br />
*** meetup.com<br />
*** lanyard<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Physical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
* ask local commerce chambers and/or municipal/governmental Tourism, Events and Economic Development offices if they have any suggestions<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
===Once a venue has been confirmed===<br />
<br />
* establish a point of contact at the venue for logistics.<br />
* have local venue coordinator send and introductory email to the logistical point of contact and the sponsor@citconf.com mailing list, including the conference organizers. <br />
* conference organizers will send the following email to the logistical contact at the venue:<br />
<br />
Thanks for hosting CITCON (Year and City)! <br />
<br />
We are excited to work with you on this event. As a venue sponsor (Venue Name) receives all of the benefits of a full conference sponsor. <br />
<br />
Could you please send us both a web ready logo (jpeg, tif, or gif) and a print quality logo (eps or ai)? We will use these on the conference website, posters, and T- shirts. Also, can you please lets us know what web address you would like your logo to link to. <br />
<br />
Here are a few things we would like to check on to get started:<br />
<br />
1. Do you have any preferred catering vendors? <br />
<br />
2. Are you willing to receive delegate give away items from event sponsors and hold them until the event? (They wouldn't arrive until shortly before the day of the event.) If so, to what address and to whose attention should these item be sent?<br />
<br />
3. What items A/V and other items are available for conference use? i.e. projectors, microphone/sound system, white boards, ect. <br />
<br />
4. Is access to the building limited, is there security, will we need cards or pass codes? <br />
<br />
Thanks again for your help!<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
For examples, see [[Menu from CITCON Sydney 2013]] and [[Menu from CITCON Budapest 2012]].<br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** you'll finalize the order amounts one week prior to the event<br />
** ask for a complete breakdown of items included, have them specify any potential food allergy items i.e. shell fish, gluten free, peanuts, tree nuts, etc.<br />
* what we need the quote for<br />
** Friday evening reception (19:30-21:00)<br />
***delivery time 19:30<br />
*** i.e. finger-food, canapés, hors d'ourves, pizza <br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks, coffee, water<br />
**** cups and ice need to be included<br />
*** beers (and maybe some wine)<br />
**** glasses need to be provided<br />
** Saturday morning breakfast (9:00-10:00)<br />
*** delivery time 8:30<br />
*** i.e. danishes, croissants, muffins, fruit<br />
**** plates, napkins and utensils need to be included<br />
*** coffee, tea, juices, water <br />
**** cups and ice need to be included<br />
** Saturday beverage service - all day<br />
*** coffee and tea<br />
**** cups need to be included<br />
*** snacks are a plus but not required<br />
** Saturday lunch (12:30-14:00)<br />
*** delivery time 12:00<br />
*** i.e. sandwiches, pizza, full catering including hot food<br />
**** a full meal is required, i.e. chips/crisps or fruit should be included with sandwiches<br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks<br />
**** ice needs to be included<br />
<br />
===Invoices, Payment===<br />
<br />
* non-English invoices are fine<br />
* Invoices should be addressed to the OIF (Open Information Foundation, PO Box 1812, North Sioux City, SD 57049)<br />
* available payment options are credit card, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==During the event==<br />
<br />
===Tweetwall===<br />
<br />
In the main hall. Normally we use visible tweets, using the following link [http://visibletweets.com/#query=citcon&animation=1 http://visibletweets.com/#query=citcon&animation=1]<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=15750Peter Zsoldos2014-09-22T19:11:56Z<p>Zsoldosp: </p>
<hr />
<div>Programmer with a passion for quality, education, community, and systems thinking. I also happen to believe in baby steps - a.k.a. the only way to run fast is to run slow.<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi<br />
LinkedIn: http://www.linkedin.com/in/zsoldosp</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Questions_on_the_right_level_and_amount_of_testing&diff=15532Questions on the right level and amount of testing2013-10-08T11:47:34Z<p>Zsoldosp: initial/brief/raw notes</p>
<hr />
<div>== Coverage ==<br />
<br />
* measure on unit tests<br />
* target levels are not important/helpful<br />
* great negative metric (i.e.: if there is 0% coverage, we can say for a fact that that code is definitely NOT tested)<br />
<br />
== Are we testing too much? ==<br />
<br />
* manual assertions (checking) vs. human (exploratory testing)<br />
* execution time increase<br />
* fragile test, we spend more time fixing tests than writing code<br />
* a lot of tests never fail<br />
* solutions:<br />
** intelligent test ordering + partial result feedback<br />
*** based on historic probability of failure<br />
*** coverage analysis of commit impact (take lines changed from diff & correlate past coverage data to unique tests)<br />
*** manually maintain test suites (quick tests, smoke tests, full tests), smoke test can change as different features are being developed, and run them on different schedule<br />
*** related past CITCON session - Josh Ram @ CITCON Australia 2008<br />
*** tools<br />
**** infitest<br />
**** team city or bamboo<br />
**** JTestMe, ProTest<br />
<br />
== reused test step ordering ==<br />
<br />
* tests can have overlapping steps, e.g.: scenario of "third attempt to log in with bad password locks account" has lot of overlap between steps<br />
** => create a graph where the nodes are the steps (e.g.: login with correct_username, wrong_password), and the assertions hang off / are the values of the nodes<br />
** => faster execution / more effective failfast (TODO: [[Peter Zsoldos]] to write it up in more detail</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Low_level_test_code_/_library_bleeding_edge&diff=15531Low level test code / library bleeding edge2013-10-08T11:45:00Z<p>Zsoldosp: added more notes from moderator and changed formatitng</p>
<hr />
<div>"bleeding edge" is relative <br />
<br />
* some don't know beyond assertEquals/assertTrue<br />
* some use hamcrest <br />
* some use something beyond that :) <br />
<br />
== Assertions ==<br />
<br />
how to deal with similar assertions easily, e.g in a e-commerce application, Assert.Order(coupon).hasCoupon and Assert.NotOrder(coupon).hasCoupon?<br />
<br />
=== hamcrest === <br />
https://code.google.com/p/hamcrest/wiki/Tutorial<br />
<br />
* don't couple your expected object to the actual object code, 'coz it makes tests fragile<br />
* write nice object assertors, so if the object under test gets a new required property, you don't have to update your tests (almost like duck typing, only interested in those properties)<br />
* nice failure messages<br />
* beware what you use it together with, e.g.: hamcrest + moquito has caused confusion for some!<br />
* you can create your custom matchers and submatchers<br />
* explicit errors<br />
<br />
=== fest ===<br />
<br />
http://thomassundberg.wordpress.com/2011/04/24/fest-assert-a-fluent-interface-for-assertions/<br />
<br />
=== scenario based testing ===<br />
<br />
e.g.: take a look at ravenDB tests<br />
* http://ravendb.net/docs/intro/ravendb-in-a-nutshell<br />
* https://github.com/ravendb/ravendb<br />
<br />
=== Pre/post conditions in the langauge ===<br />
<br />
verifications embedded and enforced in the language itself<br />
<br />
* Eifel programming language<br />
* code contracts in C#/F#<br />
* problem: with the compiler level implementation, you lose testability - since the compiler fails compiling code that violates these constraints, you cannot add tests making sure these are invalid inputs. So there is no defense against accidentally removing such conditions from the code (no regressions)<br />
** not all languages are like that, some of them are runtime checks and compile time warnings<br />
* guava: in java<br />
<br />
<br />
=== Property based testing ===<br />
<br />
* random input generator which is restricted. No more repetability of tests (unless creating a manual test with the values that failed on the build server)<br />
* point to start learning about it: http://www.natpryce.com<br />
<br />
---<br />
<br />
* Bounded model verification / theorem provers (Biere Armin)<br />
* Model Driven Testing</div>Zsoldosphttp://citconf.com/wiki/index.php?title=What_does_the_ideal_look_like%3F&diff=15530What does the ideal look like?2013-10-08T11:37:41Z<p>Zsoldosp: initial scribe notes with basic formatting</p>
<hr />
<div>== What does "ideal" look like? ==<br />
<br />
Related to the 10:00 session about improvement - what is our goal that we are striving towards?<br />
<br />
Toyota: it was the one-to-one flow (order placed, car is delivered)<br />
<br />
important differences with software:<br />
* no rework<br />
* one full process<br />
<br />
== So what does ideal look like, how software should be made? ==<br />
<br />
<br />
@PJ: after I make a change, I want to get immediate (1-2 seconds) feedback available to customer. Everything we do today is to get closer to that by parallelizing, removing human steps from delivery, and make delivery reliable<br />
<br />
=== When could such fast delivery be wrong? ===<br />
<br />
* [scribe notes, unspoken during the session, for it was too fast - e.g.: democracy was explicitly made slow with the checks and balances, plus being slow has made me realize on occasion that I'm solving the wrong problem]<br />
* capability/option should be there to put it to production so fast<br />
* is the business ready for? It's much better for a business to waste inventory than to wait on us [IT].<br />
* business competing with amazon - clearly, 1.5 years delivey is bad<br />
<br />
But to deliver reliably, there should be a clear view of *what* should be delivered (build the right thing)<br />
* lean manufacturing<br />
* by optimizing only the IT side of things you only get so far - business also needs to be doing it (i.e.: what's the point of pretty CI, fast releases of well tested features if they are unneeded/unused?)<br />
<br />
== Ideal one to one flow in software: Waterfall! ==<br />
<br />
# analyze<br />
# define done<br />
# design<br />
# implement<br />
# check<br />
# deliver<br />
# train<br />
<br />
one flow for one person/pair/team<br />
<br />
many are already trying this (do only one thing and finish it instead of multitasking, because latter is much slower)<br />
<br />
Break features/tasks down to get feedback (or approximation of) fast enough, otherwise it takes too long to learn <br />
<br />
: ideal is ideal because it's unachievable (maybe utopia is a better word?)<br />
<br />
Original waterfall paper actually requires these :)<br />
<br />
Is the one request a small enough size? i.e.: what do we do about the "unknown unknowns"?<br />
<br />
: the ideal system would fail/crash totally when an assumption is violated, i.e.: would fall apart before actual delivery<br />
<br />
Delivering features that were wanted when requested, but later not? => iterations, adjustment, it's normal<br />
<br />
=== What if the business person can just "think it" and it exists? ===<br />
<br />
* ok, in the staging environment (e.g.: like a wind-tunnel)<br />
* prior business person only things (SQL, etc.) all broke because of the pesky little technical details or corner cases<br />
* corner cases/human error will always be there, and for that we need checks and balances (like in double entry bookkeeping), but for non-technical aspects, software shouldn't be the bottleneck <br />
* [unspoken scribe notes: essential complexity will always be there, but accidental complexity should be reduced/eliminated]<br />
<br />
The ideal software process should assume perfect requirements (even if later business learns differently, see iterations above)<br />
<br />
Eliminate the feedback cycles that slow us down<br />
<br />
i.e.: in the the process from idea - design - implementation - test - release- maintenance, the later steps should all require shorter and shorter times than the prior ones<br />
<br />
==== When is maintenance needed? ====<br />
* development screwed something up<br />
* business environment (world) changed that made some assumptions void (e.g.: previously single country business goes global)<br />
* maintenance is the ceremony - logrotate, disk full, etc. operations<br />
<br />
ideal would be no CPU, memory, etc. limits<br />
<br />
Maintenance could also be addressed by "making a new thought"<br />
<br />
iterative analysis is needed<br />
<br />
everything between idea and profit/value is waste<br />
<br />
---<br />
<br />
formal specifications are great, but by the time they become useful, they are essentially the code<br />
<br />
ideal: like in the matrix, via a plugin - give me racks of guns<br />
: but why don't they think instead "my enemy should drop dead?" That's still "pesky technical detail/complexity that has to be addressed (i.e.: Neo actually performs the fight himself)<br />
<br />
but instant software delivery requirement would force software development to be more efficient<br />
<br />
What are we usually slowed down by?<br />
<br />
# legacy data (and its migration to a new schema)<br />
# incomplete requirements<br />
<br />
==== different thinking: ====<br />
<br />
business - I want 2 out 10 to be successful<br />
traditional IT - optimize for resource utilization, and thus there is no slack in the system when you would need it for something new<br />
lean - optimize for learning<br />
short cycles - single flow, feedback, then decide of next move (canning a project early due to learning can be a good/great decision!)<br />
<br />
==== Forward (the company): classic fake based development aka. market/customer validation ====<br />
<br />
# buy a bunch of adwords, see what people click on (leading to empty/under construction pages)<br />
# once figured out which ads are popular, create a static store / landing page with product pictures and all -> add to cart results in "internal server error"<br />
# idea cristallized: people are willing to buy bird cages from us -> now we can go and start the business, supplies, and build the actual webshop, etc.<br />
<br />
<br />
idea -> build -> measure -> [back to] idea (can't see in the notes, but each step is a block, and build is intentionally much smaller than the idea/measure steps, to signify that it should take much less effort than the others)<br />
<br />
: note: measure is not enough, need to analyze<br />
<br />
=== Should the ideal be defined for every single project? ===<br />
<br />
different goals, different environments, etc.<br />
<br />
all the above is useful to actually give a framework in which it can be explained why TDD is useful (to keep the "build" box small)<br />
<br />
Use utilities! A.k.a.: focus on core competencies!<br />
<br />
* e.g.: like with electricity - we should move on from the state of "how do I get power here" to "what do we do with the energy that's available here?"<br />
* 10 years ago we installed Word on the PCs, twiki's on the servers, now we just use google docs and other online tools<br />
* heroku and others make deployment and much of operations a utility<br />
* remove choices/options that are not a competitive advantage for you (power of default) => faster development<br />
<br />
Ideal is a guiding light - sometimes removing a choice is the good thing, sometimes adding it<br />
<br />
remove non-human activities<br />
<br />
=== Model Driven Architecture ===<br />
<br />
declarative<br />
<br />
* traditionally: UML -> code<br />
* restrict problem domain, so there is no need for code<br />
* state machines<br />
<br />
problem: using it bigger contexts,<br />
* data driven apps<br />
* frameworks handle persistence<br />
<br />
enables you to move faster<br />
mockup with the customer, go home and implement<br />
* approximation<br />
* specific domain<br />
<br />
future: cam't automate everything, but some things you shouldn't write at all<br />
<br />
turn your app's core into a DSL (domain specific language)<br />
<br />
one such framework: http://portofino.sf.nt / http://www.manydesigns.com<br />
<br />
Demming circle</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Continuous_Interruptions&diff=15529Continuous Interruptions2013-10-08T11:31:01Z<p>Zsoldosp: formatting</p>
<hr />
<div>* e.g.: 3 team, N features, shared build machine with parallel feature tests<br />
* when the build is broken, everyone gets feedback about the broken build<br />
** information overload => "it's broken again, but surely not by me"<br />
** address feedback to specific committer (e.g.: mail/irc only to the committers involved in the changeset that triggered the build)<br />
** is anyone working on fixing it? => put a sticky on the monitor "I'm fixing it"</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Continuous_Interruptions&diff=15528Continuous Interruptions2013-10-08T11:30:10Z<p>Zsoldosp: basic notes on the initial problem proposal</p>
<hr />
<div>e.g.: 3 team, N features, shared build machine with parallel feature tests<br />
when the build is broken, everyone gets feedback about the broken build<br />
information overload => "it's broken again, but surely not by me"<br />
==> address feedback to specific committer (e.g.: mail/irc only to the committers involved in the changeset that triggered the build)<br />
is anyone working on fixing it? => put a sticky on the monitor "I'm fixing it"</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Are_we_doing_improvement_wrong%3F&diff=15527Are we doing improvement wrong?2013-10-08T11:28:34Z<p>Zsoldosp: added initial notes from a non-explicit-scribe</p>
<hr />
<div>== Question: can we improve [eg. system thinking] without bringing in external experts? What is required for it? ==<br />
<br />
* focus on the problem<br />
* belief that you can do it<br />
* slack<br />
* humility (your answer might be wrong)<br />
<br />
Jtf was recommended the Toyota Kata book <br />
<br />
unexpectedly, only contains two katas<br />
<br />
# The improvement kata<br />
# The coaching kata (which is actually walking others through the improvement kata)<br />
<br />
=== Improvement kata ===<br />
<br />
# What is the target condition? (*NOT* the goal/result, but more like "How would we like to see the work/process being done")<br />
# What is the current state<br />
# What are the obstacles/impediments between #1 and #2<br />
# Which one of #3 will you improve<br />
# What is your next PDC (plan-do-check) cycle? When can we go and see what we have learned from that fact?<br />
<br />
=== Managing by means vs. managing by result ===<br />
<br />
* the famous "stop the line" idea was not the first line of defense, i.e.: before stopping the line, workers would first call in a supervisor (by pulling a string) to try to fix the issue locally, and only after this (timeboxed) attempt failed did they stop the line<br />
* in one factory, after some improvements the number of such inspections per shift dropped from 1000 to 700. Is that good? (question was asked to the prepped audience and hence we all answered it probably is a bad thing, though normally people think that if problems dropped by 300 is a Good Thing). In the factory's managements' interpretation it can mean two things:<br />
## People are hiding problems and not calling. This is bad, please don't do it!<br />
## The factory has improved! <br />
*** but we are still not perfect!<br />
*** we are staffed to handle 1000 pulls per shift!<br />
*** .... so they reduced inventory and waste until the factory got back to 1000 pulls per shift again<br />
<br />
---<br />
<br />
Resiliency is hiding problems - the more resilient a system is, the less tolerant it is of errors, and thus, ironically, the less resilient it is<br />
: similar to how you shouldn't do defensive programming (e.g.: explicit null checks), but let your tests catch such errors, and eliminate waste<br />
<br />
It's important to manage/lead for "True improvement" instead of outcomes <br />
<br />
:: aside: the coaching kata has a "loophole", i.e.: coaching stops once customer interests are effected (to address timeliness)<br />
<br />
one cannot jump to the ideal straight away<br />
<br />
retrospectives are backwards and usually try to improve too many ("all wrong") things at once. <br />
<br />
E.g.: at prezi, they explicitly add cards to the wall that the business/product owner did not ask for but the team feels is necessary to do.<br />
<br />
Also, prezi did away with back-to-back iterations, and thus gave people slack time which they can use as they want - to think architecture, design, to refactor, or even to sleep if they want to<br />
<br />
Break up meetings to give people enough time to think - e.g.: the planning meeting was broken up into a short 30 minutes session on Friday, where ideas/features/etc. were proposed/briefly described, and on Monday morning they created the stories/cards from it.<br />
<br />
Problem with outcome metrics: like waterfall QA, it's too late to detect problems<br />
<br />
Foster improvements by the goals you set - e.g.: Toyota once told a supplier to cut costs by 80% - 'coz if they only set a target of 20%, the supplier would just do marginal improvements or cut corners ("cheat"), but for such a huge change, they must rethink how you do things!<br />
<br />
Working on the business is not something you do outside of work but it is work! allocate time for it<br />
<br />
don't wait for the retrospective, but when there is a problem, use it as an occasion for real improvement<br />
<br />
* have one person fix the root cause instead of band-aid quickfixes e.g.: <br />
** we have memory problems, let's not just increase the JVM's heap size, but take a look at why it's happening!<br />
** failing/flickering tests often expose actual bugs (race conditions when two customers see the other's reports instead of their own due to a race condition bug... )<br />
* once you got one such person approach problems with root cause thinking, you can start have him/her do the coaching kata with someone else<br />
<br />
To ensure you can learn from the failures and turn them into a learning opportunity - let the failure go on a little longer, so you can gather evidence/diagnostics (profile, core dump, etc.) - even if the business is loosing money, because it'll pay off in the long term. Of course, use common sense, e.g.: route 90% of the traffick to an error page, and 10% to the failing server to get the needed diagnostic data<br />
<br />
Experiment at TIM group - to encourage systems thinking -: overstaff a project on purpose (didn't work). An understaffed project with more relaxed schedule has been much more promising<br />
<br />
Optimize for learning and not results!<br />
<br />
Look at facts/data points instead of statistics, since statistics can hide outliers. E.g.: routinely investigate the last 30 items<br />
<br />
There should be no sacred cows when optimizing for learning!</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Peter_Zsoldos&diff=15516Peter Zsoldos2013-09-30T14:45:09Z<p>Zsoldosp: edited my own blog's address</p>
<hr />
<div>Programmer with a passion for quality without compromising timely delivery, working in Nueremberg at http://paessler.com.<br />
<br />
Blog: http://zsoldosp.eu<br />
twitter: http://twitter.com/zsepi</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=15515OnTheWeb2013-09-30T10:20:19Z<p>Zsoldosp: update my old posts' links to reflect the blog's moved domain</p>
<hr />
<div>Technorati CITCON tag: http://technorati.com/tag/citcon<br />
<br />
WordPress CITCON tag: http://wordpress.com/tag/citcon/<br />
<br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
<br />
== CITCON Europe 2013 Turin ==<br />
<br />
Peter Zsoldos http://blog.zsoldosp.eu/2013/09/30/citcon-turin-2013/<br />
<br />
== CITCON ANZ 2013 Sydney ==<br />
<br />
https://twitter.com/search/realtime?q=citcon+sydney<br />
<br />
http://www.nztester.co.nz/oztester_files/OZTester01.pdf - Magazine with a write up on the conf (PDF)<br />
<br />
== CITCON Europe 2012 Budapest ==<br />
<br />
Attila Magyar http://athos.blogs.balabit.com/2012/10/citcon-europe-2012-tdd-is-like-sex/<br />
<br />
Željko Filipin http://filipin.eu/citcon-europe-2012-in-budapest/<br />
<br />
[[Viktor Sadovnikov]] http://prezi.com/uufxsflf00hf/citcon-2012/ - Prezi presentation of participation in CITCON<br />
<br />
== CITCON Asia 2012 Singapore ==<br />
<br />
[[Riju Kansal]] http://aaoblogkare.blogspot.co.uk/2012/04/citcon-cool-great-experience.html<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://blog.zsoldosp.eu/2011/11/citcon-london-2011.html<br />
<br />
Skillsmatter (the venue provider) put up the video recorded of the following sessions on their site at http://skillsmatter.com/event/agile-testing/citcon :<br />
<br />
* [[ To_Feature_Branch_Or_Not_To_Feature_Branch ]]<br />
* [[ Moving_an_Agile_Team_from_CI_to_CD ]]<br />
* [[ Configuration_Changes ]]<br />
* [[ Testing_for_Value ]]<br />
* [[ Radiators ]]<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://blog.zsoldosp.eu/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America �07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=15514OnTheWeb2013-09-30T10:18:45Z<p>Zsoldosp: new section for the Turin conference blogs with the first blog entry (mine) linked</p>
<hr />
<div>Technorati CITCON tag: http://technorati.com/tag/citcon<br />
<br />
WordPress CITCON tag: http://wordpress.com/tag/citcon/<br />
<br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
<br />
== CITCON Europe 2013 Turin ==<br />
<br />
Peter Zsoldos http://blog.zsoldosp.eu/2013/09/30/citcon-turin-2013/<br />
<br />
== CITCON ANZ 2013 Sydney ==<br />
<br />
https://twitter.com/search/realtime?q=citcon+sydney<br />
<br />
http://www.nztester.co.nz/oztester_files/OZTester01.pdf - Magazine with a write up on the conf (PDF)<br />
<br />
== CITCON Europe 2012 Budapest ==<br />
<br />
Attila Magyar http://athos.blogs.balabit.com/2012/10/citcon-europe-2012-tdd-is-like-sex/<br />
<br />
Željko Filipin http://filipin.eu/citcon-europe-2012-in-budapest/<br />
<br />
[[Viktor Sadovnikov]] http://prezi.com/uufxsflf00hf/citcon-2012/ - Prezi presentation of participation in CITCON<br />
<br />
== CITCON Asia 2012 Singapore ==<br />
<br />
[[Riju Kansal]] http://aaoblogkare.blogspot.co.uk/2012/04/citcon-cool-great-experience.html<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2011/11/citcon-london-2011.html<br />
<br />
Skillsmatter (the venue provider) put up the video recorded of the following sessions on their site at http://skillsmatter.com/event/agile-testing/citcon :<br />
<br />
* [[ To_Feature_Branch_Or_Not_To_Feature_Branch ]]<br />
* [[ Moving_an_Agile_Team_from_CI_to_CD ]]<br />
* [[ Configuration_Changes ]]<br />
* [[ Testing_for_Value ]]<br />
* [[ Radiators ]]<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America âÂÂ07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=15255ConferencePlanning2013-06-12T07:17:57Z<p>Zsoldosp: adding gov. offices tip to venue search based on Erik Petersen email to the citcon list</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Date & Location selection==<br />
<br />
* happens on the organization mailing lists<br />
* location requirements:<br />
** should have good (international) connections (airport, international railway stations, etc.)<br />
* date considerations<br />
** check for other conferences happening in the area - could hurt if there is a similar event just a week ago (or even on the same day), both when competing for sponsors & attendees. Impossible to achieve perfect schedule, but some places to check are<br />
*** meetup.com<br />
*** lanyard<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Phyisical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
* ask local commerce chambers and/or municipal/governmental Tourism, Events and Economic Development offices if they have any suggestions<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
For examples, see [[Menu from CITCON Sydney 2013]] and [[Menu from CITCON Budapest 2012]].<br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** you'll finalize the order amounts one week prior to the event<br />
** ask for a complete breakdown of items included, have them specify any potential food allergy items i.e. shell fish, gluten free, peanuts, tree nuts, etc.<br />
* what we need the quote for<br />
** Friday evening reception (19:30-21:00)<br />
***delivery time 19:30<br />
*** i.e. finger-food, canapés, hors d'ourves, pizza <br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks, coffee, water<br />
**** cups and ice need to be included<br />
*** beers (and maybe some wine)<br />
**** glasses need to be provided<br />
** Saturday morning breakfast (9:00-10:00)<br />
*** delivery time 8:30<br />
*** i.e. danishes, croissants, muffins, fruit<br />
**** plates, napkins and utensils need to be included<br />
*** coffee, tea, juices, water <br />
**** cups and ice need to be included<br />
** Saturday beverage service - all day<br />
*** coffee and tea<br />
**** cups need to be included<br />
*** snacks are a plus but not required<br />
** Saturday lunch (12:30-14:00)<br />
*** delivery time 12:00<br />
*** i.e. sandwiches, pizza, full catering including hot food<br />
**** a full meal is required, i.e. chips/crisps or fruit should be included with sandwiches<br />
**** plates, napkins and utensils need to be included<br />
*** soft drinks<br />
**** ice needs to be included<br />
<br />
===Invoices, Payment===<br />
<br />
* non-English invoices are fine<br />
* Invoices should be addressed to the OIF (Open Information Foundation, PO Box 1812, North Sioux City, SD 57049)<br />
* available payment options are credit card, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=14836ConferencePlanning2012-11-14T21:26:48Z<p>Zsoldosp: on picking a date & location</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Date & Location selection==<br />
<br />
* happens on the organization mailing lists<br />
* location requirements:<br />
** should have good (international) connections (airport, international railway stations, etc.)<br />
* date considerations<br />
** check for other conferences happening in the area - could hurt if there is a similar event just a week ago (or even on the same day), both when competing for sponsors & attendees. Impossible to achieve perfect schedule, but some places to check are<br />
*** meetup.com<br />
*** lanyard<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Phyisical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross.<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** that you'll finalize the order amounts then <br />
* what we need the quote for<br />
** Friday evening reception (7:30pm-9pm)<br />
*** fingerfood<br />
*** soft drinks & coffee<br />
*** beers (and maybe some wine)<br />
** Saturday morning breakfast (8-9am)<br />
*** coffee, tea<br />
*** breakfast<br />
** Saturday, 3 coffee breaks<br />
*** soft drinks & coffee<br />
*** snacks are a plus but not required<br />
** Saturday, Lunch (12:30-14:00)<br />
*** soft drinks & coffee<br />
*** food - in the past we had everything from delivered sandwiches, pizza, and full catering warm meals<br />
<br />
===Invoices, Payment===<br />
<br />
* AFAIK, non-English invoices are fine. <br />
* Invoices are due for the OIF<br />
* available payment options are creditcard, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=14835ConferencePlanning2012-11-14T21:19:38Z<p>Zsoldosp: added catering notes</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Phyisical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
<br />
==Catering==<br />
<br />
The easiest solution is when the venue already has a catering firm they routinely work with. <br />
<br />
If that's not the case, just search for location name & catering, and ask them for a quote.<br />
<br />
Also, while the word "catering" is used, it doesn't have to mean waiters - delivered food with plastic utensils can be just as OK<br />
<br />
While it helps if the vendor's people speak English, as long as one of the CITCON volunteers can communicate with them, it's OK. <br />
<br />
===Quotes===<br />
<br />
* give them our budget - be sure to explicitly say whether the amount is net or gross.<br />
* also, emphasize that you want the quote with the final number - most firms do this, but just to be on the safe side<br />
* tell them that registration only closes about a week before the event, and its implications<br />
** ask for multiple quote variations (different menus) - tell them the current number of registrants and the maximum amount of people<br />
** that you'll finalize the order amounts then <br />
* what we need the quote for<br />
** Friday evening reception (7:30pm-9pm)<br />
*** fingerfood<br />
*** soft drinks & coffee<br />
*** beers (and maybe some wine)<br />
** Saturday morning breakfast (8-9am)<br />
*** coffee, tea<br />
*** breakfast<br />
** Saturday, 3 coffee breaks<br />
*** soft drinks & coffee<br />
*** snacks are a plus but not required<br />
** Saturday, Lunch (12:30-14:00)<br />
*** soft drinks & coffee<br />
*** food - in the past we had everything from delivered sandwiches, pizza, and full catering warm meals<br />
<br />
===Invoices, Payment===<br />
<br />
* AFAIK, non-English invoices are fine. <br />
* Invoices are due for the OIF<br />
* available payment options are creditcard, bank transfer, cash (in this order of preference)<br />
<br />
===Event logistics===<br />
<br />
* make sure the catering and the venue people know each others contact details (get permission from both sides)<br />
* be sure they have discussed the logistics (will there be someone in the morning at the venue when the catering people show up? Or can they enter the building?)<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once you get the hang of it, you can do a lot in a week, even if you make a daily quota of reaching out to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=14834ConferencePlanning2012-11-14T20:45:24Z<p>Zsoldosp: marketing notes based on the Budapest experience</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Phyisical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php<br />
<br />
<br />
==Marketing for attendees==<br />
<br />
Some of the groups & communities below are the same as the ones mentioned in the venue search - not surprisingly :)<br />
<br />
* email usergroup/meetup leaders to announce on their groups ([http://sethgodin.typepad.com/ permission marketing a'la Seth Godin])<br />
* Linkedin, xing (in German speaking areas the latter is more popular)<br />
* reach out to other events' hosts (e.g.: coderetreat, devopsdays, etc.)<br />
* past relevant conferences in the area (see how far to reach out below)<br />
* exchange advertisments/mentions with other upcoming conferences in the area<br />
* twitter - always make it personal, and take it offline (email) once rapport is established<br />
* reach out to topical podcasts (e.g.: [https://twitter.com/foodfightshow @foodfightshow], [https://twitter.com/ShipShowPodcast @ShipShowPodcast], and probably a ton of others)<br />
<br />
it requires a bit more work than just broadcasting your message (aka tweeting into the void), but not much much more, and once<br />
you get the hang of it, you can do a lot in a week, even if you make a daily quote of reaching out <br />
to 2-3 people<br />
<br />
===How far to reach out for attendees?===<br />
<br />
Not sure about the rest of the world, but in Europe people are quite happy to travel, so having people from Finland attend the conference in Budapest is normal. Starting with the venue location, advertise in an ever growing radius</div>Zsoldosphttp://citconf.com/wiki/index.php?title=ConferencePlanning&diff=14833ConferencePlanning2012-11-14T20:36:51Z<p>Zsoldosp: notes added based on my experiences searching for the Budapest venue</p>
<hr />
<div>==How to Run a CITCON==<br />
The organizers use a pretty straight forward process for running the CITCON conferences. Below are the details.<br />
<br />
JTF and PJ are known for their classic opening speech for the conference. They have been doing the same speech since nearly the inception of CITCON. [[Opening Speech|More details...]]<br />
<br />
==Venue Search==<br />
Finding a suitable venue for CITCON can be challenging. It takes some creative searching. As a non-profit conference, we try to minimize the venue cost as much as possible. That tends to be the biggest hurdle. Here are the criteria for a venue that would typically be good for hosting a CITCON event.<br />
<br />
===Phyisical requirements===<br />
<br />
* One larger room, and 3 or 4 smaller rooms<br />
** We usually have one large room that can accomodate everyone at the conference (125) with 3 or 4 smaller rooms for breakout sessions that run in parallel.<br />
** We arrange the chairs in circles, instead of traditional classroom style. That changes the number of people that fit into one room.<br />
** We frequently use concentric circles to increase the capacity in the room.<br />
<br />
===Where to find to find no cost/very low cost venues===<br />
Frequently we try to seek out a venue that would be "sponsored" by the company that owns the space. For example, [http://www.citconf.com/singapore2012/ Bank of America/Merrill Lynch in Singapore].<br />
<br />
* Look at existing communities and the venues they have used<br />
** coderetreat.org<br />
** meetup.com<br />
** classic user groups<br />
** free to attend conferences<br />
** etc.<br />
* educational institutions<br />
** Second tier but upcoming universities - established leading colleges are not only renting place, but also endorse you via their reputation, and thus for a(n often significan) cost. It works in the reverse with the next group of unis that would benefit from hosting a conference<br />
** high schools with an emphasis on IT in their curriculum<br />
* (tech) training companies - they already have the venue & the experience and hosting is a kind of advertisement for them<br />
* big companies with big offices that are keen on hiring/building a cool IT company image<br />
* startup hubs/centers, coworking spaces - especially ones that already run events<br />
* might be worth asking headhunters if you know any that are more than just staffing agencies if they know of such a company<br />
<br />
===Nice to haves for a venue===<br />
<br />
* they have run events before<br />
* they have an established catering firm they work with<br />
<br />
===Choosing a venue===<br />
<br />
* probably any venue you consider describing to the list is gonna be good enough. <br />
* having a floor plan helps the committee<br />
* choosing between multiple potential venues (unless the price difference is enermous): go with the one<br />
** where the venue people have been more enthusiastic about hosting the conference<br />
** which felt more responsive during the talks/emails<br />
<br />
==Conference Registration==<br />
Once the website has been setup, for example [http://www.citconf.com/sydney2013/ the Sydney 2013 site], the organizers decide when to open registration. Once agreed upon, the following steps are followed to create the [http://www.eventwax.com/ EventWax] event and link it in to the CITCON conference site.<br />
<br />
===Create Event===<br />
# Log in to https://citcon.eventwax.com/admin/account/login<br />
#* For obvious reasons, the username and password are not included on this page. Email the committee mailing list to get authorization to do this.<br />
# Click the "Events" drop down and select "New Event".<br />
# Fill in the Event Name, e.g. "CITCON Sydney 2013".<br />
# Fill in the Venue, e.g. "Sydney Marriott".<br />
# Fill the Capacity, e.g. 150<br />
#* We have traditionally always set the capacity to 150. That allows 150 people to register. We expect about one-third no-show. So, we expect about 100 people to attend the conference. Sometimes it is more. Sometimes it is less.<br />
# Set the Currency, e.g. "Australian Dollars"<br />
# Status should be defaulted to "Open".<br />
# Set the Timezone, e.g. "Australia - Sydney".<br />
# Set the Start Date, e.g. "Feb 8, 2013".<br />
# Set the End Date, e.g. "Feb 9, 2013".<br />
# Set the Start Time, e.g. "18:00".<br />
# Set the End Time, e.g. "19:00".<br />
# Click Create Event.<br />
#* The new event should now be listed in the upcoming events on the [https://citcon.eventwax.com/admin admin page].<br />
<br />
===Create Tickets===<br />
# Click on the link for the new event.<br />
# Click the Edit Event tab.<br />
# Click the Ticket Setup tab.<br />
# Change the name for the "Standard Ticket" to "Registration Only".<br />
# Add another ticket type named "Registration + Donation - Generous Amount - Cover Costs Plus Some" set to $100 (local currency units, i.e. 100 pounds, 100 Australia dollars, etc).<br />
# Add another ticket type named "Registration + Donation - Cover Full Costs of One Participant" set to $65 (...see note above about currency units...).<br />
# Add another ticket type named "Registration + Donation - Cover Food Costs of One Participant" set to $32.<br />
# Add another ticket type named "Registration + Donation - Cover TShirt Cost of One Participant" set to $9.<br />
# For all tickets, set the start time to the time when you want people to begin being able to purchase those tickets, e.g. Now.<br />
# For all tickets, set the end time to the time when you want people to stop being able to purchase those tickets, e.g. the Friday one week prior to the start of the conference at 23:45.<br />
# Add any details you like to the "Fine Print", e.g. "* Note that the date for the event MAY change. In the event of a date change, the organizers will attempt to notify all ticket holders as soon as possible."<br />
# Click Update Event.<br />
<br />
===Adjust Promotional Pages===<br />
# Click the Promotional Webpages tab.<br />
# Set "Use EventWax hosted landing page?" to No.<br />
# Change the Return URL to an appropriate page on the CITCON conference site, e.g. http://citconf.com/sydney2013/register_success.php<br />
# In the Ticket Order Form section, click Add Field.<br />
# Name it "Tshirt Size (USA Sizes)".<br />
# Change the Type to Drop Down.<br />
# Check the Required box.<br />
# Set the Options to "Small, Medium, Large, X-Large, XX-Large, XXX-Large, No Shirt"<br />
# Click Update Event.<br />
<br />
===Change the Logo===<br />
# Click the Event Dashboard tab.<br />
# Under Upload New Logo click the Choose File button.<br />
# Upload the logo found at http://citconf.com/_Images/logos/001.png<br />
<br />
===Link the Event Registration to the Conference Site===<br />
This section assumes that you are familiar with editing the website. If not, then email the committee mailing list for help.<br />
# Copy the contents of the file "register.wasopen.php" and paste it into "register.php".<br />
# Confirm that the registration URL matches what was listed on on the EventWax Promotional Webpages, e.g. https://citcon.eventwax.com/citcon-sydney-2013/register<br />
# Double check the rest of the page. Add any comments that are important, e.g. <code>&lt;p&gt;NOTE: The venue for CITCON Syndey has NOT been finalized...</code><br />
# Commit the change and double check the live site, e.g. http://www.citconf.com/sydney2013/register.php</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2012Lodging&diff=14504CITCONEurope2012Lodging2012-09-04T19:23:35Z<p>Zsoldosp: /* Sample hotels & prices: */</p>
<hr />
<div>== Lodging and accomodation information for participants to CITCON Budapest 2012 ==<br />
<br />
Please feel free to add to the information below!<br />
<br />
=== General location ===<br />
<br />
The colabs location is rather central (few hundred meters from the Square "Ferenciek" stop with the (blue) M3 underground (metro)). Some of the streets leading there can be scary, but Petofi Sandor street is pleasant IIRC, as is the Vaci street (well, main tourist) street north of Ferenciek tere. And the Petofi street crosses Iranyi, so you just need to walk towards the Danube there (also, there is streetcar (number 2) stop near the Danube, at the end of the Iranyi street). Ferenciek Square has quite a number of pubs, and Friday/Saturday there are a lot of people (some sober). <br />
<br />
Near almost any underground station you'll run into homeless people - just an FYI.<br />
<br />
=== Sample hotels & prices: ===<br />
<br />
Below is a sample of places really close to the location, with sample price ranges (taken around Sep 2) for one person, checking in on the 19th and checking out on the 20th (two nights). The price range's minimum part is the supersaver, non cancelable, etc. ticket the site offered in the cheapest room, while the max is the opposite. However, '''these prices are only there to give you a sense of ranges, and are not actual offers'''.<br />
<br />
The hotel name is linked to the official site, while afterwards are links to some pages with reviews.<br />
<br />
<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Pilvax], $139-$240 (110 EUR - 191 EUR), [http://www.booking.com/hotel/hu/city-pilvax.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=1303289011;srpos=1 booking.com].<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Matyas], $139-$356 (110 EUR - 282 EUR), [http://www.booking.com/hotel/hu/cityhotelmatyas.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=2973235809;srpos=1 booking.com].<br />
* [http://budapest-marriott.hotel-rez.com/ Mariott], $200-$432 (159 EUR - 344 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d276351-Reviews-Budapest_Marriott_Hotel-Budapest.html tripadvisor.com].<br />
* [http://www.danubiushotels.com/en/our_hotels/hungary/budapest/hotel_erzsebet_city_center Hotel Erzsébet City Center], $165-$260 (131 EUR - 207 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d320348-Reviews-Hotel_Erzsebet_City_Center-Budapest.html tripadvisor.com].<br />
* [http://www.hotelart.hu/ Best Western Hotel Art], $102-$162 (81 EUR - 129 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d276348-Reviews-BEST_WESTERN_Hotel_Art-Budapest.html tripadvisor.com].<br />
* [http://www.promenadehotelbudapest.com/ Promenade Hotel], $101-$145 (80 EUR - 115 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d1473164-Reviews-Promenade_City_Hotel-Budapest.html tripadvisor.com].<br />
* [http://www.maverickhostel.com Maverick Hostel], $35-$55 (28 EUR - 44 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d1391433-Reviews-Maverick_Hostel_Budapest-Budapest.html tripadvisor.com]. note the price is per bed, in shared rooms. They have 2-3-4 bed rooms as well as 10 bed dorms<br />
<br />
<br />
There might be more places, and anything between Deak Square and Kalvin Square is a walkable distance from colabs.<br />
<br />
While the Buda side is also nice, there isn't a really pleasant way to cross the Danube by foot (the closest bridge is 2x3 lanes, some leading out to the highways so walking on the pedestrian's way is not a pleasant experience, and the other bridges are quite a distance away), so plan on taking the public transportation from there.<br />
<br />
<br />
There is also [https://www.airbnb.com/s/Budapest--Ir%C3%A1nyi-Street--Hungary?checkin=10%2F19%2F2012&checkout=10%2F21%2F2012 airbnb], with lower prices than the hotels offer<br />
<br />
=== Public transportation ===<br />
<br />
* [http://bkv.hu/en/ The Budapest Public ransportion Ltd.]<br />
* [http://utvonalterv.hu/ Alternative Route planner, though only in Hungarian]<br />
* smartphone apps - TODO. Keyword to search for is BKV, menetrend (timetable)</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2012Lodging&diff=14503CITCONEurope2012Lodging2012-09-04T19:22:19Z<p>Zsoldosp: /* Sample hotels & prices: */</p>
<hr />
<div>== Lodging and accomodation information for participants to CITCON Budapest 2012 ==<br />
<br />
Please feel free to add to the information below!<br />
<br />
=== General location ===<br />
<br />
The colabs location is rather central (few hundred meters from the Square "Ferenciek" stop with the (blue) M3 underground (metro)). Some of the streets leading there can be scary, but Petofi Sandor street is pleasant IIRC, as is the Vaci street (well, main tourist) street north of Ferenciek tere. And the Petofi street crosses Iranyi, so you just need to walk towards the Danube there (also, there is streetcar (number 2) stop near the Danube, at the end of the Iranyi street). Ferenciek Square has quite a number of pubs, and Friday/Saturday there are a lot of people (some sober). <br />
<br />
Near almost any underground station you'll run into homeless people - just an FYI.<br />
<br />
=== Sample hotels & prices: ===<br />
<br />
Below is a sample of places really close to the location, with sample price ranges (taken around Sep 2) for one person, checking in on the 19th and checking out on the 20th (two nights). The price range's minimum part is the supersaver, non cancelable, etc. ticket the site offered in the cheapest room, while the max is the opposite. However, '''these prices are only there to give you a sense of ranges, and are not actual offers'''.<br />
<br />
The hotel name is linked to the official site, while afterwards are links to some pages with reviews.<br />
<br />
<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Pilvax], $139-$240 (110 EUR - 191 EUR), [), [http://www.booking.com/hotel/hu/city-pilvax.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=1303289011;srpos=1 booking.com].<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Matyas], $139-$356 (110 EUR - 282 EUR), [), [http://www.booking.com/hotel/hu/cityhotelmatyas.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=2973235809;srpos=1 booking.com].<br />
* [http://budapest-marriott.hotel-rez.com/ Mariott], $200-$432 (159 EUR - 344 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d276351-Reviews-Budapest_Marriott_Hotel-Budapest.html tripadvisor.com].<br />
* [http://www.danubiushotels.com/en/our_hotels/hungary/budapest/hotel_erzsebet_city_center Hotel Erzsébet City Center], $165-$260 (131 EUR - 207 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d320348-Reviews-Hotel_Erzsebet_City_Center-Budapest.html tripadvisor.com].<br />
* [http://www.hotelart.hu/ Best Western Hotel Art], $102-$162 (81 EUR - 129 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d276348-Reviews-BEST_WESTERN_Hotel_Art-Budapest.html tripadvisor.com].<br />
* [http://www.promenadehotelbudapest.com/ Promenade Hotel], $101-$145 (80 EUR - 115 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d1473164-Reviews-Promenade_City_Hotel-Budapest.html tripadvisor.com].<br />
* [http://www.maverickhostel.com Maverick Hostel], $35-$55 (28 EUR - 44 EUR), [), [http://www.tripadvisor.com/Hotel_Review-g274887-d1391433-Reviews-Maverick_Hostel_Budapest-Budapest.html tripadvisor.com]. note the price is per bed, in shared rooms. They have 2-3-4 bed rooms as well as 10 bed dorms<br />
<br />
<br />
There might be more places, and anything between Deak Square and Kalvin Square is a walkable distance from colabs.<br />
<br />
While the Buda side is also nice, there isn't a really pleasant way to cross the Danube by foot (the closest bridge is 2x3 lanes, some leading out to the highways so walking on the pedestrian's way is not a pleasant experience, and the other bridges are quite a distance away), so plan on taking the public transportation from there.<br />
<br />
<br />
There is also [https://www.airbnb.com/s/Budapest--Ir%C3%A1nyi-Street--Hungary?checkin=10%2F19%2F2012&checkout=10%2F21%2F2012 airbnb], with lower prices than the hotels offer<br />
<br />
=== Public transportation ===<br />
<br />
* [http://bkv.hu/en/ The Budapest Public ransportion Ltd.]<br />
* [http://utvonalterv.hu/ Alternative Route planner, though only in Hungarian]<br />
* smartphone apps - TODO. Keyword to search for is BKV, menetrend (timetable)</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2012Lodging&diff=14502CITCONEurope2012Lodging2012-09-04T19:16:55Z<p>Zsoldosp: Created page with "== Lodging and accomodation information for participants to CITCON Budapest 2012 == Please feel free to add to the information below! === General location === The colabs lo..."</p>
<hr />
<div>== Lodging and accomodation information for participants to CITCON Budapest 2012 ==<br />
<br />
Please feel free to add to the information below!<br />
<br />
=== General location ===<br />
<br />
The colabs location is rather central (few hundred meters from the Square "Ferenciek" stop with the (blue) M3 underground (metro)). Some of the streets leading there can be scary, but Petofi Sandor street is pleasant IIRC, as is the Vaci street (well, main tourist) street north of Ferenciek tere. And the Petofi street crosses Iranyi, so you just need to walk towards the Danube there (also, there is streetcar (number 2) stop near the Danube, at the end of the Iranyi street). Ferenciek Square has quite a number of pubs, and Friday/Saturday there are a lot of people (some sober). <br />
<br />
Near almost any underground station you'll run into homeless people - just an FYI.<br />
<br />
=== Sample hotels & prices: ===<br />
<br />
Below is a sample of places really close to the location, with sample price ranges (taken around Sep 2) for one person, checking in on the 19th and checking out on the 20th (two nights). The price range's minimum part is the supersaver, non cancelable, etc. ticket the site offered in the cheapest room, while the max is the opposite. However, '''these prices are only there to give you a sense of ranges, and are not actual offers'''.<br />
<br />
The hotel name is linked to the official site, while afterwards are links to some pages with reviews.<br />
<br />
<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Pilvax], $139-$240 (110 EUR - 191 EUR), [http://www.booking.com/hotel/hu/city-pilvax.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=1303289011;srpos=1].<br />
* [http://www.cityhotel.hu/en/contact/booking/ City Hotel Matyas], $139-$356 (110 EUR - 282 EUR), [http://www.booking.com/hotel/hu/cityhotelmatyas.en-gb.html?sid=2a9cd185c624795098ea2501f9261d1f;dcid=1;origin=disamb;srhash=2973235809;srpos=1].<br />
* [http://budapest-marriott.hotel-rez.com/ Mariott], $200-$432 (159 EUR - 344 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d276351-Reviews-Budapest_Marriott_Hotel-Budapest.html].<br />
* [http://www.danubiushotels.com/en/our_hotels/hungary/budapest/hotel_erzsebet_city_center Hotel Erzsébet City Center], $165-$260 (131 EUR - 207 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d320348-Reviews-Hotel_Erzsebet_City_Center-Budapest.html].<br />
* [http://www.hotelart.hu/ Best Western Hotel Art], $102-$162 (81 EUR - 129 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d276348-Reviews-BEST_WESTERN_Hotel_Art-Budapest.html].<br />
* [http://www.promenadehotelbudapest.com/ Promenade Hotel], $101-$145 (80 EUR - 115 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d1473164-Reviews-Promenade_City_Hotel-Budapest.html].<br />
* [http://www.maverickhostel.com Maverick Hostel], $35-$55 (28 EUR - 44 EUR), [http://www.tripadvisor.com/Hotel_Review-g274887-d1391433-Reviews-Maverick_Hostel_Budapest-Budapest.html]. note the price is per bed, in shared rooms. They have 2-3-4 bed rooms as well as 10 bed dorms<br />
<br />
There might be more places, and anything between Deak Square and Kalvin Square is a walkable distance.<br />
<br />
While the Buda side is also nice, there isn't a really pleasant way to cross the Danube by foot (the closest bridge is 2x3 lanes, some leading out to the highways so walking on the pedestrian's way is not a pleasant experience, and the other bridges are quite a distance away), so plan on taking the public transportation from there.<br />
<br />
<br />
There is also [https://www.airbnb.com/s/Budapest--Ir%C3%A1nyi-Street--Hungary?checkin=10%2F19%2F2012&checkout=10%2F21%2F2012 airbnb], with lower prices than the hotels offer<br />
<br />
=== Public transportation ===<br />
<br />
* [http://bkv.hu/en/ The Budapest Public ransportion Ltd.]<br />
* [http://utvonalterv.hu/ Alternative Route planner, though only in Hungarian]<br />
* smartphone apps - TODO. Keyword to search for is BKV, menetrend (timetable)</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Radiators&diff=12276Radiators2012-02-05T10:24:59Z<p>Zsoldosp: video link added</p>
<hr />
<div>==Radiators==<br />
[[Tom Denley]] ran a session on using information radiators.<br />
<br />
===What To Radiate===<br />
* CI build information<br />
* CI load<br />
* Code clean-up graphs<br />
* Twitter<br />
* Prod status?<br />
<br />
===How To Radiate===<br />
* Big plasma<br />
* Multi-screen wall<br />
* Screens dotted about<br />
* Desktop application<br />
* Writing on the wall<br />
* Digital picture frames<br />
<br />
===Case Study: Radiating CI Build Information===<br />
* Builds passing/failing<br />
* Builds running/waiting<br />
* Running build progress bar<br />
* Time since last build<br />
* Committers on the current build<br />
* Failing builds marked under investigation<br />
* DOH! -- everything is red, but don't panic I'm on it<br />
<br />
===Tips===<br />
* Be wary of information overload<br />
* Be opinionated<br />
* Have fun<br />
<br />
===Demo of CI-Eye===<br />
Tom gave a demonstration of CI-Eye, an open-source build radiator that he developed whilst learning about radiators.<br />
<br />
For more information on CI-Eye, see [http://github.com/netmelody/ci-eye/wiki]<br />
<br />
===Demo of Visuwall===<br />
A demo of the Visuwall radiator was given by two of its creators.<br />
<br />
For more information on Visuwall, see [http://github.com/awired/visuwall]<br />
<br />
==Video Recording of the Session==<br />
http://skillsmatter.com/podcast/agile-testing/radiators</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Testing_for_Value&diff=12275Testing for Value2012-02-05T10:24:01Z<p>Zsoldosp: video link added</p>
<hr />
<div>[[Colin Humphreys]] explained something along the lines of [http://blog.hatofmonkeys.com/blog/2011/11/06/automating-value/ automating testing value]. [[Julian Simpson]] suggested sharing ideas with the [http://groups.google.com/group/cukes Cucumber mailing list], which [[Colin Humphreys]] is going to do.<br />
<br />
The video recording of the session is available at http://skillsmatter.com/podcast/agile-testing/test-delivering-value</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Configuration_Changes&diff=12274Configuration Changes2012-02-05T10:22:53Z<p>Zsoldosp: /* Configuration changes/Release Rolling Back vs.Rolling Forward Session */</p>
<hr />
<div>==Configuration changes/Release Rolling Back vs.Rolling Forward Session==<br />
<br />
===Planning release steps while maintaining invariants===<br />
<br />
* Andy Parker's master thesis<br />
* https://github.com/zaphod42/Coeus<br />
* start from a cluster configuration<br />
* how do you roll out a new service while keeping things going<br />
* There can be no SPOF<br />
* Define a new language (think Prolog like) to describe rules/policies -> turn declarative policies-based language into puppet execution plan<br />
* match execution plans (goal based) against policies<br />
* provisioning large systems<br />
* idea: model-checking failing systems<br />
* applying modely-checking to sysadmin<br />
* real world failures are complex, how do you model them? Problem with all model checking approaches<br />
<br />
===Why does it seem to be that so few plan for reverting releases? ===<br />
<br />
* discussion starting point: tools are concerned with going forward, so are teams. Usually no explicit backout plans, or if there is, rarely tested - when some of it can be automated (contrast it with the 3am call and hacking a bugfix forward)<br />
* problematic naming: rollback is a bad word, backout is better<br />
* you cannot roll-back time<br />
* continuous rolling forward: what happens when something goes wrong during deployment?<br />
* migrating databases? Whole concept of db refactoring (see Scott W. Ambler's book)<br />
* django south, rails migrations, etc. <br />
* link w/ application architecture: isolating things prevents failure propagation<br />
* migration use different data models<br />
* need a 3rd pipeline to build the data (after code, infrastructure)<br />
* eg. anonymizing data : cannot rollback, need to be done in production<br />
* once you got forward there are two many paths to go back<br />
* depends on your scenario? What's the difference between roll-forward/roll-back<br />
* fail in unexpected way (corrupting data could affect your application)<br />
* "stopping time" by switching systems (maintain parallel installations of systems)<br />
* easy to have a default rollback for mainline scenario, without losing newly gathered data (e.g.: added a new field to signup form, this needs to be backed out, we can remove field, and keep all data, even customer's that have signed up after the release)<br />
* what about featuretoggles? Could be used to handle suche cases.<br />
* basic issue w/ the idea of rolling-back: means losing data, you cannot rollback your data<br />
* you should implement a rollback scenario if you can (depends on the risk, costs...)<br />
* the effort to do it correctly is much higher than most people do<br />
* snapshot: need to be in a consistent state<br />
* no way to rollback after some time has passed (eg. deploy in weekend, failure occurs in week days)<br />
* if rollback is not possible, be aware of it and prepared to roll forward<br />
* come up with a design where you don't have to do it: lowers the risk enough...<br />
* clever system allow to dit by connection, by user, by feature<br />
* allow to tune for some users, provide some resource consuming feature to part of users, not to users<br />
* DI is better than feature branch for doing that<br />
* deploy schema changes alongside the code<br />
* just add to database, do not removing anything - all older versions of the app can use the new schema (consider meaningful defaults, and beware of the potential performance hit you are taking with increased record size)<br />
* featuretoggles used to test new database<br />
* deploying schemas in advance give your more confidence (but does not solve the rollback problem) - database shadowing, so it's like the additive only schema changes, just temporarily and not forever<br />
* running live data through a secondary installation that contains the old version<br />
* event sourcing provides the ability to replay stuff<br />
* pb: how much time does it take?<br />
* but the events have schemas themselves...<br />
* finding ways to mitigate your inability to do anything about something going wrong<br />
* reducing the barrier to going in production: being minutes away from delivering<br />
* how do we make people more aware of the problem? lot of developers have not worked on the ops part, dealing with the unexpected<br />
* Google engineers are on ops for a month after pushing a new release of a soft<br />
* product teams actually run the software (not always feasible due to regulations)<br />
* the whole forward/backwards discussion is not concerned with undoing multiple releases<br />
<br />
<br />
====Some scenarios given that you can't recover from in a planned way====<br />
<br />
* the new release of the application starts to generate gibberish data. How do you downgrade to the previous version and restore old data and clean data that has been generated since?<br />
* does your backout script work when the release has not completed, but failed halfway through?<br />
* what do you do with large amounts of data (though this might already be a problem for the actual release)?<br />
<br />
<br />
And unfortunately database level application integration (many apps read-write the same database tables) is not yet extinct.<br />
<br />
==Video Recording of the Session==<br />
<br />
http://skillsmatter.com/podcast/agile-testing/rolling-back-rolling-forward</div>Zsoldosphttp://citconf.com/wiki/index.php?title=To_Feature_Branch_Or_Not_To_Feature_Branch&diff=12273To Feature Branch Or Not To Feature Branch2012-02-05T10:21:09Z<p>Zsoldosp: /* Feature Branching vs. Feature Toggles */</p>
<hr />
<div>==Topic proposals that were merged into this sesion==<br />
<br />
* What makes a build a release?<br />
* How does Continuous Delivery effect the rest of the organization (sales, marketing, etc.), especially for a product, and not a SaaS company?<br />
** there weren't many people with such experience<br />
** hallway conversation suggested to check how fast existing customers react to updates - no point releasing if they don't use it<br />
* Feature Branching vs. Feature Toggles<br />
<br />
<br />
==Feature Branching vs. Feature Toggles==<br />
<br />
* we thought the branching discussion was resolved years ago, but now they are back with git! (any links to the old discussions?)<br />
* long lived branches cause problems<br />
* tools are better than they used to be<br />
* long live feature branches can cause problems - nested if hell if not removed quickly after the release<br />
* both require a lot of discipline<br />
* any practice that prevents you from refactoring is inherently a bad practice<br />
* both of these practices only seem to cause problems on larger teams<br />
* only try any of the approaches if you really have to!<br />
* CI tools would be great if they could handle multiple versions of dependencies, and should use their IDLE time to build these<br />
** what if I merged this branch to this other branch? would all tests pass? <br />
** warn if violating backwards compatibility - e.g.: in a large team, with an eclipse like plugin architecture, if I built my plugin against an older release, it should work with all releases since, so when I go to work on this plugin again, I can be assured that I can upgrade my dependency to the latest without worrying about potential issues, so that I don't have an excuse to stick with the old version<br />
<br />
'''A release is a build with confidence!'''<br />
<br />
==Video Recording of the Session==<br />
<br />
* http://skillsmatter.com/podcast/agile-testing/to-future-branch-or-not-to-future-branch</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Moving_an_Agile_Team_from_CI_to_CD&diff=12272Moving an Agile Team from CI to CD2012-02-05T10:19:57Z<p>Zsoldosp: initial edit, adding skillsmatter video link</p>
<hr />
<div>A video of the session is online at http://skillsmatter.com/podcast/agile-testing/citcon-ci-to-cd</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=12271OnTheWeb2012-02-05T10:17:59Z<p>Zsoldosp: /* CITCON Europe 2011 London UK */</p>
<hr />
<div>Technorati CITCON tag: http://technorati.com/tag/citcon<br />
<br />
WordPress CITCON tag: http://wordpress.com/tag/citcon/<br />
<br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2011/11/citcon-london-2011.html<br />
<br />
Skillsmatter (the venue provider) put up the video recorded of the following sessions on their site at http://skillsmatter.com/event/agile-testing/citcon :<br />
<br />
* [[ To_Feature_Branch_Or_Not_To_Feature_Branch ]]<br />
* [[ Moving_an_Agile_Team_from_CI_to_CD ]]<br />
* [[ Configuration_Changes ]]<br />
* [[ Testing_for_Value ]]<br />
* [[ Radiators ]]<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America âÂÂ07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html<br />
<br />
[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html reverse lookup]<br />
<br />
[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup cell]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=12270OnTheWeb2012-02-05T10:15:58Z<p>Zsoldosp: /* CITCON Europe 2011 London UK - added links to skillsmatter videos */</p>
<hr />
<div>Technorati CITCON tag: http://technorati.com/tag/citcon<br />
<br />
WordPress CITCON tag: http://wordpress.com/tag/citcon/<br />
<br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2011/11/citcon-london-2011.html<br />
<br />
Skillsmatter (the venue provider) put up the video recorded of the following sessions on their site at http://skillsmatter.com/event/agile-testing/citcon :<br />
<br />
http://citconf.com/wiki/index.php?title=To_Feature_Branch_Or_Not_To_Feature_Branch<br />
http://citconf.com/wiki/index.php?title=Moving_an_Agile_Team_from_CI_to_CD<br />
http://citconf.com/wiki/index.php?title=Configuration_Changes<br />
http://citconf.com/wiki/index.php?title=Testing_for_Value<br />
http://citconf.com/wiki/index.php?title=Radiators<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America âÂÂ07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html<br />
<br />
[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html reverse lookup]<br />
<br />
[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup cell]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=OnTheWeb&diff=11166OnTheWeb2011-11-17T09:05:24Z<p>Zsoldosp: link to a blog post about citcon 2011</p>
<hr />
<div>Technorati CITCON tag: http://technorati.com/tag/citcon<br />
<br />
WordPress CITCON tag: http://wordpress.com/tag/citcon/<br />
<br />
LinkedIn Group: http://www.linkedin.com/e/gis/132660/0011DE7A82CA<br />
<br />
See also [[Photos]]<br />
<br />
== CITCON Europe 2011 London UK ==<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2011/11/citcon-london-2011.html<br />
<br />
== CITCON Europe 2010 London UK ==<br />
[[Eric Lefevre-Ardant]] http://ericlefevre.net/wordpress/2010/11/08/citcon-london-2010/<br />
<br />
[[Gojko Adzic]] http://gojko.net/2010/11/09/beyond-basic-tdd/<br />
<br />
[[Peter Zsoldos]] http://zsoldosp.blogspot.com/2010/11/my-citcon-london-2010-experience.html<br />
<br />
== CITCON Europe 2009 Paris France ==<br />
[[Gojko Adzic]] http://gojko.net/2009/09/19/citcon-europe-09/ http://gojko.net/2009/09/21/mocks-are-not-about-isolation-but-about-responsibilities/ http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/<br />
<br />
[[Joe Schmetzer]] http://www.exubero.com/joe/2009/09/citcon-europe-2009/<br />
<br />
[[Nicolas Martignole]] [http://www.touilleur-express.fr/2009/09/20/citcon-2009-paris/ CITCON 2009] (in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-done-and-testing/ Done and Testing] (also in French), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-mock-mock-and-mock/ mock, mock and mock] (in French too), [http://www.touilleur-express.fr/2009/09/20/citcon-2009-user-acceptance-test/ user acceptance tests] (yes, in French)<br />
<br />
[[Anthony Dahanne]] http://blog.dahanne.net/2009/09/18/citcon-europe-2009-paris/<br />
<br />
[[Jérôme Van Der Linden]] http://www.javasioux.fr/blog/2009/09/20/compte-rendu-citcon-paris-2009/ (in French), and also on [http://blog.octo.com/compte-rendu-citcon-paris-2009/ Octo's blog] (in French)<br />
<br />
[[Antony Marcano]] http://www.testingreflections.com/node/view/8274<br />
<br />
[[Zouheir Cadi]] [http://www.parisjug.org/xwiki/bin/view/Blog/LeParisJugAuCITCON Paris JUG at CITCON] (in French)<br />
<br />
[[Romain Linsolas]] http://linsolas.free.fr/pro-blog/blog4.php/2009/09/21/citconf-paris-2009-autour-des-sessions (in French)<br />
http://linsolas.developpez.com/articles/conferences/citconf2009/ (in French)<br />
<br />
[[Emmanuel Servent]] http://blog.xebia.fr/2009/09/21/citcon-paris-2009/ (in French)<br />
<br />
[[Eric Lefevre-Ardant]] [http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ on mock objects], [http://ericlefevre.net/wordpress/2009/09/22/faster-tests-at-citcon-paris-2009/ on faster test], [http://ericlefevre.net/wordpress/2009/09/23/citcon-paris-2009-a-personal-retrospective-of-the-organization/ on the organization], and [http://ericlefevre.net/wordpress/2009/09/28/predictions-for-citcon-europe-2009/ on the CITCON Europe 2009 predictions]<br />
<br />
[[Xavier Bourguignon]] [http://social.hortis.ch/2009/09/24/citcon-paris-2009-le-compte-rendu/ Hortis at CITCON] (in French)<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2009-in-Paris.aspx<br />
<br />
[[Thibaut Van Spaandonck]] http://thibautvs.com/blog/?p=1001<br />
<br />
[[Fabien Duminy]] CITCON Europe 2009 : [http://www.duminy.fr/blog/?p=970&language=en in English] [http://www.duminy.fr/blog/?p=970&language=fr in French]<br />
<br />
[[Jason Sankey]] [http://www.alittlemadness.com/2009/10/02/citcon-paris-2009/ CITCON Paris 2009: Distributed SCMs] and [http://www.alittlemadness.com/2009/10/09/citcon-paris-2009-mocks-ci-servers-and-acceptance-testing/ CITCON Paris 2009: Mocks, CI Servers and Acceptance Testing]<br />
<br />
== CITCON Australia/New Zealand 2009 Brisbane Queensland ==<br />
<br />
[[Craig Smith]] http://cds43.wordpress.com/2009/07/06/wrap-up-from-citcon-brisbane/<br />
<br />
[[Alex Garrett]] http://lexecorp.com/2009/06/28/citcon/<br />
<br />
[[Rowly Emmett]] http://rowlyemmett.blogspot.com/2009/06/citcon-brisbane-2009.html<br />
<br />
[[Mirek Rzadkowski]] [http://www.softnexus.com.au/softnexus/citcon.html pencasts]<br />
<br />
== CITCON North America 2009 Minneapolis Minnesota ==<br />
<br />
[[Lisa Crispin]] http://blogs.stickyminds.com/Blogs/tabid/91/EntryId/77/Continuous-Integration-and-Testing.aspx<br />
<br />
== CITCON Europe 2008 Amsterdam Netherlands ==<br />
<br />
[[Eric Lefevre]] : [http://ericlefevre.net/wordpress/2008/10/05/back-from-citcon-europe-amsterdam-2008/ back from CITCON Amsterdam], [http://ericlefevre.net/wordpress/2008/10/07/scrum-is-evil/ Is Scrum evil?], [http://ericlefevre.net/wordpress/2008/10/08/coding-dojo-on-legacy-code/ coding dojo on legacy code]<br />
<br />
[[Harald Walker]] : [http://www.bitwalker.nl/blog/citcon-europe-2008-–-less-is-more thinks with open space that less is more]<br />
<br />
[[Hinse ter Schuur]] : has posted [http://blog4h.blogspot.com/2008/10/citcon-europe-2008.html one], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-2.html two], [http://blog4h.blogspot.com/2008/10/citcon-europe-2008-3.html three] different posts with notes from his sessions.<br />
<br />
[[Jason Gorman]] : [http://parlezuml.com/blog/?postid=702 in brief]<br />
<br />
[[Jason Sankey]] : [http://www.alittlemadness.com/2008/10/09/citcon-amsterdam-2008-retrospective/ favorite session was Flickering Builds]<br />
<br />
[[Jean-Michel Garnier]] : [http://21croissants.blogspot.com/2008/10/back-from-citcon-amsterdam-2008.html is also back from CITCON Amsterdam]<br />
<br />
[[Markus Hjort]] : [http://www.jroller.com/mhjort/entry/citcon_europe_2008_first_impressions CITCON Amsterdam first impressions]<br />
<br />
[[Olivier Gaudin]] : [http://sonar.codehaus.org/back-from-citcon-europe-2008-in-amsterdam/ posted thoughts on several sessions]<br />
<br />
[[Patrick Debois]] : was [http://www.jedi.be/blog/2008/10/09/citcon-2008-amsterdam/ convinced to go deeper into development]<br />
<br />
[[Yegor Yarko]] : [http://teamcitydev.blogspot.com/2008/10/citcon-amsterdam-2008.html is ready to meet at the next CITCON Europe]<br />
<br />
[[Matt Wynne]]: [http://blog.mattwynne.net/2008/10/08/is-the-value-fetish-killing-agile-teams/ on the value fetish]<br />
<br />
[[Willem van den Ende]]: [http://me.andering.com/2008/10/21/as-a-programmer-i-want-to-go-to-a-coders-dojo-so-that-i-can-improve-my-skills/ on the coding dojo]<br />
<br />
[[Zouheir Cadi]]: [http://www.parisjug.org/xwiki/bin/view/Blog/LeCITCONestfiniviveleprochainCITCON Don't miss the next European CITCON]<br />
<br />
[[Pierre-Emmanuel Dautreppe]]: http://www.pedautreppe.com/post/CITCON-2008-in-Amsterdam---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2008 Melbourne Australia ==<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=78 On his first night in Melbourne]<br />
<br />
[[Ronald Sunarno]] : [http://ronaldwidha.net/askbobo/event-log/citcon-anz-2008-in-melbourne/ .Net Developer had fun at CITCON]<br />
<br />
[[Tim Koopmans]] : [http://90kts.com/blog/2008/citcon-2008-melbourne/ CITCON 2008 Melbourne]<br />
<br />
[[Zutubi]] : [http://www.alittlemadness.com/2008/06/27/zutubi-citcon-asia-pacific-2008 Zutubi announces their presence at CITCON]<br />
<br />
[[Ben Kelly]] : [http://www.testjutsu.com/citcon-melbourne-2008-initial-thoughts-and-impressions Ben's initial thoughts on CITCON Melbourne]<br />
<br />
[[Colin Goudie]] : [http://gommo.tributech.net/?p=79 Thoughts on "Session Day"]<br />
<br />
[[Mark Derricutt]] : [http://www.talios.com/citcon_2008__somerset_on_elizabeth.htm Impressed by his hotel room and the conference venue]<br />
<br />
[[Eddy Pronk]]: [http://www.muftor.com/blog/?p=7 lessons learned on CITCON]<br />
<br />
[[Nigel Charman]]: [http://tutansblog.blogspot.com/2008/07/citcon-melbourne-08.html CITCON Melbourne '08]<br />
<br />
[[Stuart Moncrieff]]: [http://www.jds.net.au/news/melbourne-citcon-2008/ JDS at CITCON Asia-Pacific 2008]<br />
<br />
== CITCON North America 2008 Denver Colorado ==<br />
<br />
[[Andrew Binstock]]: [http://binstock.blogspot.com/2008/04/easy-does-it-with-easyb.html Easy Does It With easyb]<br />
<br />
[[Paul Holser]]: [http://cleveralias.blogs.com/thought_spearmints/2008/04/citcon-north-am.html shares his thoughts on CITCON Denver]<br />
<br />
[[Ben Rady]]: [http://benrady.typepad.com/radyology/2008/04/citcon-rocks.html says CITCON Rocks!]<br />
<br />
[[David Vydra]]: [http://www.testdriven.com/modules/news/article.php?storyid=678 is happy he went to CITCON]<br />
<br />
[[Jeff Peters]]: [http://www.xaware.org/myblog/citcon-continuous-integration-and-testing-conference-north-america-2008-in-denver-colorado.html recaps the sessions he attended]<br />
<br />
[[RJ Bruneel]]: [http://www.opensourceconnections.com/2008/04/08/a-skeptics-perspective-on-the-openspace-conference-format/ was skeptical about the open space format but convinced by the experience]. [http://www.opensourceconnections.com/2008/04/14/continuous-integration-and-testing-conference-citcon-in-denver-colorado/ he also wrote up some notes].<br />
<br />
[[Mark Waite]]: [http://blog.360.yahoo.com/blog-4B.afOU8erSVU28a2FPKRNU-?cq=1&p=251 was impressed by the people at the conference] and still needs to write about the conference results...<br />
<br />
[[Lisa Crispin]]: [http://lisacrispin.blogspot.com/2008/06/citcon-takeaways.html CITCON Denver takeaways]<br />
<br />
== CITCON Europe 2007 Brussels Belgium ==<br />
<br />
[[Erik Doernenburg]]: [http://erik.doernenburg.com/2007/10/20/citcon/ CITCON - CCMenu announcement]<br />
<br />
[[Marc Evers]]: [http://blog.piecemealgrowth.net/citcon-europe-2007-2/ CITCON Europe 2007]<br />
<br />
[[Eric Lefevre]]: [http://ericlefevre.net/wordpress/2007/10/24/back-from-citcon-brussels-2007/ Back from CITCON], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-jester-jumble/ Jester & Jumble], [http://ericlefevre.net/wordpress/2007/10/24/citcon-brussels-2007-hudson/ Hudson]. [http://ericlefevre.net/wordpress/2008/04/28/implementation-of-creating-change-one-tic-tac-at-a-time/ Talks about a Hudson plugin using some of the ideas from past CITCONs].<br />
<br />
[[Andrew Binstock]] [http://binstock.blogspot.com/2007/10/citcon-brussels-2007.html on Why CITCON?]<br />
<br />
[[Ivan Moore]] [http://ivan.truemesh.com/archives/000720.html recaps CITCON Brussels]. And is [http://ivan.truemesh.com/archives/000734.html looking forward to CITCON Amsterdam]<br />
<br />
[[Pierre-Emmanuel Dautreppe]] http://www.pedautreppe.com/post/CITCON-2007-in-Brussels---Part-2.aspx<br />
<br />
== CITCON Asia-Pacific 2007 Sydney Australia ==<br />
<br />
[[User:Talios|Mark Derricutt]]'s blog entries on CITCON: http://www.talios.com/tags/?/citcon<br />
<br />
[[Jason Yip]]'s [http://jchyip.blogspot.com/2007/07/key-take-away-points-from-citcon-asia.html key take away points]<br />
<br />
[[Erik Petersen]]'s [http://www.testingreflections.com/node/view/5775 mini-review] and mentions-CITCON-in-Passing <br />
[http://www.testingreflections.com/node/view/5773 musing] on Levi technique<br />
<br />
[[Kristan Vingrys]]'s blog entry on CITCON: [http://www.vinktank.com/test-automation/test-code-is-as-important-as-production-code/ one of my key take away points]<br />
<br />
[[tomjadams|Tom Adams']] [http://adams.id.au/blog/2007/08/citcon-2007/ comments]<br />
<br />
The [http://www.alittlemadness.com/2007/07/31/citcon-retrospective/ Zutubi retrospective]<br />
<br />
== CITCON North America 2007 Dallas Texas ==<br />
<br />
Jason Huggins pictures taken with his MacBook: http://picasaweb.google.com/jrhuggins/CITCONNorthAmerica2007<br />
<br />
Eric Pugh's blog entries on CITCon: [http://blog.opensourceconnections.com/?s=citcon OpenSource Connections]<br />
<br />
[[Chris Turner]]'s summary: [http://bestfriendchris.com/blog/2007/04/30/citcon-north-america-07 CITCON North America âÂÂ07]<br />
<br />
[[Andy Glover]]: http://thediscoblog.com/2007/04/28/whats-after-ant/<br />
<br />
David O'Hara: http://blog.davidohara.net/2007/05/01/citcon-2007/<br />
<br />
Vandana Shah: http://www.developertesting.com/archives/month200705/20070504-CITCONOpenSpaceConferenceRocks.html<br />
<br />
[[Matt Smith]]: http://netsmith.blogspot.com/2007/05/continuous-integration-and-testing.html<br />
<br />
[[Elisabeth Hendrickson]]: http://www.testobsessed.com/2007/05/01/the-power-of-community/<br />
<br />
[[Jason Darling]]: http://blogs.dovetailsoftware.com/blogs/jason_darling/archive/2007/05/11/citcon-2007-review.aspx<br />
<br />
== CITCON Europe 2006 London England ==<br />
<br />
Ivan Moore: http://ivan.truemesh.com/archives/000651.html<br />
<br />
Mike Cannon-Brookes: http://blogs.atlassian.com/rebelutionary/archives/2006/10/citcon_london_2.html<br />
<br />
http://www.flickr.com/photos/87709569@N00/sets/72157594318666513/<br />
<br />
Julian Simpson: http://juliansimpson.blogspot.com/2006/10/citcon-was-awesome.html<br />
<br />
Willem van den Ende: http://me.andering.com/2006/10/08/citcon-london-2006-photos/ <br/><br />
[http://www.willemvandenende.com/photos/?Qwd=./2006/citcon&Qiv=thumbs&Qis=S Willem's pictures]<br />
<br />
[[Eric Lefevre]]: http://ericlefevre.net/wordpress/2006/10/08/citcon-london-2006/<br />
* [http://ericlefevre.net/pictures/06_07_citcon/subalbum_1_slideshow.html Eric's pictures]<br />
* [http://ericlefevre.net/wordpress/2006/10/16/taking-notes-visibly-to-everyone/ Taking Notes Visibly to Everyone]<br />
* [http://ericlefevre.net/wordpress/2006/10/13/citcon-and-the-culture-of-ci-before-installing-cruisecontrol-beyond-installing-it/ The Culture of CI ]<br />
* [http://ericlefevre.net/wordpress/2006/10/11/citcon-and-random-figures/ CITCON and Random Figures]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/citcon-and-technical-excellence/ CITCON and technical excellence]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/ci-and-offshore/ CI and Offshore]<br />
* [http://ericlefevre.net/wordpress/2006/10/10/remote-cruisecontrol/ Remote (Cruise)Control: Amazon EC2]<br />
* [http://ericlefevre.net/wordpress/2006/10/09/open-space-technology/ Open Space Technology]<br />
<br />
Joe Schmetzer: http://www.exubero.com/blog/20061012_CITCON_London_2006_Retrospective.html<br />
<br />
Owen Evans:<br />
* [http://www.bgeek.net/node/199 Argument Driven Design]<br />
* [http://www.bgeek.net/node/198 CITCON Roundup]<br />
* [http://www.bgeek.net/node/195 CITCON London]<br />
<br />
Michael Kloss: http://www.clau-mich.de/weblog/archives/2006/10/#e2006-10-07T08_40_34.txt<br />
<br />
== CITCON North America 2006 Chicago Illinois ==<br />
<br />
http://java.about.com/b/a/256847.htm<br />
<br />
James Shore: http://www.jamesshore.com/Blog/Citcon-in-London.html<br />
<br />
[[Jason Huggins]]: http://www.jrandolph.com/blog/2006/04/10/does-a-testing-tool-prove-the-functionality-of-software/<br />
<br />
Al Wick: http://wickidcool.com/modules.php?op=modload&name=News&file=article&sid=44&mode=thread&order=0&thold=0<br />
<br />
Nola: http://phpgirl.blogspot.com/2006/04/never-dull-moment.html</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Organizational_Anthropology&diff=11157Organizational Anthropology2011-11-16T20:12:08Z<p>Zsoldosp: I was late for the session, thus incomplete notes</p>
<hr />
<div>* ...<br />
* existing current bad systems has evolved at one reasonable choice at a time - it was reasonable back then<br />
* there are teams where everyone, when interviewed individually, points out the same problem, but no action is taken, because it's assumed that the others want it this way<br />
* position based vs. value based proposals - the former prevents compromise, the later enables it (e.g.: I want to achieve this goal, and in the past I've used chef to get there. But note I'm interested in the result, not in using chef).<br />
* ...</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2011Sessions&diff=11156CITCONEurope2011Sessions2011-11-16T20:06:08Z<p>Zsoldosp: /* 16:30-17:45 Sessions */</p>
<hr />
<div>===10:00-11:15 Sessions===<br />
[[Root Cause Analysis]] by Squirrel<br />
<br />
[[Aramis: Why do projects fail]] by Eric Lefevre-Ardent<br />
<br />
[[Moving an Agile Team from CI to CD]]<br />
<br />
===11:15-12:30 Sessions===<br />
[[Dev and Ops and System Ops oh my]] by Squirrel<br />
<br />
[[To Feature Branch Or Not To Feature Branch]]<br />
<br />
===13:30-15:00 Sessions===<br />
<br />
[http://citconf.com/wiki/index.php?title=Configuration_Changes Configuration Changes, Rolling Back vs Rolling Forward]]<br />
<br />
[[What can we learn from CI]] by Benjamin Mitchell<br />
<br />
===15:00-16:30 Sessions===<br />
[[Do you use your tests in prod]]<br />
<br />
===16:30-17:45 Sessions===<br />
[[Radiators]] by [[Tom Denley]]<br />
<br />
[[Organizational Anthropology]] by [[Jeffrey Fredrick]]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2011Sessions&diff=11155CITCONEurope2011Sessions2011-11-16T20:05:12Z<p>Zsoldosp: /* 16:30-17:45 Sessions */</p>
<hr />
<div>===10:00-11:15 Sessions===<br />
[[Root Cause Analysis]] by Squirrel<br />
<br />
[[Aramis: Why do projects fail]] by Eric Lefevre-Ardent<br />
<br />
[[Moving an Agile Team from CI to CD]]<br />
<br />
===11:15-12:30 Sessions===<br />
[[Dev and Ops and System Ops oh my]] by Squirrel<br />
<br />
[[To Feature Branch Or Not To Feature Branch]]<br />
<br />
===13:30-15:00 Sessions===<br />
<br />
[http://citconf.com/wiki/index.php?title=Configuration_Changes Configuration Changes, Rolling Back vs Rolling Forward]]<br />
<br />
[[What can we learn from CI]] by Benjamin Mitchell<br />
<br />
===15:00-16:30 Sessions===<br />
[[Do you use your tests in prod]]<br />
<br />
===16:30-17:45 Sessions===<br />
[[Radiators]] by [[Tom Denley]]<br />
[[Organizational Anthropology]] by [[Jeffrey Fredrick]]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Do_you_use_your_tests_in_prod&diff=11153Do you use your tests in prod2011-11-16T19:51:26Z<p>Zsoldosp: more notes added (Peter Zsoldos), formatting</p>
<hr />
<div>* Ward Cunningham combines Eclipse foundation testing and documentation, in a way that's almost like reusing tests for monitoring.<br />
* Colin using cucumber tests for load testing and cucumber-nagios. Cucumber annotation allows you to push a test to cucumber-nagios.<br />
<br />
** One of his clients tests through prod to world pay with the test credit card.<br />
** Hibri's company uses a real credit card and refunds the payment.<br />
<br />
* Patrick wrote special cucumber tests to validate things in production.<br />
<br />
* JTF floats the idea that good testing in prod is important. Several people agreed that canary releases were the way to find out that your code REALLY works in prod, not just in abstract.<br />
<br />
* Claude says that functional tests suck at this, performance tests are much better. <br />
<br />
* 3 out of 30 or 40 are using functional tests in prod.<br />
* 2 of those people are in ops. Last is working on getting involved with ops team.<br />
<br />
* 6-8 out of the same group actually do perf tests.<br />
<br />
* JTF and Colin suggest that issues with NFR's are the cause of the gap.<br />
<br />
* JTF suggests that people will work with the tools available to solve a problem before they reach out to others. <br />
<br />
* Colin explains that they are having trouble making a thirdparty testing system play with their system and wants APIs to reduce duplication.<br />
<br />
* I think we need a sauce labs for perf testing. We should ask Jason Huggins while he's there.<br />
<br />
* Adrian says that developers must write the performance tests, and they continuously run them. <br />
* Claude says that perf tests can cause issues while being run, when they are blended. <br />
* Colin's issue is duplication in separate pipeline phases.<br />
* Adrian works in finance they have performance tests, and Colin works for web site owners who want a certain amount of capacity, and for many different clients. <br />
* Peter uses in-memory infrastructure to improve developer feedback, before using real - rerunning the same tests with different configs<br />
* Colin applies more realistic tests, after the 5 minute rule.<br />
* The pattern on different drivers is used, ala webdriver.<br />
* gradual releases (first enable 1% of users, then 2%, etc.) is reactive performance testing, and in some situations, you can't afford it (too few clients, or too big business impact if you upset them)<br />
<br />
<br />
Big discussions on page object pattern: http://code.google.com/p/selenium/wiki/PageObjects<br />
<br />
Firebug HTA performance info can be parsed.<br />
<br />
Squirrel points out that render time is different for different browsers<br />
Tools discussed:<br />
<br />
- Page speed <br />
- TSUNG. uses erlang. but has record and reply<br />
- blitz.io gives 1000 concurrent connections.<br />
- Appdynamics<br />
- Dynatrace<br />
- New Relic<br />
<br />
<br />
Expect monitoring and testing to become more integrated in the future<br />
<br />
Not mentioned in the discussion, but the copy of the Testing Club (news)paper given away at the conference has a nice introductory article on the topic: http://www.thetestingplanet.com/2011/11/the-future-of-software-testing-part-one-testing-in-production/</div>Zsoldosphttp://citconf.com/wiki/index.php?title=To_Feature_Branch_Or_Not_To_Feature_Branch&diff=11152To Feature Branch Or Not To Feature Branch2011-11-16T19:37:19Z<p>Zsoldosp: Peter Zsoldos's Notes</p>
<hr />
<div>==Topic proposals that were merged into this sesion==<br />
<br />
* What makes a build a release?<br />
* How does Continuous Delivery effect the rest of the organization (sales, marketing, etc.), especially for a product, and not a SaaS company?<br />
** there weren't many people with such experience<br />
** hallway conversation suggested to check how fast existing customers react to updates - no point releasing if they don't use it<br />
* Feature Branching vs. Feature Toggles<br />
<br />
<br />
==Feature Branching vs. Feature Toggles==<br />
<br />
* we thought the branching discussion was resolved years ago, but now they are back with git! (any links to the old discussions?)<br />
* long lived branches cause problems<br />
* tools are better than they used to be<br />
* long live feature branches can cause problems - nested if hell if not removed quickly after the release<br />
* both require a lot of discipline<br />
* any practice that prevents you from refactoring is inherently a bad practice<br />
* both of these practices only seem to cause problems on larger teams<br />
* only try any of the approaches if you really have to!<br />
* CI tools would be great if they could handle multiple versions of dependencies, and should use their IDLE time to build these<br />
** what if I merged this branch to this other branch? would all tests pass? <br />
** warn if violating backwards compatibility - e.g.: in a large team, with an eclipse like plugin architecture, if I built my plugin against an older release, it should work with all releases since, so when I go to work on this plugin again, I can be assured that I can upgrade my dependency to the latest without worrying about potential issues, so that I don't have an excuse to stick with the old version<br />
<br />
'''A release is a build with confidence!'''</div>Zsoldosphttp://citconf.com/wiki/index.php?title=Configuration_Changes&diff=11151Configuration Changes2011-11-16T19:24:29Z<p>Zsoldosp: Incorporated other notes (Peter Zsoldos)</p>
<hr />
<div>==Configuration changes/Release Rolling Back vs.Rolling Forward Session==<br />
<br />
===Planning release steps while maintaining invariants===<br />
<br />
* Andy Parker's master thesis<br />
* https://github.com/zaphod42/Coeus<br />
* start from a cluster configuration<br />
* how do you roll out a new service while keeping things going<br />
* There can be no SPOF<br />
* Define a new language (think Prolog like) to describe rules/policies -> turn declarative policies-based language into puppet execution plan<br />
* match execution plans (goal based) against policies<br />
* provisioning large systems<br />
* idea: model-checking failing systems<br />
* applying modely-checking to sysadmin<br />
* real world failures are complex, how do you model them? Problem with all model checking approaches<br />
<br />
===Why does it seem to be that so few plan for reverting releases? ===<br />
<br />
* discussion starting point: tools are concerned with going forward, so are teams. Usually no explicit backout plans, or if there is, rarely tested - when some of it can be automated (contrast it with the 3am call and hacking a bugfix forward)<br />
* problematic naming: rollback is a bad word, backout is better<br />
* you cannot roll-back time<br />
* continuous rolling forward: what happens when something goes wrong during deployment?<br />
* migrating databases? Whole concept of db refactoring (see Scott W. Ambler's book)<br />
* django south, rails migrations, etc. <br />
* link w/ application architecture: isolating things prevents failure propagation<br />
* migration use different data models<br />
* need a 3rd pipeline to build the data (after code, infrastructure)<br />
* eg. anonymizing data : cannot rollback, need to be done in production<br />
* once you got forward there are two many paths to go back<br />
* depends on your scenario? What's the difference between roll-forward/roll-back<br />
* fail in unexpected way (corrupting data could affect your application)<br />
* "stopping time" by switching systems (maintain parallel installations of systems)<br />
* easy to have a default rollback for mainline scenario, without losing newly gathered data (e.g.: added a new field to signup form, this needs to be backed out, we can remove field, and keep all data, even customer's that have signed up after the release)<br />
* what about featuretoggles? Could be used to handle suche cases.<br />
* basic issue w/ the idea of rolling-back: means losing data, you cannot rollback your data<br />
* you should implement a rollback scenario if you can (depends on the risk, costs...)<br />
* the effort to do it correctly is much higher than most people do<br />
* snapshot: need to be in a consistent state<br />
* no way to rollback after some time has passed (eg. deploy in weekend, failure occurs in week days)<br />
* if rollback is not possible, be aware of it and prepared to roll forward<br />
* come up with a design where you don't have to do it: lowers the risk enough...<br />
* clever system allow to dit by connection, by user, by feature<br />
* allow to tune for some users, provide some resource consuming feature to part of users, not to users<br />
* DI is better than feature branch for doing that<br />
* deploy schema changes alongside the code<br />
* just add to database, do not removing anything - all older versions of the app can use the new schema (consider meaningful defaults, and beware of the potential performance hit you are taking with increased record size)<br />
* featuretoggles used to test new database<br />
* deploying schemas in advance give your more confidence (but does not solve the rollback problem) - database shadowing, so it's like the additive only schema changes, just temporarily and not forever<br />
* running live data through a secondary installation that contains the old version<br />
* event sourcing provides the ability to replay stuff<br />
* pb: how much time does it take?<br />
* but the events have schemas themselves...<br />
* finding ways to mitigate your inability to do anything about something going wrong<br />
* reducing the barrier to going in production: being minutes away from delivering<br />
* how do we make people more aware of the problem? lot of developers have not worked on the ops part, dealing with the unexpected<br />
* Google engineers are on ops for a month after pushing a new release of a soft<br />
* product teams actually run the software (not always feasible due to regulations)<br />
* the whole forward/backwards discussion is not concerned with undoing multiple releases<br />
<br />
<br />
====Some scenarios given that you can't recover from in a planned way====<br />
<br />
* the new release of the application starts to generate gibberish data. How do you downgrade to the previous version and restore old data and clean data that has been generated since?<br />
* does your backout script work when the release has not completed, but failed halfway through?<br />
* what do you do with large amounts of data (though this might already be a problem for the actual release)?<br />
<br />
<br />
And unfortunately database level application integration (many apps read-write the same database tables) is not yet extinct.</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2011Sessions&diff=11150CITCONEurope2011Sessions2011-11-16T19:05:35Z<p>Zsoldosp: /* 13:30-15:00 Sessions */</p>
<hr />
<div>===10:00-11:15 Sessions===<br />
[[Root Cause Analysis]] by Squirrel<br />
<br />
[[Aramis: Why do projects fail]] by Eric Lefevre-Ardent<br />
<br />
[[Moving an Agile Team from CI to CD]]<br />
<br />
===11:15-12:30 Sessions===<br />
[[Dev and Ops and System Ops oh my]] by Squirrel<br />
<br />
[[To Feature Branch Or Not To Feature Branch]]<br />
<br />
===13:30-15:00 Sessions===<br />
<br />
[http://citconf.com/wiki/index.php?title=Configuration_Changes Configuration Changes, Rolling Back vs Rolling Forward]]<br />
<br />
[[What can we learn from CI]] by Benjamin Mitchell<br />
<br />
===15:00-16:30 Sessions===<br />
[[Do you use your tests in prod]]<br />
<br />
===16:30-17:45 Sessions===<br />
[[Radiators]] by [[Tom Denley]]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2011Sessions&diff=11149CITCONEurope2011Sessions2011-11-16T19:04:49Z<p>Zsoldosp: /* 13:30-15:00 Sessions */</p>
<hr />
<div>===10:00-11:15 Sessions===<br />
[[Root Cause Analysis]] by Squirrel<br />
<br />
[[Aramis: Why do projects fail]] by Eric Lefevre-Ardent<br />
<br />
[[Moving an Agile Team from CI to CD]]<br />
<br />
===11:15-12:30 Sessions===<br />
[[Dev and Ops and System Ops oh my]] by Squirrel<br />
<br />
[[To Feature Branch Or Not To Feature Branch]]<br />
<br />
===13:30-15:00 Sessions===<br />
[[]] <br />
[http://citconf.com/wiki/index.php?title=Configuration_Changes Configuration Changes, Rolling Back vs Rolling Forward]]<br />
<br />
[[What can we learn from CI]] by Benjamin Mitchell<br />
<br />
===15:00-16:30 Sessions===<br />
[[Do you use your tests in prod]]<br />
<br />
===16:30-17:45 Sessions===<br />
[[Radiators]] by [[Tom Denley]]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=User:Zsoldosp&diff=11148User:Zsoldosp2011-11-16T18:54:37Z<p>Zsoldosp: Created page with "See Peter_Zsoldos"</p>
<hr />
<div>See [[Peter_Zsoldos]]</div>Zsoldosphttp://citconf.com/wiki/index.php?title=CITCONEurope2011Registrants&diff=11099CITCONEurope2011Registrants2011-11-14T20:12:25Z<p>Zsoldosp: Created page with "CITCONEurope2011Registrants Seems that unlike last year, this year the list isn't created automatically, so add yourself to the list if you were here. Peter Zsoldos <br/>"</p>
<hr />
<div>CITCONEurope2011Registrants<br />
<br />
Seems that unlike last year, this year the list isn't created automatically, so add yourself to the list if you were here.<br />
<br />
[[Peter Zsoldos]] <br/></div>Zsoldosp