Hello everybody, 3 weeks ago we had our 1st IRC meeting about the next KohaCon in India. It seems I've been selected to start the discussion about the Hackfest ! We've had 3 KohaCon already : one in France (2006) one in USA (2009), one in NZ (2010). In Marseille, it lasted one week and was mostly about hacking. In USA it lasted 3 days, we had one day (and a half ?) teaching new developers how to hack, then one day hacking In NZ it lasted 3 days too. the 1st day was dedicated to some -technical- lightning talks (http://www.kohacon10.org.nz/2010/hackfest/index.html), then teaching new hackers, then doing a few hacking What should be the hackfest in India then ? We have two goals during those meetings: welcome new developers, and do some real hacking: it's very efficient to work in the same room and without clock/time differences ! I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !) The 1st part would be dedicated to teaching Koha to ppl wanting to know how to join: things like using git, Koha source code organisation, Koha database, working with templates, dealing with translations, submitting patches. kmkale suggested to have 2 days for this part, just before sunday (that would be a day-off) The 2nd part would be dedicated to hacking: showing what is underway, showing POC if applicable (Proof of Concept), playing with bugzilla, writing unit tests,... How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious. So how long should this part last ? kmkale said there will be a room available for us for as long as we want. My proposition would be to say 3 days (mon-wed): not too short, we will be able to do useful things, not too long, we'll be back home on tuesday, before or for the next week-end, back to work next monday. What's your opinion on those ideas ? anything to add ? Feel free to give your opinion, nothing has been decided yet ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
On 22 March 2011 10:07, Paul Poulain <paul.poulain@biblibre.com> wrote:
How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible
+1
What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious.
+1
So how long should this part last ? kmkale said there will be a room available for us for as long as we want. My proposition would be to say 3 days (mon-wed): not too short, we will be able to do useful things, not too long, we'll be back home on tuesday, before or for the next week-end, back to work next monday.
Three days sound good to me! So that would be: Monday-Tuesday-Wednesday: KohaCon Thursday: day off, sightseeing Friday-Saturday: Hackfest part 1 Sunday: day off Monday-Tuesday-Wednesday: Hackfest part 2 if I'm not mistaken? Best regards, Magnus Enger libriotech.no
On Tue, Mar 22, 2011 at 2:37 PM, Paul Poulain <paul.poulain@biblibre.com> wrote:
Hello everybody,
3 weeks ago we had our 1st IRC meeting about the next KohaCon in India. It seems I've been selected to start the discussion about the Hackfest !
We've had 3 KohaCon already : one in France (2006) one in USA (2009), one in NZ (2010). In Marseille, it lasted one week and was mostly about hacking. In USA it lasted 3 days, we had one day (and a half ?) teaching new developers how to hack, then one day hacking In NZ it lasted 3 days too. the 1st day was dedicated to some -technical- lightning talks (http://www.kohacon10.org.nz/2010/hackfest/index.html), then teaching new hackers, then doing a few hacking
What should be the hackfest in India then ? We have two goals during those meetings: welcome new developers, and do some real hacking: it's very efficient to work in the same room and without clock/time differences !
I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !)
The 1st part would be dedicated to teaching Koha to ppl wanting to know how to join: things like using git, Koha source code organisation, Koha database, working with templates, dealing with translations, submitting patches. kmkale suggested to have 2 days for this part, just before sunday (that would be a day-off)
Yes, the conference is from Monday 31st October to Wednesday 2nd November. On Thursday 3rd November, we are tentatively planning a day trip to Mumbai. It will be a nice break after 3 days of conference. ( Nothing is fixed yet about the day trip. It depends on peoples interest. It might not be a bad idea to let me know if you are interested in the day trip as well.. ). We can have the first 2 days "Learning to Hack Koha" or "become a Koha developper" part of Hackfest on Friday 4th November & Saturday 5th November. Then again a break on Sunday 6th November. ( Shopping anyone? ;) )
The 2nd part would be dedicated to hacking: showing what is underway, showing POC if applicable (Proof of Concept), playing with bugzilla, writing unit tests,...
How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious. So how long should this part last ? kmkale said there will be a room available for us for as long as we want. My proposition would be to say 3 days (mon-wed): not too short, we will be able to do useful things, not too long, we'll be back home on tuesday, before or for the next week-end, back to work next monday.
3 days * Hackfest part 2 = "do some hacking" +1 on my part. So it could be from Monday 7th November to Wednesday 9th November.
What's your opinion on those ideas ? anything to add ? Feel free to give your opinion, nothing has been decided yet !
-- Paul POULAIN
Yup, we need feedback from the Koha developer community on this so that the program could be finalised & people can start booking flights and hotels. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2
Paul Poulain wrote:
I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !)
I think splitting it would be helpful, especially if the two parts could take place in parallel somehow. [...]
How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious.
Wow, way to misrepresent the other opinion! :-( I feel most people agree that once we're there, we must make the trip worthwhile, so spend as long as *reasonable*. The difference in opinion is really: what is reasonable? It's *possible* for an Englishman to spend something like 6 months in India, so that's "as long as possible" - would anyone argue for a 6 month KohaCon and hackfest? I think kmkale would get bored with us! Every extra day is extra cost for the Koha libraries which fund that developer and it's probably even more costly than our usual community participation. I'm pretty sure that several developers were working silly hours while in NZ so that they could continue to support their libraries without reducing their participation - that's unhealthy and not to be encouraged IMO; while some were being a burden on colleagues who did/ could not attend because someone was left at home to "watch the shop". As many of us are painfully aware, there are some Koha support companies which are not participating in these events at all. How do we avoid handing them an advantage? In the surveys I've seen and done, most libraries don't care whether or not suppliers take part in hackfests. I wish it wasn't so, but that's how it seems to be. (Anyone got evidence to contradict it?) A basic question is: what is in the hackfest for developers? My biggest limitation is spare time to hack and having a hackspace full of people talking all day doesn't increase that time at all. I feel guilty if I'm in the room but ignoring someone giving a talk! So, change 1: ditch most of the talks, or move them out of the main hackspace, or only have a short one at the start of each session. Change 2: pick themes for at least some sessions. There were a few good possibilities for KohaCon10 hackfest (persistance, template toolkit and 3.6 features would have been my favourites) but I didn't really get time to hack on any of those. It felt like someone stood up with a new theme as soon as one person sat down. Maybe it got less hectic in later days, but that goes back to my earlier points: I feel guilty if I don't watch talks and extra days are expensive. (And in my case in NZ, impossible - because of other constraints, I couldn't take extra days then and I *really* wanted to see Marlborough. I didn't even get to see some stuff in Wellington I wanted to. :-/ ) Thirdly, Change 3: I'd label some of the veteran devs "roamers" for each session and introduce them at the start. Roamers would go from desk to desk, offering helps and seeing what's being hacked, to summarise in a lightning talk at the close. Then those developers are not expecting to hack in that session and there's people who new hackers know they can interrupt without disrupting. I'll stop here for now (having just lost more hacking time) but let me know if anyone likes those change suggestions. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
In my experience (which is limited compared to Paul's and MJ's), it is difficult for me to get any serious hackery done at a hackfest. The real benefit for me comes from being in a room with some of the top minds in my field, sharing ideas and plans, and re-igniting the already-roaring flame of my interest in Koha. I do feel guilty afterwards, when I have no new code to show for my days at the hackfest, but that may be a mis-alignment of expectations. I like MJ's suggestion of splitting up the theory and the practice portions of the hackfest, and running them in parallel. I could see two (or more) rooms working well; one for getting those new to the developer community trained up and interested, and one for quietly coding up bugfixes and new features. The first room can serve as that place to share ideas and interests, to coordinate efforts and draw up 'battle plans', while the second can provide fewer distractions and more concentration for getting the nitty-gritty work done, while still allowing access to some of the brilliant minds of our community. As for how long the hackfest should last, I agree there is a need to balance the overall value of the experience with the expense. The value comes from not only the conference and hackfest, but from taking time to experience India and enrich oneself culturally. The expense is not only the cost of travel, but the cost to our libraries, companies and other institutions of having one of their developers otherwise engaged. So, distilling all those obvious statements down, I think 3-4 days is sufficient, with a couple personal days for travel. Cheers, -Ian On Tue, Mar 22, 2011 at 7:27 AM, MJ Ray <mjr@phonecoop.coop> wrote:
Paul Poulain wrote:
I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !)
I think splitting it would be helpful, especially if the two parts could take place in parallel somehow.
[...]
How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious.
Wow, way to misrepresent the other opinion! :-( I feel most people agree that once we're there, we must make the trip worthwhile, so spend as long as *reasonable*.
The difference in opinion is really: what is reasonable?
It's *possible* for an Englishman to spend something like 6 months in India, so that's "as long as possible" - would anyone argue for a 6 month KohaCon and hackfest? I think kmkale would get bored with us!
Every extra day is extra cost for the Koha libraries which fund that developer and it's probably even more costly than our usual community participation. I'm pretty sure that several developers were working silly hours while in NZ so that they could continue to support their libraries without reducing their participation - that's unhealthy and not to be encouraged IMO; while some were being a burden on colleagues who did/ could not attend because someone was left at home to "watch the shop".
As many of us are painfully aware, there are some Koha support companies which are not participating in these events at all. How do we avoid handing them an advantage?
In the surveys I've seen and done, most libraries don't care whether or not suppliers take part in hackfests. I wish it wasn't so, but that's how it seems to be. (Anyone got evidence to contradict it?)
A basic question is: what is in the hackfest for developers? My biggest limitation is spare time to hack and having a hackspace full of people talking all day doesn't increase that time at all. I feel guilty if I'm in the room but ignoring someone giving a talk!
So, change 1: ditch most of the talks, or move them out of the main hackspace, or only have a short one at the start of each session.
Change 2: pick themes for at least some sessions. There were a few good possibilities for KohaCon10 hackfest (persistance, template toolkit and 3.6 features would have been my favourites) but I didn't really get time to hack on any of those. It felt like someone stood up with a new theme as soon as one person sat down. Maybe it got less hectic in later days, but that goes back to my earlier points: I feel guilty if I don't watch talks and extra days are expensive. (And in my case in NZ, impossible - because of other constraints, I couldn't take extra days then and I *really* wanted to see Marlborough. I didn't even get to see some stuff in Wellington I wanted to. :-/ )
Thirdly, Change 3: I'd label some of the veteran devs "roamers" for each session and introduce them at the start. Roamers would go from desk to desk, offering helps and seeing what's being hacked, to summarise in a lightning talk at the close. Then those developers are not expecting to hack in that session and there's people who new hackers know they can interrupt without disrupting.
I'll stop here for now (having just lost more hacking time) but let me know if anyone likes those change suggestions.
Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
On 2011-03-23, at 12:27 AM, MJ Ray wrote:
Paul Poulain wrote:
I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !)
I think splitting it would be helpful, especially if the two parts could take place in parallel somehow.
yeah, in parallel is a great idea, i think, and easily arranged once we get there... so already experienced developers can skip the 'basic' class, and start working on what looks tricky/important, etc
As many of us are painfully aware, there are some Koha support companies which are not participating in these events at all. How do we avoid handing them an advantage?
yeah, thats a bummer for everyone... :/ but hey!, think for the advantages you/me get for going to a KohaCon... 1 whole years worth of news, info, tips/tricks, work-leads, and genuine friendships with people in other parts of the world cheers, Mason
On Wed, Mar 23, 2011 at 1:59 AM, JAMES Mason <mason@kohaaloha.com> wrote:
On 2011-03-23, at 12:27 AM, MJ Ray wrote:
Paul Poulain wrote:
I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !)
I think splitting it would be helpful, especially if the two parts could take place in parallel somehow.
yeah, in parallel is a great idea, i think, and easily arranged once we get there...
so already experienced developers can skip the 'basic' class, and start working on what looks tricky/important, etc
As many of us are painfully aware, there are some Koha support companies which are not participating in these events at all. How do we avoid handing them an advantage?
yeah, thats a bummer for everyone... :/
but hey!, think for the advantages you/me get for going to a KohaCon...
1 whole years worth of news, info, tips/tricks, work-leads, and genuine friendships with people in other parts of the world
cheers, Mason _______________________________________________
So is there a consensus emerging here about splitting the hackfest and running in parallel? If yes, what days and dates? If we take a break on Thursday 3rd November, then we get Friday 4th November and may be we can work through the weekend, so that everyone can get back sooner OR we can break for weekend and continue from Monday 7th??? Lets come to some conclusion on this, so that people who want to participate in the Hackfest can plan their itinerary. Regards kmkale
Le 26/03/2011 05:44, Koustubha Kale a écrit :
So is there a consensus emerging here about splitting the hackfest and running in parallel? About splitting yes, about running in parallel, i'm still not convinced. Let me explain My main concern here is: if we run in parallel will put more pressure on experienced developers: we can't be at the same time teaching & hacking. So I'm afraid the success will heavily depend on how many experienced devs there will be ! And I think/suspect that this number won't be so high... I'm happy to teach ppl, but hacking together is invaluable too. I don't want to miss one part.
I've another concern: having some rest. In USA, we didn't stop at all. Same in NZ. In France, we had a full week-end for visiting (well, not me, as I was at home), and started the hackfest on monday morning, highly motivated & rested.
If yes, what days and dates? If we take a break on Thursday 3rd November, then we get Friday 4th November and may be we can work through the weekend, so that everyone can get back sooner OR we can break for weekend and continue from Monday 7th??? I think trying to concentrate everything on a single week is a mistake. We had better resting/visiting during the week-end and starting on monday. The idea of thursday break friday/saturday teaching, sunday break, mon->wed hacking sounds really a good idea to me: will let us have some rest to be efficient for work phases.
Is it an option to have the conference finish on friday, week-end resting, then a full week of teaching/hacking ? (was what we did in France in 2006) my 2cts -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Paul Poulain wrote:
Le 26/03/2011 05:44, Koustubha Kale a écrit :
So is there a consensus emerging here about splitting the hackfest and running in parallel? About splitting yes, about running in parallel, i'm still not convinced.
OK, so we have a consensus on part of it!
Let me explain My main concern here is: if we run in parallel will put more pressure on experienced developers: we can't be at the same time teaching & hacking. So I'm afraid the success will heavily depend on how many experienced devs there will be ! And I think/suspect that this number won't be so high...
Firstly, you can't have more than a few experienced developers teaching at the same time. The others are being disruptive (typing and talking) or being disrupted (being quiet). Secondly, let me go to the place where we've not dared: if it looks like there won't be enough experienced developers at the hackfest, should the conference look to use some sponsorship money to pay enough expenses to attract more? Would users like that? Would any experienced developers hate it or want to put any restrictions on payments? (Like: all are offered the same amount.) How do we define experienced developers anyway?
I've another concern: having some rest. In USA, we didn't stop at all. Same in NZ. In France, we had a full week-end for visiting (well, not me, as I was at home), and started the hackfest on monday morning, highly motivated & rested.
I feel that the plan in NZ was much better than the one in France. A weekend is long enough that funders will see it as a natural break, an opportunity for people to attend one part and not the other, but not long enough to travel far. I think it is better to keep the event together and let people visit things before or after. Mentioning France brings another thing to my mind: what ways can we have for people not physically there to take part in the hackfest? How was that for people in NZ? I think Nicole's blogging and the IRC were pretty good for the little bit of time when I was not physically there, available and had an internet conenction, but how was it for people not there at all? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
On Mon, Mar 28, 2011 at 3:40 PM, MJ Ray <mjr@phonecoop.coop> wrote:
Paul Poulain wrote:
Le 26/03/2011 05:44, Koustubha Kale a écrit :
So is there a consensus emerging here about splitting the hackfest and running in parallel? About splitting yes, about running in parallel, i'm still not convinced.
OK, so we have a consensus on part of it!
Let me explain My main concern here is: if we run in parallel will put more pressure on experienced developers: we can't be at the same time teaching & hacking. So I'm afraid the success will heavily depend on how many experienced devs there will be ! And I think/suspect that this number won't be so high...
Firstly, you can't have more than a few experienced developers teaching at the same time. The others are being disruptive (typing and talking) or being disrupted (being quiet).
Secondly, let me go to the place where we've not dared: if it looks like there won't be enough experienced developers at the hackfest, should the conference look to use some sponsorship money to pay enough expenses to attract more?
Would users like that?
Would any experienced developers hate it or want to put any restrictions on payments? (Like: all are offered the same amount.)
How do we define experienced developers anyway?
I've another concern: having some rest. In USA, we didn't stop at all. Same in NZ. In France, we had a full week-end for visiting (well, not me, as I was at home), and started the hackfest on monday morning, highly motivated & rested.
I feel that the plan in NZ was much better than the one in France.
A weekend is long enough that funders will see it as a natural break, an opportunity for people to attend one part and not the other, but not long enough to travel far. I think it is better to keep the event together and let people visit things before or after.
Mentioning France brings another thing to my mind: what ways can we have for people not physically there to take part in the hackfest?
How was that for people in NZ? I think Nicole's blogging and the IRC were pretty good for the little bit of time when I was not physically there, available and had an internet conenction, but how was it for people not there at all?
Thanks, -- MJ Ray (slef),
Changing the main conference dates is no good. We already have over 100 registrations from 16 countries. The dates have been well publicized in several mailing lists. To run parallel sessions, arranging for two large rooms with wi-fi should not be a major problem. For expert people ( a limited few, mind you, due to bandwidth) we can provide video conferencing ( both inward and outward ) even during Hackfest. Its an additional cost but I am hoping we will get enough sponsorship. Here is what I suggest : 1) We break for a day after the main conference on Thursday 3rd November. 2) We start Hackfest in two separate nearby rooms one for teaching / getting started sessions the other room for experienced developers to hack together at peace. The experienced developers take breaks turn by turn to deliver sessions / guidance in the first room. This goes on for two days Friday 4th November and Saturday 5th November. Experienced developers who can not be physically present but would still like to participate in the hackfest, we will try to accommodate through video conferencing. Frankly I don't know how thats gonna work for hacking together, but atleast they can deliver some guidance / tips to the newbies. End of day two of hackfest i.e. on Saturday 5th November, the developers who can not stay more can leave but they would still have had two days of hacking together. 3) Those developers who can stay more are free to continue hacking again from Monday 7th November for as long as they want. I am sure we will find a place for them to work for as long as it takes. How does that sound? Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2
Here is what I suggest : 1) We break for a day after the main conference on Thursday 3rd November. 2) We start Hackfest in two separate nearby rooms one for teaching / getting started sessions the other room for experienced developers to hack together at peace. The experienced developers take breaks turn by turn to deliver sessions / guidance in the first room. This goes on for two days Friday 4th November and Saturday 5th November. Experienced developers who can not be physically present but would still like to participate in the hackfest, we will try to accommodate through video conferencing. Frankly I don't know how thats gonna work for hacking together, but atleast they can deliver some guidance / tips to the newbies. End of day two of hackfest i.e. on Saturday 5th November, the developers who can not stay more can leave but they would still have had two days of hacking together. 3) Those developers who can stay more are free to continue hacking again from Monday 7th November for as long as they want. I am sure we will find a place for them to work for as long as it takes. Hi, How does that sound? My fear is that most of the devs will flight back during the week-end if 3) is not announced/organised. We must propose something very clearly, not just say "stay as long as you want". That's also a must-have for ppl that have a boss and must argue that
Le 28/03/2011 12:45, Koustubha Kale a écrit : they must stay for one more week. For example, I think Katrin will have some difficulties to argue & convince her boss ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
On Tue, Mar 29, 2011 at 5:06 PM, Paul Poulain <paul.poulain@biblibre.com> wrote:
Here is what I suggest : 1) We break for a day after the main conference on Thursday 3rd November. 2) We start Hackfest in two separate nearby rooms one for teaching / getting started sessions the other room for experienced developers to hack together at peace. The experienced developers take breaks turn by turn to deliver sessions / guidance in the first room. This goes on for two days Friday 4th November and Saturday 5th November. Experienced developers who can not be physically present but would still like to participate in the hackfest, we will try to accommodate through video conferencing. Frankly I don't know how thats gonna work for hacking together, but atleast they can deliver some guidance / tips to the newbies. End of day two of hackfest i.e. on Saturday 5th November, the developers who can not stay more can leave but they would still have had two days of hacking together. 3) Those developers who can stay more are free to continue hacking again from Monday 7th November for as long as they want. I am sure we will find a place for them to work for as long as it takes. Hi, How does that sound? My fear is that most of the devs will flight back during the week-end if 3) is not announced/organised. We must propose something very clearly, not just say "stay as long as you want". That's also a must-have for ppl that have a boss and must argue that
Le 28/03/2011 12:45, Koustubha Kale a écrit : they must stay for one more week. For example, I think Katrin will have some difficulties to argue & convince her boss !
-- Paul POULAIN
I completely agree that we need a fixed schedule, but IMHO its for you people i.e. Koha developers to propose how many days you need. I will try and arrange for facilities. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2
Here is what I suggest : 1) We break for a day after the main conference on Thursday 3rd November. 2) We start Hackfest in two separate nearby rooms one for teaching / getting started sessions the other room for experienced developers to hack together at peace. The experienced developers take breaks turn by turn to deliver sessions / guidance in the first room. This goes on for two days Friday 4th November and Saturday 5th November. Experienced developers who can not be physically present but would still like to participate in the hackfest, we will try to accommodate through video conferencing. Frankly I don't know how thats gonna work for hacking together, but atleast they can deliver some guidance / tips to the newbies. End of day two of hackfest i.e. on Saturday 5th November, the developers who can not stay more can leave but they would still have had two days of hacking together. 3) Those developers who can stay more are free to continue hacking again from Monday 7th November for as long as they want. I am sure we will find a place for them to work for as long as it takes. Hi, How does that sound? My fear is that most of the devs will flight back during the week-end if 3) is not announced/organised. We must propose something very clearly, not just say "stay as long as you want". That's also a must-have for ppl that have a boss and must argue that
Le 28/03/2011 12:45, Koustubha Kale a écrit : they must stay for one more week. For example, I think Katrin will have some difficulties to argue & convince her boss ! I completely agree that we need a fixed schedule, but IMHO its for you
On Tue, Mar 29, 2011 at 5:06 PM, Paul Poulain <paul.poulain@biblibre.com> wrote: people i.e. Koha developers to propose how many days you need. I will try and arrange for facilities.
Le 29/03/2011 13:56, Koustubha Kale a écrit : thread back ... I spoke with kmkale about the hackfest. We have no alternative option for the hackfest: the week before the main conference is a holiday week in india, so, everything closed. The hackfest *must* be after the main conf. As the main conf ends on wed, the best option we see is: * thursday => break * friday -> tuesday (so *including sunday*) hackfest. * as for previous hackfest, any attendee is free to leave when needed. I like the idea of having 2 separate rooms dedicated to differents things (training, hacking,...) Does anyone have another idea/suggestion ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
participants (6)
-
Ian Walls -
JAMES Mason -
Koustubha Kale -
Magnus Enger -
MJ Ray -
Paul Poulain