OriginTrail
OT-Node v6 cleanup instruction for all node runners
Listening to suggestions from our community, we decided to make OT-node and GraphDB run as a system service. We also made some breaking changes in the data layer so to continue with rapid development, we suggest everyone to purge their triple stores ( GraphDB).
To make this easy, all these changes are automated into one script that will do it for you and also do additional cleanup, so we would like to ask you to follow next instructions to prepare you OT-Node v6 for next release:
Clone this gist to the node's root directory :
cd && git clone https://gist.github.com/44e607fe4d0bb0ef4432c6de187139b4.git
Change directory and run the script:
cd 44e607fe4d0bb0ef4432c6de187139b4 && chmod 777 recreateDBsAndRunServices.sh && ./recreateDBsAndRunServices.sh
You can now safely remove this directory :
cd && rm -rf 44e607fe4d0bb0ef4432c6de187139b4
Gist with script: https://gist.github.com/zeroxbt/44e607fe4d0bb0ef4432c6de187139b4
#TraceOn
Opening an issue to report updates to the community is a very odd thing to do. I don't think this is what this feature is for...
Why not use Discord for this? And while you're at it, spend some time there assisting people who are genuinely interested in this project. It's so discouraging seeing so many people going there, ask questions and there is nobody from the team around to help.
@ngdias thanks for feedback, sorry to hear that you are not satisfied with our response time in discord, we are trying to always keep the response time as low as possible, but our primary thing is development and we need to prioritize it over providing support when we need to implement important features.
About using issue report for this I'm open for discussion to see better way. Our thinking was that the issue is that people have old data in triple stores that will not be useful for newer versions, and that we need to comunicate with everyone to delete it and also do some additional steps. So we need to share instructions and script, and also we wanted to share this on Github, Discord, Twitter and Telegram, so the best way that we could found was to create here an issue and share the link to all communication channel. Only sharing it on discord will make it harder to reach everyone and some node runners would miss it. :)
#TraceOn
OT Discord is super quiet. You have team members that post updates sometimes, I don't understand why that person wouldn't engage with the community more. Some questions are not technical at all; the questions that are technical, perhaps those could be forwarded to devs by the community manager?
I feel overall the communication has been limited to the bare minimum. I've been following this project for a few years now. This is a respectable project, you clearly work hard on it, and the community facing side of it is not up to par with the rest. You can look at it this way: Someone interested in investing drops by the Discord to research the project and get a feel of the community, team engagement, etc. They see the Discord is super quiet, people leave questions from time to time and many are left unanswered or are answered vaguely by community members who frankly have no way of knowing the correct answer sometimes. This doesn't score positive points in any evaluation.
About the reporting thing. I didn't expand as much as I should. Yes, there is a Discord channel that is a natural fit to report updates. Many community members seem to prefer Telegram, so announcing updates there also makes sense. The point is there are natural places to report updates. Those places trigger notifications on a computer, phone... I do get notifications for Issues I am participating, but I don't get updates for every issue... and I wouldn't want that, because most of them I cannot do anything about them. So I think you should use all popular means of pushing updates. I could be wrong, but more people check Discord and/or Telegram than check Github issues... Cheers for taking the time to address this.