Spotify-downloader: Continue development in the spotify-downloader organization

[linusg]

What do you think about moving development to the spotify-downloader organization? As this project grows, it's becoming less of a personal one-man project but a community project with multiple maintainers, many many contributors... Plus, we could have related projects like the spotifube project in the same group.

@ritiek @vn-ki you should have invitations to join as owners :slightly_smiling_face:

[linusg]

Push...

[linusg]

Alright, ignorance seems to work very well. Nevermind.

[vn-ki]

Here's my take on this.

1. Revert write protection.
   Reply: I disagree. Everything should go through reviews and as PRs. That way it is easier to acknowledge and reference. I have already said this.

2. Continue development in a different org.
   Reply: I personally don't disagree with this, but we have respect the developer ego. Ritiek have been the lead dev in this project and it is (will be) his idea. Most of the code in here is written by him and I'm sure he cares for this as his child(hypothetically speaking). I DO NOT want to take that away from him. So, I don't have any opinions on this point (which is why I did not respond to this issue).

3. Ignorance
   Reply: "Alright, ignorance seems to work very well. Nevermind.". These are some harsh words, friend. I am pretty busy with SunPy and ritiek is busier with his work at PlasmaPy. You should understand his position. You are asking him to take an important decision on his most important project while having to deal with GSoC on the side. We have deadline to work against. I think this issue can wait.

Although I do understand your feelings. One of us should have replied. So here, this is my take.

[linusg]

1. Something I can perfectly live with. As you pointed out, (almost) every PR will be reviewed within a day or so.
   Topic is off the table for me, in a positive manner.

2. 100% agree with you on this one. I never intended (and never will, geez!) to take the project away from him, of course he is the primary person in this project. The contributors page speaks for itself!

3. My apologies, I didn't knew @ritiek is participating in GSoC, which is awesome! Now reading your reply I feel very sorry for putting pressure on you two; but as you said, nobody answering almost drove me crazy as we have usually pretty fast responses here, which lead me to the false assumption, that this "silence" was about my specific questions.
   Of course I understand you both focus on something else atm, every developer has both limited time and multiple projects he or she cares about.

So I'm waiting for Ritiek to find some time; he shall decide about building an GH organization. Offtopic: Sadly, Guido van Rossum retired from his position as BDFL, sometimes a single person speaking a final word can make things a lot easier for all participants.
All I want is having a good time and doing open source with you guys in a friendly atmosphere which I definitely didn't supported the past few weeks. Should have seen this way earlier, sorry about the trouble. Thanks @vn-ki, your response kind of changed my whole point of sight on the situation. Have a nice day, enjoy your work despite the deadline. :)

[linusg]

Damn it, there was a didn't missing. Added in bold to the previous post.

[sdhutchins]

I accepted your invitation @linusg. I can help however - finally, getting my nose out of some Bioinformatics projects.

[linusg]

Nice to hear @sdhutchins! For now, spotifube will just continue to live at linusg/spotifube, for obvious reasons.

To be honest, I will have to look about all the React code again, it's been quite some time... :wink:

[ritiek]

I sincerely apologize for the late reply @linusg. I ignored this thread for a while, I had no idea what I am supposed to be writing here. You've already taken the initial steps and created an organization but I am not really ready to move this project to an organization account, not at least for now. I don't have any solid points to stays as is or know of any solid points to move to an organization. I know I am acting a kind of dictator but this project is really personal to me and the first thing I wrote code for on GitHub, so I don't really like the idea of it not being close enough to me. I haven't had much experience dealing with organization accounts, so I don't make any quick decisions either.

Also, if you think about it, the codebase isn't still very beginner friendly, not many big contributors to the project, we have failing tests, inefficient ways for testing our code (I know this now, after working with PlasmaPy), way too much clutter in README, many unnecessary hash comments in the code, no docstrings, no clear road map set up and honestly I don't know how having a separate organizational account would help fix these issues and invite potential contributors. Yep, we could have both spotify-downloader and spotifube (and anything else we make related) in the same organization but is that really it? Even if we do move it to an organization account, we're the only major ones writing the code, which could happen either way.

Also, as @vn-ki said, we've been quite busy with our GSoC projects lately and I don't really get a decent amount of time to work productively on any other project. I fear I'll make mistakes in haste, so I haven't been bothering much with any other project I've been involved with lately except for PlasmaPy.

[linusg]

I am not really ready to move this project to an organization account, not at least for now.

Then I will of course accept your decision! The organization name will probably not go away, so it's up to you if you ever change your mind in the future :)

I know I am acting a kind of dictator but this project is really personal to me and the first thing I wrote code for on GitHub, so I don't really like the idea of it not being close enough to me.

I totally understand! I probably wouldn't feel the exact same way, as my first contribution on GH was not in a repository of mine, and my first own repository I didn't touch in two years or so... But that's perfectly fine, I get your point!
Nothing bad about (pseudo)dictatorship in software development, worked fine with CPython the last 25+ years. :wink:

Also, if you think about it, the codebase isn't still very beginner friendly, not many big contributors to the project, we have failing tests, inefficient ways for testing our code (I know this now, after working with PlasmaPy), way too much clutter in README, many unnecessary hash comments in the code, no docstrings, no clear road map set up and honestly I don't know how having a separate organizational account would help fix these issues and invite potential contributors.

Sounds like we got a mess to clean up :grin:
No, honestly I believe it's not that bad, but sure, we can improve here in many ways.

Also, as @vn-ki said, we've been quite busy with our GSoC projects lately and I don't really get a decent amount of time to work productively on any other project. I fear I'll make mistakes in haste, so I haven't been bothering much with any other project I've been involved with lately except for PlasmaPy.

Blame is on me, I honestly didn't knew that (we should probably make use of our Gitter group from time to time...). I just saw some activity of you, thinking you were probably not in vacation or similar (which would of course be an reasonable explanation for nobody answering in a long-ish time).

Guys, enjoy your GSoC work, and take your time! Sorry for all the trouble. I hope we can continue working together in a team once GSoC is over and you feel both ready to continue here.