Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Current Version
    • Fix Version/s: Near Future
    • Component/s: OIOIOI
    • Labels:
      None
    • Sprint:
      The Second Sprint

      Description

      The current contestlogo module is quite limited:

      1. We can provide a URL to a logo image, but if we run over HTTPS and we don't have the logo on an external HTTPS-protected website, we get unacceptable warnings.

      2. Some contest types could automatically have logos determined by them. I think the controller should be able to provide a default logo, in which case we should consider two scenarios
        a) admins should be able to change or hide the logo (and menu graphics; see below)
        b) admins should have no control over the logo if the contest controller provided one

      3. The contestlogo module should also become responsible for the graphical elements in the contestant's menu. It's ridiculous that now we force to use the OI graphics with no way of changing it.

        Activity

        Connect your code to JIRA

        Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.

        Git & Mercurial in the cloud

        Collaborate across unlimited private code repositories.

        Git behind the firewall

        Manage and collaborate on Git repositories behind a firewall.

        Browse and search code

        Browse, search, and track source code repositories.

          People

          • Assignee:
            Szymon Acedański
            Reporter:
            Szymon Acedański
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile