Skip to content
This repository was archived by the owner on Feb 16, 2023. It is now read-only.
This repository was archived by the owner on Feb 16, 2023. It is now read-only.

[Other] Paperless Organization Organization #1632

@qcasey

Description

@qcasey

As seems commonly agreed in #1599, a new Github Organization should be build around this project. Can those willing to do the work of migrating to a GitHub organization for paperless-ng chime in here?

Currently created Paperless Organizations

Ordered by stars

  1. paperless-ngx (repo) (people)
  2. paperless-reborn (repo) (people)

EDIT: It appears paperless-ngx is the community's choice. The following tasks will be completed there.

Tasks (unconfirmed)

  • Invite any willing paperless-ng contributors to the organization, as they are most familiar with the codebase.
  • Create the following development teams:
    • Frontend (Angular)
    • Backend (Python)
    • Test (Manually, Docker instances)
    • Issue Triage
    • CI/CD (+Automated Testing, +Packaging Docker/Distros)
    • Translation (+Documentation)
  • Bring on willing new contributors, invite to any/all relevant teams based on experience.
  • Migrate issues (??) (github-issues-import). <-- Decided unideal
  • Merge pending PRs after tests and review by contributors (below).

Confirmed Willing Contributors

IMO, @jonaswinkler @danielquinn and @shamoon should have write access to this org, as they've all made significant contributions to the paperless project. No one should expect any help from them now, but if they want to contribute in the future it should be made easy.

Update March 10

We're creating our first release, paperless-ngx v1.6.0! Over 50 people have contributed to this revival. Thank you to everyone for your interest in preserving Paperless.

The paperless-ngx organization is going to be stricter about official membership. However, this is 100% a community project and we gladly welcome any contributions (member or not). Please have a look at the outstanding issues, PRs requiring testing, or the translations. Any help is greatly appreciated :)

If you'd like to expand on your contributions by approving future PRs and having write access to the repo, we'd love to have you. Please reach out to someone on the team or in matrix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions