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

Section 1 (Introduction) should help navigate the document #423

Closed
dwsinger opened this issue Jul 14, 2020 · 2 comments · Fixed by #520
Closed

Section 1 (Introduction) should help navigate the document #423

dwsinger opened this issue Jul 14, 2020 · 2 comments · Fixed by #520
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Type: Editorial improvements
Milestone

Comments

@dwsinger
Copy link
Contributor

Section 1 currently describes a hypothetical model of how specs get developed. It would be more helpful if it guided readers in how the document is structured, and so on.

@frivoal frivoal modified the milestone: Process 2021 Jul 15, 2020
@fantasai fantasai linked a pull request May 10, 2021 that will close this issue
@fantasai fantasai removed a link to a pull request May 10, 2021
@fantasai
Copy link
Collaborator

I believe #520 should close this issue.

@css-meeting-bot
Copy link
Member

The Revising W3C Process CG just discussed Pull Requests, and agreed to the following:

  • RESOLVED: Accept PR 519 and close 338
  • RESOLVED: Accept PR 505 and close issue 338
The full IRC log of that discussion <fantasai> Topic: Pull Requests
<fantasai> florian: Let's not look at "reorganize the document" first
<fantasai> florian: Should maybe look at 519 or ...
<wseltzer> LGTM
<wseltzer> https://github.com//pull/519
<fantasai> Subtopic: Issue 338 Where Decisions Can Be Made
<fantasai> github: https://github.com//issues/338
<fantasai> florian: I think most of this has already been addressed through Tooling section and Minutes section etc.
<fantasai> florian: But there was a leftover sentence saying that decisions can be made in person or in email, period.
<jeff_> q+
<fantasai> florian: So this PR just generalizes from email so we can do that in e.g. GH
<fantasai> dsinger: sgtm, any comments?
<dsinger> ack jef
<fantasai> jeff_: Sounds very clean and elegant
<fantasai> RESOLVED: Accept PR 519 and close 338
<fantasai> Subtopic: Rewrite the Introduction
<fantasai> s/Rewrite the Introduction/Alternate AC Rep/
<fantasai> github: https://github.com//issues/505
<wseltzer> +1
<fantasai> florian: wseltzer wrote a PR, people seem to be happy
<fantasai> dsinger: [reads the new sentence]
<plh> +1
<fantasai> dsinger: I think it's great.
<cwilso> +1
<fantasai> dsinger: wseltzer gave us the details of how that's expected to work in the issue
<fantasai> RESOLVED: Accept PR 505 and close issue 338
<jeff_> q+
<dsinger> ack jef
<fantasai> jeff_: wseltzer, you had asked questions that are in 505
<fantasai> jeff_: dsinger and I commented, anything further you need for the questions?
<fantasai> wseltzer: Thanks, I think we're good with the proposed implementation
<fantasai> wseltzer: those details don't go into the Process
<fantasai> wseltzer: So I think we can close the issue, and if people want a distinct issue for the implementation, I'll put it in the Guide and discuss over there
<fantasai> florian: Also mostly seems fine, so not sure there's an open issue
<fantasai> dsinger: Leave it in the hands of the Team to redirect discussion as needed
<fantasai> Subtopic: Rewrite the Intro
<fantasai> github: https://github.com//issues/423
<fantasai> florian: dsinger proposed a rewrite of the intro on the ML awhile ago
<fantasai> florian: This PR does that
<fantasai> florian: This is a smaller part of the general reorg of the document, but isolate part of it
<jeff_> q+
<fantasai> florian: This is a medium-size editorial change
<fantasai> florian: fantasai and I made some tweaks, but it's largely what dsinger wrote
<jeff_> q-
<fantasai> dsinger: My thought was to give an introduction of "what does this document do" and "how do you navigate it", a type of roadmap
<jeff_> q+
<fantasai> florian: I think the three of us think it's good, question is if anyone else has concerns
<fantasai> dsinger: ...
<fantasai> florian: The reorg changes the order of sections, but not really the content of the sections
<dsinger> ack jef
<fantasai> florian: so reorg doesn't affect intro
<fantasai> jeff_: I started to read, and in the first sentence I see the word "fairness"
<fantasai> jeff_: which at a human level I understand it
<fantasai> jeff_: but saw some discussion about US Congress proposals where it was causing some consternation...
<fantasai> dsinger: Interesting point, but that phrase is surviving from existing intro
<fantasai> jeff_: OK, I guess it's good by definition :)
<fantasai> florian: At least, we are not making things worse :)
<dsinger> q?
<fantasai> dsinger: Would welcome PRs to modernize further, but the goal here was to reorganize
<fantasai> [review of what's changed vs not changed in the intro]
<fantasai> florian: If we leave this meeting with only this PR and the reorg pending, we're in good shape
<fantasai> dsinger: Jeff, do you want me to leave this open one more cycle?
<fantasai> jeff_: ...
<fantasai> dsinger: OK, I'm ok to leave this open for more review
<fantasai> dsinger: Does open the question of further improvements to intro also
<wseltzer> rrsagent, pointer?
<RRSAgent> See https://www.w3.org/2021/05/12-w3process-irc#T14-28-13

@frivoal frivoal linked a pull request May 17, 2021 that will close this issue
@frivoal frivoal added the Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion label May 19, 2021
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 Type: Editorial improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants