archive
/
nuTensor
mirror of https://github.com/geekprojects/nuTensor.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
xofe-minor-fixes-3
0.8.0.0
0.8.0.0-alpha.10
0.8.0.0-alpha.11
0.8.0.0-alpha.14
0.8.0.0-alpha.15
0.8.0.0-alpha.16
0.8.0.0-alpha.17
0.8.0.0-alpha.18
0.8.0.0-alpha.19
0.8.0.0-alpha.2
0.8.0.0-alpha.3
0.8.0.0-alpha.4
0.8.0.0-alpha.6
0.8.0.0-alpha.7
0.8.0.0-alpha.8
0.8.0.0-alpha.9
0.8.0.0-rc.0
0.8.0.0-rc.1
0.8.0.0-rc.2
0.8.0.1
0.8.1.0
0.8.1.1
0.8.1.3
0.8.1.4
0.9.0.0
0.9.0.1
0.9.1.0
0.9.1.1
0.9.1.2
0.9.2.0
0.9.2.1
0.9.3.0
0.9.3.1
0.9.3.2
0.9.3.3
0.9.3.4
0.9.3.6
1.0.0
1.1.0
1.1.10
1.1.12
1.1.14
1.1.16
1.1.18
1.1.20
1.1.4
1.1.6
1.1.8
1.2.0
1.3.0
1.3.10
1.3.12
1.3.14
1.3.16
1.3.2
1.3.4
1.3.6
1.3.8
1.4.0
1.4.1b4
1.4.1b5
1.4.1b6
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '931a44ee9d'
${ noResults }
nuTensor/CONTRIBUTING.md

1.9 KiB
Raw Blame History

Submitting issues

Do not open feature requests. I just do not have the time.

Do not open issues because web pages are broken as a result of uMatrix blocking stuff because of your ruleset. The issue is with your ruleset, not uMatrix.

The issue tracker is for provable issues only: You will have to make the case that the issue is really with uMatrix and not something else on your side. To make a case means to provide detailed steps so that anybody can reproduce the issue. Be sure to rule out that the issue is not caused by something specific on your side.

For support/discussions, there is /r/uMatrix.

Issues opened which are not actual issues with the code will be closed as invalid without further comment.

Important

  1. When you file an issue, your responsibility is to provide ALL the exact steps needed for me to reproduce an issue.
  2. Ideally, never should I have to guess how to reproduce an issue.
    • Hence this is why very detailed steps must be very carefully written down the first time the issue is filed.
    • Never assume an important step is "obvious".
  3. Every single step, in order, must be provided, with ALL relevant details.
  4. Screenshots are nice, but use common sense: I can't cut and paste important text information from screenshots.
    • Regarding screenshots: common sense. Too much of a thing can easily end up as noise.
  5. Open source quality software comes from contributors carefully crafting code: conversely, issues must also be carefully crafted.
    • In other words: you benefit from the carefully crafted code, return the favor by carefully crafting issues/bug reports.
  6. If your mindset is that your time is more precious than that of my time, refrain from filing issues.

DO NOT

  • Add noise to issues by adding :+1: and other such pointless comments which add no substance.