* How to work on Sparse for Summer of Code 2008
@ 2008-03-18 4:14 Josh Triplett
2008-03-18 4:21 ` Barton C Massey
2008-03-19 2:04 ` rajika
0 siblings, 2 replies; 4+ messages in thread
From: Josh Triplett @ 2008-03-18 4:14 UTC (permalink / raw)
To: linux-sparse
[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]
Sparse did not get accepted as a mentoring organization for Google
Summer of Code 2008. However, Portland State University has
graciously agreed to accept applications for Sparse projects under the
PSU banner. Thus, any student wishing to work on Sparse for Summer of
Code 2008 should apply to Portland State University. (You do not need
to attend PSU or have any affiliation with PSU.)
Some application guidelines you should follow to improve your chances
of getting accepted (some reiterated from my previous mail):
* Clearly state that you want to work on Sparse; don't make the
mentors figure it out from context. PSU will have many different
applications for different projects.
* Explain your project as concretely as you can. Don't just give an
abstract idea like "Improve Sparse's support for $FOO."; give a
concrete proposal for what Sparse or a technology built on Sparse
will do at the end of the summer that it can't do at the beginning
of the summer.
* If your project relates to making Sparse handle a new C construct,
or detect a new type of problem, give code examples for the
construct or the problem.
* Set realistic goals. You don't have talk big to get accepted; you
have to convince us you have a project you can complete. Feel free
to set ambitious goals, just convince us you can accomplish them.
* Point to any examples of projects you have worked on in the past.
Bonus if you point to particular instances of contributions you made
and the interactions you had with the project's community to get
those contributions merged. Note that this in no way means you have
to have this type of experience in order to get accepted; on the
contrary, Google Summer of Code exists in part to help people new to
the Free and Open Source Software process. This just means that
*if* you have such experience, you should call attention to it, and
that will help us evaluate your ability to succeed with your
proposal.
* Release early, release often. Please get comfortable with the idea
of releasing your work to the Sparse mailing list, regardless of the
current state of that work.
* Explain how you plan to keep your mentor informed of your status.
* Explain how you would stay in contact with your mentor if something
happened to make you unable to get connectivity for a while.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to work on Sparse for Summer of Code 2008
2008-03-18 4:14 How to work on Sparse for Summer of Code 2008 Josh Triplett
@ 2008-03-18 4:21 ` Barton C Massey
2008-03-19 2:04 ` rajika
1 sibling, 0 replies; 4+ messages in thread
From: Barton C Massey @ 2008-03-18 4:21 UTC (permalink / raw)
To: Josh Triplett; +Cc: linux-sparse
Please see http://summer.cs.pdx.edu/propose for some more
advice about how to write a strong application for us.
Looking forward to the chance to work with some of you as
part of SoC 2008!
Bart Massey
Assoc. Prof. Computer Science
Portland State University
bart@cs.pdx.edu
In message <47DF41AD.4060701@freedesktop.org> you wrote:
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --------------enig30C952DD71625AD84960AEE4
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> Sparse did not get accepted as a mentoring organization for Google
> Summer of Code 2008. However, Portland State University has
> graciously agreed to accept applications for Sparse projects under the
> PSU banner. Thus, any student wishing to work on Sparse for Summer of
> Code 2008 should apply to Portland State University. (You do not need
> to attend PSU or have any affiliation with PSU.)
>
> Some application guidelines you should follow to improve your chances
> of getting accepted (some reiterated from my previous mail):
>
> * Clearly state that you want to work on Sparse; don't make the
> mentors figure it out from context. PSU will have many different
> applications for different projects.
>
> * Explain your project as concretely as you can. Don't just give an
> abstract idea like "Improve Sparse's support for $FOO."; give a
> concrete proposal for what Sparse or a technology built on Sparse
> will do at the end of the summer that it can't do at the beginning
> of the summer.
>
> * If your project relates to making Sparse handle a new C construct,
> or detect a new type of problem, give code examples for the
> construct or the problem.
>
> * Set realistic goals. You don't have talk big to get accepted; you
> have to convince us you have a project you can complete. Feel free
> to set ambitious goals, just convince us you can accomplish them.
>
> * Point to any examples of projects you have worked on in the past.
> Bonus if you point to particular instances of contributions you made
> and the interactions you had with the project's community to get
> those contributions merged. Note that this in no way means you have
> to have this type of experience in order to get accepted; on the
> contrary, Google Summer of Code exists in part to help people new to
> the Free and Open Source Software process. This just means that
> *if* you have such experience, you should call attention to it, and
> that will help us evaluate your ability to succeed with your
> proposal.
>
> * Release early, release often. Please get comfortable with the idea
> of releasing your work to the Sparse mailing list, regardless of the
> current state of that work.
>
> * Explain how you plan to keep your mentor informed of your status.
>
> * Explain how you would stay in contact with your mentor if something
> happened to make you unable to get connectivity for a while.
>
> - Josh Triplett
>
>
> --------------enig30C952DD71625AD84960AEE4
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: OpenPGP digital signature
> Content-Disposition: attachment; filename="signature.asc"
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFH30GtGJuZRtD+evsRAnbAAJ9SwXJb9pWAmFIxxswZncA3AqjnoACcCLyi
> nXKJ+Fnm+GQCU/uPilDaPG4=
> =g6t9
> -----END PGP SIGNATURE-----
>
> --------------enig30C952DD71625AD84960AEE4--
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to work on Sparse for Summer of Code 2008
2008-03-18 4:14 How to work on Sparse for Summer of Code 2008 Josh Triplett
2008-03-18 4:21 ` Barton C Massey
@ 2008-03-19 2:04 ` rajika
2008-03-31 6:17 ` Josh Triplett
1 sibling, 1 reply; 4+ messages in thread
From: rajika @ 2008-03-19 2:04 UTC (permalink / raw)
To: Josh Triplett; +Cc: linux-sparse
hi,
I was searching through the project list at PSU[1], but unable to locate the
open project list for sparse. Is that same as 2007[2]?, Can you please guide me
to the open project list of sparse at PSU?.
Thanks in advance.
Regards,
Rajika
[1]- http://summer.cs.pdx.edu/ideas
[2]- http://kernel.org/pub/software/devel/sparse/soc.html
Quoting Josh Triplett <josh@freedesktop.org>:
> Sparse did not get accepted as a mentoring organization for Google
> Summer of Code 2008. However, Portland State University has
> graciously agreed to accept applications for Sparse projects under the
> PSU banner. Thus, any student wishing to work on Sparse for Summer of
> Code 2008 should apply to Portland State University. (You do not need
> to attend PSU or have any affiliation with PSU.)
>
> Some application guidelines you should follow to improve your chances
> of getting accepted (some reiterated from my previous mail):
>
> * Clearly state that you want to work on Sparse; don't make the
> mentors figure it out from context. PSU will have many different
> applications for different projects.
>
> * Explain your project as concretely as you can. Don't just give an
> abstract idea like "Improve Sparse's support for $FOO."; give a
> concrete proposal for what Sparse or a technology built on Sparse
> will do at the end of the summer that it can't do at the beginning
> of the summer.
>
> * If your project relates to making Sparse handle a new C construct,
> or detect a new type of problem, give code examples for the
> construct or the problem.
>
> * Set realistic goals. You don't have talk big to get accepted; you
> have to convince us you have a project you can complete. Feel free
> to set ambitious goals, just convince us you can accomplish them.
>
> * Point to any examples of projects you have worked on in the past.
> Bonus if you point to particular instances of contributions you made
> and the interactions you had with the project's community to get
> those contributions merged. Note that this in no way means you have
> to have this type of experience in order to get accepted; on the
> contrary, Google Summer of Code exists in part to help people new to
> the Free and Open Source Software process. This just means that
> *if* you have such experience, you should call attention to it, and
> that will help us evaluate your ability to succeed with your
> proposal.
>
> * Release early, release often. Please get comfortable with the idea
> of releasing your work to the Sparse mailing list, regardless of the
> current state of that work.
>
> * Explain how you plan to keep your mentor informed of your status.
>
> * Explain how you would stay in contact with your mentor if something
> happened to make you unable to get connectivity for a while.
>
> - Josh Triplett
>
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to work on Sparse for Summer of Code 2008
2008-03-19 2:04 ` rajika
@ 2008-03-31 6:17 ` Josh Triplett
0 siblings, 0 replies; 4+ messages in thread
From: Josh Triplett @ 2008-03-31 6:17 UTC (permalink / raw)
To: rajika; +Cc: linux-sparse
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
rajika@cse.mrt.ac.lk wrote:
> hi,
> I was searching through the project list at PSU[1], but unable to locate the
> open project list for sparse. Is that same as 2007[2]?, Can you please guide me
> to the open project list of sparse at PSU?.
> Thanks in advance.
> Regards,
> Rajika
> [1]- http://summer.cs.pdx.edu/ideas
> [2]- http://kernel.org/pub/software/devel/sparse/soc.html
Yes, at the moment I just have the same project list up from 2007.
That page needs updating.
However, I would also encourage you to propose any other Sparse-related idea
you would like to work on, not just those on the fairly small ideas list.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-03-31 6:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-18 4:14 How to work on Sparse for Summer of Code 2008 Josh Triplett
2008-03-18 4:21 ` Barton C Massey
2008-03-19 2:04 ` rajika
2008-03-31 6:17 ` Josh Triplett
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.