Just an update. I have just built the Install project (which didn't build right away when I first got the code). I had to manually get enblend and set its path for CMakeSetup, since it was not part of the SDK. You might want to consider adding it to the SDK.
On Apr 1, 1:50 pm, "Mokhtar M. Khorshid" <[email protected]> wrote: > Thank you for your encouraging comments. > > Let me try to answer your question as best as I can. > > My chances of "staying" are not very low. I still am subscribed to > wxWidget's groups (and even have enhancements that I still want to > make to wxWallCtrl), I still wander on Clickteam's forums every now > and then, etc... But, as a dedicated double majors student, I am > usually occupied during semesters and I am free during the summer and > winter periods. What this means is that even though I may be around > following news, answering questions, or making ideas, my actual code > contribution will be significantly less (if at all). I am now shifting > from undergraduate study to graduate study. I do not know yet, how > much the work load will be. > > As I mentioned, I am mostly interested in the computer graphics aspect > of Hugin, not the photography part (although I did some shooting to > test Hugin, and was very impressed by the results that I am > considering using it for some special purpose of mine). So I believe > we have two issues: interest and availability. > > Let me try to suggest an action plan. Firstly, as long as there is > work in 3D space transformations or OpenGL (or any other computer > graphics work) I will be interested in doing it. I do not know how > much of that kind is in demand, but I know I will be interested on > working on that if it is available. Secondly, my research focus in > graduate school will be computer graphics, so whenever I can find a > topic of overlap between my studies and hugin, I will be able to > devote more time to contributing as it will double as studying for me. > But of course, my participation level will be uncomparable with that > during GSoC. During the summer I can work for 8 or more hours per day. > I am very thorough with my work, so whenever I'm working on something > I will do everything possible to get it done right and in time. If > things go behind schedule, I will stay all day and night to catch up. > Naturally, I can't do this all year. During semesters this can go down > to 1 hour per day (unless things get very interesting or I find > research overlaps). I also support any code I have written for as long > as I can. So regardless of how busy I am, I will always help those > that are working with my code/design, and step in to fix any bugs > found in my code. I don't know how much time regular committers in > Hugin are expected to devote per day during their work/study periods, > though. > > My objective for this summer is: Get some good (graphics programming) > experience by working on an interesting project, make a good > reputation by leaving a positive impression (so that my work can be > used as a reference), and, if possible, do this as a GSoC project. > Last year was my first experience with an open-source project, so I am > still relatively new to the world of open-source development and have > a lot to learn about on going participation. You were right in that I > do have the "well defined project" concept, basically because that's > how most projects I worked on were: I have a set of objectives to > finish before some deadline. This does not mean that I "have to" keep > that way of thinking about projects, or that I "want" to keep it that > way either, it's just what I'm used to. > > Now that you have a clear vision of how/why/when I would be available > and what my objectives are, you should be able to guide me to what > would work best for everybody. I have no problem switching to another > project if you feel my availability as described above won't cut it, > as long as it is interesting. If you feel it is acceptable for this > project or have any suggestions please let me know. > > On Apr 1, 3:14 am, Yuval Levy <[email protected]> wrote: > > > Welcome, Mokhtar. > > > Mokhtar M. Khorshid wrote: > > > I have participated in last year's GSOC program, and build the > > > wxWallCtrl for wxWidgets. > > > Thank you for your openness and straight-forwardness with which you > > filled the application in the webapp. > > > Based on your code in the wxWidgets repository and on feedback from your > > last year mentor, you do not need to provide a patch against Hugin to > > qualify. There is enough listed at > > <http://wx.ibaku.net/changelog/?d=MMK> that speaks for itself. > > > I've asked Julian if he would hire you again and the answer was yes. > > > I trust you can easily build Hugin and hack the code (wxWidgets is the > > GUI toolkit). You are welcome to do the patch exercise for completeness, > > but it is totally up to you. > > > > feel to pose any questions to me here. > > > It's a sensitive question. I'll ask it here because I think it is > > relevant also for the other students (who may want to answer it for > > themselves and maybe even to us). You may answer privately if you prefer. > > > What are the chances that you will stay with our community after GSoC > > and continue to maintain your code and further contribute code to Hugin? > > > I've asked Julian whether you are still participating in the wxWidgets > > community and whether you are still contributing to the code. You know > > the answer. > > > We see GSoC as an entrance door, as the beginning of a longer > > relationship. I have the impression that your view of GSoC is more of a > > self-contained projects. Veni vidi vici. And I have no doubt you can and > > will win. But I want this to be win-win for everybody. > > > Loyalty and relationships can not be enforced and very often they also > > can not be predicted. How do I know that a student will stick around and > > become a committer? I don't. I try to do my best at making them feel > > welcome, and I look for evidence where available. > > > In your specific case, I appreciate your openness and honesty about your > > lack of interest in photography. Add the evidence from wxWidgets and I > > get the impression that you see a GSoC project with Hugin/Panotools as a > > time-limited effort. Correct me if I am wrong. > > > There is nothing wrong with that when it is done openly, and your > > openness, added with your impressive CV, speak for you. > > > If I am right about the differing views that we have of GSoC, we can > > either seek a compromise in which both you and the community win. A > > compromize that can reconcile our need for maintainability with your > > need to move on after GSoC is over. > > > The project you are applying to is one of the longer terms commitments. > > It's open ended and I would like to assign it to somebody who is likely > > to stay around for longer. There are other projects that are more > > self-contained and if you want we can work together toward an > > application on one of those. > > > Alternatively, I can help you seek another mentoring organization for > > which it is not a problem that the relationship is time-limited. > > > Whatever you choose, let me reassure you that you have my support. Your > > CV is impressive. You have good references. Your approach and your > > communication are open, genuine and make me want to help you achieve > > your goals. With Hugin/Panotools in GSoC if there is overlap/agreement, > > or in another context. > > > Contact me any time. > > Yuv > > 1.418.948.3374 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
