Activity Feed

[andrzejkrzywda]

Once we allow submitting new projects or issues and once people profiles will be somewhat public, we can implement a basic activity feed - what has happened.

This might be a nice educational issue to work on. There is a number of different implementation strategies possible here:

• use some gems for that
• built on our own with some after-callbacks
• make it a read model, separate view component which gets populated after some other places publish events like JuniorProfilePublished or ProjectRegistered or PullRequestAccepted.

I'd go for the event-driven implementation, but this may be too hard for the beginning to many people. So for now, I'm assuming that any implementation is fine.

[n-gb]

Reference for future implementers of this issue: here is the link to pretty detailed tutorial to public_activity gem, which can be used to make Activity Feed.

@andrzejkrzywda I agree that event-driven implementation will be too complicated. Maybe it would be easier if this task was divided into a greater number of smaller tasks, so if you'd like to have this strategy specifically - please consider making them :)

[n-gb]

@andrzejkrzywda I'm also curious about PullRequestAccepted event - what do you mean by that?

[oxanayoxana]

@andrzejkrzywda have you seen Nadia’s comments?😇

[andrzejkrzywda]

For the first implementation let's go with some gem, as a start and we will see how it goes. public_activity might be a good try. Let's postpone the event-driven ideas for later.