Skip to content
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

documentation link is broken #259

Open
blockops1 opened this issue Jan 4, 2020 · 2 comments
Open

documentation link is broken #259

blockops1 opened this issue Jan 4, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@blockops1
Copy link

blockops1 commented Jan 4, 2020

This documentation link does not work:
BOS set-up and installation guide: https://bos-auto.readthedocs.io/en/develop/installation.html

It can be found on this page:
https://github.com/peerplays-network/peerplays

please provide link to updated documentation

EDIT: Details below are from the issue template and can be ignored. (added by @bobinson )

**Instructions**
Please include a detailed Title above. Next, please complete the following sections below:
* Bug Description
* Impacts
* Steps To Reproduce
* Expected Behavior
* Screenshots (optional)
* Host Environment (optional)
* Additional Context (optional)

Finally, press the 'Submit new issue' button. The Core Team will evaluate and prioritize your Bug Report for future development. 

**Bug Description**
A clear and concise description of what the bug is.

**Porting from Bitshares or other Graphene forks**

Corresponding issues:

    - [FILL in issue1]
    - [FILL in any other detail]
    
Corresponding PR:

     - [fill in corresponding PR link]

**Impacts**
Describe which portion(s) of Peerplays  may be impacted by this bug. Please tick at least one box.
- [ ] API (the application programming interface)
- [ ] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [ ] Deployment (the deployment process after building such as Docker, Gitlab, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [ ] UX (the User Experience)
- [ ] Other (please add below)


**Steps To Reproduce**
Steps to reproduce the behavior (example outlined below):
1. Execute API call '...'
2. Using JSON payload '...'
3. Received response '...'
4. See error in screenshot

**Expected Behavior**
A clear and concise description of what you expected to happen.

**Screenshots (optional)**
If applicable, add screenshots to help explain process flow and behavior.

**Host Environment**
Please provide details about the host environment. Much of this information can be found running: `witness_node --version`. 
 - Host OS:             [e.g. Ubuntu 18.04 LTS]
 - Host Physical RAM    [e.g. 4GB]
 - Peerplays Version   
 - OpenSSL Version:     [e.g. 1.1.0g]
 - Boost Version:       [e.g. 1.67.0]
 
**Additional Context (optional)**
Add any other context about the problem here.

## PBSA / Developer tasks

- [ ] Evaluate / Prioritize Bug Report
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation

@bobinson bobinson added the bug Something isn't working label Jan 6, 2020
@pbsa-github
Copy link

Documentation link has now been fixed and directs to: https://www.peerplays.tech/bookie-oracle-suite-bos

@bobinson
Copy link

bobinson commented Jan 6, 2020

@blockops1 - we have addressed the issue. Please verify from your end too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants