Skip to content
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.

Help with xchange-stream maintenance #181

Closed
nikolaenkov opened this issue May 14, 2018 · 17 comments
Closed

Help with xchange-stream maintenance #181

nikolaenkov opened this issue May 14, 2018 · 17 comments

Comments

@nikolaenkov
Copy link

Hi, @dozd could not find any other way to direct message you.

Feel free to contact me if you need help with maintenance. We had to copy xchange-stream repo locally and significantly patched/changed it to make more stable (and sometimes to make it work :)) At that time it was easier/faster for us. Now we're thinking of giving back our work to the community.

Thanks for your effort.

@declan94
Copy link
Collaborator

We are in the same situation as @nikolaenkov and are also willing to contribute to the community.

@jkolobok
Copy link
Collaborator

Same here.

@badgerwithagun
Copy link
Collaborator

Potentially also willing to assist.

Has there been any dialogue with the Xstream maintainer(s)? Having these two as separate projects will always mean this one will be constantly struggling to keep up.

@dozd
Copy link
Member

dozd commented Jun 6, 2018

Hello, sorry for the late response. I'm happy you want to help with the maintenance of the project. As I really don't know how to check the quality of your potential contribution I'd like you to make review of each others (or any other) PR for this time. If you approve PR (not yours) I have no problem with the merge.
I think you can assign yourself as a reviewer for any PR, so feel free to pick any and approve / comment it. I added you as contributors (with the read access only for now). Also, submit yours PR if you haven't done it yet,

When I started the project I have only one goal: the simplicity for the end user. So have this also in your mind :).

@badgerwithagun About the Xchange integration: There was streaming support for some exchanges in the Xchange library itself but because of the bad implementation they found it hard to maintain and remove it. I think a separate library works very well and it's really not hard to be up to date with the latest release version of the Xchange. Even there can be a branch that is "prepared" for the upcoming Xchange release and it can depend on the snapshot version of the Xchange.

@jkolobok
Copy link
Collaborator

jkolobok commented Jun 7, 2018

@dozd Only contributors with write access can approve PRs. Others can just comment. There are some of PRs with comments.
e,g my PR here (unfortunately several fixes in one PR ) #185

PRs with comments:)
#188
#191

@dozd
Copy link
Member

dozd commented Jun 8, 2018

@jkolobok I think that when you assign yourself as an reviewer and click start the review, you can then submit review as Approve or Changes requested. So if you are fine and approve the PR without any requested changes, all checks will be passed and I just click (for now) the merge button.

@jkolobok
Copy link
Collaborator

I added reviews #188 (review)

@jkolobok
Copy link
Collaborator

Any updates? Or the project can be considered dead?

@dozd
Copy link
Member

dozd commented Jun 24, 2018

No response from anyone else 👎, nor on your requested changes in the review. Not dead, but I cannot find spare time now.

@jkolobok
Copy link
Collaborator

I can verify and merge changes if you want. Everyone is doing it in their own repo and everyone gets out of sync (we are doing it in our own - https://github.com/KapitalTrading/xchange-stream). The project dies...

@dozd
Copy link
Member

dozd commented Jun 28, 2018

Sure you can, just mark the changes that are good to merge with positive review. That's all :-).

@badgerwithagun
Copy link
Collaborator

I've added reviews with suggested changes, but they're still marked as "awaiting review" (even though I've added a review) and there's been no follow-up from the contributors.

I'd just fix up the code and merge it if I could.

@dozd
Copy link
Member

dozd commented Jul 18, 2018

@badgerwithagun You could fix PR code by pushing to the PR repository and then marked the change as OK

@badgerwithagun
Copy link
Collaborator

@dozd I don't seem to have permission for that. I just tried to push a merge of develop into @bryantharris 's branch.

@dozd
Copy link
Member

dozd commented Sep 17, 2018

@badgerwithagun link to the PR you have tried to merge

@badgerwithagun
Copy link
Collaborator

#160. All I wanted to do was to merge develop into the PR's branch to resolve the conflicts.

@dozd
Copy link
Member

dozd commented Oct 8, 2018

#224

@dozd dozd closed this as completed Oct 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants