[Pywps-dev] [ GSOC 2014 ] Database output storage idea.
Naveen Panwar
panwarn09 at gmail.com
Wed Mar 19 08:23:45 PDT 2014
Respected Sir,
I have submitted my proposal on melange.
https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014/panwar9/5668600916475904
@jorge and @jachym Thank you sir for helping me on building a good and
"Strong" proposal.
@joege, Thanks sir for editing in the time line. Changes lead proposal in a
new directions.
Any comment and suggestion on proposal at melange are most welcomed.
looking forward to hack this summer in PyWPS.
On Wed, Mar 19, 2014 at 1:45 PM, Jorge de Jesus
<jorge.mendesdejesus at wur.nl>wrote:
> Hi Naveen
>
> I've made my last modifications, now is up to you to do any final
> adjustments and submit the proposal.
>
> Naveen, My mother tongue is Latin based so some of the English
> prepositions that you use sound a bit strange to me and I tend to use a
> bit more abstract sentences, PLEASE read the text and see if it makes
> sense to you.
>
> Cheers
> Jorge
>
>
> On 03/18/2014 09:47 PM, Jachym Cepicky wrote:
> > Naveen, I let you some comments in the chat of the document - hope, you
> can
> > reach it.
> >
> > Generally speaking, the proposal seems very nice, looking forward to get
> your
> > project selected :)
> >
> > Jachym
> >
> > On Tue, Mar 18, 2014 at 02:51:16AM +0530, Naveen Panwar wrote:
> >> Respected Sir,
> >> I have updated the proposal on drive. Please go through and suggest
> >> changes.
> >> Let know me know if it is ok. then I will put proposal in melange.
> >>
> >>
> >> On Mon, Mar 17, 2014 at 1:29 PM, Jachym Cepicky
> >> <[1]jachym.cepicky at geosense.cz> wrote:
> >>
> >> Hi,
> >>
> >> Naveen, thank you for your introduction. I also agree, that, if you
> >> want, your
> >> work should cover all "possible" database storage, which you are
> feeling
> >> would
> >> be able to do. Also, during hacking around PyWPS, you will
> probably face
> >> some
> >> code, you would want/need to modify as well and you are strongly
> >> encouraged to
> >> do so - that might take some of your time too.
> >>
> >> Remote storage is about ftp, webdav, dropbox, googl-drive and
> similar
> >> services,
> >> which basically do serve in similar manner, like simple
> file-storage
> >> does. But
> >> let us not distract your focus too much, you do the database stuff
> (if
> >> you
> >> prefer).
> >>
> >> About the "how things are done in open source world" topic: every
> >> project is
> >> different. I GRASS e.g., everybody is working for himself, with
> very low
> >> interaction. In OpenLayers, the code is carefully watched by
> others, it
> >> has to
> >> follow lot's of formal rules to be accepted. In PyWPS, we are
> somewhere
> >> in the
> >> middle of those two extremes, but still we should give you an idea
> of
> >> how we
> >> work.
> >>
> >> Thank you for joining and thank you, Jorge, to put efforts into
> this
> >>
> >> J
> >>
> >> On Sun, Mar 16, 2014 at 04:30:23PM +0000, Mendes de Jesus, Jorge
> wrote:
> >> > Hi Naveen
> >> >
> >> > Good answers and I think we have a lot to offer concerning code
> >> development and I believe that you will enjoy learning TDD (Test
> >> development driven)
> >> >
> >> > I've to tell you a story, when I was in university I would
> prefer to
> >> go to bed early and sleep properly instead of doing studying till
> 4am
> >> like my collegues, and then go to the exam.... I saw some of my
> friends
> >> go totally blank during exams by the lack of sleep and then
> getting a
> >> miserable grade because of it. I would prefer to sleep and then
> wake up
> >> at 4am to study LOL
> >> >
> >> > Anyway,
> >> >
> >> > Yes the PostGIS and Sqlite are more or less the same idea, so
> they
> >> should be together (why are they separated?)
> >> >
> >> > The FTP and remote storage is more the idea of Soeren (also it
> is
> >> what he needs), the FTP storage implementation was already done on
> >> PyWPS3.2 and personally I would prefer to see the all the
> proposal to
> >> be Database oriented, specially the final part concerning NoSQL,
> the
> >> NoSQL is still something a bit novel and I believe that we could
> >> connect the final part of NoSQL storage into "future developments"
> since
> >> few projects in OsGEO use NoSQL.
> >> >
> >> > IF, you still thing that working on the remote storage is a
> proper
> >> topic I will send and email to Soeren to get some feedback and I
> will
> >> change a bit the proposal, since then we have a more generic
> "storage"
> >> proposal
> >> >
> >> > So, I think that things are going ok just missing a proper
> timetable.
> >> You will do it correct?
> >> >
> >> > Cheers
> >> > Jorge
> >> >
> >> >
> >> > ________________________________________
> >> > From: Naveen Panwar [[2]panwarn09 at gmail.com]
> >> > Sent: 15 March 2014 06:57
> >> > To: Mendes de Jesus, Jorge
> >> > Cc: Jachym Cepicky
> >> > Subject: Re: [Pywps-dev] [ GSOC 2014 ] Database output storage
> idea.
> >> >
> >> > On Sat, Mar 15, 2014 at 1:50 AM, Mendes de Jesus, Jorge
> >> <[3]jorge.mendesdejesus at wur.nl<mailto:[4]
> jorge.mendesdejesus at wur.nl>>
> >> wrote:
> >> > Hi Naveen
> >> >
> >> > I've just sent you a Google doc with a kick start of the Database
> >> output storage idea
> >> >
> >> > I've elaborate the idea a bit in detail and will continue during
> the
> >> weekend.
> >> >
> >> > Please extend it as you see fit
> >> >
> >> > Naveen, I would like some answers to the following questions, I
> tend
> >> to be very direct so don't fell offended.
> >> >
> >> > 1) What do you expect to learn from the summer school (and from
> the us
> >> )
> >> >
> >> > My main aim for GSOC is that I want to learn professional style
> of
> >> coding. and
> >> > How to write code for development of open source software or any
> >> commercial software, To understand how actually development happen
> in
> >> industry.
> >> > Till now I have written code only for myself . Writing a code for
> >> university course project is way different then how actually
> happen in
> >> real world.
> >> > And I don't have this experience till now. That is why I join
> summer
> >> of code.
> >> > Hopefully while coding for PyWPS I get to know about all these
> things
> >> in a better manner.
> >> >
> >> >
> >> > 2) For what I saw from your work and background, it seems that
> your IT
> >> level is very high. With very interesting research topics, I'm
> concern
> >> that the pypws/database proposal maybe to simple, or not so
> exciting
> >> for your level. Think: Will you be happy doing a simple
> programming job
> >> that is not so IT research oriented????
> >> >
> >> > Yeah, I have been working in IT research since my graduation
> years.
> >> And I already have pretty much going on with my research.
> >> > I joined PyWPS, because of my love for PYTHON. and I always love
> >> backhand programming which is there in database proposal. Also
> PyWPS has
> >> small community where scope for me is more.
> >> > Also I have noticed in big community like GRASS, QGIS etc.. GSoC
> >> project goes to regular developer[ less scope for newbie].
> >> > as last year I proposed idea for GRASS but it didn't get
> selected :(
> >> [although last time I was little late too.] .
> >> >
> >> > I am happy because my motivation for GSOC is not as a
> programming job.
> >> As I said earlier, I have my own reason of doing it.
> >> > My guide always said "Keep your work simple and stupid" and I
> >> following it.
> >> > [of course distance work and money are good reason to make a man
> >> happy]
> >> >
> >> > 3) This is not so much a question...If you are not satisfy with
> >> direction and proposal please let us know as soon as possible, and
> >> comments,proposals, new ideas are more than welcomes. What I love
> the
> >> most about teaching is that I learn alot from students. So this is
> >> actual a 2 way learning :)
> >> >
> >> > I think we have to do good work on proposal/Idea .
> >> > From my past experience, In OSGeo SOC only those Guest Project
> or
> >> Idea got slot for summer of code which are really good and
> convincing.
> >> >
> >> > We have to make our proposal strong enough so that OSGeo admins
> >> preferred PyWPS Idea over other projects. If they think it is
> simple and
> >> not worth it, then They won't give us slot.
> >> >
> >> > We have to show them Our idea has scope of 35-40 hours/week work
> from
> >> student side.
> >> >
> >> > I think We should put a combined Idea of all three ideas
> presented on
> >> PyWPS page. [suggestion ??]
> >> > i.e. Database output storage - PostGIS, Database output storage -
> >> SQLite , Remote output storage.
> >> >
> >> > And make all of them worth for GSOC project.
> >> > I am still working in this direction. don't know how much we
> have to
> >> take from last idea(remote storage).
> >> >
> >> > I am working for project timeline. will send update on that in
> google
> >> doc.
> >> >
> >> > Please correct me If I am going wrong and too far.
> >> >
> >> >
> >> > Finally, THANK YOU for participating on the PyWPS hangout, I
> know that
> >> 21:00CET is not the most pleasant time for you.
> >> > No one sleeps before 2AM while pursuing their graduation. I
> think we
> >> all know it ;)
> >> >
> >> >
> >> >
> >> > Cheers
> >> > Jorge
> >> >
> >> > ________________________________________
> >> > From: Naveen Panwar
> >> [[5]panwarn09 at gmail.com<mailto:[6]panwarn09 at gmail.com>]
> >> > Sent: 13 March 2014 16:43
> >> > To: Mendes de Jesus, Jorge; Jachym Cepicky
> >> > Cc: [7]pywps-dev at lists.osgeo.org<mailto:[8]
> pywps-dev at lists.osgeo.org>
> >> > Subject: Re: [Pywps-dev] [ GSOC 2014 ] Database output storage
> idea.
> >> >
> >> > Respected Sir,
> >> >
> >> > Followings are the points which needed to be answer regarding the
> >> proposal according to OSGeo Guideline.
> >> >
> >> > 1. Introduction --
> >> > 2. Background --
> >> > 3. The idea --
> >> > 4. Project plan [ Detailed Time-line (Probably 13-week ) ] --
> >> > 5. Future ideas / How can your idea be expanded ?
> >> >
> >> > I think we should consider these points on tonight hangout
> >> >
> >> >
> >> > >> > On 03/11/2014 12:31 AM, Jachym Cepicky wrote:
> >> > >> > > Hi,
> >> > >> > >> exporting
> >> > >> > >>
> >> > >>
> >> [4][6][9]
> https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227
> >> > >> > >> (will be moved to separate file soon, or maybe
> >> package)
> >> > >> > >> J
> >> > >>
> >> >
> >> > --
> >> > ISRIC - World Soil Information Post: PO box 353, 6700 AJ,
> Wageningen,
> >> > The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
> >> > Wageningen (Bdg. 101), Office: C.013 Office Phone: +31 (0) 317 4
> 83715
> >> > Mobile Phone: +31 (0) 613 9 06950 OpenPGPKey: 0xA3D0065A
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Regards,
> >> > Naveen Panwar
> >> > Senior Undergraduate Student
> >> > IIIT-Hyderabad, India.
> >> >
> >> > [10]http://lsi.iiit.ac.in/naveen.panwar
> >> >
> >>
> >> --
> >> Jachym Cepicky
> >> URL: [11]http://geosense.cz
> >> e-mail: jachym.cepicky at geosense cz
> >> PGP: [12]http://les-ejk.cz/pgp/JachymCepicky.pgp
> >> @jachymc
> >>
> >> --
> >> Regards,
> >> Naveen Panwar
> >> Senior Undergraduate Student
> >> IIIT-Hyderabad, India.
> >> [13]http://lsi.iiit.ac.in/naveen.panwar
> >>
> >> References
> >>
> >> Visible links
> >> 1. mailto:jachym.cepicky at geosense.cz
> >> 2. mailto:panwarn09 at gmail.com
> >> 3. mailto:jorge.mendesdejesus at wur.nl
> >> 4. mailto:jorge.mendesdejesus at wur.nl
> >> 5. mailto:panwarn09 at gmail.com
> >> 6. mailto:panwarn09 at gmail.com
> >> 7. mailto:pywps-dev at lists.osgeo.org
> >> 8. mailto:pywps-dev at lists.osgeo.org
> >> 9. https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227
> >> 10. http://lsi.iiit.ac.in/naveen.panwar
> >> 11. http://geosense.cz/
> >> 12. http://les-ejk.cz/pgp/JachymCepicky.pgp
> >> 13. http://lsi.iiit.ac.in/naveen.panwar
> >
>
>
> --
> ISRIC - World Soil Information Post: PO box 353, 6700 AJ, Wageningen,
> The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
> Wageningen (Bdg. 101), Office: C.013 Office Phone: +31 (0) 317 4 83715
> Mobile Phone: +31 (0) 613 9 06950 OpenPGPKey: 0xA3D0065A
>
>
--
Regards,
Naveen Panwar
Senior Undergraduate Student
IIIT-Hyderabad, India.
http://lsi.iiit.ac.in/naveen.panwar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20140319/2ae2fc04/attachment-0001.html>
More information about the pywps-dev
mailing list