Skip to content
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
Manish Goregaokar edited this page Nov 30, 2015 · 3 revisions

Instructions for adding a new TWiS blog post:

Generally, you want to add a draft to _drafts, and the actual post to _posts. Ideally we should publish on tuesdays, after the meeting.

Firstly, name the file with the date, eg 2015-03-17-twis-28.md.

Give it a header, like the one below (Generally it's easier to just copy an old one):

---
layout:     post
title:      This Week In Servo 28
date:       2015-04-02 20:30:00
summary:    What's up with Servo for the week of 12 - 19 March 2015
categories:
---

A standard post has an intro section (no header), and then the "Notable Additions", "New Contributors", "Meeting", and sometimes "Screenshots" sections

In the intro section it's good to mention any major news about Servo. I try to start it off with the number of PRs merged. I find this out via git log --since="Tue Feb 3 22:45:35 IST 2015" | grep "Auto merge" | wc -l, where the since is the commit date of the last TWiS post (be sure to copy the whole date from git log, including the timezone -- some of us live in the future and you might end up missing a day).

For the notable contributions, I scroll through Pulse and the list of recently closed PRs. Note that bors sometimes closes PRs instead of letting them get marked as merged, so Pulse will miss these altogether.

For new contributors, I use (adjusted for the date of the last twis):

git log --since="Thu Mar 12 01:01:01 IST 2015" | grep "Auto merge" | grep -v "\(jdm\/\|Ms2ger\/\|servo\/servo\|glennw\/\|metajack\/\|larsbergstrom\/\|Manishearth\/\|mbrubeck\/\|pcwalton\/\|kmcallister\/\|saneyuki\/\|nnethercote\/\|Adenilson\/\|frewsxcv\/\|ChrisParis\)"

followed by going through the list of usernames, making sure that none have already been mentioned in a TWiS (grep -r username in the blog repo), and checking that this is their first contribution (git log | grep -C 5 username on Servo master).

A faster method is this one (slightly better script), but note that new users who have had their PRs merged this week with commits from a previous week won't be listed.

For the meeting section, just drop a link to the minutes and a couple of points on what was discussed.

Clone this wiki locally