Giter Site home page Giter Site logo

help's Introduction

help's People

Contributors

hugovk avatar jazzband-bot avatar jezdez avatar jstockwin avatar tony avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

jstockwin gitter-badger hercules261188 isabella232 sjoerds seanpm2001

help's Issues

404 at https://jazzband.co/docs

The link to guidelines in the list under "Joining" is wrong. I believe it should be /docs/guidelines rather than just /guidelines.

Review transfer of project test-repo

This issue tracks the transfer of the GitHub project test-repo (https://github.com/jazzband/test-repo)Transferred to Jazzband by: @jezdez (https://github.com/jezdez)Please review the TODO list below carefully and adapt it to the project if needed.

The goal of this issue is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or newly created.

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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)

  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)

  • Fix project URL in GitHub project description

  • Review project if other services are used and port them to Jazzband

    GitHub project details

    Description
    just a test
    Homepage
    None
    Stargazers
    0
    Open issues
    0
    Forks
    0
    Default branch
    master
    Is a fork
    False
    Has downloads
    True
    Has Wiki
    True
    Has Pages
    False

django-widget-tweaks

Hey, I want to move https://github.com/kmike/django-widget-tweaks to jazzband org. Are you ok with that? Did I get it right, and the required steps are:

  1. CONTRIBUTING.md file with a link to jazzband and Contributor Code of Conduct?
  2. setup pypi deployments via Travis (is it required?) and grant jazzband access to it;
  3. transfer the repo, update links?

Implement Jazzband guidelines for project pip-tools

This issue tracks the implementation of the Jazzband guidelines for the project pip-tools

It was initiated by @nvie 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description A set of tools to keep your pinned Python dependencies fresh.
Homepage
Stargazers 1972
Open issues 120
Forks 201
Default branch master
Is a fork False
Has Wiki False
Has Pages False

Implement Jazzband guidelines for project TvShowApp

This issue tracks the implementation of the Jazzband guidelines for the project TvShowApp

It was initiated by @dhilipsiva 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description A TvShow app which demonstrates the use of Dagger 2 , MVP and RxJava.
Homepage
Stargazers 0
Open issues 0
Forks 0
Default branch master
Is a fork True
Has Wiki True
Has Pages False

Move django-debug-toolbar to Jazzband

Hi @robhudson, @dcramer, @aaugustin,

Since I wasn't sure what we ended up deciding, if at all, I just wanted to open this issue to track potential steps needed, feel free to join the Jazzband (on https://jazzband.co/) and then edit the following list yourself.

TODOs

  • fix links in docs and readme
  • enable coveralls/codecov/etc
  • enable travis-ci/other CI
  • add jazzband to PyPI entry (and answer if auto release via Travis should be enabled)
  • add jazzband-bot to ReadTheDocs project

proposing django-admin-bootstrapped

Hello, i'd like to propose moving django-admin-bootstrapped [0] to jazzband organization. The app is in good shape but i don't have much motivations to keep it updated (django 1.9 support is missing atm) as i don't have much use for it anymore.
Looking at the guidelines we should be ok with everything, some minor nits like moving the contributing section we have on our README.md to a separated files and jazzband tags and CoC links.

[0] https://github.com/django-admin-bootstrapped/django-admin-bootstrapped

Proposing django-autoslug

Hi roadies,

I've been recently advised to move my semi-abandoned but still somewhat popular pet project django-autoslug to JazzBand. There are a few pull requests which are necessary to merge, but I haven't had enough time for that for quite a while. I think it would be beneficial for the community to at least partially delegate maintenance to the organisation.

Questions:

  1. Is it desirable for the organisation?
  2. What steps do I need to take apart from creating CONTRIBUTING.md as per the Guidelines?
  3. Is it possible to easily transfer all the issues and pending pull requests?

Thanks!

Regards,
Andy

Review transfer of project test-repo

This issue tracks the transfer of the GitHub project test-repo (https://github.com/jazzband/test-repo) that was initiated by: @jezdez

Please review the TODO list below carefully and adapt it to the project if needed.

The goal of this issue is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or newly created.

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

GitHub project details

Description just a test
Homepage None
Stargazers 0
Open issues 0
Forks 0
Default branch master
Is a fork False
Has Wiki True
Has Pages False
## TODOs - [ ] Fix all links in the docs (and README file etc) from old to new repo - [ ] Add the [Jazzband badge](https://jazzband.co/about/guidelines#badges) to the `README` file - [ ] Add the [Jazzband contributing guideline](https://jazzband.co/about/guidelines#contributing-guidelines) to the `CONTRIBUTING.md` file - [ ] Check if continuous testing works (e.g. [Travis-CI](https://travis-ci.org/), [CircleCI](https://circleci.com), [AppVeyor](https://www.appveyor.com), etc) - [ ] Check if test coverage services work (e.g. [Coveralls](https://coveralls.io), [Codecov](https://codecov.io), etc) - [ ] Add `jazzband` account to [PyPI](https://pypi.python.org/) project as maintainer role (URL: `https://pypi.python.org/pypi?:action=role_form&package_name=`) - [ ] Add `jazzband-bot` as maintainer to the [Read the Docs](https://readthedocs.org/) project (URL: `https://readthedocs.org/dashboard//users/`) - [ ] Fix project URL in [GitHub project](https://github.com/jazzband/test-repo) description - [ ] Review project if other services are used and port them to Jazzband

Implement Jazzband guidelines for project pip-tools

This issue tracks the implementation of the Jazzband guidelines for the project pip-tools

It was initiated by @nvie 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description A set of tools to keep your pinned Python dependencies fresh.
Homepage
Stargazers 1972
Open issues 120
Forks 201
Default branch master
Is a fork False
Has Wiki False
Has Pages False

Implement Jazzband guidelines for project localshop

This issue tracks the implementation of the Jazzband guidelines for the project localshop

It was initiated by @mvantellingen 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description local pypi server (custom packages and auto-mirroring of pypi)
Homepage
Stargazers 290
Open issues 38
Forks 101
Default branch develop
Is a fork False
Has Wiki True
Has Pages False

Can't join the group

As your the website ask me, I open an issue:
I logged in with GitHub this afternoon and had an error after give permissions.
This make me the same thing tonight

Take over djmail

The package https://github.com/bameda/djmail seems not actively maintained anymore. I have contributed a few times, leading to the latest release, and use it for several projects. However, sinc a few months the current maintainer does not reply anymore. Aso the documentation was changed with the last PR, but he has not updated the site where it is located after the merge/release. There is an open pull request from December 11th 2016, with no reply whatsoever, also after I pinged him. Would it be possible to transfer this project over to Jazzband?

The project itself is in good shape. It works with python 2/3 and all currently supported Django versions. It has automated testing with Travis CI and good documentation. I have been using it in production for a few years now. It's on PyPi and Django-packages.

Implement Jazzband guidelines for project localshop

This issue tracks the implementation of the Jazzband guidelines for the project localshop

It was initiated by @mvantellingen 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description local pypi server (custom packages and auto-mirroring of pypi)
Homepage
Stargazers 290
Open issues 38
Forks 101
Default branch develop
Is a fork False
Has Wiki True
Has Pages False

Review transfer of project test-repo

This issue tracks the transfer of the GitHub project test-repo (https://github.com/jazzband/test-repo)Transferred to Jazzband by: @jezdez (https://github.com/jezdez)Please review the TODO list below carefully and adapt it to the project if needed.

The goal of this issue is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or newly created.

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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)

  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)

  • Fix project URL in GitHub project description

  • Review project if other services are used and port them to Jazzband

    GitHub project details

    Description
    just a test
    Homepage
    None
    Stargazers
    0
    Open issues
    0
    Forks
    0
    Default branch
    master
    Is a fork
    False
    Has downloads
    True
    Has Wiki
    True
    Has Pages
    False

Implement Jazzband guidelines for project localshop

This issue tracks the implementation of the Jazzband guidelines for the project localshop

It was initiated by @mvantellingen 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description local pypi server (custom packages and auto-mirroring of pypi)
Homepage
Stargazers 290
Open issues 38
Forks 101
Default branch develop
Is a fork False
Has Wiki True
Has Pages False

Implement Jazzband guidelines for project tasty

This issue tracks the implementation of the Jazzband guidelines for the project tasty

It was initiated by @lwm 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description Modern and extensible testing framework for Haskell
Homepage http://documentup.com/feuerbach/tasty
Stargazers 0
Open issues 0
Forks 0
Default branch master
Is a fork True
Has Wiki True
Has Pages False

Implement Jazzband guidelines for project pip-tools

This issue tracks the implementation of the Jazzband guidelines for the project pip-tools

It was initiated by @nvie 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 file
  • Check if continuous testing works (e.g. Travis-CI, CircleCI, AppVeyor, etc)
  • Check if test coverage services work (e.g. Coveralls, Codecov, etc) N/A
  • Add jazzband account to PyPI project as maintainer role (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/) N/A
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description A set of tools to keep your pinned Python dependencies fresh.
Homepage
Stargazers 1972
Open issues 120
Forks 201
Default branch master
Is a fork False
Has Wiki False
Has Pages False

Review transfer of project test-repo

This issue tracks the transfer of the GitHub project test-repo that was initiated by: @jezdez

Please review the TODO list below carefully and adapt it to the project if needed.

The goal of this issue is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or newly created.

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

GitHub project details
Description just a test
Homepage None
Stargazers 0
Open issues 0
Forks 0
Default branch master
Is a fork False
Has Wiki True
Has Pages False

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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Implement Jazzband guidelines for project localshop

This issue tracks the implementation of the Jazzband guidelines for the project localshop

It was initiated by @mvantellingen 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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description local pypi server (custom packages and auto-mirroring of pypi)
Homepage
Stargazers 290
Open issues 38
Forks 101
Default branch develop
Is a fork False
Has Wiki True
Has Pages False

IRC notifier

Dear Roadies,

A long time ago, I enabled a IRC notifier on django-pipeline, and forgot about it. And now I find it really annoying, but can't disable it, could you please be kind and remove it from django-pipeline?

Thanks for tuning my guitars.

Communication

I have a strong feeling that we are missing a huge thing here. Communication is the key to a good community.

The existing irc channel, is it enough? Does it suit well? Since there's a strong opinion of irc being deprecated.

What are my suggestions?

  • Slack team (I have actually already created a team for the jazzband)
  • Integrations for different services
  • Add links and information to website, social accounts, emails, etc

Anything I am missing?

p.s. I think I need to set @jezdez as a slack-admin, send me a note, please.

Pypi credentials

I've just added the deploy part to django-pipeline, it just lacks a password.

Proposing to move localshop to jazzband

Hi all, I'd like to move a project of mine here: https://github.com/mvantellingen/localshop

I know it's still used by a lot of companies today so I hope this will be a good place to continue the development of it. Scanning other tickets it seems I just need to move the repo here if there is an 'OK' and an issue with a list of steps required will then be created by a bot?

contextlib2 as a JazzBand project?

At the moment, I'm a single point of failure for new releases of contextlib2, the backport of the standard library's contextlib module to earlier Python versions. That's normally not a major problem (it's not like it needs to be updated very often), but it does mean it can lag behind the standard library version for quite a while after a new Python release goes out, and problems specific to the backport can take some time to get fixed (even though merging the PR is just a click of a button, actually spinning the release still takes additional work).

I'm currently in the process of migrating the project from BitBucket to GitHub and Travis CI for easier collaboration. Once it's here, would it be a suitable candidate for inclusion?

  • fix links in docs and readme (@jezdez)
  • enable coveralls/codecov/etc (@jezdez)
  • enable travis-ci/other CI (@jezdez)
  • Should auto release via Travis be enabled? (@ncoghlan)?
  • add "jazzband" user to PyPI entry (and answer if auto release via Travis should be enabled) (@ncoghlan)
  • add "jazzband-bot" as maintainer to ReadTheDocs project (@ncoghlan)

Review project test-repo

This issue tracks the review of the GitHub project test-repo that was initiated by @jezdez

See the TODO list below for common tasks to work on. The goal of this review is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or was newly created.

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 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 (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description just a test
Homepage None
Stargazers 0
Open issues 0
Forks 0
Default branch master
Is a fork False
Has Wiki True
Has Pages False

Have teams for each "skill"

I currently get pinged via "jazzband/members" to review Django projects. While I would love to help, I have never used Django at all.

Proposal: Create teams for each "skill". There'd be a team for "Django", one for "Python", one for "Security"... Then everybody can join/subscribe to the teams they feel competent enough for, and people can CC those teams for more targeted calls for help.

Implement Jazzband guidelines for project collectfast

This issue tracks the implementation of the Jazzband guidelines for the project collectfast

It was initiated by @antonagestam 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 file
  • Check if continuous testing works (e.g. Travis-CI, CircleCI, AppVeyor, etc)
  • Add jazzband-bot as maintainer to the Read the Docs project (URL: https://readthedocs.org/dashboard/<PROJECTNAME>/users/)
  • Check if test coverage services work (e.g. Coveralls, Codecov, etc)
  • Add jazzband account to PyPI project as maintainer role (URL: https://pypi.python.org/pypi?:action=role_form&package_name=<PROJECTNAME>)
  • Fix project URL in GitHub project description
  • Review project if other services are used and port them to Jazzband

Project details

Description A Faster Collectstatic
Homepage
Stargazers 188
Open issues 2
Forks 30
Default branch master
Is a fork False
Has Wiki True
Has Pages False

Review transfer of project test-repo

This issue tracks the transfer of the GitHub project test-repo (https://github.com/jazzband/test-repo) that was initiated by: @jezdez

Please review the TODO list below carefully and adapt it to the project if needed.

The goal of this issue is to make sure the project adheres to the Jazzband guidelines after it has been transferred to the Jazzband GitHub organization or newly created.

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

GitHub project details

Description
just a test
Homepage
None
Stargazers
0
Open issues
0
Forks
0
Default branch
master
Is a fork
False
Has Wiki
True
Has Pages
False
## TODOs - [ ] Fix all links in the docs (and README file etc) from old to new repo - [ ] Add the [Jazzband badge](https://jazzband.co/about/guidelines#badges) to the `README` file - [ ] Add the [Jazzband contributing guideline](https://jazzband.co/about/guidelines#contributing-guidelines) to the `CONTRIBUTING.md` file - [ ] Check if continuous testing works (e.g. [Travis-CI](https://travis-ci.org/), [CircleCI](https://circleci.com), [AppVeyor](https://www.appveyor.com), etc) - [ ] Check if test coverage services work (e.g. [Coveralls](https://coveralls.io), [Codecov](https://codecov.io), etc) - [ ] Add `jazzband` account to [PyPI](https://pypi.python.org/) project as maintainer role (URL: `https://pypi.python.org/pypi?:action=role_form&package_name=`) - [ ] Add `jazzband-bot` as maintainer to the [Read the Docs](https://readthedocs.org/) project (URL: `https://readthedocs.org/dashboard//users/`) - [ ] Fix project URL in [GitHub project](https://github.com/jazzband/test-repo) description - [ ] Review project if other services are used and port them to Jazzband

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.