Closed hvgazula closed 1 year ago
To me it's part of the 247 team, not part of 247-main. I don't see the benefit of putting it there – it will just confuse for people looking for just 247 projects. If anything, there can be a podcast-main that can house both podcast-encoding and podcast-decoding.
sure, but that's not how I created the main repo and I don't think there will be any confusion with wiki and README.md being adopted now. Again, the goal is to keep the codebase consistent across both projects, and with the end of 247-encoding replication, I plan to bring everything under the same umbrella.
The code for podcast shouldn't need to change from now on. If we can use your new code to reanalyze podcast, that's great, but the code we used for podcast should be replicable as is. Also, you can still make them consistent without both being in 247-main. From an organizational perspective, I think it's clearer if there is a clear distinction without one needing to go to the README or wiki.
Okay, but it would be nice if I am aware of what's going on with repos I created. So, some heads-up will be helpful.
@zkokaja Let's revisit this conversation the next time we group.
Sure.
archived.
@zkokaja I think we should keep the podcast repos too in the 247-main project. The podcast is a subset of 247 and there are a lot of common functions between them. It will be helpful to maintain a minimal code base across all sub-projects. That way any inconsistencies in the pipelines can be address simultaneously.