Skip to content

README Roadmap and Intended PR Schedule#10

Open
etontackett wants to merge 40 commits into
mainfrom
docs/readme-roadmap
Open

README Roadmap and Intended PR Schedule#10
etontackett wants to merge 40 commits into
mainfrom
docs/readme-roadmap

Conversation

@etontackett

Copy link
Copy Markdown
Collaborator

Add project roadmap and anticipated pull request schedule to README

Description

This PR updates the README with a project roadmap which includes:
-Intended source code structure and organization
-Planned development sequence
-An expected PR schedule for future work

Motivation and Context

The goal of this PR is to make the project structure and development plan clear for contributors and reviewers.

Types of changes

  • CI
  • Docs
  • Feature
  • Fix
  • Performance
  • Refactor
  • Style
  • Test
  • Other (use sparingly):

Checklists:

Code and Comments
If this PR includes modifications to the code base, please select all that apply.

  • My code follows the code style of this project.
  • I have updated all package dependencies (if any).
  • I have included all relevant files to realize the functionality of the PR.
  • I have exported relevant functionality (if any).

API Documentation

  • For every exported function (if any), I have included a detailed docstring.
  • I have checked the spelling and grammar of all docstring updates through an external tool.
  • I have checked that the docstring's function signature is correctly formatted and has all arguments.
  • I have checked that the docstring's list of arguments, fields, or return values match the function.
  • I have compiled the docs locally and read through all docstring updates to check for errors.

Manual Documentation

  • I have checked the spelling and grammar of all manual updates through an external tool.
  • Any code included in the docstring is tested using doc tests to ensure consistency.
  • I have compiled the docs locally and read through all manual updates to check for errors.

Testing

  • I have added unit tests to cover my changes. (For Macros, be sure to check
    @code_lowered and
    @code_typed)
  • All new and existing tests passed.
  • I have achieved sufficient code coverage.

@vp314 vp314 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Please think through what the file structure should look like. In the PR section, each PR should be its own subsection and there should be a table indicating what functionality/files are being implemented, their purpose, etc.

Comment thread README.md Outdated
Comment on lines +17 to +44
src/
RidgeRegression.jl

algorithms/
bidiagonalization.jl
closed_form.jl
gradient_descent.jl
stochastic_gradient_descent.jl

datasets.jl
design.jl

test/
runtests.jl

dataset_tests.jl
design_tests.jl
bidiagonalization_tests.jl
closed_form_tests.jl
gradient_descent_tests.jl
stochastic_gradient_descent_tests.jl

docs/
src/
index.md
design.md
api.md
```

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Use vertical bars and dashes to ensure spacing is correct

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