For the past few days, I have been reading the whitepaper and understanding the codebase the protobufs and the architecture.
I found some good issues to start on.
Can anyone confirm whether these have already been done or not? I am asking cause I found many issues which are completed but still open.
Also please suggest to me some good issues to work on.
Thank you.
These tickets still exists. It sounds like you want to pickup one of these tickets? You might want to stay away from tickets that are already assigned to a project. There is a risk that somebody is already working on it and by the time you submit your PR it might be already merged. If you extend the project information you can see if it is assigned to a sprint and what the current status is. If it isn’t assigned to a sprint yet and still in backlog or no status you could take it. Maybe drop a message here which one you would like to work on and I can make sure it doesn’t get double booked by one of us.
What types of issues interest you? Backend? Frontend? Web-based? CLI-based? Network protocols? Debugging features? Etc, etc. We have enough projects that it might be good to hear what types of things you are interested in doing.
Yes, I wanted to take one of them. I asked for taking and just got the response that these tasks are currently blocked due to a schema freeze. I think I need to find some new ones.
I notice that a few of the tickets are regarding the multinode dashboard. Improving the multinode dashboard (the service that connects to one or more nodes) has a variety of possible improvements needed. It is supposed to be a service that can connect directly to multiple nodes over the WAN, with little setup. I imagine that, even if the tickets in this list aren’t of interest to you, searching the forum for issues with the multinode dashboard will reveal a good many number of needed improvements, which you could fix! The core team isn’t spending a lot of time on the multinode dashboard, but it still can be a useful tool.
Improving the multinode dashboard setup (adding and registering a new node to a multinode dashboard) would be a great introduction to how our protocols work (certificate identity, DRPC, etc)
Multitude dashboard interrogates nodes synchronously. If one is stuck or does not respond —as in port closed — the multitude dashboard is stuck also. This is far from good shape.
UI shall be decoupled from data fetches.
The node ids in the list shall be node names user given.
The list shalll be longer than 3 items.
Etc.
There is pretty to do before it even begins to resemble any shape.
I fixed the port offline issue and you can add any number of nodes. I think you need an update.
Although there may be some bugs because some of my PR’s haven’t merged yet.
List of satellites shall display satellite name, not the human-unreadable ID. ID does not tell me anything and is not useful.
On the Bandwidth and Disk tab, please show some indication that some things are going on on the background: e.g. when I change what satellite to view, it takes a few seconds to refresh – and there is no indication that I shall wait. First impression is that nothing happens and everything is broken.
There shall be a version of the multinode app in the UI somewhere.
If that matters – browser is currently released Safari.
./storj/multinode version --log.level=ERROR
Development build
Build timestamp: 14 Oct 24 14:28 UTC
Git commit: cf3f095336af1c2f83d75ab3cf42f921c72f25df
