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

Improve Protocol Library Build Process #1568

Closed
6 tasks
ryanRfox opened this issue Feb 8, 2019 · 1 comment
Closed
6 tasks

Improve Protocol Library Build Process #1568

ryanRfox opened this issue Feb 8, 2019 · 1 comment
Assignees
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2a Discussion Needed Prompt for team to discuss at next stand up. 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 4a Low Priority Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists 6 Build Impact flag identifying the build process

Comments

@ryanRfox
Copy link
Contributor

ryanRfox commented Feb 8, 2019

User Story
As a developer I want the **protocol library** build system improved so we can evaluate the benefits/viability of converting the remaining **bitshares-core** repository to Meson from CMake.

Additional Context (optional)
Recommendation: initially create both build systems for the protocol library to allow for a direct side-by-side comparison at small scale, at which point a prediction for the advantages of Meson to be apparent.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@ryanRfox ryanRfox added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2a Discussion Needed Prompt for team to discuss at next stand up. 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 Build Impact flag identifying the build process labels Feb 8, 2019
@ryanRfox ryanRfox added the 4a Low Priority Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists label Feb 8, 2019
@nathanielhourt
Copy link
Contributor

This issue was created to follow up #1506, and remove the protocol library from the main BitShares repo altogether once it was separated from the chain library.

This would be done primarily to support/encourage development of third party implementations of the BitShares core protocol, independent of the reference implementation. Since there is presently no project to do this, splitting off protocol from the main repo is not a priority.

Closing this issue due to lack of interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2a Discussion Needed Prompt for team to discuss at next stand up. 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 4a Low Priority Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists 6 Build Impact flag identifying the build process
Projects
None yet
Development

No branches or pull requests

2 participants