Show incomplete proposals

[blazeu]

Will show incomplete proposals by default and can be changed by ticking a checkbox.

[blazeu]

@mhils Storing the production files (app.bundle.js) on the repo makes the diff messy, I'd recommend removing this file from the repo.

[mhils]

Hi,

Thanks for the efforts, but I still feel this is misguided. Can you clarify how and why you want to use this tool before the submission deadline?

[mhils]

@mhils Storing the production files (app.bundle.js) on the repo makes the diff messy, I'd recommend removing this file from the repo.

I think it's quite useful to be able to run this without installing a huge number of dependencies, so I feel the bundle isn't too bad - this project is small enough that I don't mind polluting the git history. If you use yarn to install dependencies, you'll get the same package versions and the diff will be minimal.

[blazeu]

Thanks for the efforts, but I still feel this is misguided. Can you clarify how and why you want to use this tool before the submission deadline?

I think @jayvdb has written a good reason about it in #6

If you use yarn to install dependencies, you'll get the same package versions and the diff will be minimal.

I'm already using yarn, will try rebuilding again from the last commit. (still huge diff ..)

[mhils]

I think @jayvdb has written a good reason about it in #6

Maybe I'm missing something, but I still don't understand why/how you would use this before the submission deadline. I'd like to first understand the use case better.

At Honeynet, we use this to collect multiple concise reviews for each proposal from mentors, maybe similar to academic paper review if that makes sense. Early feedback on proposals etc. is handled by mentors 1-on-1 with students directly - no need to put that into a system IMO. Mentors only summarize that with a short statement in the system on how well they communicated.