Adarnof's Little Things

[Adarnof]

Edit: Finger slipped and hit enter before I added anything. Goddammit.

I'm looking to clean up the codebase and improve the functionality of auth without adding new features. Below is the list of things I want to tackle. If you have a suggestion please comment with it. If I accept it, I'll add to the list. I'm not looking for new features - I'm looking to tweak how auth runs.

Edit: Some of these little things are big. Oops. I'll keep track of them separately

Big Things Needed For Little Things:

• Update django version to 1.10
• Remove member and blue_member permissions #342 Remove member/blue permissions
• implement user states
• implement Django's messaging framework for site feedback

Little Things:

• remove pathfinder support
• Fleet Doctrine  #531 remove fleet fits page
• remove wormhole tracker
• Storing plain text passwords in "Available Services" #177 do not store service passwords
• request supervisor instructions #521 Daemonize celery processes #266 supervisor instructions + configs for celery tasks and authenticator
• Feature request: Synchronize all user groups #448 buttons on admin site to sync service groups
• show number of notifications
• fix all button css
• Checks when adding APIs #350 rewrite and centralize API checks
• bulk mark read / delete for notifications
• replace hard-coded urls with reverse by name
• python 3 compatibility

[CokkocZateki]

Since I noticed you want to remove some pages how about removing FAT?

[Adarnof]

I haven't decided what to do about FAT. With the Django 1.10 upgrade my SSO package is compatible, so I'm considering a replacement powered by CREST.

[RichterSR]

When you change member/blue permissions, can you divide blue member in +5 (light blue) and +10 (dark blue), because we would like to share fewer informations with a +5 friend then with a +10. Thank you. 😉

[CokkocZateki]

If crest is an option then that will be awesome.

On 09 Sep 2016 17:02, "RichterSR" notifications@github.com wrote:

When you change member/blue permissions, can you divide blue member in +5
(light blue) and +10 (dark blue), because we would like to share fewer
informations with a +5 friend then with a +10. Thank you. 😉

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#535 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/APVF4dk3dZB2G352xxCteo05DmjxRgKMks5qoXUXgaJpZM4J4b3A
.

[Adarnof]

If anything more than just member/blue, it makes more sense to create a dynamic, user-definable state system which is the basis of a per-app (or even per-model!!) ACL system. While I like the idea, oh god that's not a little thing at all. I'd prefer to focus my ACL efforts on [https://github.com/adarnof/adarnauth-acl](my ACL app in development) and perhaps graft it on at a later date.

The problem with introducing even a half-fix of splitting +5s and +10s is that the site operator would need an easy way of defining where each access restriction takes place. This requires much more work to make user-accessible.

[RichterSR]

I am still learning django but will take a look on it 😎

[Adarnof]

Guys you're letting my productivity slip. Give me another project.

[ghost]

what about #121 ? :p We will not let your productivity going out like that ! :D

[CokkocZateki]

@Adarnof what about a FAT update since the igb is bye bye?