Forwarded conversationSubject:
Continue Working on Proposal------------------------
From: pravendra rathore <address@hidden>
Date: Tue, Apr 22, 2014 at 8:36 AM
To: address@hidden, Jishnu Mohan <address@hidden>, Santhosh Thottingal <address@hidden>, Vasudev Kamath <address@hidden>
Hi there,
for me it's depressing to not getting selected into GSoC, because I needed money :D , but still I don't have anything interesting to do in summers.
I'm just posting it here because I got in mail that if I want then I can think on working on my proposal for SMC.
My proposal was to `Developing Project-SILPA API and tool related to it helping `
So just asking that what should be the procedure, if you people allow me to work on this and what kind of help I will get.
----------
From: Vasudev Kamath <address@hidden>
Date: Tue, Apr 22, 2014 at 12:44 PM
To: pravendra rathore <address@hidden>
Cc: Jishnu Mohan <address@hidden>, Santhosh Thottingal <address@hidden>
On Tue, Apr 22, 2014 at 8:36 AM, pravendra rathore <
address@hidden> wrote:
> or me it's depressing to not getting selected into GSoC, because I needed
> money :D , but still I don't have anything interesting to do in summers.
Probably you should know the reason why we didn't consider your application.
Before proposing any idea you should consider discussing it with
mentors, to see if its really worth. This is most important for any
FOSS project, you should communicate with team propose the idea get
feed back and then proceed but your idea came to us from no where! We
were surprised to see this idea being proposed because we don't need
any such tools or dashboard.
You might have sent mail when you proposed idea but there were many
mails and replying to every one isn't possible for us with limited
time so we didn't select to respond back. I've also seen you showing
up in IRC and saying "Are you there?" now that really doesnt't help!.
I keep my IRC nick online every day from my server so I will respond
only when I come online. Now "Are you there?" doesn't give me idea
what you wanted to ask! So ask question in IRC and wait there till
people show up, saying "Hi", "Are you there" won't get you anywhere.
So if you want quicker reply better is reaching us over email, you
could write to
address@hidden and we could have responded.
I'm telling all these because I assume this is your first time with
FOSS communities, so you can consider this as learning experience.
>
> I'm just posting it here because I got in mail that if I want then I can
> think on working on my proposal for SMC.
> My proposal was to `Developing Project-SILPA API and tool related to it
> helping `
As a community we need more developers to help improve tool, So you
are always welcome to join and help us but probably your dash board
idea has not convinced none of us, if you still think its needed then
convince us first!.
>
> So just asking that what should be the procedure, if you people allow me to
> work on this and what kind of help I will get.
There is no procedure, if you have idea talk to us over mailing list
discuss details, show us proof of concept then if all goes well raise
us a PR.
I'm currently doing major restructure of SILPA code, and at the moment
there are too much open ends which I need to tie together, once that
is done I will write and update documents and write what remains to be
done etc. Mean while you can have a look at issues on github and see
what you can fix.
PS: I've seen your PR but didn't get enough time to act on, When I've
time I will revert back to you.
Cheers,
--
Vasudev Kamath
http://copyninja.info
address@hiddenfrndk.de|vasudev.homelinux.net}
----------
From: pravendra rathore <address@hidden>
Date: Tue, Apr 22, 2014 at 2:43 PM
To: Vasudev Kamath <address@hidden>
Cc: Jishnu Mohan <address@hidden>, Santhosh Thottingal <address@hidden>
Hi,
first of all thanks for description you have written about wrongs I have done.
>
> I'm telling all these because I assume this is your first time with
> FOSS communities, so you can consider this as learning experience.
Yes! it was my first experience with a FOSS community in GSoC, I have contributed to Open-Source and have Development experience in Teamwork but this was different from what I have done.. So, thanks for that.
as, you wrote about disliking Dashboard tool proposed
>
> but probably your dash board idea has convinced none of us, if you still think its needed then convince us first!.
Here I'm confused that you are talking about all three tools I proposed or only Dashboard one.
anyway, I am trying again to convince you people.
Proposal Project was divided in 2 parts :
1. REST API Development
2. Tools Related to Project-SILPA
I know first was clear to you as it was mentioned already there in ideas list.
I proposed second part of project because I see/use related things daily here for my software group(SDSLabs) or on internet.
it consisted 3 tools :-
(a). Admin/Developer Control Panel
Now lets see some problems or issues in daily life work, for example :
- You are debugging an existing module(ex. Transliteration) and don't want production side API affected by your code changes. So a solution separating Development and Production API's is needed here.
- API service is working fine, suddenly you want to remove a particular module or add(or in simple way kind of enable/disable)
- if we move ahead (as Project-SILPA is growing) and implement authentication based API then it can help Admin to stop service for a particular client, in case client is creating some issue (Security related feature)
now, both 'Status Board' and 'Developer Dashboard' are basically same as a purpose, having difference only that some Statistics that you don't want to be publicized are in 'Developer Dashboard' additionally to 'Status Board'.
some features that I proposed for them are :-
- Status on API use
- Relative Distribution of modules in API use
- API Response Time
- API Service Uptime
an Additional feature in 'Developer Dashboard' as I said can be 'Tracking API use by clients' if we move ahead with authentication based API. now obviously we don't want it to be public as I defined.
>
> We were surprised to see this idea being proposed because we don't need any such tools or dashboard.
I proposed this all by seeing continuous Development under Project-SILPA as Android SDK related project got selected this year, so there will be android apps powered by SILPA and so on.
may be, you will say one day on your own that we need this, if project carry on going under development.
and about 'Status/Dashboard'..
yes, in my view, having an API status board is not a thing that you need necessarily as a Developer Role,
but people using your API will need it for their applications they want to implement using your service.
actually I liked the project, its use cases and have experience in API Development, so got more interested.. thats why still want to contribute. Hope this make things clear to you.
Thanks..
----------
From: Vasudev Kamath <address@hidden>
Date: Tue, Apr 22, 2014 at 4:05 PM
To: pravendra rathore <address@hidden>
Cc: Silpa mailing list <address@hidden>
On Tue, Apr 22, 2014 at 2:43 PM, pravendra rathore <
address@hidden> wrote:
>> but probably your dash board idea has convinced none of us, if you still
>> think its needed then convince us first!.
>
> Here I'm confused that you are talking about all three tools I proposed or
> only Dashboard one.
> anyway, I am trying again to convince you people.
>
> Proposal Project was divided in 2 parts :
>
> 1. REST API Development
> 2. Tools Related to Project-SILPA
>
> I know first was clear to you as it was mentioned already there in ideas
> list.
> I proposed second part of project because I see/use related things daily
> here for my software group(SDSLabs) or on internet.
Ok some nitpicking here so that we can openly think on these points.
>
> it consisted 3 tools :-
>
> (a). Admin/Developer Control Panel
> Now lets see some problems or issues in daily life work, for example :
>
> - You are debugging an existing module(ex. Transliteration) and don't want
> production side API affected by your code changes. So a solution separating
> Development and Production API's is needed here.
Probably I can still do these running a
dev.silpa.org.in and
silpa.org.in separately where development code can be tested on
dev.silpa.org.in and I will not cause problems to production code!. Am
I missing any scenario which you are trying to solve?
> - API service is working fine, suddenly you want to remove a particular
> module or add(or in simple way kind of enable/disable)
I can simply comment out the module in configuration and our services
are configured to reload the entire app on file touch and Wala it
works :). But probably a front end to config may be good idea!.
> - if we move ahead (as Project-SILPA is growing) and implement
> authentication based API then it can help Admin to stop service for a
> particular client, in case client is creating some issue (Security related
> feature)
Probably security thing is not the problem which we need to solve in
our framework isn't it?. there are tools like iptables or fail2ban
which can be enforced on misbehaving clients. Also we don't hold any
state and don't plan to do that in future also. Having no state our
application doesn't care who sends us requests then how do you plan to
solve this problem? (but I prefer external utilities to safe guard
from misbehaving clients).
>
> now, both 'Status Board' and 'Developer Dashboard' are basically same as a
> purpose, having difference only that some Statistics that you don't want to
> be publicized are in 'Developer Dashboard' additionally to 'Status Board'.
>
> some features that I proposed for them are :-
> - Status on API use
> - Relative Distribution of modules in API use
> - API Response Time
> - API Service Uptime
Can you explain more on this status thingy? I'm unclear what you were
trying to solve here.
>
> an Additional feature in 'Developer Dashboard' as I said can be 'Tracking
> API use by clients' if we move ahead with authentication based API. now
> obviously we don't want it to be public as I defined.
Authentication will probably never be implemented in our case I guess.
>
>>
>> We were surprised to see this idea being proposed because we don't need
>> any such tools or dashboard.
>
> I proposed this all by seeing continuous Development under Project-SILPA as
> Android SDK related project got selected this year, so there will be android
> apps powered by SILPA and so on.
> may be, you will say one day on your own that we need this, if project carry
> on going under development.
May be my explanation above will give you picture on why we were
surprised! :). And if you have discussed it with us before probably we
could have converted it into much productive idea :). But anyway.
>
> and about 'Status/Dashboard'..
> yes, in my view, having an API status board is not a thing that you need
> necessarily as a Developer Role,
> but people using your API will need it for their applications they want to
> implement using your service.
>
> actually I liked the project, its use cases and have experience in API
> Development, so got more interested.. thats why still want to contribute.
> Hope this make things clear to you.
The REST api implementation is still open but you might need to look
for development branch before implementing it!. Also there aree tons
of refactoring needs to be done most of them are inside my brain only
which is bad, I'm trying to find some time to document it but if you
can join us I can share those information and you can see what you can
implement in those.
Yes please send it to
address@hidden, so others can also contribute.