Remove prefix and fullname fields.

I agree with proposal on this issue more than on person.
I never knew what to put in fullname and prefix for Storm Org. fullname of organization? fullname of main contact?

Does anyone use these fields for different purposes?

I agree. I've been helping a customer implement a Storm installation and they keep asking about this.
I would have thought that Prefix would be more useful under Person (i.e. Mr, Mrs, Miss or whatever, controlled through attributes).

A patch for testing.

Does not remove data from db.

I'm undecided over whether to do this with this change immediately or give users a grace period where the data is hidden but present before putting in an update function to remove it.

+1 to drop the fields.

On the grace period question, the question is how do you warn people? Do you make Full Name an option that can e turned off and on in the Organization settings?

Warn people via release notes. The reason that we have done grace periods for things like this in the past (generally ~3months or a couple of releases later) is because some people won't read the release notes (unadvised anyway!)

It isn't a setting, this is meant to be a simplification by removing something that is unnecessary in 99% of cases.

Needs retesting against 2.x.

#3: storm--685140-3.patch queued for re-testing.

Committed to 2.x. Will not be backported to 1.x.

Created #1046930: Clean up prefix and fullname data to handle the data cleanup followup.