Re: [pcp] Interested to contribute to PCP in GSoC 16

[Sitaram Shelke <sitaramshelke@xxxxxxxxx>]

Hello Nathan,
I built htop from source and looked at the source code. I noted few key points which can help to understand the flow of htop.
htop is an interactive process viewer for Unix based systems. It uses 'ncurses'[1] toolkit to provide its interactive interface across independent terminals. How htop displays the data is by monitoring the local '/proc' directory for its files such as stat and meminfo. These functions are defined in the distribution specific directories for eg 'LinuxProcessList_scanCPUTime(LinuxProcessList* this)' in 'Linux/LinuxProcessList.c' in my case. So the project idea proposed is to make htop to be able read data from the pcp APIs so that htop can display historical data as well.
Does this sounds right?
If yes what would you suggest me to do next?
if no please correct me where am I wrong. :)

[1] https://en.wikipedia.org/wiki/Ncurses

Regards.
Sitaram

On Tue, Mar 8, 2016, 11:35 AMÂNathan Scott <nathans@xxxxxxxxxx> wrote:

Hi Sitaram,

----- Original Message -----
> [...]
> Thank you for the reply, so first thing I will do is to download and build
> htop from source and try to dive in into the code to get its better
> understanding.
> Once I am done with that we can discuss further on this. Meanwhile I am
> trying to set up a bouncer to log messages on irc thus I will stick to the
> mailing list for some time.

Sounds good. Keep an eye on the timeline from Google too -
https://developers.google.com/open-source/gsoc/timeline

At the end of this week of familiarization, the next step will involve putting
together a detailed proposal of the work - which is due by the end of the
following week. So as you're looking through the code and discussing it with
me, keep notes and start building up that proposal document as you go - it'll
need to be submitted to the GSoC site relatively soon.

http://teom.org/blog/kde/how-to-write-a-kick-ass-proposal-for-google-summer-of-code/

It's a bit KDE-specific, but all the same principles apply. Note especially:
"get it reviewed [...] well before submitting it to the Google Summer of Code
web application."

cheers.

--
Nathan