@dansup @freemo Dan, I know you're trying to get it perfect, but maybe you should push some non-federation-critical code so the testers have something to test and don't get... testy. :P
I'll also say that putting the time in to write any PRs right now is hit-or-miss because I feel like there's a good chance of duplicating or conflicting with something you already did but just haven't pushed yet...
🇳🇱
@trwnh @dansup I have to agree, keeping commits "secret" tends to be an open-source killer. branches are used to help keep it out of main code while still letting contributors work with (rather than against) the main contributor.
Sitting on the commits (for over a month now) tends to create a lot of fallout from OSS communities on projects where one person does most of the code.
Its your project of course, so do what makes you happy. But if the goal is to create contribution (and discourage forking) its usually a good idea to commit often.
@freemo @dansup One other thing to add that I think might be relevant: new features are nice and all, but there needs to be an MVP. If you keep adding new features and pushing release back month after month, then there's going to be too many changes at once, which makes it hard to test or to get feedback.