Backend Issues to work on

Developer Discussions
, , ,
1

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.

  1. Low STORJ balance email
  2. Satellite DB: Add “API key settings” table
  3. Console: Add “API key settings” endpoints
  4. Satellite UI: Implement API key settings endpoints

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.

2

Hello @ptdatta,
Thank you for your interest!

I forwarded your question to the team.

1 Like
3

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.

1 Like
4

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.

2 Likes
5

I am interested in all of this. But to be specific I love to work on Backend and Network protocols.

6

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.

7

Hey @jtolio do you have anything for me to work on for the backend and network protocol side?

8

It looks like we have a couple of issues already tagged as “Good first issue” here: Issues · storj/storj · GitHub

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)

3 Likes