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

Update project name, copyright #55

Merged
merged 8 commits into from Feb 24, 2022
Merged

Update project name, copyright #55

merged 8 commits into from Feb 24, 2022

Conversation

qcasey
Copy link
Member

@qcasey qcasey commented Feb 15, 2022

Closes #54

Should these be merged into dev?

@gador
Copy link
Contributor

gador commented Feb 15, 2022

The docs are build with master branch set, so the changes wont be reflected until we merge dev into master.

I'd suggest merging them into dev right now and collect any other changes we want to include in the docs and merge them later all together into master. What do you think?

@qcasey qcasey changed the base branch from master to dev February 15, 2022 21:28
@qcasey
Copy link
Member Author

qcasey commented Feb 15, 2022

Yep fine by me

@dblitt
Copy link
Contributor

dblitt commented Feb 15, 2022

Should we change "2021" to "2015-2022"? Obviously 2022 is the current year, and it looks like Daniel Quinn's contributions go back to December 2015 as per the git history.

@qcasey
Copy link
Member Author

qcasey commented Feb 15, 2022

Yup definitely, I missed that

@coveralls
Copy link

coveralls commented Feb 15, 2022

Pull Request Test Coverage Report for Build 1883041401

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.038%

Totals Coverage Status
Change from base Build 1882562900: 0.0%
Covered Lines: 3942
Relevant Lines: 4283

💛 - Coveralls

@dblitt
Copy link
Contributor

dblitt commented Feb 15, 2022

I just changed a bunch of references to paperless-ng to paperless-ngx in README.md. Things I noticed that still need to be changed:

  • Crowdin button is to the old project
  • Same for docker hub
  • I had issues pointing the coveralls button to the master branch, so its still the old project
  • We seem to be holding on to the paperless-ng section before introducing paperless-ngx, so the links to the docs there still point to paperless-ng
  • Crowdin issue (212 on paperless-ng)

@qcasey
Copy link
Member Author

qcasey commented Feb 16, 2022

Thanks! I added that issue of crowdin to #1. Perhaps we should do the README and coveralls/docker button update in a new PR once those are ready.

I think we're starting with ghcr anyway (https://github.com/paperless-ngx/paperless-ngx/tree/feature-docker-build-fix)

@qcasey qcasey added this to the Successful Merge + Migration milestone Feb 17, 2022
Copy link
Contributor

@jovandeginste jovandeginste left a comment

Choose a reason for hiding this comment

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

My remarks

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@yschroeder yschroeder added the documentation Improvements or additions to documentation label Feb 18, 2022
@qcasey
Copy link
Member Author

qcasey commented Feb 22, 2022

Not really related to this PR, but I think the README.md should be restructured. The first wall of text focuses a lot on the difference between paperless-ng and the original paperless project.

Instead we could move the paperless-ngx explainer up higher, and move the Paperless compat stuff to a ## Original Paperless Compatibility/Migration section?

@shamoon
Copy link
Member

shamoon commented Feb 22, 2022

Not really related to this PR, but I think the README.md should be restructured. The first wall of text focuses a lot on the difference between paperless-ng and the original paperless project.

Instead we could move the paperless-ngx explainer up higher, and move the Paperless compat stuff to a ## Original Paperless Compatibility/Migration section?

Very much agree, it should be edited way down to give people a quick headline about the project, more screenshots, etc. Would you want that as part of this PR?

@qcasey
Copy link
Member Author

qcasey commented Feb 22, 2022

Cool, I can draft that.

Would you want that as part of this PR?

No, this PR's scope has already creeped a bit, I'd rather start fresh :)

@bauerj bauerj merged commit e23859f into dev Feb 24, 2022
@bauerj bauerj deleted the readthedocs-patch-1 branch February 24, 2022 14:00
@github-actions
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Other] Allow access to webhooks for readthedocs
8 participants