GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Remove FAQ section on github branch :) by Mariatta · Pull Request #93 · python/devguide

Conversation

@Mariatta

@Mariatta Mariatta commented Jan 3, 2017

Copy link
Copy Markdown
Member

Move the following items from FAQ:

  • disagreement with issue resolution -> tracker.rst
  • regenerating configure -> setup.rst
  • porting python to a new platform -> porting.rst (new file)

In index.rst:

  • change any reference to FAQ into Help.
  • remove faq from TOC
  • add porting to TOC

Closes #27

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Mariatta
Remove FAQ section on github branch :)
2d0bbc5
Move the following items from FAQ:
- disagreement with issue resolution -> tracker.rst
- regenerating configure -> setup.rst
- porting python to a new platform -> porting.rst (new file)

In index.rst:
- change any reference to FAQ into Help.
- remove faq from TOC
- add porting to TOC

Closes python#27
@the-knights-who-say-ni the-knights-who-say-ni added the CLA signed label Jan 3, 2017
brettcannon
brettcannon requested changes Jan 3, 2017
View reviewed changes
Comment thread tracker.rst Outdated

If you still feel the resolution is incorrect, then raise the question on
`python-dev`_. If the consensus there supports the disputed resolution, please
take any further objections to `python-ideas`_ (or some other forum). Further

@brettcannon brettcannon Jan 3, 2017

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

If python-dev has already said that the resolution was right, then sending them to python-ideas to continue to vent isn't productive. Also mention that people should not re-open an issue once a core developer has closed it.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Mariatta reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

@Mariatta Mariatta Jan 4, 2017

Copy link
Copy Markdown
Member Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

Thanks @brettcannon :) I updated this section.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Mariatta
Improve tracker docs about conflict resolution
1516b54
Drop the mention of python-ideas
Forbid the reopening of issues closed by core dev

:)

Closes python#27
willingc
willingc approved these changes Jan 4, 2017
View reviewed changes

@willingc willingc left a comment

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

@Mariatta LGTM. One small suggestion but certainly fine as is also. Thanks!

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread tracker.rst Outdated
`python-dev`_. Further argument on `python-dev`_ after a consensus has been
reached amongst the core developers is unlikely to win any converts.

You should not reopen issues that have been closed by a core developer.

@willingc willingc Jan 4, 2017

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

@Mariatta This is fine as is. A slight refinement might be more direct and welcoming: Issues closed by a core developer have already been carefully considered. Please do not reopen a closed issue.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Mariatta
Improve message about not reopening closed issue :)
694498a
Closes python#27
@Mariatta

Mariatta commented Jan 4, 2017

Copy link
Copy Markdown
Member Author

Thanks @willingc I updated it based on your suggestion :)

willingc reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

willingc
willingc approved these changes Jan 4, 2017
View reviewed changes

@willingc willingc left a comment

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

Thanks @Mariatta 👍

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
brettcannon
brettcannon approved these changes Jan 4, 2017
View reviewed changes
@brettcannon
brettcannon merged commit c5b0a49 into python:github Jan 4, 2017
@brettcannon

brettcannon commented Jan 4, 2017

Copy link
Copy Markdown
Member

thanks!

willingc reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

AA-Turner pushed a commit to AA-Turner/devguide that referenced this pull request Jun 17, 2022
@Mariatta @brettcannon
Remove FAQ (python#93)
35923b5
Move the following items from FAQ:
- disagreement with issue resolution -> tracker.rst
- regenerating configure -> setup.rst
- porting python to a new platform -> porting.rst (new file)

In index.rst:
- change any reference to FAQ into Help.
- remove faq from TOC
- add porting to TOC

Closes python#27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@brettcannon brettcannon brettcannon approved these changes
@willingc willingc willingc approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@Mariatta @brettcannon @willingc @the-knights-who-say-ni
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.