Mirror of space-wizards/SS14.Jetfish
Find a file
2025-10-10 14:55:33 +02:00
.github/workflows Add unit testing 2025-04-16 19:31:33 +02:00
.idea/.idea.SS14.Jetfish/.idea finalize most stuff™️ 2025-07-22 16:21:05 +02:00
SS14.Jetfish Implement editor help panel 2025-10-10 14:55:33 +02:00
SS14.Jetfish.Tests Implement event bus unit tests 2025-09-05 20:20:18 +02:00
.dockerignore Add project files 2025-04-08 16:31:11 +02:00
.editorconfig Add .editorconfig 2025-05-04 09:13:58 +02:00
.gitignore Merge branch 'refs/heads/master' into markdown 2025-07-22 16:34:46 +02:00
compose.yaml Add project files 2025-04-08 16:31:11 +02:00
Licence.txt Added first files outlining the project. 2025-04-05 01:13:58 +02:00
README.md Update readme 2025-04-22 09:39:37 +02:00
SS14.Jetfish.sln Add unit testing 2025-04-16 19:31:33 +02:00
SS14.Jetfish.sln.DotSettings Add jetfish as word in dictionary 2025-04-19 23:57:43 +02:00

SS14.Jetfish

SS14.Jetfish is our solution to enterprise confusion. It is a Project Management tool.

This is a work in progress.

What does it do? (Project Outline)

  • SSO support with options for required claims / roles.
  • Teams
  • Kanban boards (global and under a team)
    • Comments
      • Proper system for replies so you can follow a conversation along
    • Labels for items
    • Assigned Users
    • Rich Display (See trello cards)?
      • Emojis
    • GitHub integration to automatically move items to "done"
  • File hosting for images etc.
    • Caching / Etags
    • File administration
    • Compression!!!!
    • Animated WebP Support (should work ootb)
  • Administration
    • IDP claim role mapping for global policies
    • Fine grained access control using Global and resource-based access policies and roles
    • Team and user management allowing admin teams, project focused teams etc.
  • Minimal use of PII
    • Development starts with the assumption that emails won't be required, though no promise is made to keep it that way

What does it NOT do?

  • Time tables (Think of "For when is something supposed to be done")
  • Bug/Ticketing features
    • Use github issues for that

What we need to do better than others?

  • Do not leak users PII to other users
  • Made in a real programing language (C#)
  • Not look like absolute ass

Things to consider after v1.0