For what it's worth I've also made it clear that making these changes at this point is totally unreasonable. This is creating work for our admins - like they need more work.
I'm not sure how much impact this will have. Certainly if there is no way to know who voted what our system will break completely. At present this is the case but devs have promised to fix this. If there are a number of issues like this I strongly suggest considering using a spreadsheet for the evaluation (assuming the new interface enables us to export the data). The reason I say this is that this system has been evolved and fine tuned over the last 6 years. It has been very hard developing a system that everyone feels is fair, trying to come up with a new one now will require new documentation and discussion. Ross Sent from my mobile device. On 30 Mar 2011, at 18:32, "Ulrich Stärk" <u...@apache.org> wrote: > Thanks Luciano. > > As this year's co-admin I took this issue to the gsoc-mentors list and we > are in the process of clarifying some things now. I'll shortly start a > discussion here on how we can adjust our process to the new system. > > Uli > > Am Mi, 30.03.2011, 19:16 schrieb Luciano Resende: >> Org Admins and Mentors, >> >> Please have a look at how Melange was changed around scoring >> student proposals, as that would have an impact on how we score Apache >> proposals. In the past, we were able to use the minus scores to zero >> out invalid scores, but it seems that this is not available anymore, >> and the workaround might be bumping out all other proposals which >> might be a little more complex or more work. Anyway, this is more like >> a heads up if you haven't seen this thread yet. >> >> [1] >> http://groups.google.com/group/google-summer-of-code-mentors-list/browse_thread/thread/1f5ce1d17195ea39?hl=en >> >> -- >> Luciano Resende >> http://people.apache.org/~lresende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ >> > >
