[07:45] <dholbach> good morning
[16:43] <xdatap1> dholbach, good evening
[16:44] <dholbach> hey xdatap1
[16:44] <xdatap1> dholbach, let me introduce to you l3on, he's a dear friend from the Italian LoCo. He wrote that post on the planet about a tool for making easier the merge process.
[16:44] <dholbach> hey l3on - nice to meet you
[16:44] <l3on> Hi all! hi dholbach, thank you xdatap1
[16:46] <xdatap1> dholbach, we were chatting about this post, so I tought that you were the best person for asking some feedbacks
[16:46] <l3on> Hi dholbach, I'm here to get some feedbacks about my idea ( "Hym" ), I would know if it could be useful into ubuntu development cycle and If yes how I can improve it before start do develop
[16:46] <dholbach> can you give me a link to the blog post again, so I can refresh my memory?
[16:47] <l3on> of course → http://en.leoiannacone.com/2011/05/hym-help-you-to-merge/
[16:47] <xdatap1> http://en.leoiannacone.com/2011/05/hym-help-you-to-merge
[16:48] <dholbach> ah yes
[16:49] <dholbach> would it make use of grab-merge (in ubuntu-dev-tools) and visualise the changes? or use bazaar internally?
[16:51] <dholbach> (I'm not sure which part of the merging workflow Hym would take care of)
[16:53] <l3on> dholbach: grab-merges or bazaar - I don't know actually...
[16:54] <dholbach> so which part of the workflow would Hym take care of?
[16:55] <l3on> what do you mean with "workflow" ? :)
[16:55] <l3on> I have thinked: With Hym I can:
[16:56] <l3on> 1) Take a complete view of available merges (merges.u.c)
[16:56] <l3on> 2) choose which one I want to merge
[16:57] <l3on> 3) automatic "dput" of debian and old_ubuntu packages in the "hym_workspace"
[16:58] <l3on> 4) use gui to get a complete view of changes involeved last ubuntu packages. Apply changes (if necessary) and constantly see the diff.
[16:59] <l3on> 5) Build package
[16:59] <l3on> 6) Report sync or Upload packages somewhere
[16:59] <dholbach> can I also use hym to edit if there are merge conflicts?
[17:00] <l3on> This is how I have imaged HYM.
[17:00] <l3on> dholbach: I'm not a "great experience ubuntu developer", what mean "merge conflicts" ? :)
[17:01] <dholbach> if changes that happened in debian and ubuntu happened in the same place, they might conflict
[17:01] <dholbach> so you have to resolve them manually
[17:02] <l3on> yes of course, hym could be improved with this feature.
[17:03] <dholbach> if you resolve them manually you have to edit files - would hym also do that?
[17:03] <l3on> But I have to touch what "merge conflict" is really, but yes... I don't see any difficult to introduce this aspect in HYM.
[17:04] <l3on> dholbach: of course!! maybe are you missing the complete mockup? → http://people.ubuntu.com/~l3on/hym/myImage.png
[17:05] <dholbach> ah ok, now I see it
[17:05] <l3on> When I wrote "default/preferred EDITOR" I've intended there will be a "gedit panels" (gedit is just an example)
[17:06] <dholbach> I like the idea of making it easier for new contributors to contribute and do something - I'm just a bit concerned as it looks like quite a lot of work
[17:06] <l3on> in other words: you'll be able to edit all files you want.
[17:07] <dholbach> two things I'm wondering about are 1) for other development tasks, will new contributors have to use different tools? (there's more than merging that needs to be done), 2) does Hym hide too much complexity so new contributors don't learn enough about the tools / build process
[17:08] <l3on> yes you're right. When I think the roadmap I see a "long term" project (but, well engineered)
[17:08] <dholbach> I think you should talk to a few more people, maybe on one of the development mailing lists (ubuntu-motu-mentors@lists.ubuntu.com might be good to get input from new contributors and also people who have been developing for a bit longer)
[17:10] <l3on> for point 1): have you some example?
[17:11] <l3on> 2) yes, unlucky It will hide some dev stuffs
[17:15] <dholbach> regarding 1) taking the package and fixing stuff in the source code, updating the package to a new version, etc
[17:18] <l3on> Well we can structure application to work between two general debs, instead of
[17:18] <l3on> debian - ubuntu
[17:19] <dholbach> sometimes you just take the current source in ubuntu and work on the source
[17:29] <l3on> Yes, understood. I'll work on, but I think is simple (just remove the panel below, which represents the "old" ubuntu package). I'll think about that.
[17:30] <dholbach> ok
[17:30] <dholbach> I think it'd be a good idea to talk to a lot of people first and find out how they work
[17:30] <l3on> thanks dholbach for info and ideas :). I'll contact motu mentors (and motu too?, boh!).
[17:30] <dholbach> awesome