Bi-weekly meeting for Hive developers, meeting 1

We're tentatively scheduling the first such meeting on Monday, April 6th, at 4pm UTC (6pm CET).

@howo has offered to schedule a zoom meeting.

Please add comments to this issue for anything you'd like to discuss during the meeting.

added discussion label

changed the description

We should briefly discuss the plans for the upcoming hardfork, and what our general process should be for documentation, testing, feature freeze time delay before release, etc for future hardforks.

Are there any plans to keep records of these meetings and upload them to various video-sharing platforms for the blockchain users? Could be a very nice way to keep the blockchain users up-to-date.

@hiveio can share these meetings with short excerpts pointing out the important subjects.

my goal will be to distill these meetings into HiveIO posts that can help people understand them without feeling the need to attend, yes. A TL;DR that is more like 'too complex; didn't watch', if you will.

I don't see any reasons why those meetings should not be public. I envision them to be like those eth core dev meetings https://www.youtube.com/watch?v=zSRzlC_dCx8

@howo I wouldn't necessarily share Zoom Meeting ID and Password publicly in the issue. As it is a hassle to handle more members (and I believe it is not free) it will definitely be better and more efficient overall if someone just livestreams the event after joining Zoom and/or uploads a recording.

If, it is decided that the meeting should be public in the first place.

changed the description

Zoom is free for as many users as we want. There is a 40 minute time limit though. So it may make more sense to use hangouts. But at the same time I don't think we necessarily want those meetings to be longer than that.

And yeah I forgot that the gitlab was now public

Actually, that 40-minute limit might be useful.

People in the meeting can take a break, rest and come back after some time and start a new meeting. So I don't think it's really a problem. Google Hangouts is losing its popularity day by day anyways. Even Discord group chat is better than that.

40 minutes is more than enough if we are well organized enough.

We should also establish which projects are "core" in the sense that they affect other projects, and decide on review processes to detect any potential problems prior to a release of any core project that might impact the ecosystem. The same goes for any software where a bug could potentially cause a loss of funds to a user.

I think "core" projects would be :

• libraries (dhive/beem/hive-js/...)
• the hive blockchain itself
• tooling around it (hivemind/jussi/cli_wallet/...)

Seconding this, any other project can be moved to another "public repository" to be honest. No need for them to clutter the main group "hive".

I actually like having one place to find all the projects, not just the core ones. Its useful to see the whole ecosystem. As long as the projects have reasonable top-level descriptions, it shouldn't get too confusing.

Let's add at least Keychain and HiveSigner.

Yeah what Howo said, tools that benefit the entire ecosystem and the projects built with them. It should include a status update on nodes where necessary. (In my opinion, the later in the day the better)

2pm UTC (4pm CET)

Please add comments to this issue for anything you'd like to discuss during the meeting.

• Blockchain state (development, plans, ongoing work...)
• RPC and tools state (rpc nodes, hivemind, jussi, cli, docker images...)
• Libraries state (libraries js, python, ruby, go...)
• Services state (devportal, hive.io, signup faucet, auth (keychain, hivesigner), if time left, we could discuss further what services and apps struggling with and how we can help?!)

In my opinion, Last point has wide range of topics, could only be considered, if there is more time and all above points are already discussed.

"we could discuss further what services and apps struggling with and how we can help?!)" I don't really think it's the point of these meetings.

That's why I said could only be considered, if there is more time . Point of meeting is to improve entire ecosystem from developers perspective, right?!

Point of the meeting is to sync and discuss roadmaps, not a helpdesk. These kind of issues should be solved via text.

exactly!

Points for the first meeting imo :

• Update on what everyone has been doing (On core subjects, your work on your app is not the focus)
• Discussion on workflow and how to use gitlab issue tracker to do project management
• Scope of hard fork 24
• Initial work repartitions for the scope (more of a show of hand, "who wants to do this" and if nobody replies we'll see later)
• libraries status and what's left to be done
• Work repartitions for the libs as well

I think the most important part should be gitlab and hard fork 24, in order to clearly define how we are going to work from now on as a community.

added To Do label

Probably was seen elsewhere, but adding a link here: https://hive.blog/hive/@blocktrades/hive-workflow-proposal

changed the description

• RPCs, account history nodes, get_transaction op
• Optimize Jussi for better efficiency

• Update on what everyone has been doing (On core subjects, your work on your app is not the focus)

• Discussion on the workflow using blocktrade's post a baseline read it here if you have not https://hive.blog/hive/@blocktrades/hive-workflow-proposal

• Roles: devs, who can review what, who can deploy what etc...

• Should we have regular scheduled deployments? Automated/manual?

• How do we prioritises issues to be dealt with first?

• Git branching strategy? Maybe a "staging" branch that gets automatically deployed to a staging website upon new merge.

• Core blockchain

  • Scope of hard fork 24
  • RC delegation
  • RPCS, account history nodes, get_transaction op improvements
  • Discuss on SMTs, it's current state and where we are going
  • How can we optimize Jussi for better efficiency

• brainstorm on what's left to do on libraries

expected outputs :

• Sync between the various devs to know who's working on what
• issues to be created from the recording to set various tasks
• A final workflow to be applied (and improved on later on if needed)

changed title from Bi-weekly meeting for Hive developers to Bi-weekly meeting for Hive developers #1

changed title from Bi-weekly meeting for Hive developers #1 to Bi-weekly meeting for Hive developers, meeting 1

I have decided to open a new issue for each new meeting so that people can come back to those issues and see the discussions that led up to the meeting.

here is the youtube link to this meeting:

https://www.youtube.com/watch?v=v4cfY6wxGdg

closed

mentioned in issue #8 (closed)

mentioned in issue #11 (closed)

mentioned in issue #12 (closed)

mentioned in issue #17 (closed)

mentioned in issue #18 (closed)

mentioned in issue #19 (closed)

mentioned in issue #20 (closed)

mentioned in issue hive#73 (closed)

mentioned in issue #22 (closed)

mentioned in issue #23 (closed)

mentioned in issue #24 (closed)

mentioned in issue #27 (closed)

mentioned in issue #28 (closed)

mentioned in issue #29 (closed)

mentioned in issue #30 (closed)

mentioned in issue #31 (closed)

mentioned in issue #32 (closed)

mentioned in issue #33 (closed)

mentioned in issue #34 (closed)

mentioned in issue #35 (closed)

mentioned in issue #36 (closed)

mentioned in issue #37 (closed)

mentioned in issue #39 (closed)

mentioned in issue #40 (closed)

mentioned in issue #41 (closed)

mentioned in issue #43 (closed)