polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <hedh...@gmail.com>
Subject Fwd: [Fwd: Time to propose a CS Capstone Project!]
Date Tue, 23 Aug 2016 04:05:48 GMT
---------- Forwarded message ----------
From: <shathawa@e-z.net>
Date: Aug 23, 2016 11:35
Subject: [Fwd: Time to propose a CS Capstone Project!]
To: <dev@community.apache.org>

I have participated in Oregon State University (Corvallis, Oregon USA)
undergraduate senior projects in the past. The Capstone program is an
opportunity for our open source software communities to propose a
three-term project for students and provide mentors to the projects.  The
mentors get to interact with students and their evaluation becomes a part
of their performance evaluation grade.

These Capstone university projects can readily support the Apache Software
Foundation health.

I live and work within commute distance of the university.  One of the
previous projects had a mentor in Denmark.  International cooperation can
be accommodated.

Steven J. Hathaway

---------------------------- Original Message ----------------------------
Subject: Time to propose a CS Capstone Project!
From:    "D. Kevin McGrath" <dmcgrath@eecs.oregonstate.edu>
Date:    Mon, August 22, 2016 12:30 pm
To:      shathawa@e-z.net

Colleagues --

Have you always wanted a particular software tool developed for your use,
have never had the time to do it yourself? Well then, read on. Have I got
a deal
for you!

My name is Kevin McGrath. I am the instructor who runs the OSU Computer
Senior Capstone class. The Capstone class is a 3-quarter (Fall, Winter,
"career preparation" experience. The major piece of this is doing a
3 member team project.

When the students come to the first class on September 24, I want to present
them with a list of exciting, creative, and real-experience software
project possibilities. This is where you come in. I am looking for you to
your needs and experience to propose those project possibilities.

A web site has been setup to give you more information, and let you enter
edit your project proposals:


You have until September 15 to get yours in. If any clarification would be
necessary, you'd have from the 15th to the first day of term to clarify.
That is
when the students will see them, and will start the selection process. In
process, I ask the students to "bid" on their top 5 choices. I ultimately
the final project assignments, but endeavour to take their preferences into
account. I find I get better results that way.

There will likely be more projects proposed than students teams to do
them. *So,
really sell your project.* Definitely don't understate its cool-ness
factor! The
more excited you sound in the description, the more excited they are
likely to
be when doing it. Excitement is contagious! If you'd be interested in
your project to the students in person, please let me know! Personally
projects tend to generate more excitement from the students.

After projects have been selected, we will follow a client-contractor
model in
which I "run" the software contract company and you are one of our valued
clients. The students "report" to me, but you, as client, work directly with
them to design the requirements, set the timeline, approve the progress. You
also get to help assign grades.

This year I'm asking you to explicitly distinguish the projects that are
research oriented vs. those that are more software engineering focused. If
would like to propose a research project for the students, please indicate
using the Additional Comments field.

Given the nature of a research oriented project, I find that better
results are
had if the students are initially aware of the type of project. If you are
unsure, that is not a problem. I'm happy to work with you on the details
of your
project -- just submit it, and then we can chat about any changes that
might be

Any project can be proposed from anybody. I don't care where you are from,
that your project represents an excellent software engineering experience
the students.

Do remember, however, that these are seniors. They have taken the core
so far, but most have not taken some of the electives that would really
help in
some projects, such as graphics, AI, computer vision, etc. Keep that in mind
when proposing.

Several additional points to keep in mind:

         1) We ask for about 1 hour per week to interact with the students

         2) If you propose a project that will be handed off to another
             engineer/developer to mentor, please list their name as well
             as an additional contact.

         3) Any IP restrictions need to be listed. These can include NDAs,
             assignment of IP, etc. University policy is that students own
the IP
             of their projects, so if you have something else in mind, be
             clear from the proposal. Negotiations/agreements will be
between you
             and the students, rather than you and the university.

         4) The general scope of the project is what you would give one

If you have questions or want to discuss project possibilities, feel free to
contact me at:

                 D. Kevin McGrath
                 Instructor, Computer Science
                 Oregon State University
                 2109 Kelley Engineering Center

Thanks for your time -- I look forward to working with you!

                                                 -- Kevin McGrath

To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message