search

engasmaa / google-summer-of-code

Automatically exported from code.google.com/p/google-summer-of-code
0 stars 0 forks source link

Potential conflicts not shown #90

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
=== What steps will reproduce the problem? ===

1.  Have a student with different applications to two organizations.
2.  Have the two organizations assign mentors to both applications.
3.  Have one organization rank their application above the line and the
other rank theirs below the line.

Look at my organization's students for an example of this.  We have no
marker, even though another organization has a mentor assigned.

=== What is the expected output? What do you see instead? ===

Both organizations should see conflict warnings in the student application
page.  Instead, the organization that has the student below the line sees a
warning, but the other organization does not.

=== What version of the product are you using? On what operating system? ===

2007 web app via Firefox on OS X.

=== Please provide any additional information below. ===

The documentation says that a conflict will be shown on the student's page
if another organization has assigned a mentor.  That's, ah, incomplete; the
actual test is that the other organization has assigned a mentor AND the
application is above their line, that is, that it's an "actual" conflict.

At a minimum that conjunction should be an OR, that is, the web app should
show _potential_ conflicts as well as actual conflicts.  That's an easy bug
fix, but this really should be considered an enhancement request: the web
app should show more detail about conflicts.

First, the app should show conflicts within the organization.  That is, if
a student submits more than one application, it's possible that more than
one application could make the cut (perhaps because they were rated by
independent sets of evaluators).  Even if it's within an organization, it's
a conflict, and it should be highlighted (maybe not in red; perhaps a
bright orange?).

Moreover, the app should distinguish between actual conflicts (which must
be resolved or a slot will be lost) and potential conflicts (which should
be cleared up, but aren't as urgent).  The three cases that the web app
should show are these:

 - "selected by another organization": a mentor has been assigned and the
application is above the line.

 - "above the line at another organization": the application is above the
line but a mentor has not been assigned.

 - "mentor assigned by another organization": a mentor has been assigned
but the application is below the line.

I wouldn't object if the latter two were grouped as "potential" but I'd
prefer to see them separated out.  It's easy (and much more common) for the
second one to turn into an actual conflict by assigning a mentor than it is
for the third one to turn into a conflict by climbing in the rankings.

Original issue reported on code.google.com by Greg.Noe...@gmail.com on 11 Apr 2007 at 7:48

GoogleCodeExporter commented 9 years ago 
This is scary indeed.  We will take another look at our conflict detection code 
for
the next iteration of the web app.

Original comment by LHospo@gmail.com on 16 Apr 2007 at 8:48

GoogleCodeExporter commented 9 years ago 
Note that this issue is a superset of issue#96.  Does Google's issue tracker 
have the
ability to mark an issue as a duplicate?

Original comment by Greg.Noe...@gmail.com on 21 Apr 2007 at 9:23

GoogleCodeExporter commented 9 years ago 
Note that this issue is a superset of issue#100.  Does Google's issue tracker 
have
the ability to mark an issue as a duplicate?

Original comment by Greg.Noe...@gmail.com on 21 Apr 2007 at 9:53

GoogleCodeExporter commented 9 years ago 
The main thing about conflicts that would be helpful from my org admin 
perspective
would be for the application list page to show conflicts.  Right now, it is 
necessary
to check each app individually, which is time-consuming and error-prone.

Original comment by kberr...@gmail.com on 22 Apr 2007 at 5:33

GoogleCodeExporter commented 9 years ago 
http://groups.google.com/group/google-summer-of-code-discuss/browse_thread/threa
d/
592dcfd3eb9fb0fb?hl=en

This is indeed a very disturbing and UNFAIR issue. 

This is not a bug - its a cheat. Nothing less

Original comment by yankees2...@gmail.com on 18 Apr 2008 at 12:03