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

[Sitaram Shelke <sitaramshelke@xxxxxxxxx>]

Hello Community,

I have uploaded my proposal for "PCP versions of console tools" and shared it on the GSoC website.

I would like to get feedback on it so that I can improve it further before final submission.

Thank you.

Regards,

Sitaram

On Tue, Mar 15, 2016 at 3:40 AM, Nathan Scott <nathans@xxxxxxxxxx> wrote:

Hi Sitaram,

Lukas just mentioned to me that it is now open... so got for it.

cheers.


----- Original Message -----
> Hello Nathan,
> Thanks for the reply. I will take a good look into pidstat and mpstat as
> well and will try to write details about them in the proposal.
> Yes, I have already started writing the proposal and will share it once the
> GSoC Proposal link opens so that I can get it reviewed multiple times.
> Regards,
> Sitaram Shelke
>
> On Mon, Mar 14, 2016 at 10:38 AM, Nathan Scott <nathans@xxxxxxxxxx> wrote:
>
> > Hi Sitram,
> >
> > ----- Original Message -----
> > > 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.
> >
> > Good stuff.
> >
> > > '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?
> >
> > Yes, spot on - that's the first part of the project. Beyond the code, it'd
> > be a good idea to document your work (see htop.1) and test it (looks like a
> > test_spec.lua exists in the htop source that may be helpful there).
> >
> > > If yes what would you suggest me to do next?
> > > if no please correct me where am I wrong. :)
> >
> > You're following the idea well, no problems at all. The project
> > description
> > also goes into writing other simpler tools like pidstat and mpstat using
> > the
> > PCP APIs - I think it would be a good idea to include at least these two in
> > your proposal also.
> >
> > In terms of what to do next, I recommend you follow the timeline on the
> > GSoC
> > website - the next step is for you to write a detailed proposal of
> > everything
> > you intend to achieve over the summer, based on the discussions we've had.
> > Have a read through the docs for students there, and elsewhere on the net -
> > there's alot been written about how to write a good GSoC proposal.
> >
> > Make sure you submit draft copies to the GSoC site; these are visible to
> > the
> > project mentors and we can do some initial proof-reading, to give you early
> > feedback before the submission deadline arrives.
> >
> > cheers.
> >
> > --
> > Nathan
> >
>
>
>
> --
> -sitaram
>

--

-sitaram