Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
scheduling-system
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SMASCH
scheduling-system
Commits
0ac755df
Commit
0ac755df
authored
8 years ago
by
Piotr Gawron
Browse files
Options
Downloads
Patches
Plain Diff
old todo list removed
parent
d11ffb8f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
todos.txt
+0
-25
0 additions, 25 deletions
todos.txt
with
0 additions
and
25 deletions
todos.txt
deleted
100644 → 0
+
0
−
25
View file @
d11ffb8f
* TODO List
** Notice
Moved all the important stuff to gitlab issues
** Important
- label for's => give them correct html id's (all html forms).
Currently it works, but it's not valid HTML, as the ID (for labels) are all the same.
It requires a hack, because django forms are not-so-flexible
- implement `on leave` button
- what about possible sunday in availabilities?
- in beta remember to disable Guest Access
- in beta remember to forbid not-logged users to browse the API
** Visual
- None
** Possible improvements
- breadcrumbs - make them stack. Currently, they are made "half-manually".
While it is not a great problem, it is not a flexible solution
- make some names sound/look more pythonic. Unfortunately, due to
programmistic experience of our team, instead of sticking to python convencies
(lower case methods, fields; using underscore to break words instead of
camelCase), using full names and not abbrieviations, the code sometimes
resembles a mess.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment