Contribute

[Manan Patel]

Hi,

I'd like to contribute to the BitCoinJS project. How do I help? Any specific tasks I can take on?

Thanks,

Manan

[Jason Dreyzehner]

Hi Manan,

You may be interested in Bitcore (http://bitcore.io/). Bitcore is actively maintained by a growing group of developers, and it's being used for some awesome projects (like Insight http://insight.bitcore.io/). We're always looking for more developers!

Thanks,
Jason

> --
> You received this message because you are subscribed to the Google Groups "BitcoinJS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinjs+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Manan Patel]

Hi Jason,

I just heard about Bitcore yesterday from BitPay CEO Tony watching the CoinSummit panel yesterday. It is definitely interesting.

How do I start contributing? Should I just have a look around and take a jab at the issues?

Thanks!

You received this message because you are subscribed to a topic in the Google Groups "BitcoinJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bitcoinjs/FJ8zdqJXGJU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bitcoinjs+...@googlegroups.com.

[Jason Dreyzehner]

Hi Manan, (and other interested developers)

Great! Exactly- you can see the current list of issues here: https://github.com/bitpay/bitcore/issues

There’s also a #bitcore IRC channel on Freenode that’s pretty constantly active now.

Welcome!

[Kyle Drake]

Hi Manan,

If you wanted to contribute to bitcoinjs-lib, the procedure is very simple. Fork the repository, create topic branches, and then send pull requests with your changes. We will review the changes and commit if they look ok.

Right now we're working on finishing up the testing. In particular there's some missing tests on the multisig transaction code, and little refactors here and there. Wei has also been working to finish up the wallet implementation.

Running the tests is simple: npm test

Running the coverage report is also easy: npm run-script coverage

We're currently at 87% coverage, so we're made good progress, and would love your help to get it to 100%.

Thanks!

-Kyle

--