| File TODO changed (mode: 100644) (index 84be9e7..d608cd4) |
| 1 |
1 |
== Where I stopped last time == |
== Where I stopped last time == |
| 2 |
|
[ ] test docker |
|
| 3 |
|
[ ] Is the length of the password is check for forget_link page? |
|
| 4 |
|
[ ] clean_cookies must be used everywhere! |
|
| 5 |
2 |
[ ] |
[ ] |
| 6 |
3 |
|
|
| 7 |
4 |
== BEFORE NEXT RELEASE == |
== BEFORE NEXT RELEASE == |
|
5 |
|
[ ] Add a minimum password length and enforce it everywhere. |
|
6 |
|
[ ] Never redirect if the Host:'s port is different from SERVER_PORT. |
|
7 |
|
(see docker with redirects) |
|
8 |
|
[ ] Add also "normal" we page (without virtualhost) |
|
9 |
|
to be able to start with the current server? |
|
10 |
|
[ ] For repo stats, we may want to use --all or --branches. |
|
11 |
|
[ ] When showing a commit, Create links for "Parents"/"Tree". Probably others. |
|
12 |
|
https://rocketgit.com/user/coria/coria-backend/source/log/commit/34fd00db0525b875e2f9afbe5a10af28fe06b03b |
|
13 |
|
[ ] For 'diff' add an option to ignore white space. |
|
14 |
|
[ ] Update session in background after I send the page to the user. |
|
15 |
|
Also other queries for sure we can delay them. |
|
16 |
|
[ ] I get some AVCs about gpg - maybe when git tries to verify a gpg signature? |
|
17 |
|
Add a functional test for this! |
|
18 |
|
allow httpd_t user_home_dir_t:file { getattr open }; |
|
19 |
|
Maybe I can find an interface for httpd_t - gpg. |
|
20 |
|
[ ] When creating the admin account, redirect to settings? |
|
21 |
|
[ ] Add AGPL logo to main web page? |
|
22 |
|
[ ] Add 'depends/number' label to mark some bugs as a dependency on another. |
|
23 |
|
What about duplicates? Confidential? |
|
24 |
|
[ ] We do no track of the visitors. Also in git announce? |
| 8 |
25 |
[ ] Use 'restrict' when generating authorized_keys file. |
[ ] Use 'restrict' when generating authorized_keys file. |
| 9 |
26 |
[ ] In report, report also the space used and a top 5? |
[ ] In report, report also the space used and a top 5? |
| 10 |
27 |
[ ] At login time to destroy all forgot password pending tokens? |
[ ] At login time to destroy all forgot password pending tokens? |
| 11 |
|
[ ] promise to not sell user data. |
|
|
28 |
|
[ ] promise to not sell user data (tos/main page). |
| 12 |
29 |
[ ] admin settings: disable reports by e-mail. |
[ ] admin settings: disable reports by e-mail. |
| 13 |
30 |
[ ] web: How can you help: sponsor us! |
[ ] web: How can you help: sponsor us! |
| 14 |
31 |
[ ] ldap: add groups support |
[ ] ldap: add groups support |
| |
| ... |
... |
to add a worker? Also, no hint is presented. |
| 437 |
454 |
virtual machines etc.). We must save this info to be able recover! |
virtual machines etc.). We must save this info to be able recover! |
| 438 |
455 |
[ ] build: do load testing (Cosmin R) |
[ ] build: do load testing (Cosmin R) |
| 439 |
456 |
[ ] We may want to cut the network access for user 'build' inside the worker. |
[ ] We may want to cut the network access for user 'build' inside the worker. |
| 440 |
|
[ ] If user is using firewalld: |
|
| 441 |
|
firewall-cmd --permanent --add-port=19999/tcp |
|
| 442 |
|
firewall-cmd --reload |
|
| 443 |
457 |
[ ] Register with freecode.club |
[ ] Register with freecode.club |
| 444 |
458 |
[ ] build: allow user to install some dependencies (done). |
[ ] build: allow user to install some dependencies (done). |
| 445 |
459 |
Or maybe try to detect from the spec file? |
Or maybe try to detect from the spec file? |
| |
| ... |
... |
to add a worker? Also, no hint is presented. |
| 483 |
497 |
This means that the 'rights' tabs should be moved in settings?! |
This means that the 'rights' tabs should be moved in settings?! |
| 484 |
498 |
Probably no. But we will need also rights in Settings to control |
Probably no. But we will need also rights in Settings to control |
| 485 |
499 |
!repo stuff. |
!repo stuff. |
| 486 |
|
[ ] Unit testing for API keys |
|
|
500 |
|
[ ] More unit testing for API keys. |
| 487 |
501 |
[ ] Probably, also ssh keys must have some actions allowed attached to them. |
[ ] Probably, also ssh keys must have some actions allowed attached to them. |
| 488 |
502 |
How it will work?! By default, all rights. |
How it will work?! By default, all rights. |
| 489 |
503 |
Use case: allow a key only to push on some repos (regex) |
Use case: allow a key only to push on some repos (regex) |