NEO developer community (CoZ) Weekly Report #6 - 2017.08.15

in blockchain •  7 years ago  (edited)

City of Zion (CoZ) is a community of open source enthusiasts spread across the world that has the shared goal of helping NEO fulfill its potential. It is not a corporation, nor a devshop, nor a consulting firm nor a for-hire group. The way it works is by having central places for the community to share knowledge and contribute to projects, they are namely the slack and CoZ github org. Any consistent contributor is eligible to be added to CoZ org and start projects, the only restriction is that code on the org should be licensed as MIT, there is no application process, you need to do the work first. CoZ has a governance, you should read it in our page. The NEO council has been together with us since the very beginning providing support to the community that CoZ redistribute every week, in this past 6 weeks we have rewarded dozens of developers, totaling 7149 NEO.

Our governance can be seen here

The community has decided to reward 336 NEO for the efforts listed below

Very busy once again, this week we had no time to do a refined report, we are cooking a in-deep QA session with CoZ council members and NEO core, unfortunally network problems pushed it to next week report.

This week you will see the end of forks in CoZ, only community projects will be on our GitHub org, and we ask contributors from the community to go directly to NEO official projects. All CoZ council and some key community members are now collaborators in NEO GitHub repositories and will be helping review and add new code.

Work done at CoZ during this week:

Core

  • New organization for making core code modular as NuGet packages
  • Initial NEP5 example implementation (this is a token standard equivalent to ERC20)
  • Initial NEP2 implementation (standard to safely hold keys in storage and memory)

Neo slack bot

  • Price functionality by command
  • Price updates in #market every 3 minutes
  • Fixed some bugs which caused the bot to crash in rare occasions
  • Some minor improvements
  • #announcements channel bot to keep it clean

Neo Discord bot

  • Refactored skills
  • Added optional mongoDB
  • PR reviewing
  • Preparing for installation on another Discord

Admin Panel

  • Deployed to Heroku and official domain
  • Added option for more than 1 wallet
  • Fixed some bugs regarding invites
  • Added market prices and wallet amounts
  • Fixed some minor bugs

Neon Wallet:

  • Refactor neon-js library as import
  • New organization around redux modules
  • New tests
  • Website setup at neonwallet.com
  • CircleCI integration

Neon Wallet API:

  • Debug issue where official Neo client sends multiple vouts of one asset to a single address (affects gas claiming)
  • Debug load issue with indexing

Neon Wallet Support:

Neon JS:

Neo Python:

  • Full sync / validation/ and persistence of block / transaction/ account data
  • Now operates with peer discovery option
  • More runtime introspection ( viewing memory consumption / other statistics ) via CLI
  • Ability to configure logging on /off at runtime
  • Began work on python VM Smart contract interpreter
  • And, as always, more tests!

NeoScan:

  • Full sync.
  • Integration of new background network monitor app.
  • Network monitor API.
  • DB debug and optimization.

Go SDK

  • Golang SDK for interacting with the Node RPC endpoint

Documentation

  • German translation of Neo White Paper and NeoContract White Paper

That is it, stay tuned for our next report with our council + core QA session.

FCC on behalf of CoZ council.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Looking forward to the future of $NEO $GAS...keep up the great work :)

@canesin I am interested in contributing to the NEO or CoZ ecosystem. I am only a 4th Year Computer Science major, but I am pretty sure I could be useful in some way. Can you recommend a good place for me to start? Even if it's just reporting bugs or writing tests.

  ·  7 years ago (edited)

Go to our slack and talk to people on #develop, you certainly will not regret it. Also, the easiest way is just doing.. learn where you can contribute and contribute, don't wait for approvals.

Thank you. Will do!

Hi. I am a volunteer bot for @resteembot that upvoted you.
Your post was chosen at random, as part of the advertisment campaign for @resteembot.
@resteembot is meant to help minnows get noticed by re-steeming their posts


To use the bot, one must follow it for at least 3 hours, and then make a transaction where the memo is the url of the post.
If you want to learn more - read the introduction post of @resteembot.
If you want help spread the word - read the advertisment program post.


Steem ON!

Awesome work....love it!

Awesome.
You should add the programming tag, maybe in place of the market one.