Summer Projects

[murrown]

This is a short checklist of major tasks that we'd like to implement over the summer.

• DNS records' container #653 Add containers to DNS objects and make sure permissions work correctly
• Domain name conflicts can clobber foreign key relationships #688 Update, don't delete objects when resolving domain name conflicts
• Upgrade to a newer version of Django? #644 Upgrade to a version of Django that was released in the past year (shouldn't be too difficult)
• Object audit log #690 Get object changelogs working
• Add attributes to containers #693 Create a custom attributes form for users
• More/better user preferences in general

[zeeman]

I might be interested in working on #690. What kinds of user preferences are we talking about?

[murrown]

The basic examples are setting the default container in a more intuitive way, and allowing users to create a list of attributes to ask for every time the user creates a new object. These things seem to necessitate a new view devoted to user preferences, so we might as well open it up to suggestions.

Though, I'm beginning to think that the attributes list should be a setting in the ctnr scope, and not the user scope.

@akeym what do you think, and are there any other preferences we should consider? Was there something about how it's tedious to remove objects from containers, as well?

[akeym]

I think attributes list can be a container-level setting, that only container admins (or above) can manipulate.

The other user prefs I was thinking of were 'theme', and how many results to show per-page (obviously capped at some amount, or pre-defined values offered).

As for tedious to remove objects from containers.. not sure what you're referring to?