Whatever we decide, I'd like to thank and everyone who contributed to SwiftBar for building it. Agree some product ownership and decision making processes to ensure the project is able to continue to develop into the future (and more importantly, doesn't go stale!).Moving the repo is important so we get the GitHub redirection from the current repo Find a neutral org on GitHub and move the BitBar repo there (unfortunately bitbar is taken, but I'm sure we can find something that works).PR the SwiftBar code into the BitBar repo (Ideally we would keep the history of all contributors).Momentum (more and more people are still discovering BitBar every day).History and reputation (it's used by lots of people, and has been featured in a few places, like TechRadar and Mac Format magazine).Swift is accessible to many more developers too, including more junior devs who would be able to get involved (a point well made by A built-in plugin browser, which is a massive boost in UX, and opens the project up to non-techy users.This makes it much easier to contribute to, bug fix, and maintain. A fresh codebase written in a modern language □.I would like to propose that we take the best of both projects, and join forces. It isn't written in Objective-C for a start what's not to like? Over the years, the BitBar codebase became stale, difficult to maintain, impossible to build in some cases, and a frustration to many. SwiftBar is everything I dreamed BitBar could become.
0 Comments
Leave a Reply. |