Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / bigchaindb/beps issues and pull requests
#46 - In v2, transaction operation can't be "GENESIS"
Pull Request -
State: closed - Opened by ttmc over 6 years ago
#45 - Problem: Upsert validator approach is error prone (BEP-21)
Pull Request -
State: closed - Opened by kansi over 6 years ago
- 23 comments
#45 - Problem: Upsert validator approach is error prone (BEP-21)
Pull Request -
State: closed - Opened by kansi over 6 years ago
- 23 comments
#44 - [WIP] Problem: Validators cannot vote on proposals (BEP-18)
Pull Request -
State: closed - Opened by vrde over 6 years ago
- 8 comments
#44 - [WIP] Problem: Validators cannot vote on proposals (BEP-18)
Pull Request -
State: closed - Opened by vrde over 6 years ago
- 8 comments
#43 - Problem: BEP-10 goals are vague.
Pull Request -
State: closed - Opened by ldmberman almost 7 years ago
- 5 comments
#43 - Problem: BEP-10 goals are vague.
Pull Request -
State: closed - Opened by ldmberman almost 7 years ago
- 5 comments
#42 - Problem: No page of transaction specs to link to
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#42 - Problem: No page of transaction specs to link to
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#41 - Problem: BigchainDB is not listed in Azure Marketplace (BEP-17)
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#41 - Problem: BigchainDB is not listed in Azure Marketplace (BEP-17)
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#40 - Discuss: BEP-14
Issue -
State: closed - Opened by ttmc almost 7 years ago
- 7 comments
Labels: discuss existing BEP
#40 - Discuss: BEP-14
Issue -
State: closed - Opened by ttmc almost 7 years ago
- 7 comments
Labels: discuss existing BEP
#39 - Use GitHub's new "code owners" feature to assign an owner to each BEP (subdirectory)?
Issue -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#39 - Use GitHub's new "code owners" feature to assign an owner to each BEP (subdirectory)?
Issue -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#38 - Discuss: BEP-10
Issue -
State: closed - Opened by ldmberman almost 7 years ago
- 16 comments
Labels: discuss existing BEP
#38 - Discuss: BEP-10
Issue -
State: closed - Opened by ldmberman almost 7 years ago
- 16 comments
Labels: discuss existing BEP
#37 - Problem: the BEP template does not ask to specify solution criteria
Pull Request -
State: closed - Opened by ldmberman almost 7 years ago
- 6 comments
#37 - Problem: the BEP template does not ask to specify solution criteria
Pull Request -
State: closed - Opened by ldmberman almost 7 years ago
- 6 comments
#36 - Problem: Wrong spelling of "obvious" is in BEP-7
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#36 - Problem: Wrong spelling of "obvious" is in BEP-7
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#35 - Problem: drivers reliability is low
Pull Request -
State: closed - Opened by vrde almost 7 years ago
- 1 comment
#35 - Problem: drivers reliability is low
Pull Request -
State: closed - Opened by vrde almost 7 years ago
- 1 comment
#34 - Problem: Forgot to update title in index page
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#34 - Problem: Forgot to update title in index page
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#33 - Problem: Need to start refactoring the transaction-related code (BEP-9)
Pull Request -
State: open - Opened by ttmc almost 7 years ago
- 5 comments
Labels: new BEP
#33 - Problem: Need to start refactoring the transaction-related code (BEP-9)
Pull Request -
State: open - Opened by ttmc almost 7 years ago
- 5 comments
Labels: new BEP
#32 - Problem: The current shortnames are weird and hard to use/remember
Issue -
State: open - Opened by ttmc almost 7 years ago
- 2 comments
#32 - Problem: The current shortnames are weird and hard to use/remember
Issue -
State: open - Opened by ttmc almost 7 years ago
- 2 comments
#31 - Problem: BigchainDB 2.0 has design issues
Pull Request -
State: closed - Opened by vrde almost 7 years ago
- 7 comments
#31 - Problem: BigchainDB 2.0 has design issues
Pull Request -
State: closed - Opened by vrde almost 7 years ago
- 7 comments
#30 - Problem: Recent news & feedback not incorporated in BEP-5 yet
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#30 - Problem: Recent news & feedback not incorporated in BEP-5 yet
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#29 - Problem: intro is not the first thing to read
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#29 - Problem: intro is not the first thing to read
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#28 - Problem: BEP-3 not really all that "insecure"
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#28 - Problem: BEP-3 not really all that "insecure"
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#27 - Problem: BigchainDB Transaction Spec docs should live under bigchaindb/BEPs
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#27 - Problem: BigchainDB Transaction Spec docs should live under bigchaindb/BEPs
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#26 - Removed last section. Redundant.
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#26 - Removed last section. Redundant.
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#25 - Add 8/CRASH-RECOVERY to README.md
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#25 - Add 8/CRASH-RECOVERY to README.md
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#24 - Fixing typos again
Pull Request -
State: closed - Opened by muawiakh almost 7 years ago
#24 - Fixing typos again
Pull Request -
State: closed - Opened by muawiakh almost 7 years ago
#23 - Problem: Public Contracts undefined
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#23 - Problem: Public Contracts undefined
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#22 - Problem: working in a shared space is difficult
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#22 - Problem: working in a shared space is difficult
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#21 - Problem: Unclear who does what
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#21 - Problem: Unclear who does what
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#20 - Problem: No BEP discussing the UTXO implementation
Pull Request -
State: open - Opened by kansi almost 7 years ago
- 2 comments
Labels: BEP idea
#20 - Problem: No BEP discussing the UTXO implementation
Pull Request -
State: open - Opened by kansi almost 7 years ago
- 2 comments
Labels: BEP idea
#19 - Problem: Typos in BEPs and project README
Pull Request -
State: closed - Opened by muawiakh almost 7 years ago
- 5 comments
#19 - Problem: Typos in BEPs and project README
Pull Request -
State: closed - Opened by muawiakh almost 7 years ago
- 5 comments
#18 - Problem: 1/C4 and 2/COSS are raw but in use
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#18 - Problem: 1/C4 and 2/COSS are raw but in use
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#17 - Problem: it's not clear how to number BEPs
Issue -
State: closed - Opened by vrde almost 7 years ago
- 5 comments
#17 - Problem: it's not clear how to number BEPs
Issue -
State: closed - Opened by vrde almost 7 years ago
- 5 comments
#16 - [8/CRASH-RECOVERY] Problem: There is no crash recovery technique.
Pull Request -
State: closed - Opened by kansi almost 7 years ago
- 2 comments
#16 - [8/CRASH-RECOVERY] Problem: There is no crash recovery technique.
Pull Request -
State: closed - Opened by kansi almost 7 years ago
- 2 comments
#15 - Problem: The BigchainDB Public API isn't defined
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 3 comments
#14 - Spec to standardize docker-compose workflows
Pull Request -
State: closed - Opened by muawiakh almost 7 years ago
- 5 comments
#13 - [5/IDRP] Problem: Node operators need to know what to do about illegal data.
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#12 - Problem: BEP type incorrect, copyright unspecified
Pull Request -
State: closed - Opened by kansi almost 7 years ago
#11 - Add 3/UPSERT-VALIDATORS to the table
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
#10 - Problem: Unclear what a "Public Contract" is in this context
Issue -
State: closed - Opened by ttmc almost 7 years ago
- 5 comments
#9 - Problem: Evolution of Public Contracts not linked
Pull Request -
State: closed - Opened by ttmc almost 7 years ago
- 1 comment
#8 - Problem: RFC is a too generic name
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#7 - Problem: 1/c4 and 2/coss don't have a type
Pull Request -
State: closed - Opened by vrde almost 7 years ago
#6 - Problem: there is no template for a spec
Pull Request -
State: closed - Opened by vrde about 7 years ago
#5 - Problem: Muawia's proposal template is not yet incorporated in our 2/COSS
Issue -
State: closed - Opened by ttmc about 7 years ago
- 1 comment
#4 - Rename this repository?
Issue -
State: closed - Opened by ttmc about 7 years ago
- 3 comments
#3 - Spec to dynamically add/update/remove validators at runtime
Pull Request -
State: closed - Opened by kansi about 7 years ago
- 10 comments
#2 - Problem: there is no way to propose improvements
Pull Request -
State: closed - Opened by vrde about 7 years ago
- 3 comments
#1 - Problem: there is no collaboration model
Pull Request -
State: closed - Opened by vrde about 7 years ago
- 6 comments