Add option to remove author from the admin

[yakky]

Some deployment does not need any author field, keeping it can be confusing for the users

[mikek]

Can be possibly added through NewsBlogConfigForm

[mikek]

@yakky, @tom I've completely forgot to consider doing this through NewsBlogConfigForm in #77 Can we use the simple setting approach now and look into the per instance configuration in some next iteration?

[yakky]

Sure, it makes perfectly sense

[intellectronica]

Sure, makes sense.

[yakky]

@mikek This issue is meant to completely remove the "author" field in the admin, actually
Similar to #65

[mikek]

Sorry, I just have noticed this is another issue. Reopening.

[mkoistinen]

What's the consensus on this? Can I suggest we make this setting a boolean on the NewsBlogConfig rather than creating new settings entries. This would also allow a Blog instance of this app to use an author field, whilst allowing a News instance to ignore it in the same project.

[stefanfoulis]

+1 on making this a setting of NewsBlogConfig. This kind of thing is one of the main reasons it exists. News entries might not need authors. Blog entries usually do. In any case, author should not be a mandatory field.
And it should be auto-populated with the following priorities:

1. the current user already has a Person associated: use it
2. the current user has a first_name and last_name: auto create a Person and associate it.
3. set author to None.

Templates should handle missing authors gracefully.

If NewsBlogConfig says there should be no authors:

• hide the author field in admin

@intellectronica @FinalAngel @yakky what do you think?

[intellectronica]

Yes to all except for auto-creating a Person. IMO that's overreaching.

[yakky]

@stefanfoulis +1

[FinalAngel]

@stefanfoulis +1