Hello,
First of all thank you so much for all the provided details and info. I've
managed to look more on the already existent code-base for the projects
(besides OpenMonitor, which I have seen on the other threads that is not
available yet) and get a pretty good idea of what each project is really
about. I have to say that what umitproject has done so far is really really
cool and I would be really happy if I could spend my summer contributing to
the projects.
Altough most of the ideas seem interesting, when we submit the proposal for
the GSOC we'll have to choose only one, or we can submit multiple proposals?
Now, I have 2 more questions regarding the projects:
- Status Site: Well, here there are 2 possibilities:
- we make a solution that we manage and people just come to our
website, register their website and then they have access to a monitoring
tool. However we cannot do anything to automate the redirection
process if
their server is completely down. However, we could create some
nice scripts
in the most used developing languages (php, jsp) or some plugins (for
joomla, wordpress etc), that the user can somehow integrate in their site
and allows them to put the website in "maintenance mode" (or something
similar), when they are working on the website or when they know it will
not be available. The script/plugin would redirect user to our
status site
that provides live details recarding the availabilty.
- Some thought on the idea: we can develop it on appengine as it
has pretty nice free plans, however, at some point, the site
will grow so
much that it will need to go to paying (which we will have to handle)
- we make the solution as a website that can be installed by users on
their own servers. However, this has also some aspects we have
to consider:
- if it runs on the same server/hosting to the same one that
crashes (has downtime), it will not work either.
- most of the users will not be to eager to set up a new website
(even though we make it really easy). Some people simply have
a hosting
taken somewhere which gives them some limitations regarding how many
websites they can host...
- it will be extremely difficult to provide a working solution for
everyone (php, jsp, wordpress, ruby on rails, python, etc).
- So, which one should we go with?
- Regarding the Aggregator for the open monitor, it really seems
interesting for me, as I have quite some experience using Appengine and
Java. The ideea of supporting slave aggregators is really cool. Besides
being simple aggregators, I would also add a "client agent" functionality
on them, and I'll explain why. If we make the slave aggregators easy
installable by people everywhere around the world, as they "should" be
online all the time, they can also be used to provide information about
that part of the world. I was also thinking of creating (besides the
Desktop and Mobile Agents), a Server Agent, that could be installed be
people on their own server (which, conversely to desktop and mobile agents)
run all the time and can provide much more information. Is this a feasible
idea?
Thanks,
Cosmin
On Thu, Mar 22, 2012 at 17:14, Adriano Marques <[email protected]> wrote:
> Hi Cosmin!
>
> I'm glad you liked our ideas!
>
> You seem to be a good fir and to have a nice background!
>
> Let me answer your question below...
>
> On Thu, Mar 22, 2012 at 9:05 AM, Cosmin Stefan-Dobrin <
> [email protected]> wrote:
>
>> Hello,
>>
>> My name is Cosmin Stefan-Dobrin and I am a student at the Politechnics
>> University of Bucharest, Computer Science faculty. I am an extremely
>> passionate programmer (and soon-to-be engineer), who's always interested in
>> the latest technologies and latest trends in IT development. I am
>> interested in applying for Google Summer Of Code 2012, and the projects
>> proposed by UMIT are extremely interesting. I'm a fast learner and I have
>> quite a lot of experience in Java, C/C++, HTML, CSS, JS, SOAP/REST
>> principles, Google Appengine and using git/svn as I've worked on numerous
>> projects at the university and on my spare time (one of the biggest
>> projects I've recently worked on is www.feedrz.com, which is only at its
>> beginnings and which I have developed with a friend, during the free time).
>>
>> I am interested in working on Umit during the GSOC. Two of the proposed
>> tasks ( *"Site Status"[1]* and any of the "*Android projects***" [2] or
>> [3]) have particularly caught my attention, altough they're not the only
>> UMIT projects that seem interesting. Anyway, I would like to know what
>> should I do next (in the following days), to get better connected to the
>> project?
>
>
> You can checkout the repository for the android projects, run locally and
> see how you can improve it.
> For site status, we don't have code on the repo yet, but you can already
> look for ideas to improve the original one.
>
>
>> And, I am going to ask pretty straight and honest, which of the projects
>> is the most important for Umit, as I would be interested in helping you
>> with what you need most.
>>
>
> Open Monitor is definitely our most interesting and important project at
> the moment. It has the potential to literally touch and help millions of
> internet users world wide and is a very promising project in terms of
> engineering challenges.
>
> Nevertheless, all projects listed there are of great importance, although
> we may not end up developing all of them.
>
>
>> Regarding the projects, I would also have some questions:
>>
>>
>>
>> - for the Site Status project, I'm not sure if I've got the idea ok:
>> We are supposed to develop a site-status system (as a web-page or as an
>> addon?) that can be used by other web-developers in their own projects, so
>> that when their main website is down, the users are redirected to this
>> status page, where the described features are available? I have quite a
>> lot
>> of experience with GAE, JSP and servlets. Should it be developed with
>> these
>> technologies?
>>
>>
> This is meant to be a standalone site, that can be easily used to monitor
> any site on the web, regardless of the technology they are written. The
> redirect feature is very important, althought it is little we can do to
> automate this in a generic way for any website. But think of this as a full
> featured system, that runs on its own, on different hosting server, relying
> on different servers and services completely so it can reliable keep track
> of availability of servers somewhere else. I am the one who envisioned this
> idea, so if you need more insights, keep asking :)
>
>
>>
>> -
>>
>> [1] -
>> http://dev.umitproject.org/projects/umitproject/wiki/GSoC2012Ideas#4-Site-Status<https://code.google.com/p/zaproxy/source/browse/trunk/src/org/zaproxy/clientapi/>
>> [2] -
>> http://dev.umitproject.org/projects/umitproject/wiki/GSoC2012Ideas#9-Network-Scanner-Android-Devices<http://dev.umitproject.org/projects/umitproject/wiki/GSoC2012Ideas#9-Network-Scanner-Android-Devices>
>> [3] -
>> http://dev.umitproject.org/projects/umitproject/wiki/GSoC2012Ideas#13-Mobile-Sniffer-for-Android<http://dev.umitproject.org/projects/umitproject/wiki/GSoC2012Ideas#13-Mobile-Sniffer-for-Android>
>>
>>
>> Thank you and have a wonderful day,
>> Cosmin
>>
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> Umit-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/umit-devel
>>
>>
>
>
> --
> Adriano Monteiro Marques
>
> http://www.openmonitor.org
> http://www.umitproject.org
> http://www.thoughtspad.com
>
> "Don't stay in bed, unless you can make money in bed." - George Burns
>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel
