Mark which GSoC students haven't updated their blogs in at least seven days

[asmeurer]

This is what Python does at http://soc.python.org/.

[certik]

Right. One way to implement this would be to hack planet-venus software to look at the feed, see when the last update was, and if it's older than 7 days, change the color of the name.

[asmeurer]

That site uses planet. I wonder if it is open source. I'll ask on the Python mentors list.

[asmeurer]

See http://mail.python.org/mailman/private/soc2011-mentors/2011-May/000051.html (must be subscribed to the Python mentors list to see it).

[asmeurer]

Quoting Arc Riley:

For now just set your planet's activity threshold to 7 days, anyone who hasn't blogged in that time will show red (or however your css is set) on the list.

Any idea how to do that?

[asmeurer]

Based on http://people.gnome.org/~jdub/bzr/planet/2.0/examples/fancy/config.ini, I think I know how to do it. Pull request forthcoming (it should be #3). I don't have planet installed, so you will have to test this to see if it works.

[asmeurer]

I guess GitHub does not number issues retroactively :-)

[asmeurer]

What version of Planet are you running on your server? Maybe try it in the dev branch. If that doesn't work, we should open a ticket with them.

[certik]

Yeah. I'll try once I have some free time. Note that anyone can try
this very easily, just checkout the repository and follow the readme.

Ondrej

On Thu, May 26, 2011 at 12:18 AM, asmeurer
[email protected]
wrote:

What version of Planet are you running on your server?  Maybe try it in the dev branch.  If that doesn't work, we should open a ticket with them.

Reply to this email directly or view it on GitHub:
#2 (comment)

[vperic]

Just a thought, should we remove this and/or lower the time limit? None of us are writing much outside the GSoC period and all the names being underlined with red looks a bit ugly. :)

[certik]

We should. Can you send a pull request?

[vperic]

What to do? Lower it to like.. 30 days? 90 days even? I'll try to do it tomorrow, when I get a chance.

[certik]

I would turn it off completely, until the next gsoc.

[asmeurer]

We can just leave it off forever. We need a better solution than this to manage GSoC blog posts (I never even used this).

[vperic]

To be fair, I've checked some other organisations and we wrote more
blog posts than most. Hardly one per week (I know I've personally
skipped quite a few weeks towards the end), but a bunch. I know eg.
some of the KDE students wrote just one or two posts for the whole
summer.

On Mon, Nov 21, 2011 at 9:38 PM, Aaron Meurer
[email protected]
wrote:

We can just leave it off forever.  We need a better solution than this to manage GSoC blog posts (I never even used this).

---

Reply to this email directly or view it on GitHub:
#2 (comment)

Vladimir Perić

[asmeurer]

Let's discuss this requirement next spring when we apply to Google. We talked about it a little at the mentor summit, but I want to see what the overall opinion of this is.