Hi Sergio,
2017-06-16 6:03 GMT-05:00 Sergio Fernández <wik...@apache.org>: > Hi Gustavo, > > On Thu, Jun 15, 2017 at 6:49 AM, Gustavo Mora <gmora1...@gmail.com> wrote: >> >> Yes and sorry, I was in my midterm exams, so I had to stop almost for a >> week. > > > Please, be aware that when you signed for GSoC the program you committed > with full-time dedication during the program time. We could be a bit > flexible, but you would need to catch-up the lost time if you want to pass > the mid-term review at the end of month. > Yes, I'm so sorry for that week. I've working on weekends to recover lost time. > > >> Francisco has been helping me a lot, he is guiding me a lot with the >> code. We have meetings in the college or in weekends we Skype, and we > > agreed to comment each commit why the modification was done; it's an easy >> way to remember. I think I can submit the documentation from each commit >> 'cause I try to be as detailed as possible. >> > > Well, while you don't need to document each commit, it's fine if you share > publicly with the community such meetings and coument the key pieces. > > The idea of documenting or give detail to commits is to remember why was something done. BTW, I forget about a commit sometimes; there a lot of code. Okay, I'll share all of it. > As I said when we started, you should keep engadge with this mailing list, > so we can follow the actual progress and you can ask questions and/or > ideas. > > I created my account, my user is gmora1223. >> > > Perfect. I've added you to the contributors group https://wiki.apache.org/ > marmotta/ContributorsGroup so you can now edit the wiki. > Thanks! > > Cheers, > > > 2017-06-07 10:57 GMT-05:00 Sergio Fernández <wik...@apache.org>: >> >> > Hi Gustavo, >> > >> > sorry for the delay, but I've been travelling last with limited >> > connectivity. But it's important to following the planning if we want to >> > success. >> > >> > Following the methodology for GSoC we have agreed in previous editions >> > [1], we'd love to hear from you on regular basis (weekly?): about your >> > progress, your issues, your questions, etc. >> > >> > According the official timeline [2] you should have started to work on >> > your project for a week already. I've seen you make good the time you >> got >> > in the Community Bonding Period [3]. I hope the build issue doesn't make >> > your life even harder; we'll try to support you on that. BTW, now you >> have >> > some patches upstream you may need to merge. Remember to periodically >> keep >> > updated your fork [4]. >> > >> > In parallel I'd recommend you to start drafting some technical/internal >> > documentation on our wiki [5] (you need to register at [6] and tell me >> your >> > username to give you karma there). What Francisco did couple of years >> ago >> > [7] is a very good example why documentation is as important as code. >> > >> > Good luck! >> > >> > Cheers, >> > >> > [1] https://wiki.apache.org/marmotta/GSoC/Methodology >> > [2] https://developers.google.com/open-source/gsoc/timeline >> > [3] https://github.com/gmora1223/marmotta/commits/MARMOTTA-659 >> > [4] https://help.github.com/articles/syncing-a-fork/ >> > [5] https://wiki.apache.org/marmotta/GSoC/2017/MARMOTTA-659 >> > [6] https://wiki.apache.org/marmotta?action=newaccount >> > [7] https://wiki.apache.org/marmotta/GSoC/2015/MARMOTTA-584 >> > >> > > Cheers, Gustavo.
