Get rid of multiple unrelated repositories and merge issues

[pfurini]

Hi @jshrt , I'm looking at this library because I'm a follower of the SAM channel (https://gitter.im/jdubray/sam), but as I said in the channel I've found two unrelated repos (not in fork relation) of SAMx.
This one, and this: https://github.com/invisible-tech/samx
In addition, this repo is a fork of https://github.com/samxsm/samx, so one would think that the base repo is the official one, and that the issues and feature requests should live there. But for what I've seen, the base repo has zero issues, while this fork has a few (in fact I'm writing one more here)..

It is confusing, especially because each repo contain different issues, and pull requests. A potential contributor (or user alike) should have a single "source of truth" where looking for issues to fix, or features to contribute.

Can you consider choosing one of the repos (maybe the best candidate is https://github.com/samxsm/samx) and make it the official one, maybe copying the other's issues into it?
Then you could delete the other (https://github.com/invisible-tech/samx), or make it private, just to avoid confusion.

If you don't have the time to copy the issues, just let me know what do you want ported, and I'll do it for you.

Thx!
Paolo

[derrandz]

Hi @pfurini

Thank you a lot for taking the time to contribute this feedback and for showing interest in the repo.

So initially, I've worked on this repo me and Leonardo Kewitz when I was working with Invisible technologies, and now that I have switched to expertlead, we wanted to use SAMx in here too. Thus my desire to centralize SAMx in samxsm/samx

Unfortunately I do not have a say anymore on what happens on invisible-tech, and I kindly requested the guys to fork out of the main repo like we just did in Expertlead, however apparently they are not able to do so just yet.

So to answer your question, the samxsm organisation is the main support behind samx for now, and I am looking to make it official, so if you can help moving the issues to the main repo, that will be great.

Would you be interested in joining the github organisation so that you can help manage the repo?

Thank you

[derrandz]

Hey guys! @gunar @kewitz

Including you in the thread as to get your opinion and consent, hopefully for us to join efforts and centralize our work in one main repo.

[pfurini]

So initially, I've worked on this repo me and Leonardo Kewitz when I was working with Invisible technologies, and now that I have switched to expertlead, we wanted to use SAMx in here too. Thus my desire to centralize SAMx in samxsm/samx

I see.. thank you for the clarification, now it makes more sense!

So to answer your question, the samxsm organisation is the main support behind samx for now, and I am looking to make it official, so if you can help moving the issues to the main repo, that will be great.

What about the issues on invisible-tech/samx? Do you think they should be merged with the ones on this repo and re-created on samxsm/samx?

Would you be interested in joining the github organisation so that you can help manage the repo?

Sure, I can try to do something in my spare time.. I'm also going to review the code and try to use it in TypeScript, adding proper typings to the APIs. Or at least this is my goal, I hope to find enough time to do it in a timely manner ;)

Bye
P.

[derrandz]

Hi @pfurini

Awesome, I think merging the issues from both repos makes sense, and if you are looking to dive into code, I am about to write a roadmap for the repo this week, and perhaps we can sync and have a call on how to do it.

What is your preferred way of communication?

Best

[pfurini]

Awesome, I think merging the issues from both repos makes sense

Good, then we can proceed with that and leave this issue open for tracking the activity.

What is your preferred way of communication?

@jshrt I left you a PM on Gitter..

P.