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 basic documentation #26

Merged
merged 24 commits into from
Aug 17, 2017
Merged

Add basic documentation #26

merged 24 commits into from
Aug 17, 2017

Conversation

jambonrose
Copy link
Contributor

This commit:

  • adds a code of conduct
  • adds contributing document
  • adds service badges to the Read Me
  • adds the basic structure for Sphinx documentation
  • creates templates for issues and pull-requests

@codecov
Copy link

codecov bot commented Aug 17, 2017

Codecov Report

Merging #26 into development will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           development    #26   +/-   ##
==========================================
  Coverage          100%   100%           
==========================================
  Files                7      7           
  Lines              171    171           
  Branches            11     11           
==========================================
  Hits               171    171

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b9294de...20a882a. Read the comment docs.

Copy link

@Jimillback01 Jimillback01 left a comment

Choose a reason for hiding this comment

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

OK

Copy link

@Jimillback01 Jimillback01 left a comment

Choose a reason for hiding this comment

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

Very minuscule point but maybe the last sentence which ends with the URL should have a period at the end to close the sentence out.

Copy link

@Jimillback01 Jimillback01 left a comment

Choose a reason for hiding this comment

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

This may not be a problem, but when I open up the page using "View", the Issue template starts with "Specification" and all the sentences before that are not shown. Further, only the title headings are shown, not any of the sentences defining those headings.
(These do look like HTML comments, so that might be OK).

Copy link

@Jimillback01 Jimillback01 left a comment

Choose a reason for hiding this comment

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

Possible issues:

  1. "We will look at the issues and pull-requests as soon as possible." - the dash between pull and requests maybe isn't needed.
  2. "or notes that it is claimed in in the comments..." - maybe should be "..are in the comments,,,"
  3. "on the issue to avoid duplication work" - maybe should be "to avoid duplicate work"
  4. "Use your best judgement to assess the situation" - the spelling should be "judgment".
  5. "your contribution would be welcome." - should end with the past tense "welcomed"
  6. "Read to contribute?" - I think it should start with "Ready..."

Copy link

@Jimillback01 Jimillback01 left a comment

Choose a reason for hiding this comment

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

OK

[http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/

Choose a reason for hiding this comment

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

Very minuscule point but maybe the last sentence which ends with the URL should have a period at the end to close the sentence out.

* Fill out what you can
* Delete what you do not fill out
-->

Choose a reason for hiding this comment

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

This may not be a problem, but when I open up the page using "View", the Issue template starts with "Specification" and all the sentences before that are not shown. Further, only the title headings are shown, not any of the sentences defining those headings.
(These do look like HTML comments, so that might be OK).

Copy link
Contributor Author

@jambonrose jambonrose Aug 17, 2017

Choose a reason for hiding this comment

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

This is my first time setting up Github templates - my understanding is that the comment will be shown to the developer writing the issue, but that (in the event they don't delete the comment) the comment won't be shown. If my understanding is correct, then the comment is desirable. If not, then we should be changing this. Unfortunately, we won't really know until we merge this. ¯\_(ツ)_/¯

CONTRIBUTING.rst Outdated
request.

Please remember that this is a volunteer-driven project. We will look at
the issues and pull-requests as soon as possible.

Choose a reason for hiding this comment

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

Is the dash proper? Or should it be 2 words here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

2 words. Thanks!

CONTRIBUTING.rst Outdated

Look through the `Github issue tracker`_ for bugs. Anything tagged with "bug"
and "help wanted" is open to whoever wants to implement it. If someone
has been assigned, or notes that it is claimed in in the comments,

Choose a reason for hiding this comment

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

maybe remove the double "in".

CONTRIBUTING.rst Outdated
and "help wanted" is open to whoever wants to implement it. If someone
has been assigned, or notes that it is claimed in in the comments,
please reach out to them to work together on the issue to avoid
duplication work. Note that, as volunteers, people sometime are unable

Choose a reason for hiding this comment

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

Maybe make this "duplicate".

CONTRIBUTING.rst Outdated
duplication work. Note that, as volunteers, people sometime are unable
to complete work they start, and that it is reasonable after a certain
amount of time to assume they are no longer working on the issue. Use
your best judgement to assess the situation.

Choose a reason for hiding this comment

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

Misspell - should be "judgment".

CONTRIBUTING.rst Outdated
The documentation aims to provide reference material, how-to guides, and
a general tutorial for getting started with Django and
django-improved-user. If you believe the documentation can be expanded
or added to, your contribution would be welcome.

Choose a reason for hiding this comment

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

Maybe use the past tense "welcomed" to match above verbs "expanded" and "added".

CONTRIBUTING.rst Outdated
Your First Contribution
----------------------------

Read to contribute? Let's get django-improved-user working on your local

Choose a reason for hiding this comment

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

First word is probably "Ready".

:alt: Updates

.. end-badges

Read Me

Choose a reason for hiding this comment

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

Below, there are 2 links that use the wrong format. This wasn't part of the change, so I can't tie this comment directly to the lines where they occur. Sorry.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No worries! Thank you for pointing this out. I believe that 6b3ab4d fixes this. In the future, feel free to open an issue.

# Django Improved User documentation build configuration file, created by
# sphinx-quickstart on Thu Aug 17 10:44:16 2017.
#
# This file is execfile()d with the current directory set to its

Choose a reason for hiding this comment

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

Just a question - is the execfile()d proper?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

A great question. I don't really know! Given that it's generated by Sphinx, I'm going to leave it. ¯\_(ツ)_/¯

docs/conf.py Outdated

# List of patterns, relative to source directory, that match files and
# directories to ignore when looking for source files.
# This patterns also effect to html_static_path and html_extra_path
Copy link

@Jimillback01 Jimillback01 Aug 17, 2017

Choose a reason for hiding this comment

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

Should be "These patterns". I'd suggest changing "effect" because it is vague to me. Does it mean the patterns are added to these two specific paths? Or overwrite both paths? Or delete from both paths?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've changed this to read:

# This list of exclusions will affect the files found in the paths
# specified in html_static_path and html_extra_path

I believe that is right, but I am not 100% sure.

docs/conf.py Outdated
# -- Options for HTML output ----------------------------------------------

# The theme to use for HTML and HTML Help pages. See the documentation for
# a list of builtin themes.

Choose a reason for hiding this comment

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

Should be "built-in" I think.

docs/conf.py Outdated
# html_theme_options = {}

# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,

Choose a reason for hiding this comment

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

Again, I think it should be "built-in"

docs/conf.py Outdated

# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,
# so a file named "default.css" will overwrite the builtin "default.css".

Choose a reason for hiding this comment

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

Again for "built-in".

@jambonrose jambonrose merged commit ec3f6fd into development Aug 17, 2017
@jambonrose jambonrose deleted the initial_documentation branch August 17, 2017 22:39
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.

None yet

2 participants