linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: dragos.bogdan@analog.com, JManeyrol@invensense.com,
	linux-iio@vger.kernel.org
Subject: Re: [GSOC][RFC] Proposal
Date: Sun, 1 Mar 2020 14:34:18 +0000	[thread overview]
Message-ID: <20200301143418.438ce7f9@archlinux> (raw)
In-Reply-To: <5e581673.1c69fb81.9fd7b.25c2@mx.google.com>

On Fri, 28 Feb 2020 00:50:15 +0530
Rohit Sarkar <rohitsarkar5398@gmail.com> wrote:

> On Tue, Feb 25, 2020 at 09:41:37PM +0530, Rohit Sarkar wrote:
> > Hi,
> > I am proposing to work on the accelerometer MPU6050 as my primary
> > project for the summer. The work items are outlined in [1] thanks to
> > Jean.
> > If time permits (which it should), I will be picking up other tasks
> > outlined in [2] by Jonathan and Alexandru.
> > 
> > 
> > Would like to hear people's views on this.
> > 
> > [1]: https://marc.info/?l=linux-iio&m=158257639113000&w=2
> > [2]: https://marc.info/?l=linux-iio&m=158261515624212&w=2
> > Thanks,
> > Rohit
> >   
> 
> Hey guys,
> would love some feedback on this.
> There are no proposals as such on the GSOC IIO page [1].
> Was wondering if there is any new iio driver that can be made into a
> gsoc project.

Hi Rohit,

A couple of questions.   Do you have a gsoc mentor lined up?

You should discuss a proposal with whoever that is.

My gut feeling is that the features suggested by Jean-Baptisite
do not form a particularly good focus for the body of a gsoc project.
There are too many rather disassociated items, without a connected
'story'.

They are good items for getting familiar with the subsystem and
a particular driver but for the actual project you probably want
something that is more 'yours' in the sense that you drive it from
initial prototypes through to final upstream code.

Previous projects have (I think) mostly centred on support for a new
driver. 

Thanks,

Jonathan



  reply	other threads:[~2020-03-01 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 16:11 [GSOC][RFC] Proposal Rohit Sarkar
2020-02-27 19:20 ` Rohit Sarkar
2020-03-01 14:34   ` Jonathan Cameron [this message]
2020-03-02  5:03     ` Rohit Sarkar
2020-03-03 20:29       ` Jonathan Cameron
2020-03-04 17:57         ` Rohit Sarkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200301143418.438ce7f9@archlinux \
    --to=jic23@kernel.org \
    --cc=JManeyrol@invensense.com \
    --cc=dragos.bogdan@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=rohitsarkar5398@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).