[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
* better gitjour I'm working on it. Should have some goodies up on github as soon as catching up on work and life allows me to surface. Keep on eye of http://github.com/lachlanhardy/gitjour for the funk. (and, preferably, fix my nooby Ruby) * 70 people too many I completely disagree. 70 people is only too many if you don't know them all. The first couple of camps we had a pattern that broke the ice, formed new groups and gave us all awesome inspiration to hack. We didn't have that this time. For future camps, I recommend we structure things a little more to shape the weekend. Sunday afternoon/evening/late night began to feel a lot more like Railscamp than the massive LAN party we'd been having until then. I say we go back to the stupid introductory ice-breaking activities that everybody thinks are kinda lame. They are. We know. But they *work*. You get to meet other cool people and learn what they're into. It's heaps more fun hacking with folks you don't meet with regularly cause it broadens just about everything you can learn from them / with them So bring back crazy ruby-oriented pizza making. Or Half-baked. Or some ruby and/or web quiz. Anything as long as everybody has to participate in mixed random teams that they don't get to pick. This can be introduced via the welcome to Railscamp and intro to the rules and facilities (which is also a nice way to make sure generous folks like Nigel don't spend an hour cleaning up after everyone on the first morning). So that should deal with breaking the ice, meeting new peeps and forming new groups. Then we need some inspiration: First thing. Blog the fuck out of railscamp. Talk about what you like about it, what you want to do there. What you want to build. Point folks to your code for existing projects or map out plans for new ones. We should set up some aggregration based on #railscamp to get your ideas to everybody (and your post-camp love after you get home!) Butchers paper/ whiteboards should be made available from the start of the camp for organising sessions for Saturday and Sunday (this can also get pimped in the welcome). But what I'd really love to see is lightning talks on the Friday night. Show off shizzle you've already done. Show off some half-finished project that you'd love to crack on with over the weekend. Show off a new framework or app. Anything really. The idea would be for as many folks as possible to roll through. 5 mins max - even down to 2-3 minutes. The more folks step up and show something, the more we know about each other and the more likely we are to find somebody/something cool that we want to hack with/on. We had this at the first railscamp with Tim's preso on Twatter. Everybody spent the rest of the weekend writing Camping apps. We had it at the second camp with Duke, and Tim's preso-cum-workshop on Git, and Dan asking people why they hadn't used Merb yet then helping them install 0.4(!). The third camp had the *jours and Duke (again!). And Twetter. And... The list goes on. If my agenda for Railscamp could be summarised easily, it would be this: 1. Meet awesome new friends. 2. Start grand crazy projects with them. 3. Demo sexy-delicious-awesomeness. 4. Profit! Just some stuff I've been thinking about since I turned to Tim at about 9pm on Sunday night after the presentations had been flowing thick and fast for nearly 7 hours and said: Now, *this* is railscamp! I'd like to add my congratulations to Radar and Richo, though. Fucking awesome camp, gentlemen. Big ups to all who helped out. And much love for everybody I met. I had a completely sensational time and learned a lot from all of you. Hopefully next time I can meet the rest of you (I think I missed at least 10 peeps), plus some new folks, and we can build something amazing! Lachlan Hardy --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Yo yo. Bigs up all the SA peeps which made it happen, I had an awesome time. I've been talking about the number of people and I don't think that it was necessarily too many just that I have too many friends there now to collaborate and even get to have beers with them all, and also you gotta scale the way you run things with the number of people there. People have always wanted to game at Railscamp, bzflag, UT or otherwise... and we've always wanted guitar hero... and we've always wanted places to chill-out and do serious hacking (I have memories of Lach, Dan and others in the other room last railscamp going hardcore whilst the rest of the camp was fooling around in the main room). Maybe you have to segregate spaces a little bit to let some good stuff happen in isolation... maybe rather than people sitting at the same desk all weekend we make sure everyone knows it's about floating around? Also the Sunday night demos were awesome, glad we started them then and not later (like last time). If we could have that kinda stuff interspersed across the weekend that'd be better. Also maybe we should keep the demos limited to stuff we did *at* Railscamp, make that a little more clear for those who didn't understand (I did like the steak knives though). Some more tools to help a room full of hackage would always be useful— gitorious works but is a bit clunky, the web-based gitjour will be great for discovery of projects etc and I'm sure there's a bunch of other stuff we could all pitch in and build before or at the camp. In regards to letting everyone know what hackery is going on, and helping those who want to get involved, maybe we have a big board called Crazy Cool Projects and Crazy Cool People were you can go put down the name of your project, and people can put their ichat/ twitter name if they're looking for something to hack on. I think as soon as you have something developed you can demo you should be able to take the floor and demo what you built, not wait til Sunday. Maybe some Rules of Railscamp would be awesome again. Stuff like cleaning up (though that seemed to go alright), how to mix gaming/ coding, etc. Some people had mixed opinions about the food but for a *camp* I personally found it spot on. All in all I had an awesome time and can't wait til the next one! -- tim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
On 20/11/2008, at 12:04 PM, Tim Lucas wrote: Some more tools to help a room full of hackage would always be useful— gitorious works but is a bit clunky, the web-based gitjour will be great for discovery of projects etc and I'm sure there's a bunch of other stuff we could all pitch in and build before or at the camp. The web stuff that was added to Gitjour was pretty good...with a little bit more love (perhaps Grit integration to generate sparklines of activity / forking action), leaving that up on the projector would work really well. As people gitjour serve'd their stuff, everyone would see it. Also, someone mentioned that using Gitjour on Linux was impossible, but someone actually did create a fork of Gitjour using Net::DNS::MDNS at the camp. Probably wasn't advertised well enough (probably as a side-effect of the lack of project visibility that everyone's talking about), but this should make it easier for everyone to participate in the *jour action next time around. Cheers, -- Nathan de Vries PS: Radar, remember that I still owe you money (+20% interest for being slack), so that cuts off $100. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Hey, the web gitjour stuff is up on github: http://github.com/DylanFM/sup-gitjour/tree/master 2008/11/20 Nathan de Vries [EMAIL PROTECTED] On 20/11/2008, at 12:04 PM, Tim Lucas wrote: Some more tools to help a room full of hackage would always be useful— gitorious works but is a bit clunky, the web-based gitjour will be great for discovery of projects etc and I'm sure there's a bunch of other stuff we could all pitch in and build before or at the camp. The web stuff that was added to Gitjour was pretty good...with a little bit more love (perhaps Grit integration to generate sparklines of activity / forking action), leaving that up on the projector would work really well. As people gitjour serve'd their stuff, everyone would see it. Also, someone mentioned that using Gitjour on Linux was impossible, but someone actually did create a fork of Gitjour using Net::DNS::MDNS at the camp. Probably wasn't advertised well enough (probably as a side-effect of the lack of project visibility that everyone's talking about), but this should make it easier for everyone to participate in the *jour action next time around. Cheers, -- Nathan de Vries PS: Radar, remember that I still owe you money (+20% interest for being slack), so that cuts off $100. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
:lachie http://smartbomb.com.au http://www.flickr.com/photos/lachie/ On Thu, Nov 20, 2008 at 2:01 PM, Nathan de Vries [EMAIL PROTECTED] wrote: On 20/11/2008, at 12:04 PM, Tim Lucas wrote: Some more tools to help a room full of hackage would always be useful— gitorious works but is a bit clunky, the web-based gitjour will be great for discovery of projects etc and I'm sure there's a bunch of other stuff we could all pitch in and build before or at the camp. The web stuff that was added to Gitjour was pretty good...with a little bit more love (perhaps Grit integration to generate sparklines of activity / forking action), leaving that up on the projector would work really well. As people gitjour serve'd their stuff, everyone would see it. Also, someone mentioned that using Gitjour on Linux was impossible, but someone actually did create a fork of Gitjour using Net::DNS::MDNS at the camp. Probably wasn't advertised well enough (probably as a side-effect of the lack of project visibility that everyone's talking about), but this should make it easier for everyone to participate in the *jour action next time around. I didn't actually realise that this was the issue... or I might have suggested http://github.com/lachie/zeroconf/tree/master A Frankenstein marriage of net-mdns and dnssd. Cheers, -- Nathan de Vries PS: Radar, remember that I still owe you money (+20% interest for being slack), so that cuts off $100. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
I think there should be more c# programming I don't know whether to cry or laugh at that... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Aww now cmon guys, let's not be selective. Let's throw in some COBOL!! On Thu, Nov 20, 2008 at 3:56 PM, Ryan Bigg [EMAIL PROTECTED] wrote: Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Ummm. Can we leave the PHP out? ... and I would love to hear more about Flex/actionscript on the frontend. On 20/11/2008, at 3:56 PM, Ryan Bigg wrote: Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Oh I know! CakePHP! Impostors are so much better than the Real Thing. - Ryan Bigg Freelancer http://frozenplague.net On 20/11/2008, at 3:28 PM, Adam Salter wrote: Ummm. Can we leave the PHP out? ... and I would love to hear more about Flex/actionscript on the frontend. On 20/11/2008, at 3:56 PM, Ryan Bigg wrote: Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
We shouldn't be too harsh on PHP guys, quite a few of us had PHP as a stepping stone ;) On Thu, Nov 20, 2008 at 4:07 PM, Ryan Bigg [EMAIL PROTECTED] wrote: Oh I know! CakePHP! Impostors are so much better than the Real Thing. - Ryan Bigg Freelancer http://frozenplague.net On 20/11/2008, at 3:28 PM, Adam Salter wrote: Ummm. Can we leave the PHP out? ... and I would love to hear more about Flex/actionscript on the frontend. On 20/11/2008, at 3:56 PM, Ryan Bigg wrote: Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
Yes, let's blame everything else for our own inadequacies in development =P Let's also blame the government for letting us getting too drunked and place higher taxes on our alcohol, 'cos we all know that will work! =D On Thu, Nov 20, 2008 at 4:17 PM, Alan Harper [EMAIL PROTECTED] wrote: Myself included. We should be harsh on PHP letting me easily write spaghetti code On 20/11/2008, at 3:14 PM, Torm3nt wrote: We shouldn't be too harsh on PHP guys, quite a few of us had PHP as a stepping stone ;) On Thu, Nov 20, 2008 at 4:07 PM, Ryan Bigg [EMAIL PROTECTED]wrote: Oh I know! CakePHP! Impostors are so much better than the Real Thing. - Ryan Bigg Freelancer http://frozenplague.net On 20/11/2008, at 3:28 PM, Adam Salter wrote: Ummm. Can we leave the PHP out? ... and I would love to hear more about Flex/actionscript on the frontend. On 20/11/2008, at 3:56 PM, Ryan Bigg wrote: Let's throw in some .NET and PHP too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
[rails-oceania] Re: [railscamp] Railscamp 4: What worked well; how can we improve?
On 20/11/2008, at 3:58 PM, Adam Salter wrote: ... and I would love to hear more about Flex/actionscript on the frontend. I've had some joy with Haxe as a way to write Flash to embed in a Rails frontend. The app hasn't gone public yet, but I'll let you know when it does. Haxe is a pretty sweet language, and AS3 isn't that hard to learn. You can use Flex with it, but I haven't. See haxe.org anyhow; it's open source. I've also managed to integrate dragdrop using Prototype, dragging over and dropping on the Flash stage, but it causes redraw funnies in some browsers, incl FF2 on OS/X :-(. I have patches for Prototype to allow that. You can also drag from Flash out to HTML land too, and call functions in both directions, which allows pretty tight integration. I plan to use Haxe a fair bit more in the new year. Clifford Heath. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Ruby or Rails Oceania group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~--~~~~--~~--~--~---
