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

Consider amending description of code FRG050 #338

Open
mrshll1001 opened this issue Nov 29, 2022 · 4 comments
Open

Consider amending description of code FRG050 #338

mrshll1001 opened this issue Nov 29, 2022 · 4 comments

Comments

@mrshll1001
Copy link
Contributor

The code FRG050 has a description of:

Grant awarded to an organisation acting as an agent for the funder, to make grant payment on its behalf to the defined recipient(s).

It's possible that this should be amended to:

Grant awarded to an organisation acting as an agent for the funder, to make grant payment(s) on its behalf to the defined recipient(s).

This is because there may be multiple grant payments to the defined recipient.

This would be a PATCH level change

@mariongalley
Copy link
Contributor

Thanks @mrshll1001 - I take it this would need approval by the SC then to go ahead?

@mrshll1001
Copy link
Contributor Author

Reading this through I think it may actually be a PATCH. If so, it may just require approval from a 360G team member + an SC member.

@mariongalley
Copy link
Contributor

@KDuerden What do you think about this suggested change?

@KDuerden
Copy link
Contributor

A PATCH has an approval process that involves posting on the Forum with one week notice for comments from SC or others.

Potentially this could be considered a non-normative change to a normative part of the Standard, in which case we can sign off internally. However given we have a few changes of this type being bundled together, I think once everything is ready, we should do a post to cover everything, giving the necessary notice (eg if there are any MINOR updates bundled in there too, we'll need to give 2 weeks notice)

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

3 participants