Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename buyer #156

Closed
jpmckinney opened this issue Nov 4, 2014 · 4 comments
Closed

Rename buyer #156

jpmckinney opened this issue Nov 4, 2014 · 4 comments
Milestone

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Nov 4, 2014

The terms seems to create confusion, since a "procuring entity" is the one doing the buying, the one appearing on contracts, so it's also the buyer. CoST uses "Project owner" instead of buyer to relieve this confusion.

Feedback:

"buyer" probably is not the correct name for this field ("endUser"/"Customer" as suggestions)

@jpmckinney
Copy link
Member Author

contractingEntity?

@birdsarah birdsarah added this to the After 1.0 milestone Nov 4, 2014
@birdsarah birdsarah added the Field label Nov 4, 2014
@jpmckinney
Copy link
Member Author

Need to hear if anyone is a strong supporter of "buyer" before switching.

@AlCollier
Copy link

Additional disadvantage of 'buyer' is it often (usually?) means the employee doing the buying

@timgdavies
Copy link
Contributor

The issues here can be taken forward in #368 which provides more flexibility in the labelling of the parties to a contract should 'buyer' not capture the key relationships to be monitored.

It does not, however, currently propose at this stage changing the definition of buyer, as we have not seen major issues in practice with use of the buyer field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants