I am submitting this project application in order to reserve the cc project namespace so the module hierarchy proposed below will work.
The crypto currency framework will make integrating crypto currencies into your drupal site simpler.
The proposed structure and module hierarchy for the project at the moment will be:
Crypto Currency library
The Crypto Currency library will provide a generic namespace, classes, interfaces, and abstractions common to all crypto currencies. The library will contain only PHP code so that it is portable throughout different systems and platforms (including non drupal systems). Individual crypto currencies can provide a namespace for Bitcoin, Litecoin, Namecoin, etc. to integrate any specific functionality or features.
This is going to be a collaboration between several skilled PHP developers from other systems and frameworks.
I am currently in discussion and evaluating https://github.com/afk11/bitcoin as a foundation for this library.
Cryto Currency module suite
The Crypto Currency module suite is a collection of modules providing the drupal related functionality, integration, and wrappers with the Crypto Currency library.
Here is an overview of the proposed module structure and hierarchy:
- cc: Provides the main crypto currency foundation, api, administration section, etc.
- cc_btc: Provides the bitcoin crypto currency integration, CryptoCurrency Bitcoin library wrappers, bitcoinjs, etc.
- cc_{nmc, ltc, doge}: Provides the alt coin crypto currency integration
- cc_gateways: Provides the gateway functionality, classes, api, and connection handling to the crypto currency network
- cc_btc_gateway_core: Provides the bitcoin core client gateway, connection settings, etc.
- cc_btc_gateway_{bc,insight,bitcoinj,blocktrail,etc.}: Provides the {blockchain.info, insight, bitcoinj, blocktrail, etc.} gateway, administration settings form, api keys, etc.
- cc_addresses: Provides the address functionality, api, formapi element, and field subsystem plugins
- cc_btc_address_core: Provides addresses sourced by the bitcoin core client
- cc_btc_address_hd: Provides addresses sourced by hd pub keys
- cc_btc_address_bc: Provides addresses sourced by a blockchain.info wallet
- cc_amount: Provides the crypto currency amount functionality, formapi element, and field subsystem plugins
- cc_currencies: Provides the fiat currencies functionality, and api, which leverages the currency module (https://www.drupal.org/project/currency)
I have evaluated the bitcoin, bitcoin_commerce, and cointools modules. These modules provide functionality specific to individual crypto currencies, but are not generic enough to comfortable expand to encompass multiple crypto currencies.
The link is the current sandbox is here:
https://www.drupal.org/sandbox/mikedance/2398623
The project can be viewed at:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/mikedance/2398623.git crypto_currencies
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxmikedance2398623git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
PA robot commentedProject 1: https://www.drupal.org/node/2434289
Project 2: https://www.drupal.org/node/2421913
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
avpaderno