[kfalconer - Kyle Falconer (codeforsanjose)] @therebelrobot Hey Trent, I love that you guys are continuing to work on this. I’ve been hesitant to put effort towards making a brigadehub theme for Code For San Jose mostly because I’ve been concerned about API changes. I don’t want to spend a lot of time on something that may end up being obsolete in a month or two.
Would you say that the models and APIs are fairly stable, or stable enough to not be worried about this?
[brigadehub/core] Pull request submitted by jszwedko
This removes the public_repo scope which grants complete write access to a user's public repositories which has caused trepidation for new users. This scope is not needed for basic user authentication to the site.
Opening this in part for discussion as my familiarity with the code base is pretty limited. I'm an organizer of Code for San Francisco and had some, in my view founded, concern about granting write access to the users' repositories just to log into the site. I couldn't think offhand anywhere this scope might actually be required to utilize the functionality of brigadehub, but someone please correct me.
Still trying to build this locally, but I'll look for CI failures.
[chris - Chris Alfano (NAC) (cfa)] thanks oz!
As always, Code for Philly offers freely hosted Laddr instances for anyone looking for a dynamic platform for brigades. We're actively developing Laddr and just built a team for a major push into project lifecycle and member onboarding support