Page 8 of 9
Re: Working on 2.0: Developer sprint
Posted: Thu Jun 13, 2013 4:11 pm
by yellowled
onli wrote:If someone wants to help develop, we have some areas I would happily give someone to work on (new JS-hook for plugins, remove no-smarty-fallbacks from the core, UTF-8 the translation) or help implement ideas you yourself have.
Also: replacing inline on* handlers. Man, there are still a lot of those little buggers in there …
YL
Re: Working on 2.0: Developer sprint
Posted: Sun Jul 07, 2013 4:47 pm
by onli
I'd like to invite to a next devtalk!
The smartification is done, everywhere it matters. We did a lot in the backend and are starting to tackle
the next set of bigger changes.
I'd like to do two things:
1. (Let YL) Present the current version of the new admin backend interface and talk about what is needed next for that.
2. Create an opportunity to talk about the linked and additional bigger changes to the core
No bigger target, just to either wrap things up or add to the discussion.
The plan is to make it happen next weekend or the weekend after that, if that is too soon or the timeslots are wrong, please write here. Else the doodle:
http://www.doodle.com/vatu2da5miqmvxqs
Re: Working on 2.0: Developer sprint
Posted: Sun Jul 07, 2013 6:33 pm
by yellowled
I don't remember – did we use Garvin's Mumble for this the last time or the InfoCamp Mumble? We should probably agree on one so nobody gets lost.
YL
Re: Working on 2.0: Developer sprint
Posted: Fri Jul 12, 2013 9:06 pm
by yellowled
Given the current state of the Doodle, I guess we'll take Saturday, the 20th? Should we say 15:00 then, on Garvin's Mumble server? Or is 17:00 better for everyone?
YL
Re: Working on 2.0: Developer sprint
Posted: Sat Jul 13, 2013 3:28 am
by Don Chambers
Guys - I will try to participate, although I am very far out of "the loop".
Re: Working on 2.0: Developer sprint
Posted: Mon Jul 15, 2013 9:49 am
by garvinhicking
Hi!
15:00 would be fine for me.
Re: Working on 2.0: Developer sprint
Posted: Mon Jul 15, 2013 10:44 am
by onli
For me too.
As far as I remember, we used Garvins Mumble. Is that still an option?
Re: Working on 2.0: Developer sprint
Posted: Mon Jul 15, 2013 2:27 pm
by garvinhicking
Hi!
My mumble is open, yes

Re: Working on 2.0: Developer sprint
Posted: Mon Jul 15, 2013 5:48 pm
by mattsches
I'll try to be there, too.
Re: Working on 2.0: Developer sprint
Posted: Mon Jul 15, 2013 6:12 pm
by yellowled
Great. This is really (for me at least, although it shouldn't be limited to that) about getting some feedback and impressions from people who haven't worked on it for some … months, I guess. Anybody who finds the time should be welcome to join us, although I realize 15:00 CEST is kind of brutal in Don's timezone …
YL
Re: Working on 2.0: Developer sprint
Posted: Fri Jul 19, 2013 3:19 pm
by onli
Ok. The date seems to be: Saturday, 15 pm CET, Garvins Mumble. Cozy 4 to 5 People.
Re: Working on 2.0: Developer sprint
Posted: Fri Jul 19, 2013 4:00 pm
by garvinhicking
***SATURDAY*** not Sunday!
Re: Working on 2.0: Developer sprint
Posted: Fri Jul 19, 2013 5:08 pm
by onli
Right! Thx. I really mixed that up.
Re: Working on 2.0: Developer sprint
Posted: Fri Jul 19, 2013 5:49 pm
by yellowled
Just to confirm (and to keep a tradition going): I'll be there and I'll try to not fall asleep again.
YL
Re: Working on 2.0: Developer sprint
Posted: Sun Jul 21, 2013 10:50 am
by onli
Ok. In short what happened:
1. YL showed Garvin the new backend. He liked it -> we will proceed.YL got much needed input about detail questions.
2. The next step will be to make some tests with users.
3. We realized that there is a conflict between our two aims to 1. relase the new backend as fast as possible and 2. to implement new featues like a db-layer. Kind of an answer was to try to do 1 regardless of the new features, while developing them in feature-branches and merging when possible without real breakage, which I think should be possible.
4. Mattsches suggested that Unit-Tests could help with that (I agree)
5. In the end, we had a short talk how to notify YL or me about bugs and where our TODO-list is (on paper so far in my case), so we spontaneously decided to use
githubs issue tracker with labels for that. See
http://board.s9y.org/viewtopic.php?f=11&t=19451
Please add if I forgot something.