Re: Website integrated mobile app for disaster

[Aymeric Augustin]

Hi Akanksha,

As far as I know, the DSF looks for GSoC proposals to work *on* Django, not *with* Django.

While there’s definitely some merit in your idea, I don’t think it would qualify as a Django GSoC.

-- 

Aymeric.

On 10 janv. 2014, at 19:07, Akanksha Shrivastava <akanksha.s...@gmail.com> wrote:

Hello everyone!

I am currently working on this project of mine and was looking forward for your feedback. I am looking forward to present this idea as my idea for Google Summer Of Code, and I am really looking forward to join this community and contribute whatever I can for this community.

They say change is inevitable. The nature has its own path, it hears no one and follows no one. It is unbiased to all and has been the most furious of all the changes. The very sudden changes in nature lead to what we call calamity or disaster. Our priority at such a time is to pray for safety of the lives and work as hard as we can for the very same. However, we always wonder what if we had even a little idea about what was about to happen. And if not the magical time machine then at least time to reach up to this information should have been early. For the most uncertain and unpredictable events of life like these, I would like to present to you my idea.

Project-A website integrated mobile app which traces a person all the time continuously and as soon as any calamity occurs, alerts the website within minutes, thus, allowing us to take action in a quick and swift manner. This may be highly beneficial in saving lives by expanding our time interval to respond and react. The location can be integrated by google maps or google earth, while the mobile app can be integrated with the website containing the database of people, whose current status of nature of environment will be in constant scanning under this project.

Area of Application-This idea can be implemented at places where there is a very high risk of calamity like Japan (people residing there) and at places where travelers may be affected, like a train (people travelling) accidents or any such unfortunate event.

This app is highly useful at places where calamity strikes and we search out for either newspapers or media for information regarding the very same. However, we still remain uncertain regarding our family or friend as we only get the idea of the situation of the place and of the incident that has taken place. Not only we will be in touch with our near and dear once, but we will also be informed about the calamity and may reach out to as many people and as soon as possible. This app is highly beneficial not only for safety of our near and dear ones but also gives us a chance to prove humanity. This is a simple app which does not require millions of buttons selections, neither it involves to confuse people by weird and annoying passwords, especially at the time of calamity who could afford to type passwords and choose from list of buttons instead of saving his or her life. This is a disaster management technique which will ensure people that their families or any close person has the idea that he or she is in danger or trouble, so one can respond to the very same as soon as one can think of. One knows the value of human life today, and this will help us to save plenty of such lives.

Past cases-This project could have been implemented in the most unfortunate cases of tsunami and earthquakes which created a massive life loss, whereas it could also have been used for train accidents and airplane crashes. There are plenty of cases in the world which signify the power of mother earth, and these are the only things which are not controlled by human beings yet. This app gives us a chance to prove that we can at least try our level best to keep track of such mishaps.

Success criteria-This project will ensure faster disaster recovery and disaster management in every country.

• One looks up to a source of information regarding their close ones, we provide them very same and in shorter span of time.

• We will be alerted of any mishap much before the usual timing.

Technology involved-In this project, we have made an app which gets and returns the data from the database which is placed in the website. This app is always active with the people who are about to be affected. We get constant alerts regarding their current state and as soon as any disaster occurs, the person just clicks a button in the phone, it is instantly updated on our website and in the case of emergency, there is alert which is sent to the people close to them (whose database is already collected and stored in the website) also, we alert as many people a little far around that area regarding the incident and thus ask for help and recovery. The status of people will be displayed by google earth or google map. Alerts can be sent via phone, text or e-mail.

Work progress-I have been working on this project since past few months. About one fourth of the work is completed. Currently I am working on how to integrate google map with the phone app and the website. I have considered the following stages of development of my project:

1. Developing the mobile app and developing a website.

2. Integrating the app with the website.

3. Integrating the google map or google earth for clearer view of the position of the individual.

4. Scaling for the database and management of the same.

5. Integrating the database from the mobile app.

6. Measure the correct sending and retrieval of data.

Conclusion-I would like to present this app from this community as I think that this app will be a big contribution for Open-Source. And in my opinion Django Software Foundation will be helpful towards me in presenting my idea further and taking it to the next level by their highly acknowledged guidance and mentoring. If given a chance by Google, I would make sure that I complete this project in the specified time limit and make the Django Community proud of this project. I would make sure that the community does not regret the decision of selecting my project and will make sure that I work very hard to complete the same with guidance from you.

-- 
You received this message because you are subscribed to the Google Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5ab62601-53e7-4f11-bbf2-223c72f78509%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Russell Keith-Magee]

Hi Akanksha,

As Aymeric has said - this sounds like a great project, but it isn't appropriate for Django's Summer of Code program - we are looking for projects to work on and improve Django itself. 

You may want to try and get in contact with the Google Crisis Response team:

http://www.google.org/crisisresponse/

They have a number of tools in this space which they activate when an emergency occurs; and since they're a Google project to start with, they may be interested in running something as part of the SoC. If you don't have any luck getting in contact with them, let me know and I'll see if I can poke someone I know who works in that group.

Another possibility is the Humanitarian Open Street Map Team:

http://hot.openstreetmap.org

I don't know if they've done work with SoC in the past, but they might be interested.

Yours,

Russ Magee %-)

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6617C213-CC08-490D-8E05-3A80CEAED304%40polytechnique.org.

[Akanksha Shrivastava]

Thankyou so much for your guidance sir! i m looking forward to present my ideas for improvement of django. However it would be great if you all could please suggest me with some ideas regarding SoC. Waiting for your reply eagerly and to work for the very same too.

[Russell Keith-Magee]

Hi Akanksha,

We haven't started the GSoC process internally yet, so we haven't put together a collection of sample projects for this year; but if you want to see what we recommended last year, it's on our Wiki:

https://code.djangoproject.com/wiki/SummerOfCode2013

Out of those projects, the Validation project was completed last year, so it's obviously off the candidate list. 

I can think of one additional project that has been mentioned in passing on the developers list: formalising the Meta class.

This project would involve refactoring and documenting the interface to the Model._meta object. This interface is central to the operation of Django itself, but *technically* isn't backwards compatible. There are some aspects of this interface that aren't especially well designed from a public facing perspective, and there are some features that involve subtle duplication. The refactoring project would take a look at all these interfaces, and come up with a clean API that we can formally publish. As a proof of concept that the API definition is complete, the project might involve developing an alternate implementation for some other data source -- for example, a simple wrapper for a NoSQL store -- that can then be used as a duck-type compatible replacement for a "normal" Django model.

The key part about any project proposal for GSoC - you need to convince us that you know what you're planning to do, and convince us that your able to complete it. A key part of this is a project plan with fine grained estimates. A proposal that says "12 weeks - refactor meta" won't convince us; a proposal that gives plausible blocks of work filling 3 days-1 week chunks indicates that probably understand the problem, and will be able to deliver. However, in order to develop this sort of project plan, you're going to need to do some research about the problem - and that research *isn't* something we're going to help with. The fact that you are able to do the research at all is part of our application process to establish that you're capable of completing the project.

Yours,

Russ Magee %-)

--

You received this message because you are subscribed to the Google Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a112cd29-9b07-4716-9ee4-fbeb61ff040f%40googlegroups.com.