Separate Python and NPM source

Open
#80 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the repository layout and the linked Debian bug report to understand how the Python and npm sources are currently combined. Done means the sources are separated into two projects so Debian no longer receives two source packages.

Written by the indexing model from the issue text.

Description

Hi,

There's a request for package [0] for this package. It would be great if you can consider separate the source code in two projects, one for the Python package and another for npm package. This will avoid have two source package in Debian.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083020

Thanks!

Dominant language
JavaScript
Stars
33
Forks
26
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 web-push-libs/encrypted-content-encoding

All issues in web-push-libs/encrypted-content-encoding

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.