Re: [Publicity] Another reason why our "hackathons" should be called something else

[George Dunlap <George.Dunlap@xxxxxxxxxx>]

I think we should definitely change the name; if I hadn't specifically invited 
Jan Beulich this year, he wouldn't have come, since he naturally assumed that 
it was about extended coding sessions propped up with beer, pizza, and 
caffeine.  I'm pretty sure there are lots of people who might come if they knew 
what it was really about.

"Architecture huddle"?  I might use "scrum" except that's already been taken by 
the Agile folks.

If more people knew Icelandic, we could call it "Xenthing" (after "Althing"[1], 
the yearly meeting that was held in Iceland in the middle ages to pass laws and 
resolve disputes).

Other ideas welcome...

 -George

[1] http://en.wikipedia.org/wiki/Althing
________________________________________
From: publicity-bounces@xxxxxxxxxxxxxxxxxxxx 
[publicity-bounces@xxxxxxxxxxxxxxxxxxxx] on behalf of Amir Chaudhry 
[amc79@xxxxxxxxx]
Sent: 02 December 2014 16:26
To: Lars Kurth
Cc: publicity@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [Publicity] Another reason why our "hackathons" should be  called 
something else

While calling them 'Meetings' might appeal to industrial partners (a 
work-related, expensable visit?), it might turn off potential attendees.

Of course, you could just call the same event different things for different 
audiences.

Best wishes,
Amir


On 2 Dec 2014, at 16:20, Lars Kurth <lars.kurth.xen@xxxxxxxxx> wrote:

> We should probably call them something else. e.g. Developer Meetings or 
> Design Summit or Developer and Design Meetings (better ideas are welcome)
> It became very clear that the label Hackathon is not very well understood by 
> many people outside the core attendees. For example Intel, Fujitsu, Alibaba 
> and others were quite interested in participating when I explained the 
> concept as it is today. The Hackathon label led them to ignore mails that 
> were sent related to these events in the past
>
> Cheers
> Lars
>
> On 30 Nov 2014, at 15:54, Amir Chaudhry <amc79@xxxxxxxxx> wrote:
>
>> I'm not sure what the context is, since I haven't been at any Xen-related 
>> hackathons before.  However, the linked article doesn't present many 
>> convincing arguments imho and most points have trivial rebuttals.  For me, 
>> most of the impression of an event comes from how it's communicated to 
>> (potential) attendees in advance.
>>
>> As a contrast to a hackathon, you can checkout the OCaml Compiler Hacking 
>> sessions run in Cambridge (see links below). These are fairly relaxed 
>> evenings with food, drinks and occasionally a short talk.  Not everyone does 
>> compiler hacking either -- last time I spent the evening trying to get an 
>> OCaml side-project working.
>>
>> blog: http://ocamllabs.github.io/compiler-hacking/
>> wiki: https://github.com/ocamllabs/compiler-hacking/wiki
>> list: http://lists.ocaml.org/listinfo/cam-compiler-hacking
>>
>> Best wishes,
>> Amir
>>
>> On 28 Nov 2014, at 17:01, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
>>
>>> http://infotrope.net/2014/11/28/why-i-dont-like-hackathons-by-alex-bayley-aged-39-12/
>>>
>>> I don't recognise our events in (most of) that.  But we don't want to
>>> be giving that kind of impression.
>>>
>>> Ian.
>>>
>>> _______________________________________________
>>> Publicity mailing list
>>> Publicity@xxxxxxxxxxxxxxxxxxxx
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity
>>
>>
>> _______________________________________________
>> Publicity mailing list
>> Publicity@xxxxxxxxxxxxxxxxxxxx
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity
>


_______________________________________________
Publicity mailing list
Publicity@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity
_______________________________________________
Publicity mailing list
Publicity@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity