laddr
laddr copied to clipboard
CodeForPhilly
Incorporate github commits into project pages
Many projects are worked on by people not attending hack nights, or don't get good updates written up. It would be great to leverage the github API to pull recent commit activity into project pages, both to provide information and to make it easier to tell that projects are live.
(Obviously this only applies to github-based projects, but the reality is that most are.)
I like this idea in theory but we need to flesh out what level of detail and how this fits in to the project page. My worry is that if we do the obvious thing and just put all the commits in the project activity stream they'll drown out the more human storytelling we want from updates/buzz/blogs. We discussed just pulling a last commit time metric, maybe we can show the last commit time somewhere, or a "latest commit" headline, or some kind of activity chart?
Entirely agreed about not wanting to drown out human updates. I'd suggest a "latest commit" at the top, possibly with the commit message, and that's all. I like the idea of an activity chart in theory but I'm not how to do one usefully for our type of project - even an active CfP project has a low commits-per-time rate compared to others. I think a chart might work best if it was also incorporating the other activity types like check-ins and updates, to reflect "project health" rather than codebase churn.
Further thoughts on implementation:
- Ideally all projects would include a CfP webhook and push update events to us. Easy for stuff in the CfP org.
- For projects that don't include the webhook, we'll have to periodically poll. Hourly?
Chiming in:
I would say publishing commit messages might be problematic. I know that many of our messages are nonsense sometimes or just "updates". The activity chart is a good idea though. Or perhaps just "Latest commit by [github user name] with a link to the commit"
On Wed, Aug 19, 2015 at 9:27 AM, Ben Novack [email protected] wrote:
Further thoughts on implementation:
- Ideally all projects would include a CfP webhook and push update events to us. Easy for stuff in the CfP org.
- For projects that don't include the webhook, we'll have to periodically poll. Hourly?
— Reply to this email directly or view it on GitHub https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132596530 .
100% agreed. Time of last push is fine; I'm really just looking for ways to track project activity/health when people don't always show up at hack nights, don't necessarily write blog posts, etc.
On Wed, Aug 19, 2015 at 11:04 AM, Corey Acri [email protected] wrote:
Chiming in:
I would say publishing commit messages might be problematic. I know that many of our messages are nonsense sometimes or just "updates". The activity chart is a good idea though. Or perhaps just "Latest commit by [github user name] with a link to the commit"
On Wed, Aug 19, 2015 at 9:27 AM, Ben Novack [email protected] wrote:
Further thoughts on implementation:
- Ideally all projects would include a CfP webhook and push update events to us. Easy for stuff in the CfP org.
- For projects that don't include the webhook, we'll have to periodically poll. Hourly?
— Reply to this email directly or view it on GitHub < https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132596530
.
— Reply to this email directly or view it on GitHub https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132631444 .
Yeah, I think it is a great idea for that reason.
On Wed, Aug 19, 2015 at 11:08 AM, Ben Novack [email protected] wrote:
100% agreed. Time of last push is fine; I'm really just looking for ways to track project activity/health when people don't always show up at hack nights, don't necessarily write blog posts, etc.
On Wed, Aug 19, 2015 at 11:04 AM, Corey Acri [email protected] wrote:
Chiming in:
I would say publishing commit messages might be problematic. I know that many of our messages are nonsense sometimes or just "updates". The activity chart is a good idea though. Or perhaps just "Latest commit by [github user name] with a link to the commit"
On Wed, Aug 19, 2015 at 9:27 AM, Ben Novack [email protected] wrote:
Further thoughts on implementation:
- Ideally all projects would include a CfP webhook and push update events to us. Easy for stuff in the CfP org.
- For projects that don't include the webhook, we'll have to periodically poll. Hourly?
— Reply to this email directly or view it on GitHub <
https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132596530
.
— Reply to this email directly or view it on GitHub < https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132631444
.
— Reply to this email directly or view it on GitHub https://github.com/CfABrigadePhiladelphia/laddr/issues/73#issuecomment-132633312 .
Further thought about github integration: Could use it to pull in issues too, so we can enrich product pages with them and help identify where work is needed.
It was also discussed in ticket #37 I also suggested adding Github login as option to login to Laddr
Worth checking "on-the-githubs": https://github.com/kvz/on-the-githubs
Demo: https://kvz.github.io/on-the-githubs/#repos/kvz/nsfailover
@schlos thanks for sharing! I really like the formatting they use, I think it would be good to replicate how they present the grouped timeline.
We have some initial GitHub integration in the code, at least enough to make API calls about particular projects, there's a demo of this capability on this page (only on cfp.org currently) http://codeforphilly.org/projects-activity
That screen is looking at slack messages and GitHub commits for each project