Split patchwork into multiple apps

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue does not name any files, entry points, or existing tests. Start by mapping the project structure and current unit tests for bundling, todo lists, tagging, email subscriptions, and the XML-RPC API; done means these features are separated into distinct apps with their own unit tests.

Written by the indexing model from the issue text.

Description

refactoring

Overview

Patchwork contains a sizable amount of code. Many of its features are orthogonal and could be broken up into different apps. I can see at least the following features:

  • Bundling
  • Todo Lists
  • Tagging
  • Subscriptions via email
  • XML-RPC API

These apps don't have to be reusable, but they should be separate enough to have their own unit tests. They could inherit from a "core" project if necessary.

Alternatives

Leave things as they in a monolithic application.

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.