From cd5d5cf674e839f9ca0aacdab6c29c26bf103c94 Mon Sep 17 00:00:00 2001 From: Bluenix Date: Sat, 23 Jul 2022 00:34:25 +0200 Subject: Relax rule about usage of non-WebSocket communication --- pydis_site/templates/events/pages/code-jams/9/rules.html | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html index 7bc31ef2..285a332c 100644 --- a/pydis_site/templates/events/pages/code-jams/9/rules.html +++ b/pydis_site/templates/events/pages/code-jams/9/rules.html @@ -11,19 +11,17 @@ {% block event_content %}
    -

  1. Your solution must use one of the approved frameworks (a list will be released soon). It is not permitted to circumvent this rule by e.g. using the approved framework as a wrapper for another framework.

    2. +

  2. Your solution must use one of the approved frameworks. It is not permitted to circumvent this rule by e.g. using the approved framework as a wrapper for another framework.

  3. -

    Your solution must only communicate through WebSockets. Any communication between the client and server (or any two server workers), must utilize WebSockets.

    -

    - An exception to this rule is that communication with databases and files is allowed for accessing resources or for storage purposes. - For example, you may use PostgreSQL as a database but not its NOTIFY command. - Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also allowed. + The core of your project must use WebSockets as its communication protocol.. + This means that you are allowed to use other methods of communication where WebSockets cannot be implemented, however, that should be a non-significant portion of your project. + For example, serving static files for a website cannot be done over WebSockets and it does not pose as a significant portion of a project.

    -

    Another exception is made for serving static files, which normally uses HTTP. You are allowed to serve a JavaScript-implemented client for your WebSocket server.

    +

    This rule does not apply to databases and files when used for storage purposes even though that may be a significant portion of your project. Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also exempted of this rule.

    -

    If you're interested in utilizing a particular non-WebSocket method of communication, reach out to the Events Team for discussion and approval

    +

    Reach out to the Events Team for advice if you're about your use of non-WebSocket communication.

  4. Your solution should be platform agnostic. For example, if you use filepaths in your submission, use pathlib to create platform agnostic Path objects instead of hardcoding the paths.

  5. -- cgit v1.2.3 From a796945dacd0f6c37b8f336d86d48946ed5530a3 Mon Sep 17 00:00:00 2001 From: Bluenix Date: Sat, 23 Jul 2022 02:37:04 +0200 Subject: Fix past-tense "exempt" typo Co-authored-by: wookie184 --- pydis_site/templates/events/pages/code-jams/9/rules.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html index 285a332c..61af2248 100644 --- a/pydis_site/templates/events/pages/code-jams/9/rules.html +++ b/pydis_site/templates/events/pages/code-jams/9/rules.html @@ -19,7 +19,7 @@ For example, serving static files for a website cannot be done over WebSockets and it does not pose as a significant portion of a project.

    -

    This rule does not apply to databases and files when used for storage purposes even though that may be a significant portion of your project. Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also exempted of this rule.

    +

    This rule does not apply to databases and files when used for storage purposes even though that may be a significant portion of your project. Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also exempt from this rule.

    Reach out to the Events Team for advice if you're about your use of non-WebSocket communication.

    6. -- cgit v1.2.3 From bf753d137db8bbd405841c70f908d6fec2632127 Mon Sep 17 00:00:00 2001 From: Bluenix Date: Sat, 23 Jul 2022 02:40:09 +0200 Subject: Rework sentence urging reaching out to the events team Co-authored-by: wookie184 --- pydis_site/templates/events/pages/code-jams/9/rules.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html index 61af2248..f17431e9 100644 --- a/pydis_site/templates/events/pages/code-jams/9/rules.html +++ b/pydis_site/templates/events/pages/code-jams/9/rules.html @@ -21,7 +21,7 @@

    This rule does not apply to databases and files when used for storage purposes even though that may be a significant portion of your project. Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also exempt from this rule.

    -

    Reach out to the Events Team for advice if you're about your use of non-WebSocket communication.

    +

    If you're unsure about your use of non-WebSocket communication, please reach out to the events team.

  6. Your solution should be platform agnostic. For example, if you use filepaths in your submission, use pathlib to create platform agnostic Path objects instead of hardcoding the paths.

  7. -- cgit v1.2.3 From 0a462106c0834a1142da24ba5854b8e7af0b1b34 Mon Sep 17 00:00:00 2001 From: Bluenix Date: Sat, 23 Jul 2022 02:41:20 +0200 Subject: Be explicit about example in rule being an allowed use-case --- pydis_site/templates/events/pages/code-jams/9/rules.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html index f17431e9..9a28852f 100644 --- a/pydis_site/templates/events/pages/code-jams/9/rules.html +++ b/pydis_site/templates/events/pages/code-jams/9/rules.html @@ -16,7 +16,7 @@

    The core of your project must use WebSockets as its communication protocol.. This means that you are allowed to use other methods of communication where WebSockets cannot be implemented, however, that should be a non-significant portion of your project. - For example, serving static files for a website cannot be done over WebSockets and it does not pose as a significant portion of a project. + For example, serving static files for a website cannot be done over WebSockets and it does not pose as a significant portion of a project, therefore it is allowed.

    This rule does not apply to databases and files when used for storage purposes even though that may be a significant portion of your project. Working with subprocesses (through stdin/stdout or multiprocessing.Pool()/concurrent.futures.ProcessPoolExecutor()) is also exempt from this rule.

    -- cgit v1.2.3