aalto-letech / aplus-courses Goto Github PK

do we add copyrights to our code (classes etc.) and how about using 3-party code (like google stylesheet case (GPL))?

investigate a bit, ask to ask lawyers if feasible (I'd do that anyway)

maybe https://pages.github.com/ will do?

and don't forget the ScalaDoc 😉

should contain info such as year and a list of downloadable modules (URLs)

• design the course conf file format (inspiration from EDUTools)
• versioning the format
• take the required plugins into account

make a first manual (required) upload to JB plugin repo

as to begin with, some simpler layout/placeholder can be created as a PoC. at the initial stage, they may follow the approach taken in TMC plugin @nikke234

• ensure there's testing (dummy) data
• automated integration testing
• selection of the integration testing library

update the manual testing environment (this probably needs some changes somewhere)

• add .svg logo
• add icons for buttons etc.
• add also screenshots to the JB's repo

• add naming

Find suitable linter and configure it.
If possible, add GitHub plugin that enforces lint rules (e.g. prevent PR merge if case of lint errors)

get .iml s

• unit tests
• automated tests

we don't test the UI, we try to meet 80% code coverage requirement

a student can ask plugin to convert the current project into an "A+ O1" course (or into another A+ course)

• license compatibility checker (fossa)
• dependencies vulnerabilities scanner (snyk)
• add "nikke234"
• code quality checker (codacy)

this should reflect in plugins settings and consequently in JB plugin repo descriptions

when installing any (for the first time) module, you get all the required deps

• push from travis build
• integrate w slack

for installation of scala plugin:

• follow: https://www.jetbrains.org/intellij/sdk/docs/basics/plugin_structure/plugin_dependencies.html#gradle
• check this (optional): https://github.com/JetBrains/gradle-intellij-plugin#configuration

• [configuration of proper naming, contacts, logo, etc.](configuration of proper naming, contacts, logo, etc.)
• uploading to plugins repository
• designing the layouts (menu/right-side menu)
• logging in?
• making hints on missing plugins (org.intellij.scala and possibly others) figure out if you can install other 3-party plugins as well? - check only once we are aware that the course is O1
• ensure no-restart mode
• plugin is easily removable and leaves no unwanted artifacts (proper cleanup)

this is about an .epf file (Eclipse style) for personal configs + comments:
https://letech.slack.com/archives/CQ92SAHNY/p1579085949033700?thread_ts=1579014556.027300&cid=CQ92SAHNY

protocol to open stuff in the IDEA

it would be a nice to have thing ansible playbooks for #67

• removing the personalized preferences (persistant settings)

1: reproduce the bug

• drop codacy
• unused private field rule to get disabled (check), as important if using the GUI creator

• required plugins

programmatically or via .imls of those latter modules

take into account the possibility of some files/modules/course materials to get updated

• check what Aalto's K8S has to offer
• decide and configure testing environments

auth against local A+ user DB or HAKA

in terms of images on Linux (Ubuntu), Windows and MacOS latest (can we find the images, what are the costs etc.)

something like the TMC has: https://github.com/superseacat/tmc-intellij/blob/22f8399de81aca7e86d1e9fff88bf0012f3efd42/tmc-plugin-intellij/src/main/java/fi/helsinki/cs/tmc/intellij/actions/StartupEvent.java#L57-L60

still pointing to the 2020 zips: https://grader.cs.hut.fi/static/O1_2020/projects/o1_course_config.json

current plan:
docker image w nginx and injected data (module zips + course configs)

(org.intellij.scala and possibly others) figure out if you can install other 3-party plugins as well? - check only once we are aware that the course is O1

plugins repo and plugins repo beta

scala plugin deps = ooptional

• The plugin runs the REPL in whichever module is currently open for editing or otherwise selected within IntelliJ.

persisted over restart?

well, it seems, that atm the plugin is installing in a no-restart mode, but to keep that feature, we must follow: http://www.jetbrains.org/intellij/sdk/docs/basics/plugin_structure/dynamic_plugins.html

https://grader.cs.hut.fi/static/O1_2020/projects/o1_course_config.json

this comes from (don't forget to update if changed): https://version.aalto.fi/gitlab/jsorva/o1matsku/blob/s2020/projects/o1_course_config.json

arrange the physical machines, if feasible. alternatively, we could have a mixed environment, with linux (and possible windows) containerized and Mac as a physical machine (ask Otto for that)

In the module panel, for easier handling of statuses we have:

• toggle as in the attached screenshot (like e.g. when running tests in IDEA)
• icons represent the module statuses (based on @oseppala 's made icons)

one step is to delete as "not show" and another one is "reset"

there is a delay between "push to JB" and "can download from JB", so let's store the latest build of the artifact somewhere else (details):

https://letech.slack.com/archives/CSDV9CA31/p1580802391039100?thread_ts=1580802082.038600&cid=CSDV9CA31