[Worker Proposal] Project administration & essential maintenance

vikram · April 03, 2017, 12:20:41 AM

Fixed a crash in get_ticker and get_24_volume API calls as identified by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/250)

Chris4210 · March 24, 2017, 05:45:38 PM

Hi Vikram,

thank you for the update, unfortunately these updates are not regular enough to understand what you worked on the past few days and what you would like to improve next. Regular communication to all BitShares Shareholders is very important.

Until the communication has been improved, I removed my support for this worker.

Best regards,

Christoph

cass · March 24, 2017, 04:55:50 PM

Quote from: vikram on March 23, 2017, 03:54:23 PM
Since the last update I've basically:

Merged a few bitshares-core PRs (https://github.com/bitshares/bitshares-core/pulls?utf8=%E2%9C%93&q=is%3Apr)
Including a large API notification patch that @ElMato and @oxarbitrage have been working on for some time (https://github.com/bitshares/bitshares-core/pull/249)
I also simplified the internal time system to help improve the consistency of the code (https://github.com/bitshares/bitshares-core/issues/76)
Merged a few minor updates to bitshares-fc (https://github.com/bitshares/bitshares-fc/commits/master)
Including merging an upstream feature from steemit-fc to help log the time taken by API calls (https://github.com/bitshares/bitshares-fc/commit/1f41494f360a1800fc967d647631cf64fdc549ee)

As mentioned previously, there is not a whole lot of core/fc development activity at the moment, so I think roughly monthly updates strike a good balance. Again, part of the intent of this worker is to be a clearly defined agent that can encourage and integrate contributions, but while ensuring that the stability of the network does not suffer while doing so.

This worker is unlikely to make big enhancements or other potentially nonessential upgrades on its own, but if there is a specific issue really hurting service integration or usability, of course let me know.

Shoutout to @oxarbitrage, @ElMato, @svk, and TheTaconator (@Taconator ?) for their patches or other work!

Thanks for your updates! Much appreciated

vikram · March 23, 2017, 03:54:23 PM

Since the last update I've basically:

Merged a few bitshares-core PRs (https://github.com/bitshares/bitshares-core/pulls?utf8=%E2%9C%93&q=is%3Apr)
Including a large API notification patch that @ElMato and @oxarbitrage have been working on for some time (https://github.com/bitshares/bitshares-core/pull/249)
I also simplified the internal time system to help improve the consistency of the code (https://github.com/bitshares/bitshares-core/issues/76)
Merged a few minor updates to bitshares-fc (https://github.com/bitshares/bitshares-fc/commits/master)
Including merging an upstream feature from steemit-fc to help log the time taken by API calls (https://github.com/bitshares/bitshares-fc/commit/1f41494f360a1800fc967d647631cf64fdc549ee)

As mentioned previously, there is not a whole lot of core/fc development activity at the moment, so I think roughly monthly updates strike a good balance. Again, part of the intent of this worker is to be a clearly defined agent that can encourage and integrate contributions, but while ensuring that the stability of the network does not suffer while doing so.

This worker is unlikely to make big enhancements or other potentially nonessential upgrades on its own, but if there is a specific issue really hurting service integration or usability, of course let me know.

Shoutout to @oxarbitrage, @ElMato, @svk, and TheTaconator (@Taconator ?) for their patches or other work!

fav · March 22, 2017, 07:37:50 PM

Quote from: cass on March 20, 2017, 03:29:20 PM
Any updates about your worker!?

last report was almost 3 weeks ago. removed my vote.

cass · March 20, 2017, 03:29:20 PM

Any updates about your worker!?

Chris4210 · March 10, 2017, 03:07:56 PM

Good. I am looking for more active updates about your work Vikram. Please also join us on Telegram for direct communication. We also have a developer channel.

vikram · March 04, 2017, 11:30:07 PM

Recent updates:

Continued handling PRs (great work especially by @oxarbitrage)
Updated seed nodes based on reports in seed node thread (https://bitsharestalk.org/index.php/topic,23715.0.html)
Cleaned up README (https://github.com/bitshares/bitshares-core#bitshares-core)

xeroc · February 01, 2017, 10:17:07 AM

great work ...

pc · February 01, 2017, 06:29:08 AM

+1

Good work!

vikram · February 01, 2017, 05:47:38 AM

Quote from: Thom on February 01, 2017, 03:28:38 AM
Just to clarify, to build the latest from source what is the top level repo to clone, https://github.com/bitshares/bitshares-core? If building from a clean slate (no existing src tree locally), is it necessary to update build scripts with anything besides the top level repo URL? If so is that reflected in a script or step by step build instructions?

Yup, bitshares-core. The old URLs (bitshares-2) will still work because GitHub redirects from the old name--but I will indeed be updating some of the build instructions (intended as part of my last point above).

Thom · February 01, 2017, 03:28:38 AM

Quote from: vikram on January 31, 2017, 07:57:05 PM
Latest updates:

bitshares-fc

Created new fc fork https://github.com/bitshares/bitshares-fc for use by BitShares and to keep ongoing compatibility
Includes most updates and PRs from https://github.com/steemit/fc and https://github.com/cryptonomex/fc
Merged some new PRs (great work @ElMato!)
bitshares-core (https://bitsharestalk.org/index.php/topic,23716.msg301955.html#msg301955)

Renamed https://github.com/bitshares/bitshares-2 into https://github.com/bitshares/bitshares-core
Moved all the issues from https://github.com/cryptonomex/graphene into https://github.com/bitshares/bitshares-core
Closed many old issues
Updated git submodule remotes to point to bitshares forks instead of cryptonomex forks (defined here https://github.com/bitshares/bitshares-core/blob/master/.gitmodules)
Changed default bitshares-core branch from bitshares to master
Merged some new PRs (great work @ElMato!)

Active developers and those building from source can update their submodule remote URLs using "git submodule sync --recursive".

I am also the one that reorganized the BitSharesTalk subforums (https://bitsharestalk.org/index.php/topic,23650.0.html).

Some things I want to look at next:

Continue to handle outstanding PRs for bitshares-core
Continue to incorporate upstream fc updates and PRs
Clean up bitshares-core branches and include/merge applicable branches from https://github.com/cryptonomex/graphene
Improve bitshares-core documentation on developing/contributing

Wow, great work @vikram! You H A V E been busy!

Just to clarify, to build the latest from source what is the top level repo to clone, https://github.com/bitshares/bitshares-core? If building from a clean slate (no existing src tree locally), is it necessary to update build scripts with anything besides the top level repo URL? If so is that reflected in a script or step by step build instructions?

That would sure be nice for any newbies that are trying to build a witness or seed node from scratch.

vikram · January 31, 2017, 07:57:05 PM

Latest updates:

bitshares-fc

Created new fc fork https://github.com/bitshares/bitshares-fc for use by BitShares and to keep ongoing compatibility
Includes most updates and PRs from https://github.com/steemit/fc and https://github.com/cryptonomex/fc
Merged some new PRs (great work @ElMato!)

bitshares-core (https://bitsharestalk.org/index.php/topic,23716.msg301955.html#msg301955)

Renamed https://github.com/bitshares/bitshares-2 into https://github.com/bitshares/bitshares-core
Moved all the issues from https://github.com/cryptonomex/graphene into https://github.com/bitshares/bitshares-core
Closed many old issues
Updated git submodule remotes to point to bitshares forks instead of cryptonomex forks (defined here https://github.com/bitshares/bitshares-core/blob/master/.gitmodules)
Changed default bitshares-core branch from bitshares to master
Merged some new PRs (great work @ElMato!)

Active developers and those building from source can update their submodule remote URLs using "git submodule sync --recursive".

I am also the one that reorganized the BitSharesTalk subforums (https://bitsharestalk.org/index.php/topic,23650.0.html).

Some things I want to look at next:

Continue to handle outstanding PRs for bitshares-core
Continue to incorporate upstream fc updates and PRs
Clean up bitshares-core branches and include/merge applicable branches from https://github.com/cryptonomex/graphene
Improve bitshares-core documentation on developing/contributing

vikram · January 13, 2017, 03:20:49 AM

Quote from: JonnyBitcoin on January 12, 2017, 02:47:57 PM
where are @vikram latest updates ?

Pushed some updates to bitshares/fc to bring it into sync with steemit/fc: https://github.com/bitshares/fc/compare/31adee49...master

Should be compatible with latest gcc and clang compilers. Boost compatibility past Boost 1.60 will still have to wait on upstream development from Steemit.

Hoping to do some reorganization of the bitshares-2 repo soon before updating it to reflect the fc upgrades.

JonnyB · January 12, 2017, 02:47:57 PM

where are @vikram latest updates ?