Thanks @hiimbex for organizing, and thanks @lee-dohm, @anglinb, @wilhelmklopp, @jbjonesjr, @gr2m for coming by!
Here are my notes from the discussion.
- Want to release "1.0" soon and do a little marketing push to try to raise awareness of all the awesome apps that have been built with Probot in the next couple weeks
- @gr2m: "just ship it" and don't worry about version numbers and marketing
- @hiimbex: now is good timing since we just finished changing terminology (plugin => apps) and website is in pretty good shape
- @bkeepers: Would like to get more apps listed on website
- Best ways to list/organize apps on website
- currently just ordered by stars. PR open to add # of installations, which is probably a better metric https://github.com/probot/probot.github.io/pull/18
- @gr2m: editorial to show diversity of types of apps
- @lee-dohm: look at how Electron lists apps (recently listed)
- Fetch app descriptions on website from repository README - https://github.com/probot/probot.github.io/issues/37
- _lots of discussion here that I didn't get good notes for_
- @anglinb: We can ask a fair bit from our submission guidelines because we are "making an app store"
- @anglinb: could load special file, like
LISTING.md, if it exists, and fall back to README if it doesn't. We could also manually open PRs to create this file.
- conclusion: just show readme for now
- @wilhelmklopp: What kind of apps should be listed on the website?
- @hiimbex: directions and criteria: https://github.com/probot/probot.github.io/blob/master/CONTRIBUTING.md#adding-your-app
- @bkeepers: I've debated a lot about this and don't feel settled on the right approach. Only listing "official" apps with an instance hosted by us would ensure high quality, but listing everything would give exposure to a lots of cool things people are building
- @anglinb: "Hosted by …" badge
- @anglinb: Would also be cool to to show other users who have this installed
- Roadmap: what do you think are things we should be focusing on?
- Onboarding
- redirect to issue/form on installation - https://github.com/probot/probot/issues/187
- Open PR with default config file
- Org-wide management
inherit_from: repo in .github/config.yml
- punt upstream to GitHub? Maybe, but probably shouldn't depend on changes to GitHub
- Persistence
- Streamline Hosting
- Error messages to users
- Health endpoint (shows error rates, uptime, etc like status.github.com)
- Require post-install
- Took an informal NPS survey ("Would you recommend the Probot Office Hours to a friend?"): 83%
Most helpful comment
Thanks @hiimbex for organizing, and thanks @lee-dohm, @anglinb, @wilhelmklopp, @jbjonesjr, @gr2m for coming by!
Here are my notes from the discussion.
LISTING.md, if it exists, and fall back toREADMEif it doesn't. We could also manually open PRs to create this file.inherit_from: repoin.github/config.yml