Skip to content

Issues: PowerNex/PowerNex

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

Create memory map documentation effort: low The issue will probably take a single contributor no more than one day of work to resolve. priority: low The issue has only a small impact on people using the software. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation.
#89 opened Jun 21, 2018 by Vild Version 0.3
Fix the error messages inside of PowerD effort: low The issue will probably take a single contributor no more than one day of work to resolve. meta: good first issue The issue is especially suitable for first-time contributors. priority: low The issue has only a small impact on people using the software. type: polish The issue involves making existing functionality more usable.
#88 opened May 3, 2018 by Vild
Update kernel code effort: high The issue will probably take a single contributor several days of work to resolve. meta: next release The issue must be resolved before the next package version can be released. priority: critical The issue must be resolved as soon as possible. type: code quality The issue involves code organization and readability.
#87 opened Feb 27, 2018 by Vild Version 0.3
[Jenkins] Fix setGitHubPullRequestStatus for PR effort: low The issue will probably take a single contributor no more than one day of work to resolve. meta: good first issue The issue is especially suitable for first-time contributors. priority: trivial The issue has very little impact on people using the software. type: integration The issue involves interactions with other software.
#85 opened Feb 27, 2018 by Vild
[q] how to start as a contributor issue: question The issue is a question, and it should be closed after the question is answered.
#83 opened Feb 27, 2018 by vladp
toolchainManager.d - Clone and compile powernex-dmd, binutils, gdb effort: low The issue will probably take a single contributor no more than one day of work to resolve. meta: good first issue The issue is especially suitable for first-time contributors. priority: low The issue has only a small impact on people using the software. type: feature The issue involves adding new or extended behavior to the package.
#80 opened Sep 25, 2017 by Vild Backlog
Add comments effort: moderate The issue will probably take a single contributor one or two days of work to resolve. meta: next release The issue must be resolved before the next package version can be released. priority: medium The issue makes it more difficult for people to use the software. type: code quality The issue involves code organization and readability. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation.
#61 opened Oct 4, 2016 by Vild Version 0.3
SATA effort: high The issue will probably take a single contributor several days of work to resolve. priority: medium The issue makes it more difficult for people to use the software.
#59 opened Sep 14, 2016 by Vild Version 0.4
IPC effort: high The issue will probably take a single contributor several days of work to resolve. priority: medium The issue makes it more difficult for people to use the software.
#58 opened Sep 14, 2016 by Vild Version 0.4
Shared memory effort: high The issue will probably take a single contributor several days of work to resolve. priority: medium The issue makes it more difficult for people to use the software.
#57 opened Sep 14, 2016 by Vild Version 0.4
Make a build guide with all dependencies effort: low The issue will probably take a single contributor no more than one day of work to resolve. meta: good first issue The issue is especially suitable for first-time contributors. meta: next release The issue must be resolved before the next package version can be released. priority: low The issue has only a small impact on people using the software. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation.
#55 opened Aug 29, 2016 by Vild Version 0.3
Logo/Mascot
#30 opened Mar 23, 2016 by Vild Backlog
ProTip! Exclude everything labeled bug with -label:bug.