Ben Novack

One downside of Discourse for this purpose is that it creates a topic for every single page it's embedded in; it seems reasonable to have a topic per project but...

What would you imagine if the maintainer has lost interest, never responds, etc? On Thu, Nov 5, 2015 at 9:24 PM, Chris Alfano [email protected] wrote: > ## @bennovack I really...

I don't know that I have a strong opinion about 1 vs 3, but I don't think an error message is appropriate: Friendly or not, the user did nothing wrong....

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...

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...

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...

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.

This would also set the stage for filtering projects out from default views that are "dead" in some respect (vaguely defined, never went anywhere, etc) but that we don't actually...

It doesn't render at all if the section has nothing at all in it. ie: foo {contentBlock "name"} causes a min-height contentBlock to render. {contentBlock "name"} nothing appears at all,...