So many nooks and crannies here.

Top display

• Logo
• Phases (previous, current, next)
• Reward
• Organizer

The v1.5 header is pretty nice:

Main area

Should probably have the following tabs/sections:

• Details
  • Should show all of the "pages" the competition creator has made
• Participate
  • Phase selection somehow
  • Submission description + submit button, like old style, also showing the results of your submissions
• Leaderboard
  • Have phase selection at top
  • Display leaderboard + columns
  • Clicking on a column should sort it the opposite way
  • Should have the default column sorted the default way right off the bat
• Discussion
  • Similar forum/discussion as existing version?
• Teams?
  • Teams will be competition specific, I believe?

Ted couldn't get up and running forever, we had to use these defaults:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'NAME': 'postgres',
        'USER': 'postgres',
        'PASSWORD': 'postgres',
        'HOST': 'db',
        'PORT': '5432',
    }
}

Ex error:

Is the server running locally and accepting
    connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?```

Because the homepage height is not relative to the viewport, the jumbotron does not display to the bottom of the page. This can leave a gap depending on the size of the screen viewing the Codalab homepage.

This may be due to some kind of race condition, like the elements don't exist yet?

This is probably the culprit, in init.js:

    // create sidebar and attach to menu open
    $('.ui.sidebar').sidebar('attach events', '.toc.item')

Originally V1.5 idea: codalab/codalab-competitions#2157

v1.5 pushes to Chahub, make v2 push as well.

• Competitions
• Submissions ??? (probably not implemented well enough)

Spec

• Full name
• Job title
• Avatar (gravatar ??)
• Bio
• Location
• Competition list (participation or organization of competition -- display 2)
• Website
• Github
• Linkedin
• Twitter

The ability to make submissions and view their output. Output should be streamed live during processing.

https://github.com/evonove/django-oauth-toolkit

Set this up, auth yourself in from a remote place, and see how it all works.

TY for advice Levi!

• HTML ???
• Javascript ???
• flake8 for python

For example, we could implement a very basic "blog" that only administrators can reach and edit.

Should contain

• A user filter field where the input filters on user name, email, etc.
• A Competition typeahead dropdown where you select which competition to filter on
• A table displaying all relevant submissions, pagination probably required
• Table should show details about the submission(s):
  • file name
  • size
  • submitted at
  • started processing at
  • finished processing at
  • Which compute worker did it?
  • What queue was it on
  • What docker image(s) were used?
• The table should have buttons for actions at the top and checkboxes on the left of each submission; there should also be a way to check ALL submissions (even on every subsequent page)
• Available actions:
  • Re-run
  • Stop/cancel
  • Delete

Sometimes it's annoying to make changes to scoring program or reference data and have to re-zip it between each upload. Instead, allow specifying a directory in the bundle. The specified directory will be zipped and treated like a normal dataset from there!

When I upload a dataset now, I make a dummy Data object to hold all of the information while it's being uploaded. This means if we try to make a file with a unique name, upload fails, and we attempt to re-make the file we get a "Name is in use!" error.

I think we should re-factor this to not make a dummy dataset, but how should we handle it?

Flow

1. POST to get a dataset, must provide name and type. Name must be unique to you. upload_completed_successfully is set to False by default
2. From the above POST you receive a signed URL to upload to
3. Begin the upload
4. Finish upload, POST that upload is finished. upload_completed_successfully is set to True now

This is pretty gross, I feel.

New flow

1. POST to get an upload URL, like /tmp/something
2. Upload to that URL
3. Tell Codalab you are finished, THEN create dataset with name and such

Problem here is what if dataset form has other errors... like missing/unique name and such...

Just thinking aloud, will want to make this work better before too much is built on top of it.

With the current form, I can already tell it is going to be annoying to manage animations. We have a nice "form -> progress bar" for file input, we can just leave that exactly the same. We should allow people to re-upload and retry without having to reload the page, as well.

In the header we currently use the basic javascript animation, but we should make a small addition like bouncing a "signal" between each thing. We can figure out the code where it decides to draw a line between nodes and "amplify" it :)

Potential problems

• How do we get custom docs into DR?
• DRF is not displaying the inline data for nested form creation

Screenshots of current form:

Current problems with form

1. The validation for each page is pretty bad. It does not update in a nice way, often times you have to click "test save" to get validation to fire properly. This needs to be refactored.

Should contain

• A keyword filtering box:
  • Works with emails, username, first name, last name, etc. all relevant fields; use django-filters in DRF for this
• A table of users, sign up date, email, etc. probably limited to the first 50 results
• I don't think pagination will be required

Questions

• What do we need this for? We haven't had to "ban" anyone from Codalab v1.5, what user management should we need really?

Should show the currently overall stats, like:

• Total # of users
• Total # of public competitions
• Total # of submissions

Then a breakdown per year, per month... maybe like a tab for each year:

2015 - 2016 - 2017 - 2018

Then under each tab breakdowns

Work out an API to pull out information programmatically via a web service.

Give elastic search a shot!

https://imgur.com/O56U5qf

Form inputs aren't properly inheriting their width from the container they're inside. Needs some styling done for proper mobile display. Image of the issue added above.

Can basically be like it is in v1.5, maybe a little prettier

Could also make this a nice popout/modal so you don't have to go between pages

This feature should output code for an iframe that a user logged into Chahub can submit to.

Iframe content should be dynamically generated, because we may flip on/off features so the view of the embed may change

• Move $(document).ready stuff to appropriate pages -- shouldn't be in base template
• Don't style .column, use Grids
• Fix auth urls, shouldn't have direct links in urls.py for them
• Fix login page, doesn't seem to be working?
• Signup page doesn't seem to be working?

Probably just use regular old npm scripts?

• shows gauges/such kind of like health/status page right now.
• CPU/memory usage and such
• Links to rabbitmq mgmt, flower like current setup

Some way to generate:

• 10 new users
• 10 new submissions
  • creating users if not provided
  • competition must be provided
  • optionally automatically execute submissions
  • optionally automatically attempt to add to leaderboard
• 10 new competitions
  • must create phase/etc. required fields
  • optionally creating users
  • optionally creating submissions

Use factory boy

If you try to create a competition now, columns have no way of referencing each other!

I suggest we make it so you cannot add column computations until a competition is saved. Also, you shouldn't be able to reference columns until they are individually saved, so when editing a competition that has already been saved, new column additions should be saved automatically.

Todo:

• Make competition form "disable" computation section while competition.id == undefined
• Make columns save as soon as input is saved, IF competition.id != undefined
• Remove any columns without a .id from computation_columns selector
• Make ColumnSerializer throw an error if you try to pass computation_columns during a create//when it doesn't have a parent yet

- OR -

• Don't allow editing Leaderboard at all until competition has been saved, and then Leaderboard interacts with a leaderboard API all on its own..? This could be the same with collaborators tab!

We don't want to reveal the organizers email, so we can use an email relay or some such to forward the message from competition participant to competition organizer.

• Use reconnecting web socket
• Receive random things from the server
• Use toastr to show these random things

We're hoping to use Markdown (or RST or whatever, can make sure we can change it later), so be sure to convert the old HTML in legacy bundles to Markdown. I believe HTML is valid in Markdown, but for nice editors we should probably convert it?

https://pandao.github.io/editor.md/examples/full.html

Quote 11, lfinish by december 1st.