Urgent: end-term evaluation upcomming
Willebil
Some students have provided me with some progression reports, but in
general it has been very silent.
I just want to notify all students that the end-term ends at August
20th. Students need to have uploaded their code to the Google Summer
of Code project repository and the mentors begin final evaluations. We
are less then a week to go, just notifying everyone.
Wilco
Charl van Niekerk
> The last interaction I have seen was around the mid-term evaluation.
> Some students have provided me with some progression reports, but in
> general it has been very silent.
The last few weeks have been very silent indeed; both on the list and on IRC. :(
> I just want to notify all students that the end-term ends at August
> 20th. Students need to have uploaded their code to the Google Summer
> of Code project repository and the mentors begin final evaluations. We
> are less then a week to go, just notifying everyone.
As far as I understand, students can upload their code to the GSoC
Google Code repository between the 20th and the 31st and continue work
after the 20th but will only be evaluated based on work done up to
19:00 UCT on the 20th (or at least, that's what I gather from the
students mailing list). Does that sound correct?
Regarding work done afterwards, where can we commit that? I can create
two "branches" on my project repository (for example "JXHTML/trunk"
and "JXHTML/soc"). Maybe I should rather register a new Joomlacode
project and commit the "trunk" stuff to there for the longer term?
Regards,
Charl
--
Charl van Niekerk
http://charlvn.za.net
Enno Klasing
>> I just want to notify all students that the end-term ends at August
>> 20th. Students need to have uploaded their code to the Google Summer
>> of Code project repository and the mentors begin final evaluations. We
>> are less then a week to go, just notifying everyone.
> As far as I understand, students can upload their code to the GSoC
> Google Code repository between the 20th and the 31st and continue work
According to
http://groups.google.com/group/google-summer-of-code-announce/web/how-to-provide-google-with-sample-code
we do *not* have to upload any code *before* we get a passing evaluation.
> after the 20th but will only be evaluated based on work done up to
> 19:00 UCT on the 20th (or at least, that's what I gather from the
> students mailing list). Does that sound correct?
Correct.
> Regarding work done afterwards, where can we commit that? I can create
> two "branches" on my project repository (for example "JXHTML/trunk"
That's how I plan to handle it. I will still need to make some
adjustments (no code changes, just adding the README for Google,
deleting some files that are not part of my work etc.) after Monday
evening, and I'm gonna do them in a separate branch, where I will
prepare the tarball for Google. If neccessary, I'll do any further code
changes (which will not be part of the evaluated code) in my main trunk.
> and "JXHTML/soc"). Maybe I should rather register a new Joomlacode
> project and commit the "trunk" stuff to there for the longer term?
Unless Wilco or anyone else of the program admins tells us not to do so,
I'd maintain the code in the SoC SVN, even after SoC ends. After all,
you usually do want to have the history. Starting a new project on
joomlacode would mean to start without any of the history. Also, anyone
who is/was watching your code would have to switch over to the new SVN -
additional work that can be avoided.
Enno
Charl van Niekerk
> According to
> http://groups.google.com/group/google-summer-of-code-announce/web/how-to-provide-google-with-sample-code
> we do *not* have to upload any code *before* we get a passing evaluation.
Doesn't make any difference to me - I'll upload it and get it done
with rather. :)
> > after the 20th but will only be evaluated based on work done up to
> > 19:00 UCT on the 20th (or at least, that's what I gather from the
> > students mailing list). Does that sound correct?
>
> Correct.
They're trusting us to be honest here. I like it to be trusted. :)
> That's how I plan to handle it. I will still need to make some
> adjustments (no code changes, just adding the README for Google,
> deleting some files that are not part of my work etc.) after Monday
> evening, and I'm gonna do them in a separate branch, where I will
> prepare the tarball for Google. If neccessary, I'll do any further code
> changes (which will not be part of the evaluated code) in my main trunk.
Yeah I need to add blank index.html files in all my directories but I
don't feel that's really important for now; only if my code gets used
afterwards in practice.
> Unless Wilco or anyone else of the program admins tells us not to do so,
> I'd maintain the code in the SoC SVN, even after SoC ends. After all,
> you usually do want to have the history. Starting a new project on
> joomlacode would mean to start without any of the history. Also, anyone
> who is/was watching your code would have to switch over to the new SVN -
> additional work that can be avoided.
Yeah that's true. I have high hopes some of my code will be used in
the Joomla! trunk; if I'm _really_ lucky I'll get commit access but
let's see what happens. Otherwise maybe I can send my changes /
improvements through my mentor Rob Schley or whoever necessary. But
whatever happens I really need subversion access afterwards.