jeanpimentel / github-summary Goto Github PK

I wanted to summarize and group these events to have a simple timeline and I decided to parse each event. But each event type has a different format and I had to parse each one to return a readable message.

I didn't build all types yet and sometimes we see a "notImplementedYet" message on timeline.

See: Event Types

@jeanpimentel What are your thoughts on using some Respect components?

With Rest instead of Silex for example, we could use the same controller/route as an HTML and a REST (api) route. This could be useful for us in many ways...

But I (and I belive @alganet too) don't really want to put something that sits in the way between you and the code. I think it is important for all of us to feel confortable with the code, I am confortable with the used components since I already used them for some things... =D

If you fork or watch some repository, by example "ios games", github should give you a sugestion of the the related repositories in the same tag, language or user. To do this, first will have to add tags on the repositories.

Think about it... =)

We could implement a "new" watch or something similar. I think of twitter as a great push notification system, some things I really would like to get a mention and see what's going on (this project for example).

How do you think this could work?

PS: @alganet has some work on Respect\Http that would make this very easy to do =D

This is a priority to me, maybe we should even play in ways to grouping this in other forms, but just this would already be awesome =D

What do you think?