Implement Jazzband guidelines for webpack-bundle-tracker

[jazzband-bot]

This issue tracks the implementation of the Jazzband guidelines for the project webpack-bundle-tracker

It was initiated by @owais who was automatically assigned in addition to the Jazzband roadies.

See the TODO list below for the generally required tasks, but feel free to update it in case the project requires it.

Feel free to ping a Jazzband roadie if you have any question.

TODOs

• Fix all links in the docs (and README file etc) from old to new repo
• Add the Jazzband badge to the README file
• Add the Jazzband contributing guideline to the CONTRIBUTING.md or CONTRIBUTING.rst file
• Check if continuous testing works (e.g. Travis CI, CircleCI, AppVeyor, etc)
• Check if test coverage services work (e.g. Coveralls, Codecov, etc)
• Add jazzband account to PyPI project as maintainer role (e.g. URL: https://pypi.org/manage/project/webpack-bundle-tracker/collaboration/)
• Add jazzband-bot as maintainer to the Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/webpack-bundle-tracker/users/)
• Add incoming GitHub webhook integration to Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/webpack-bundle-tracker/integrations/)
• Fix project URL in GitHub project description
• Review project if other services are used and port them to Jazzband
• Decide who is project lead for the project (if at all)
• Set up CI for Jazzband project releases if needed and open ticket if yes

Project details

Description	Spits out some stats about webpack compilation process to a file
Homepage	None
Stargazers	224
Open issues	21
Forks	96
Default branch	master
Is a fork	False
Has Wiki	True
Has Pages	False

[owais]

This is not a Python project but it's the main dependency of https://github.com/jazzband/django-webpack-loader. This project enable JS integration for django-webpack-loader.

[jezdez]

Hey, so this won't work, Jazzband is only supporting Python based projects at the moment due to maintenance constraints. I know how to do Python project maintenance well, but don't for JS based projects.

I can transfer the repo back to you or delete it, please respond in the next 48 hours.

[owais]

I see. Can you please transfer it back to me?

This is a bit concerning as it really is a single project divided into two repos. It's critical that same set of people maintain both. What if I moved the JS "project" into django-webpack-loader? A lot of Django projects/apps ship with JS code so it wouldn't be anything new. Would that be an acceptable solution? Jazzband members interested in helping out can help with the JS side of things but mainly it'd be a Python project (as it actually is). The JS code is mostly just "glue code" that hooks Python side with Webpack.

If you think that's not viable, please transfer this repo back to me.

[jezdez]

I'm really skeptical that this could work since it would increase the maintenance burden for the CI pipeline quite a lot. E.g. Jazzband provides an own staging Python package index to allow releases that are done by none-project leads, so that releasing does not become a bottleneck and project leads can simply do a review when other Jazzband members have prepared the new release.

Yet, with an additional NPM package like webpack-bundle-tracker we couldn't use that pattern since Jazzband simply doesn't support NPM uploads by design to have a small scope and not deal with the much faster-paced JS world.

While individual Jazzband members may have the abilities to maintain the project, I need to keep an eye on whether this package can be maintained long-term and that includes the operational aspects. I wish I could do more, but I'm afraid the features are limited by design due this being a volunteer based project. I hope you understand.

Do you want me to transfer both project back to you?

[owais]

Thanks. That's understandable. Yes, please transfer both back to me.

[jezdez]

@owais Apologies for the delay, I've sent you a transfer request for both repos.