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

The process does not include any disposition for updating the Patent Policy #305

Closed
frivoal opened this issue Jul 27, 2019 · 3 comments · Fixed by #309
Closed

The process does not include any disposition for updating the Patent Policy #305

frivoal opened this issue Jul 27, 2019 · 3 comments · Fixed by #309
Assignees
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Milestone

Comments

@frivoal
Copy link
Collaborator

frivoal commented Jul 27, 2019

The process does not include any disposition for updating the Patent Policy. Effectively, I suppose this means it can (and can only) be done by the director's fiat, but that's probably not ideal. An alternative understanding would be that since the Patent Policy is normatively referenced by the Process, and since the AB is in charge of the Process, then it is in charge of the Patent Policy as well.

I'd suggest explicitly stating that the Patent Policy can be updated in the same way as the Process can: prepared by the AB, then proposed to an AC Review (which implies a director's approval as well, as long as there is a Director). We might also want to say that PSIG ought to be involved, but then again, PSIG's existence is not mandated by the Process, so I'm not sure. Even if we don't mention them explicitly, so long as PSIG exists in its current form, I'd expect the AB to consult with them, and for the Team / AC / Director to push back if they haven't.

I don't expect updating the Patent Policy will be a frequent occurrence, but that doesn't mean we shouldn't know how to update it when we want/need to.

@frivoal frivoal self-assigned this Jul 27, 2019
@chaals
Copy link
Contributor

chaals commented Jul 27, 2019

Given the Patent Policy is part of the Process, I think it's OK to leave the whole thing as "you update the Patent Policy as if it were part of the Process" .

We have made one update in 15 years, that was developed through PSIG as a proposal, and effectively it was proposed to the AC in an AC review, and then adopted.

@michaelchampion
Copy link

I fear we are spending too much time picking nits that aren't causing tangible problems out of the Process Document. Let's focus on fixing problems that arise from the execution of the process as it is understood, not on fixing the language of the document itself unless it is creating actual misunderstandings.

@frivoal
Copy link
Collaborator Author

frivoal commented Aug 2, 2019

I feel that the Patent Policy hasn't been updated in years in part because we want it to be stable (which is a good thing), but also because it doesn't have a clear owner, and so most of the time nobody thinks it's their job to even consider what fixes might be desirable. I'd prefer to establish clear ownership, and it seems to me that this can either be the Director, or the AB. I'd rather go with the later.

frivoal added a commit to frivoal/w3process that referenced this issue Aug 8, 2019
@frivoal frivoal added this to the Process 2020 milestone Aug 14, 2019
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) labels Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants