new GSoC rules
Leo Franchi
lfranchi at kde.org
Thu Jul 23 01:33:17 CEST 2009
On 22 Jul 2009, at 19:10, Lydia Pintscher wrote:
> Folks,
>
> - Communicate about your project in our IRC channel, not queries!
> - Send emails about your project to this list, not just your mentor!
> - Status reports are due Monday evening your time. I mean it.
> - Commit your code to gitorious so it can be reviewed. Show me the
> code.
> - Daily scrum meetings with Ian where applicable.
> - This should be a full-time job.
> - If you have a problem ask. And don't get stuck waiting for your
> mentor. Ask the rest of the team.
>
> => Non-public progress is considered no progress.
+1
Communication is important. Progress is important. We have gitorious
now---there is exactly 0 reason to not have your code up there. This
obviously doesn't apply to everyone, but the message seems not to be
getting through to some people. Yes, weekly status updates are
required. That doesn't mean that weekly status updates are ALL that is
required---general communication, committing, and being a part of the
community as other developers is as if not more important.
So, please, send your updates, discuss with your mentor in .dev, and
commit your code publically. For those doing the scrum thing with Ian,
please respond and stick to the times. That's the whole point of the
system.
Chasing after people is not our job. It's detrimental to everyone.
leo (wearing the SoC admin hat)
>
> What happened to the "we are all mentoring the students together" we
> did last year? So far communication is _really_ failing and it shows
> in the progress of some of the projects.
> I really really want you all to finish your projects successfully.
> Failing because you/your mentor are not communicating with each other
> or the rest of us would be a big loss.
What we can't see we can't evaluate. Just going on words is fine---
once a basic foundation of trust has been established.
leo
---
Leo Franchi (650) 704 3680
Tufts University 2010
lfranchi at kde.org
leonardo.franchi at tufts.edu
More information about the Amarok-devel
mailing list