You are viewing a single comment's thread from:

RE: The Myth of Slack

So, where are the decisions labeled, "this feature/update is being added by community input" when I've seen no onchain posts asking for such input?

I've seen this statement many times in @blocktrades and a few other lead developer updates, but never a source for where this input originated from...

Sort:  

Gitlab. Keep up with it.

No thanks, I have enough accounts. So, the Community has not truly been consulted. Good to know...

It's not possible to put all the code on the chain. Look at the Gitlab and see the Issues https://gitlab.syncad.com/hive No post is going to convey everything that's part of the code and that's being discussed.

We don't need to see the code to give our opinion on new proposed features and other changes...

How about this, open the Gitlab link and go over to the whitepaper, then click the link mentioned there. You can send your opinion to that one through any means you wish.

I've been encouraging such on-chain conversations to take place in a community called "Hive Improvement", so that they are easy to find. Which as a side note, is where this current post is located.

Here's one such post, which is relevant to my recent such statement about the rate at which Hive in hive.fund will be converted to HBD:
https://hive.blog/hive-102930/@howo/public-debate-at-which-rate-should-the-non-airdropped-stake-be-converted-to-hbd

I've read most of your articles and rarely if ever do I see you ask the community much. I do see you explaining what you and your small group are doing though.

I'm not even sure which "small group" you're referring to. Do you mean the devs that work for my company? Or other devs? I don't actually usually write about what other devs are doing, instead I generally leave that to them to do. My last post did mention some work done by other devs, because they are also people working on tasks directly related to the release of the core code, and their work has some bearing on the timeline for the release itself.

There's two separate things here: discussing what to do, and discussing what's being done or has been done recently. I do post about both, but most of the time I post about the latter, because that is what tends to consume most of my time.

When I'm posting about ideas about things to do for Hive, I usually post in "Hive Improvements". When I post about dev work we're doing, I usually post in "Hive Devs". If I'm writing something more in the way of blockchain theory, and not actively soliciting ideas for Hive, I usually post on my own blog.

They all show up in trending,so where you post isn't relevent, but you verified my last comment.

Well, it's certainly still relevant, as posts don't last more than a few days on trending.

As for public input, that can and is done via the public channels, i.e. Discord, hive.blog, PeakD and most importantly when talking about the code, Gitlab.

How much input from people who are not witnesses or coders is on these channels of communications isn't dependent on those doing the work. It is the individual responsibility of each and every stakeholder to be active.

There isn't nor shall there be anyone going around whipping people and forcing them to be active in any communications.

I mean, seriously, each of us needs to look in the mirror as far as what we do or don't do in terms of our own efforts to be informed, constructive contributors and proactive in what we do.

Lol, nice spin😂

So, the answer is; the community wasn't asked!

Source for the onchain discussion please?

No, what I stated are FACTS.

Backed by the Gitlab Repo and if you were to subscribe to it, you may actually fall over backwards with just how many email notifications you will get daily.

You won't even need to go to Gitlab, it will all be delivered to your inbox.

So, the only people putting a "spin" on things are those that haven't even tried to follow anything anywhere, but "assume" things, simply because they themselves are not prepared to even try and get to the FACTS.

FACTS vs opinions and emotions.

I choose FACTS.

I thought so, git isn't Hive and the convo should be HERE... So it seems, you shouldn't even have weighed in on my comment, because you don't possess the info I asked for nor are you in a high enough position here.

Judging from your posts, you simply have a very subjective opinion about everything and rarely are on topic.😛

Well, maybe you should try and learn a thing or two about things before commenting on them.

i.e. Where coders work their magic!

i.e. Gitlab, Github

I guess all coders need to do things how you want them to do it and not how all the professionals do it.

Enjoy the day.

& likewise, you can NEVER put a spin on the following FACT:

"The primary job description of a witness is to ensure the existential security of the blockchain."

That far outweighs any "opinions" or "emotions".

In fact, emotions need to be set aside when that primary role and responsibility is put to the test.

I rest my case.

But you can feel free to waffle on, you have every right to do so.

Nope, coders are NOT the Hive Community... They are a SMALL FRACTION of it!

Anyway, not one of your replies were on topic.(talk about waffling on)

If witnesses are being called the community, then that's misleading. Quit saying 'community' and call it what it is!