public inbox for [email protected]help / color / mirror / Atom feed
GSoC Project Timeline and Proposal 3+ messages / 2 participants [nested] [flat]
* GSoC Project Timeline and Proposal @ 2019-05-24 06:40 Yosry Muhammad <[email protected]> 2019-05-24 06:40 ` Re: GSoC Project Timeline and Proposal Yosry Muhammad <[email protected]> 2019-05-24 08:34 ` Re: GSoC Project Timeline and Proposal Dave Page <[email protected]> 0 siblings, 2 replies; 3+ messages in thread From: Yosry Muhammad @ 2019-05-24 06:40 UTC (permalink / raw) To: pgadmin-hackers Dear all, The official coding phase for GSoC starts by May 27th. As I have stated in my previous email, I will not be able to start working until the 2nd of June, however, I will compensate for the lost time by working extra during the first week or two. Anyway, I would like to use this time to evaluate my timeline and plan and make any necessary corrections, create milestones, etc. I would really appreciate it if you all took the time (especially my mentor, Mr. Page) to go through my project proposal and timeline and give me your suggestions and feedback. Thanks, *Yosry Muhammad Yosry* Computer Engineering student, The Faculty of Engineering, Cairo University (2021). Class representative of CMP 2021. https://www.linkedin.com/in/yosrym93/ ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: GSoC Project Timeline and Proposal 2019-05-24 06:40 GSoC Project Timeline and Proposal Yosry Muhammad <[email protected]> @ 2019-05-24 06:40 ` Yosry Muhammad <[email protected]> 1 sibling, 0 replies; 3+ messages in thread From: Yosry Muhammad @ 2019-05-24 06:40 UTC (permalink / raw) To: pgadmin-hackers My proposal: https://docs.google.com/document/d/1cQssYfPWLSCKAmFwnN-jEPjlldGQtr5fbPaU788UrwM/edit?usp=sharing On Fri, May 24, 2019 at 8:40 AM Yosry Muhammad <[email protected]> wrote: > Dear all, > > The official coding phase for GSoC starts by May 27th. As I have stated in > my previous email, I will not be able to start working until the 2nd of > June, however, I will compensate for the lost time by working extra during > the first week or two. > > Anyway, I would like to use this time to evaluate my timeline and plan and > make any necessary corrections, create milestones, etc. > > I would really appreciate it if you all took the time (especially my > mentor, Mr. Page) to go through my project proposal and timeline and give > me your suggestions and feedback. > > Thanks, > *Yosry Muhammad Yosry* > > Computer Engineering student, > The Faculty of Engineering, > Cairo University (2021). > Class representative of CMP 2021. > https://www.linkedin.com/in/yosrym93/ > -- *Yosry Muhammad Yosry* Computer Engineering student, The Faculty of Engineering, Cairo University (2021). Class representative of CMP 2021. https://www.linkedin.com/in/yosrym93/ ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: GSoC Project Timeline and Proposal 2019-05-24 06:40 GSoC Project Timeline and Proposal Yosry Muhammad <[email protected]> @ 2019-05-24 08:34 ` Dave Page <[email protected]> 1 sibling, 0 replies; 3+ messages in thread From: Dave Page @ 2019-05-24 08:34 UTC (permalink / raw) To: Yosry Muhammad <[email protected]>; +Cc: pgadmin-hackers Hi On Fri, May 24, 2019 at 7:40 AM Yosry Muhammad <[email protected]> wrote: > Dear all, > > The official coding phase for GSoC starts by May 27th. As I have stated in > my previous email, I will not be able to start working until the 2nd of > June, however, I will compensate for the lost time by working extra during > the first week or two. > > Anyway, I would like to use this time to evaluate my timeline and plan and > make any necessary corrections, create milestones, etc. > > I would really appreciate it if you all took the time (especially my > mentor, Mr. Page) to go through my project proposal and timeline and give > me your suggestions and feedback. > I think the timeline looks fine. As they say though, no battle plans survive first contact with the enemy. The same often applies with software engineering; expect the unexpected, and expect to change plans and adapt. One thought that did cross my mind; I wonder if the detection of the query result type (e.g updateable vs. non-updateable) should be handled in a backend function? It might be useful, and perhaps easier, to have that in the server for possible reuse, and because you'll have direct access to psycopg2 and the database connections there. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2019-05-24 08:34 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2019-05-24 06:40 GSoC Project Timeline and Proposal Yosry Muhammad <[email protected]> 2019-05-24 06:40 ` Yosry Muhammad <[email protected]> 2019-05-24 08:34 ` Dave Page <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox