Add utility scripts for problem resource generation and testing

.gitignore

@@ -0,0 +1,25 @@
+* emacs temp files
+*~
+
+* MAC
+*.DS_STORE
+Thumbs.db
+
+*.zip
+*.exe
+a.out
+*.o
+*.orig
+*.bak
+*.bat
+
+# libinteractive
+*.cbp
+*.layout
+*.bat
+libinteractive
+libinteractive.jar
+Makefile
+
+.vscode
+results

.lint.config.json

@@ -0,0 +1,35 @@
+{
+  "lint": {
+    "clang-format": {
+      "allowlist": [".*\\.cpp$"]
+    },
+    "karel": {
+      "allowlist": [".*\\.(kp|kj)$"]
+    },
+    "json": {
+      "allowlist": [".*\\.json$"]
+    },
+    "markdown": {
+      "allowlist": [".*\\\\Palindromos\\\\.*\\.cpp"]
+    },
+    "python": {
+      "allowlist": [".*\\.py$"],
+      "pylint_config": ".pylintrc"
+    },
+    "problematic-terms": {
+      "terms": [
+        {
+          "regexps": ["^[ \\t]*using\\s+namespace\\s+std\\s*;[ \\t]*$"],
+          "message": "El uso de `using namespace std;` es no-deseable.\n\nEl comité de C++ se reserva el derecho de usar cualquier nombre en `std::`, porque hacer `using namespace std;` es una causa común de errores al momento de cambiar de compilador. Por ejemplo, C++17 introdujo `std::count()`[1], así que todos los códigos de C++ que usan `using namespace std;` y declaran algo con el nombre `count` tienen un CE instantáneo.\n\n1: https://en.cppreference.com/w/cpp/algorithm/count"
+        },
+        {
+          "regexps": [
+            "^[ \\t]*#\\s*include\\s*<\\s*bits/stdc\\+\\+\\.h\\s*>[ \\t]*$"
+          ],
+          "message": "El uso de `bits/stdc++.h` es no-deseable.\n\nTodas las cabeceras de `bits/` son específicas al compilador y la arquitectura. Una causa común de errores de compilación locales es el uso de esta librería."
+        }
+      ],
+      "allowlist": [".*\\\\Palindromos\\\\.*\\.cpp"]
+    }
+  }
+}

README.md

@@ -1 +1,22 @@
-# public-courses
+# Public Courses on Omegaup
+This repository contains the course content for the public courses on Omegaup.
+
+## How to Contribute
+You can contribute to the courses by adding new content, fixing typos, or improving existing materials. To do so, please follow these steps:
+1. Fork the repository.
+2. Create a new branch for your changes.
+3. Make your changes and commit them with a clear message.
+4. Push your changes to your forked repository.
+5. Create a pull request to the main repository.
+
+## How to Sync Courses:
+If you think that a course content in this repository has ran out of sync with the omegaup.com you can raise a pull request to sync the content.
+To do this, follow these steps:
+1. Fork the repository.
+2. Create a new branch for your changes.
+3. Edit the `sync-course.json` file to include the course name and the specific content that is out of sync.
+4. Commit your changes with a clear message.
+5. Push your changes to your forked repository.
+6. Create a pull request to the main repository with target branch sync-course.
+7. When your pull request is merged a github action will run to sync the course content with omegaup.com and add commit to your pull request.
+8. Now the admins will merge this pull request to the main branch.

problems.json

@@ -0,0 +1,3 @@
+{
+  "problems": []
+}

utils/Pipfile

@@ -0,0 +1,22 @@
+[[source]]
+
+url = "https://pypi.python.org/simple"
+verify_ssl = true
+name = "pypi"
+
+
+[dev-packages]
+
+mypy = ">=0.782"
+pycodestyle = ">=2.6.0"
+
+
+[packages]
+
+libkarel = ">=1.0.2"
+omegaup = ">=1.3.0"
+
+
+[requires]
+
+python_version = "3.8"