| *** tpb has joined #melange | 00:00 | |
| *** robbyoconnor has quit IRC | 00:10 | |
| *** robbyoconnor has joined #melange | 00:10 | |
| *** robbyoconnor has joined #melange | 00:10 | |
| *** schultmc has quit IRC | 00:32 | |
| *** dirigeant has quit IRC | 02:35 | |
| *** mithro has joined #melange | 04:56 | |
| *** ChanServ sets mode: +v mithro | 04:56 | |
| *** tansell-laptop has joined #melange | 04:56 | |
| *** ihalip_ has joined #melange | 05:02 | |
| *** tansell has quit IRC | 05:28 | |
| *** tansell has joined #melange | 05:29 | |
| *** sttwister has quit IRC | 05:34 | |
| *** sttwister has joined #melange | 05:43 | |
| *** sttwister has quit IRC | 05:47 | |
| *** ihalip_ has quit IRC | 06:09 | |
| *** sttwister has joined #melange | 08:05 | |
| *** Merio has joined #melange | 08:18 | |
| *** ChanServ sets mode: +v Merio | 08:18 | |
| sttwister | Merio, ping | 08:20 |
|---|---|---|
| *** madrazr has joined #melange | 08:21 | |
| *** ChanServ sets mode: +v madrazr | 08:21 | |
| Merio | sttwister: pong :) | 08:21 |
| sttwister | Merio, ready for the meeting ? | 08:22 |
| Merio | sttwister: yup :) so, I've seen your blog post, it's very good :) | 08:23 |
| sttwister | thanks :) | 08:23 |
| Merio | Only one thing: as you probably already know, in open source crediting the others is always important, so I think it's better if you tell also which OS projects you used for your images | 08:23 |
| Merio | It's also good because it reflects your internal reasoning to develop a solution to the problem | 08:24 |
| sttwister | Oh, you're right, I was actually thinking about that before the blog post, but I forgot when I wrote it, silly me :| | 08:24 |
| Merio | No problems, just edit it as a first action item of your TODO agenda in the wiki after the meeting :) | 08:25 |
| sttwister | sure thing | 08:25 |
| Merio | So, UML schema is done, maybe (another action item) we should discuss with the community whether we want to integrate what you coded in the main branch as well | 08:28 |
| Merio | So, e.g. I can output the same images that you did in my own instance during evolution of the data model | 08:28 |
| sttwister | yep, I just need to beautify the code a bit and add some command line options, everything is a bit hardcoded right now | 08:29 |
| Merio | Just a question, this is not mandatory: is it easy to code some way to output the diff between generated images? Either in the image or in a simple text file? | 08:29 |
| Merio | I understand :) | 08:29 |
| sttwister | also, I found that there is in fact a script that draws diagrams already in the codebase, but doesn't really seem as pretty | 08:29 |
| Merio | That's awesome then, as another action item we can ask Sverre (as I think he committed the former script) whether to leave it as another option in the code base or just remove that script and use yours instead | 08:30 |
| sttwister | the way I do it is to generate a text .dot file before transforming it into an image which can then be diffed with other versions | 08:31 |
| Merio | That's good, just name the dot file with a sort of date in YYYYMMDDHHIISS format | 08:31 |
| Merio | (if you didn't do that already :)) | 08:32 |
| Merio | So *maybe* (another thing to ask, please take note of everything ^__^) we can leave those in the code base as well, as they're simple little text files | 08:32 |
| Merio | Showing differences between data models would be great to me, but maybe that's not so interesting/useful for the rest of the community :) | 08:33 |
| sttwister | ok, noted | 08:33 |
| sttwister | showing diffs in a graphical manner might prove a bit more difficult though | 08:34 |
| Merio | When you finish to polish your code I'd suggest you post it in rietveld so the others can post comments on your code before committing | 08:34 |
| Merio | that would be good before next conference call, so we can announce it in the DEV list (if you do that before Monday) or during conference call | 08:34 |
| Merio | no need for that (diffs in image), we can do that later, if we want, based on the text files I guess | 08:35 |
| Merio | we can also build a script to generate an animation from the very first commit to the end, but this is waaaay too much for the moment :D | 08:36 |
| Merio | Like code swarm for commits, you know that project? | 08:36 |
| sttwister | sounds interesting, I'm not familiar with that project though | 08:36 |
| Merio | It builds an animation based on commits and commits name | 08:37 |
| Merio | You can see some posted on youtube by myself, they're linked in my last blog post for last year, I think it's just before Savitha's post | 08:37 |
| sttwister | oh, actually I think I've seen that kind of animations | 08:37 |
| sttwister | yes indeed, I've saw them :) | 08:38 |
| Merio | However, anything you did in these days/plans for the next days? | 08:38 |
| sttwister | well, I was thinking on starting to work on the design documents, now that I have a pretty clear image of the entities model | 08:39 |
| sttwister | should I instead focus on merging the script first ? | 08:39 |
| Merio | I'd suggest to post in the wiki a schedule for your project till the end of GSoC, and to set weekly milestones (with particular care on midterm and final evaluations) associated with issues in your cloned code | 08:40 |
| Merio | Hmm I think it's better if you work on design documents, keeping track with what we decided in the first meeting | 08:41 |
| Merio | Community bonding is going to end in 12 days, so it's better that you've and give the community clear ideas on what you're going to do, so we can discuss it | 08:41 |
| Merio | Than we can ask during Monday meeting if we're going to merge your script now or not. | 08:42 |
| sttwister | yep, that's what I was thinking too :) | 08:42 |
| Merio | Do you think you can explore the local/remote and the XML/YaML/Fixtures thing before Monday? | 08:43 |
| Merio | So you can focus on designing a solution for the interface and eventually prototype something in the last week of community bonding | 08:43 |
| Merio | But on Monday we can discuss with the community the core solution in the backend | 08:44 |
| sttwister | yes, that sounds reasonable | 08:44 |
| Merio | Along with the short-term destiny of your script ^_^ | 08:44 |
| Merio | In the meantime I would focus on some thoughts about the interface and we can discuss during our Monday meeting after the conference call | 08:44 |
| Merio | (action item for me, too ;)) | 08:45 |
| sttwister | ok, we'll see how the interface and the configuration file that I'll be working on will integrate | 08:46 |
| Merio | fine with me | 08:47 |
| Merio | We really have few time so push as much as you can ^_^ | 08:47 |
| sttwister | yes indeed, I'll do my best | 08:48 |
| *** dirigeant has joined #melange | 08:48 | |
| sttwister | I have signed the CLA online btw, anything else I need to do about that ? | 08:49 |
| Merio | Great, so we don't have to follow this step when we're going to commit your script | 08:49 |
| Merio | No you don't have to do anything else | 08:49 |
| sttwister | great | 08:50 |
| Merio | Is there something not clear about your project? I mean about the different situations of seeding data | 08:51 |
| Merio | The seeding reflecting timeline is very interesting to me, but I don't know if it's clear enough on the wiki idea I've written | 08:52 |
| sttwister | what do you mean by interesting ? | 08:53 |
| Merio | I mean that I don't know if it's critical for the community, but it would be very useful to me when testing JavaScript | 08:53 |
| Merio | So it would ease my work if I have to test the JavaScript used for midterm evaluations | 08:54 |
| Merio | for example | 08:54 |
| sttwister | I don't think I understand what you mean | 08:56 |
| Merio | I mean that there should be a way to configure the data seeder to make Melange having a predefined state | 08:57 |
| Merio | You know that Melange shows different interfaces depending on the user access level | 08:57 |
| Merio | and depending on the timeline | 08:57 |
| Merio | For example midterm surveys appear only ... well.. when the time for midterm survey is encountered | 08:57 |
| sttwister | ohh I see | 08:58 |
| Merio | So I would like not to care about what to seed to reach that state | 08:58 |
| Merio | So there should be a sort of configuration file that drives the data seeder to seed the data to reach that state | 08:59 |
| sttwister | or maybe some kind of option to manually switch to a specific state by force, after the data has been seeded ? | 09:00 |
| sttwister | i.e.: seed data, then see how it looks like in the proposal phase, then jump to the midterm phase with the exact same seeded data, etc | 09:00 |
| sttwister | not sure how easy this is to achieve though | 09:01 |
| Merio | Well, if to you it's not so difficult to code yes, but even from scratch it could be enough. Obviously if you can track the current state of the DB that would be awesome (so we can show it on the web GUI too) but I remember that the others told me that it's not so easy to get from AppEngine | 09:01 |
| Merio | So well, action item for Monday conference call... ask it :) | 09:02 |
| sttwister | well, I haven't studied the code internals so I don't know if it's easy or not | 09:03 |
| sttwister | we'll see about that | 09:03 |
| Merio | actually it some that you should see in appengine documentation I guess | 09:04 |
| Merio | s/it/it's | 09:04 |
| Merio | Because you have to get that data from the datastore, as something can be seeded without the seeder, but just manually | 09:05 |
| Merio | But I think it could be something to add if there's time | 09:05 |
| sttwister | how does Melange track the current phase of a program? is it solely by date or are there any switches in the DB to reflect that ? | 09:05 |
| Merio | Let's keep it simple at the beginning, doing everything from scratch | 09:05 |
| Merio | AFAIK it should be timeline based, but there are some changes in the models too: for example a student proposal object becomes a student project object when acceptance date is passed | 09:06 |
| Merio | Action item, ask on Monday :) | 09:07 |
| Merio | Or maybe madrazr is online to respond ;) | 09:07 |
| Merio | Well, I think not :) | 09:08 |
| sttwister | isn't a NEW model (the student project) created when acceptance date is passed ? | 09:08 |
| sttwister | rather than converted I mean | 09:08 |
| madrazr | Merio: yes? | 09:08 |
| sttwister | madrazr, how does Melange track the current phase of a program? is it solely by date or are there any switches in the DB to reflect that ? | 09:08 |
| Merio | Hi, good morning Madhusudan :) | 09:09 |
| madrazr | Merio: good morning | 09:09 |
| Merio | sttwister: you can collect some questions for the community we identified during this meeting and post them in the dev list so you can get a response before Monday too :) | 09:09 |
| madrazr | sttwister: I did not get your question | 09:10 |
| madrazr | can you explain it a bit more? | 09:10 |
| Merio | madrazr: e.g. how Melange knows that it has to show midterm surveys? | 09:10 |
| sttwister | Merio, will do, I'll also ask about the many-to-many relations issue | 09:10 |
| madrazr | Merio: Oh it is all very simple | 09:10 |
| Merio | madrazr: is there some check on the timeline or is there some other "magic button" to press? | 09:10 |
| madrazr | Merio: sttwister: we have a model called Timeline which is associated with the programme | 09:10 |
| madrazr | Merio: former is correct | 09:11 |
| Merio | madrazr: fine then, maybe you can point sttwister to some code line that does this check? | 09:11 |
| madrazr | Merio: all through the code there are access checks and other kind of conditionals which include checks on timeline | 09:11 |
| sttwister | madrazr, so this check happens each time a request is made ? | 09:11 |
| madrazr | Merio: yeah sure, give me a moment, I will navigate through the code and point out | 09:11 |
| madrazr | sttwister: yes | 09:11 |
| Merio | madrazr: thanks | 09:11 |
| madrazr | Merio: NP | 09:12 |
| sttwister | madrazr, cool, thanks ;) | 09:12 |
| madrazr | sttwister: to begin with very important file to look at is ./app/soc/logic/helper/timeline.py | 09:13 |
| madrazr | sttwister: and if you go to app/soc/views/helper/access.py you can see many usage of timeline_helper.isActivePeriod(survey, 'survey') or timeline_helper.isAfterEvent or something like that | 09:14 |
| sttwister | madrazr: thanks, checking it out right now | 09:14 |
| madrazr | sttwister: NP | 09:14 |
| madrazr | sttwister: and with it I think you can navigate through the code and figure out where all it is used and how it is used | 09:14 |
| madrazr | Merio: That information would be helpful I suppose? | 09:15 |
| Merio | madrazr: I think for this question yes, I don't know whether sttwister has additional questions about this topic for the moment without having to wait responses on Dev List/on conference call on Monday | 09:17 |
| madrazr | sttwister: app/soc/modules/gsoc/views/models/program.py method _getTimeDependentEntries() at line 257 | 09:17 |
| madrazr | you have some really useful information there as to how time dependent items are built for sidebar and stuff | 09:17 |
| madrazr | Merio: sttwister: if you want some help regarding timeline or some stuff you can ping me any time I am here. I will be more than happy to tell you whatever I know | 09:18 |
| madrazr | saves time I guess | 09:18 |
| sttwister | madrazr: thanks, that code really helped, will definitely ask in the future if I have any other questions ;) | 09:19 |
| madrazr | sttwister: cool! | 09:19 |
| Merio | thanks madrazr, you're awesome as always ^_^ | 09:19 |
| madrazr | Merio: No problem at all :) as always WE (Melange team) is awesome :D | 09:20 |
| Merio | madrazr: sure :) | 09:22 |
| sttwister | Merio: so, anything else on the agenda for today ? | 09:23 |
| Merio | sttwister: I think not, just post in the wiki action items (identified explicitly by me or implicitly during the discussion) and references to the logs... and don't forget the schedule (but this can be postponed for the very beginning of coding phase, so you have clearer ideas on what you have to do) | 09:26 |
| sttwister | I've already written notes as we spoke | 09:27 |
| sttwister | well then, I'll see you later I guess :) | 09:27 |
| Merio | sttwister: awesome! :) I'll be online on GTalk also on my mobile as last week, so everything you need you'll get :D | 09:28 |
| Merio | sttwister: keep up the good work and have a nice day! :) | 09:28 |
| sttwister | Merio: thanks, you too, bye! | 09:29 |
| *** mithro has quit IRC | 09:48 | |
| *** mithro has joined #melange | 10:10 | |
| *** ChanServ sets mode: +v mithro | 10:10 | |
| *** SRabbelier has quit IRC | 10:47 | |
| *** madrazr has quit IRC | 10:57 | |
| *** madrazr has joined #melange | 10:58 | |
| *** ChanServ sets mode: +v madrazr | 10:58 | |
| *** Merio has quit IRC | 11:01 | |
| madrazr | ah | 11:01 |
| *** SRabbelier has joined #melange | 11:06 | |
| *** ChanServ sets mode: +o SRabbelier | 11:06 | |
| *** sttwister has quit IRC | 11:09 | |
| *** sttwister has joined #melange | 11:13 | |
| *** neo7 has joined #melange | 11:19 | |
| *** neo7 has quit IRC | 11:24 | |
| *** madrazr has quit IRC | 12:03 | |
| *** robbyoconnor has quit IRC | 12:22 | |
| *** r0bby|android has joined #melange | 12:43 | |
| *** madrazr has joined #melange | 13:31 | |
| *** ChanServ sets mode: +v madrazr | 13:31 | |
| *** schultmc1 is now known as schultmc_ | 14:08 | |
| *** schultmc has joined #melange | 14:28 | |
| *** schultmc has quit IRC | 14:41 | |
| *** mithro has quit IRC | 14:42 | |
| *** mithro has joined #melange | 14:59 | |
| *** ChanServ sets mode: +v mithro | 14:59 | |
| *** madrazr has quit IRC | 15:08 | |
| *** sttwister has quit IRC | 15:23 | |
| *** sttwister has joined #melange | 15:33 | |
| *** sttwister has quit IRC | 15:39 | |
| *** ihalip has joined #melange | 15:42 | |
| *** ihalip has joined #melange | 15:42 | |
| *** sttwister has joined #melange | 16:02 | |
| *** durin42 has quit IRC | 16:10 | |
| *** madrazr has joined #melange | 16:11 | |
| *** ChanServ sets mode: +v madrazr | 16:11 | |
| *** durin42 has joined #melange | 16:14 | |
| *** ChanServ sets mode: +v durin42 | 16:14 | |
| *** durin42 has quit IRC | 16:15 | |
| *** sttwister has quit IRC | 16:18 | |
| *** durin42 has joined #melange | 16:21 | |
| *** ChanServ sets mode: +v durin42 | 16:21 | |
| *** mithro has quit IRC | 16:48 | |
| *** madrazr has quit IRC | 17:05 | |
| *** mithro has joined #melange | 17:06 | |
| *** ChanServ sets mode: +v mithro | 17:06 | |
| *** r0bby|android has quit IRC | 17:22 | |
| *** lfranchi has quit IRC | 18:27 | |
| *** lfranchi has joined #melange | 18:27 | |
| *** robbyoconnor has joined #melange | 18:37 | |
| *** robbyoconnor has joined #melange | 18:37 | |
| *** dhaun has joined #melange | 19:11 | |
| *** robbyoconnor has quit IRC | 21:34 | |
| *** dhaun has quit IRC | 21:57 | |
| *** ihalip has quit IRC | 22:19 | |
| *** dirigeant has quit IRC | 22:36 | |
| *** schultmc has joined #melange | 22:50 | |
| *** dirigeant has joined #melange | 23:23 | |
| *** robbyoconnor has joined #melange | 23:30 | |
| *** robbyoconnor has joined #melange | 23:30 | |
| *** mithro has quit IRC | 23:36 | |
| *** dirigeant has quit IRC | 23:46 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!