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

Update wording of what a secretary cannot be an editor of #1261

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

navarr
Copy link
Contributor

@navarr navarr commented Jan 5, 2022

To support PSRs and PERs

@navarr navarr requested a review from a team as a code owner January 5, 2022 20:48
Copy link
Member

@Jean85 Jean85 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As said by @Crell, even if this is minial, it should require a bylaw vote.

Let's try to see if there are other cases like this to compound under a single vote.

@ashnazg
Copy link
Contributor

ashnazg commented Jul 24, 2022

As said by @Crell, even if this is minial, it should require a bylaw vote.

Let's try to see if there are other cases like this to compound under a single vote.

If nothing else has been spotted, should we go ahead with a vote on this?

@@ -44,7 +44,7 @@ Whilst there are a number of defined functions below but they should also perfor

All FIG Secretaries are expected to remain impartial and professional when acting in an official capacity as Secretary and should also remain aware that even when not acting in an official capacity, their actions reflect back on the PHP FIG and the FIG must not be brought into disrepute.

In order to ensure impartiality, Secretaries may not concurrently serve as a Project Representative, Core Committee Member, or Editor of a PSR. They may, however, be a member of a Working Group. Secretaries must also publicly declare all conflicts of interest for example if they are participating in a working group or are a core team member of a Member Project.
In order to ensure impartiality, Secretaries may not concurrently serve as a Project Representative, Core Committee Member, or Editor of any working group. They may, however, be a member of a Working Group. Secretaries must also publicly declare all conflicts of interest for example if they are participating in a working group or are a core team member of a Member Project.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In order to ensure impartiality, Secretaries may not concurrently serve as a Project Representative, Core Committee Member, or Editor of any working group. They may, however, be a member of a Working Group. Secretaries must also publicly declare all conflicts of interest for example if they are participating in a working group or are a core team member of a Member Project.
In order to ensure impartiality, Secretaries may not concurrently serve as a Project Representative, Core Committee Member, or Editor of any working group. They may, however, be a member of a Working Group. Secretaries must also publicly declare all conflicts of interest, for example, if they are participating in a working group or are a core team member of a Member Project.

Minor grammatical point as long as we're here.

@ashnazg
Copy link
Contributor

ashnazg commented Mar 5, 2024

Would this be a good first voting experience for the new folks? :D

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

Successfully merging this pull request may close these issues.

5 participants