Author Topic: [Worker Proposal] Project administration & essential maintenance  (Read 22928 times)

0 Members and 1 Guest are viewing this topic.

Offline vikram


Offline Chris4210

  • Sr. Member
  • ****
  • Posts: 431
  • Keep Building!
    • View Profile
    • www.payger.com
  • BitShares: chris4210
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
Vote Chris4210 for Committee Member http://bit.ly/1WKC03B! | www.Payger.com - Payments + Messenger | www.BitShareshub.io - Community based fanpage for the BitShares Blockchain

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
Since the last update I've basically:

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
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline vikram

Since the last update I've basically:

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!
« Last Edit: March 23, 2017, 04:02:53 pm by vikram »

Offline fav

  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Any updates about your worker!?

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

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline Chris4210

  • Sr. Member
  • ****
  • Posts: 431
  • Keep Building!
    • View Profile
    • www.payger.com
  • BitShares: chris4210
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.
Vote Chris4210 for Committee Member http://bit.ly/1WKC03B! | www.Payger.com - Payments + Messenger | www.BitShareshub.io - Community based fanpage for the BitShares Blockchain

Offline vikram

Recent updates:

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline vikram

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).

Offline Thom

Latest updates:

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

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.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline vikram

Latest updates:

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

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
« Last Edit: January 31, 2017, 10:41:04 pm by vikram »

Offline vikram

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.

Offline JonnyB

  • Hero Member
  • *****
  • Posts: 636
    • View Profile
    • twitter.com/jonnybitcoin
I run the @bitshares twitter handle
twitter.com/bitshares