Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] thumbsup emoji
    Sameroom
    @sameroom-bot
    [brigadehub-twitter]
    https://twitter.com/citizen_labs/status/872113012144046080
    Thanks to the great work of the @brigadehub team! https://twitter.com/brigadehub/status/859452963013525504
    BrigadeHub extends a warm welcome to @citizen_labs and @CodeForOrlando for joining our ragtag team of beta users! https://brigadehub.github.io/
    Sameroom
    @sameroom-bot
    [brigadehub-github]
    [brigadehub/theme-public-c4sf] Pull request submitted by BasSondag
    brigadehub/theme-public-c4sf#44
    the event description shows the HTML tags. I changed p=event.discription to p!=event.discription to fix this
    Sameroom
    @sameroom-bot

    [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?

    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] @kfalconer Hey Kyle, unfortunately I haven’t had much time to devote to brigadehub the past month or two, work’s picking up and i’m getting ready to move to Hayward. Because of that, the API hasn’t changed drastically since maybe december. That being said, it is still in beta, and i was hoping to move from jade/pug to react or maybe next.js, which would drastically change the theme landscape. While you’re more than welcome to deploy it as is right now, i’m really wanting to get a larger refactor in place before this hits stable v1 (though right now I think that’s a long ways off until things settle down a bit)
    Sameroom
    @sameroom-bot
    [mdupont - Michael duPont (codefororlando)] @kfalconer We use CSS overwrites in the admin portal so we could still customize it without having to make a new theme while the project is still in beta. Works well for us
    [mdupont - Michael duPont (codefororlando)] codefororlando.com
    [mdupont - Michael duPont (codefororlando)] http://www.codefororlando.com
    Sameroom
    @sameroom-bot

    [brigadehub-github]
    [brigadehub/core] Pull request submitted by jszwedko
    brigadehub/core#38
    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.

    Sameroom
    @sameroom-bot
    [brigadehub-github]
    [brigadehub/core] Pull request closed: brigadehub/core#38 by therebelrobot
    Sameroom
    @sameroom-bot
    [kfalconer - Kyle Falconer (codeforsanjose)] One of the things we’d like to have is to create an additional (custom) page, and the only way I can think to do this is with a theme
    @kfalconer We use CSS overwrites in the admin portal so we could still customize it without having to make a new theme while the project is still in beta. Works well for us
    Sameroom
    @sameroom-bot
    [Jesse Szwedko, sfbrigade] thumbsup emoji we are also interested in that so I'd be curious to see how you implement it
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] @kfalconer @jszwedko this was the next piece on my todo list before work started picking up hella about a month ago. I’ve got a few ideas on how it’d work, most likely similar to how the blog pages are being generated (stored and rendered from markdown), but I honestly haven’t had the time personally nor the development team to keep the roadmap moving as steadily as I’d like as of late. Once I have a bit more time I can circle back on it, I just can’t say when that’ll be.
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] Update: As I've got some downtime this week as I'm transitioning to another job, I'll be working on modernizing the brigadehub codebase, working primarily in the next repo. I'll update here as I have more to show, but hopefully I'll be able to get a good chunk of the work done this week to make the entire experience much more developer and user friendly.
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] Highlights of the upcoming updates: moving to a simpler codebase structure (goodbye multiple repos), and a much better client experience (specifically SSR React using Next.js). Also looking into a database restructure/migration into postgres for a less bandaid-like structure for the data being stored. Also played with the idea of using SQLite instead of mongo/postgres since most installations don't need to scale/shard databases, and having a separate db service is more overhead for most brigade administrators, but I'm still looking into the feasibility of all that. Stay tuned!
    [chris - Chris Alfano (NAC) (cfa)] @therebelrobot I'd love to work with you on seeing what it's like to deploy brigadehub with habitat as you move to a single repo, imagine being able to deploy to containers, VMs, and bare metal with ANY base on and NEVER having environmental or upstream package version issues
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] From the habitat website at least, I'm pretty interested in this, defs gonna take a look at it. I was planning on keeping deployment the same for the time being since there's quite a bit of codebase change needed, but if you'd like to take a look at that in tandem with the work I'm pushing for the code update, you're more than welcome to ^_^ I appreciate the interest!
    [Oz Haven, sfbrigade] My main focus right now is to keep the onboarding for developers, redeployers, brigade admins, and brigade members as low friction as possible, and habitat for sure looks like it may make deployments / redeployments a lot easier.
    Sameroom
    @sameroom-bot
    [chris - Chris Alfano (NAC) (cfa)] it does, I've been hacking with and contributing to it a ton lately
    [chris - Chris Alfano (NAC) (cfa)] the best part is it lets you KNOW what features you can rely on in service deps
    [chris - Chris Alfano (NAC) (cfa)] no wondering what version of postgres or node will be around on someone's machine
    [chris - Chris Alfano (NAC) (cfa)] if brigadehub likes postgres 9.6.3, it's always going to have postgres 9.6.3
    [chris - Chris Alfano (NAC) (cfa)] it is a good idea to remove an active DB as a dep though, you're right that most brigade sites will never need to support the volume. It's one of the advantages in a lot of civic apps thanks to our local nature...internet scale is never really a requirement
    [chris - Chris Alfano (NAC) (cfa)] i want to move laddr to a git-based DB eventually :-X
    [chris - Chris Alfano (NAC) (cfa)] how beautiful it will be to clone a DB to a test site, branch it, etc
    Sameroom
    @sameroom-bot
    [slackline] @mjturtora connected codefortampabay to #brigadehub
    Sameroom
    @sameroom-bot
    [vivek - Vivek Bansal (codeforsanjose)] Yo are we doing something wrong with the meetup integration
    Sameroom
    @sameroom-bot
    [Mike Turtora, sfbrigade] Thinking about a Florida Day of Civic Hacking. Just got the word that Miami is rescheduling and here in Tampa we are as well.
    Sameroom
    @sameroom-bot
    [carlvlewis - Carl V. Lewis (cfa)] @mjturtora We're rescheduling here in Savannah too
    [Mike Turtora, sfbrigade] So, FL/GA Day of Civic Hacking? AND I SURE HOPE THAT'S THE END OF IT!
    Sameroom
    @sameroom-bot
    [carlvlewis - Carl V. Lewis (cfa)] switching themes to "controlling the spread of disinformation in emergency situations."
    [carlvlewis - Carl V. Lewis (cfa)] *misinformation
    [carlvlewis - Carl V. Lewis (cfa)] not disinformation
    [Mike Turtora, sfbrigade] hey that sounds like a really good topic! keep in touch.
    Sameroom
    @sameroom-bot
    [vivek - Vivek Bansal (codeforsanjose)] @hassan
    Sameroom
    @sameroom-bot
    [brigadehub-github]
    [brigadehub/brigadehub.github.io] Pull request submitted by therebelrobot
    brigadehub/brigadehub.github.io#2
    [brigadehub-github]
    [brigadehub/brigadehub.github.io] Pull request closed: brigadehub/brigadehub.github.io#2 by therebelrobot
    [Oz Haven, sfbrigade] Hello team. I've posted an important update regarding Brigadehub on the main site: https://brigadehub.github.io/
    [Oz Haven, sfbrigade] long story short, I'm retiring BrigadeHub as an active project. I go into more detail on the post at the site above, so feel free to check that out, and reach out to me over DM if you have any questions or concerns. All the best!
    Sameroom
    @sameroom-bot
    [luigi - Luigi Ray-Montanez (cfa)] Thanks for all your hard work on it Oz!

    [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

    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] ^ this, for sure. I've also linked to Laddr in the post above (just to the repo, not sure if you have a landing page, @chris)
    Sameroom
    @sameroom-bot
    [chris - Chris Alfano (NAC) (cfa)] We don't have a landing page, we should up our presence as a project and offerings of hosting
    [chris - Chris Alfano (NAC) (cfa)] Repo is best for now
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] thumbsup emoji
    [Oz Haven, sfbrigade] I'll keep these channels connects for a little while for visibility purposes, but in a week or two I'll be disconnecting the cross-team slack channels and gitter/irc bridge. If you need to get a hold of me for any reason, I'm available on twitter at (https://twitter.com/therebelrobot), and email: (github@therebelrobot.com)
    [Oz Haven, sfbrigade] *connected
    Sameroom
    @sameroom-bot
    [Oz Haven, sfbrigade] Again, for those just coming into this channel, Brigadehub is being retired as an active project. If you or your team would like to pick it up for continued development, feel free to reach out to me, otherwise I suggest moving to a more widely-supported platform like Laddr or another more general-purpose CMS like Squarespace or Wordpress. Feel free to reach out to me if you have any questions or concerns.
    [Oz Haven, sfbrigade] Thank you all for the support you've shown me and my various team members over the past couple years, it's been a pleasure getting to know each of you. I'll be working in a limited capacity on a subsection of the brigadehub featureset, namely the decentralized project data api, but that's still in it's research phases and will be a while before anything of note is available. Let me know if you have any interest in contributing to that.