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

Add reference to issue #46. #80

Closed
wants to merge 2 commits into from
Closed

Conversation

msporny
Copy link
Member

@msporny msporny commented Mar 16, 2016

Add reference to issue #46.

@adrianba
Copy link
Contributor

This issue should be flagged in the method-identifiers.html document like issues #10 and #11.

@adrianba
Copy link
Contributor

See 3c52892

@adrianba adrianba closed this Mar 17, 2016
@msporny
Copy link
Member Author

msporny commented Mar 17, 2016

-1 for closing this issue. I raised this PR to help the reader understand that we're still discussing payment method identifiers while they're reading the Payment Request API spec. They wouldn't understand that payment method identifiers are under active discussion unless they went and read the Payment Method spec and I don't think we can hope that folks that read the specs read all of them to understand the lay of the land. We can't get the WG to read all the specs as it is.

@ianbjacobs
Copy link
Collaborator

I agree that we need readers to understand that there are active discussions on a variety of topics. But I think we should make life simpler for readers by conveying that a small number of times, and not overloading them with redundant issue flags.

So for example, in the Payment Request API spec section "3. Dependencies" we would add a statement like: "Note: Each of the specifications published by this Working Group includes issue flags where the group is seeking input."

I also expect to write a blog post framing all the publications and letting people know that there are issues and questions for feedback in each of the specs. (I'll discuss that at today's call.)

Ian

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

Successfully merging this pull request may close these issues.

3 participants