Skip to content

Remove FAQ section on github branch :) #93

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

Merged
merged 3 commits into from
Jan 4, 2017

Conversation

Mariatta
Copy link
Member

@Mariatta Mariatta commented Jan 3, 2017

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

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

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
Copy link
Member

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.

Copy link
Member Author

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.

Drop the mention of python-ideas
Forbid the reopening of issues closed by core dev

:)

Closes python#27
Copy link
Collaborator

@willingc willingc left a 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!

`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.
Copy link
Collaborator

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.

@Mariatta
Copy link
Member Author

Mariatta commented Jan 4, 2017

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

Copy link
Collaborator

@willingc willingc left a comment

Choose a reason for hiding this comment

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

Thanks @Mariatta 👍

@brettcannon brettcannon merged commit c5b0a49 into python:github Jan 4, 2017
@brettcannon
Copy link
Member

thanks!

AA-Turner pushed a commit to AA-Turner/devguide that referenced this pull request Jun 17, 2022
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants