Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for contributors #78

Open
kniren opened this issue Jan 16, 2019 · 26 comments
Open

Looking for contributors #78

kniren opened this issue Jan 16, 2019 · 26 comments

Comments

@kniren
Copy link
Collaborator

kniren commented Jan 16, 2019

I have been neglecting this project for long enough. It is time to recognize that I don't have enough time to finish the original vision for Gota. This however does not mean that the project can't move forward!

If you are interested in taking the mantle feel free to contact me and we can either arrange the transfer of ownership or set up a working group (Assuming more than one individual wants to work on it).

During this time, some alternatives to Gota have surfaced:

[sbinet-gonum/exp]: Proposal to implement a DataFrame package integrated with gonum and backed by Apache Arrow.
[tobgu/qframe]: Immutable dataframes, mainly been driven by the requirements from qocache. Also seems to move towards an Apache Arrow implementation.

These proposals have their own merits, but do not fit with the vision of Gota as a dependency-free in-memory DataFrame wrangling package. In fact I believe we should remove all dependencies not on the standard library to make this library as lightweight as possible.

If you are interested, email would be the best way of reaching me, but I also will try to keep an eye out for replies on this issue.

@danicat
Copy link
Contributor

danicat commented Jan 24, 2019

Just to keep things documented, I've just sent you an e-mail offering my help. :)

@kyp0717
Copy link

kyp0717 commented Feb 15, 2019

Hello. I would like to contribute to this as well. Please let me know how I can reach you. Feel free to send me an email too. Thanks!

@kniren
Copy link
Collaborator Author

kniren commented Feb 15, 2019 via email

@kyp0717
Copy link

kyp0717 commented Feb 15, 2019

Hi Alex,
I have about 1 year experience in Go. However, I have been working in software engineering for over 15 years with focus on R, Python and SAS. In my spare time, I have been learning Haskell and Rust for the past few years.

I would like to get deeper into Go so that is why I decided to support this project. Let me start by looking at open issues to see what I can do. Also, I have started to review the source code.

As I get more into this project, it would be good to connect. In the mean time, I hope you enjoy your travels in Brazil.

Best,
Ky

@kniren
Copy link
Collaborator Author

kniren commented Feb 20, 2019 via email

@kyp0717
Copy link

kyp0717 commented Feb 22, 2019

Hi Alex,
I have started reviewing the PRs. A few PRs are simple basic changes that I think should be approved (like PR #51). Other PRs required more research on my part. I need to understand the code better and how to use the API better.

Also, is there a better way to communicate? Should we be using this thread to discuss PRs and related issues? Lastly, I am new to github change/pull request. I have only created and modified my own repo, not others.

Thanks,
Ky

@vikram-rawat
Copy link

I am willing to be a part of the team as well. I am a shiny developer and an R user for a long time. I have started learning golang 2 years ago and I understand it enough to get started. I would surely like to help. Please let me be a contributor as well.

@kniren
Copy link
Collaborator Author

kniren commented Sep 26, 2019

It seems that after the first round of collaborators came in, not a lot of progress has been made in this project. For this reason, I will pin this issue to try to get some more help from active contributors.

Please, do not misunderstand my intentions here @danicat, @kyp0717, @zeroviscosity, @Rpereira23. I appreciate the people that reached out to me in the first place, but it has been 6 months without PRs, merges, or simply answering issues. If you are still interested in collaborating, you are welcome to stay. Otherwise, I hope you understand the call for help.

@kniren kniren pinned this issue Sep 26, 2019
@kyp0717
Copy link

kyp0717 commented Oct 4, 2019 via email

@danicat
Copy link
Contributor

danicat commented Oct 4, 2019 via email

@mannharleen
Copy link

@kniren I would like to volunteer to invest some time on gota. I have been going through the source code in the past week and would find it really interesting to collaborate on. I will go through the open issues and help classify / attempt to address those. I have around 6 months of go experience and more than 10 years of dev experience in python, java, JavaScript.

@kniren
Copy link
Collaborator Author

kniren commented Jan 16, 2020

@mannharleen Great! Thank you very much. I'm back from vacation so I will try to go through some of the PRs that pop up during the weekend. I'll update you soon.

@mannharleen
Copy link

Welcome back!! I do see some PRs there. One of them is mine 😁.

@evanmcclure
Copy link

I'm learning ML and I'm interested in using Gota to explore my data. Count me in to help as a bug fixer/ committer.

@tbal999
Copy link

tbal999 commented Feb 23, 2020

I'm also interested! Great work by the way. This is a good project.

@prithvipal
Copy link
Contributor

I am interested.

@kniren
Copy link
Collaborator Author

kniren commented May 1, 2020

Hi, @prithvipal, @tbal999, @evanmcclure, @mannharleen,

A while back you expressed interest in becoming collaborators for the Gota project. Are you still up for it?

The easiest way to get started is to address old issues still lingering, triaging if they are worth pursuing or not, and closing old issues. Submitting PRs that address those issues (or reviewing existing ones) is another option for collaboration.

If you are still interested, please let me know (Or just try to do these things I've just suggested), and let's try to keep having a conversation about the process.

My time is currently very limited, so I only pop in Github every now and then, but if there is interest in keeping the project alive, I'll do my best to consider your input, suggestions, and PRs. What I really want is to pass the torch to a new team, but in doing so I want to make sure that the project is still going to be maintained. (Not that I'm doing much these days in terms of maintenance).

Let me know your thoughts on this.

Best,
Alex

@jfussion
Copy link
Contributor

jfussion commented May 4, 2020

Hi @kniren, Thank you for creating this project. I'm interested to contribute and I've created a PRs as a start.

@utkarshmalik211
Copy link

utkarshmalik211 commented May 23, 2020

Hi, this project has been a lifesaver for me as I used Pandas extensively in python. I’d like to contribute to this project.
I'd like to start with #92 @kniren Please tell if there are any new developments with this issue.

@andrewm4894
Copy link

dependency-free in-memory DataFrame wrangling package

Love this idea as is exactly the sort of approach i am looking into using this library for. Unfortunately i've just started learning Go but i do work at an open source company and we do have some Go dev's so i might try and see if i can maybe ask some of them to help me learn Go and maybe i can try and shape it as one or two contributions maybe as i see things i (and others) would need like a fill() method as an example.

I think it's a great library and will be important as more and more people move over from Python. Would love to learn enough Go myself over the next 6 months or so to be of some use.

@prithvipal
Copy link
Contributor

@kniren are you planning to use the go module in this repo?

@d3an
Copy link

d3an commented Jan 13, 2021

Hi @kniren,

I'm interested in being an active contributor for this repo. I'm currently using go-gota rather significantly in my other project finviz. I've been working with Go for nearly 2 years now, but have become rather fluent with all parts of the language (including concurrency, type assertions, more structured interfaces) in the last 6 months. Additionally, I've just started working as a full-time Go backend developer in Waterloo.

I have enough spare time to manage this repo, and would like to continue maintaining it and adding new features as is necessary. I'll do my best to start triaging existing issues/PRs to show my commitment, but I hope you'll pop back up on GitHub sometimes soon.

Best,
James

@kniren
Copy link
Collaborator Author

kniren commented Apr 18, 2021

Dear All,

I've included @chrmang in the maintainers team. He will work on addressing the current open PRs to try to get this project to an stable state again.

I'll also be removing the rest of the people in the maintainers team to try to start anew since there hasn't been much activity lately. If someone feels they want to be a part of it again, I'll be happy to include them back.

Best,
Alex

@danielpcox
Copy link

danielpcox commented Jun 26, 2021

Hey @kniren and @chrmang, I'm interested in contributing features that I miss from Pandas. My company (greymatter.io) contributes features to open source projects we use, and also has a monthly mini-hackathon thing, so I should have plenty of time for this if PRs are still welcome. We're using gota for service-mesh metrics crunching, so my first contribution attempt is concise vector arithmetic: #153

@chrmang
Copy link
Contributor

chrmang commented Jun 27, 2021

Hey @danielpcox ,

thank you for contribution. Unfortunately my spare time is limited these days, so I didn't had the time to review your PR. I created a Slack channel for easy communication.

@mickgardner
Copy link

I'd love to see a project like this mature and become comparable with something like Pandas.
In my day job I work as a project / program manager for software engineering projects, while my hobby is software development.
Is there anything I can help with to push the project along a bit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests