bits.debian.org

When to submit a blog post

How to submit a blog post

Depending on blog post, you can drop a line on IRC or send and email to debian-publicity@ about it and ask people to write about it. Or you can write the post yourself. To write the post, just use markdown. There is a template at https://anonscm.debian.org/cgit/publicity/bits.git/plain/template.md and then submit it to the mailing list or contact the editors on IRC.

Posts ideas

Sprint report

When writing a post about a sprint, you should cover the following points:

Debian in the Field

Steps for anyone to write a Debian in the Field post:

  1. Find an amazing person or organisation using Debian in some form
  2. Find out what is special about it, a paragraph in general terms that someone outside of IT will understand, and with enough technical detail to fill another paragraph
  3. Get permission from the person or organisation to use this information publically.
  4. Get some gripping images to illustrate what is special about them.
  5. Get permission to use the images, see the licence.
  6. Include the disclaimer: This use in the field is shared to show Debian in use and does not express the view of nor is an endorsement from the Debian Project.

Blog categories

This is work in progress

* Category: general (this is the default one: bits.debian.org ) - bi-month post with new DDs and DM:

* Category: new packages [bits.debian.org/newpackages/ ] - weekly post every Monday

* Category: debaday [bits.debian.org/debaday/ ] - whenever a post is ready

* Category: dif (Debian in the field) [bits.debian.org/dif/ ] - whenever a post is ready

* Category: WDYD (What do you do) [bits.debian.org/wdyd/ ] - whenever a post is ready

* Category: debconf (bits.debian.org/debconf ) - for debconf posts is people doing debconf publicity want this

Ana's TODO for bits.debian.org

Things that ana plans to do:

* add categories: Post by default don't have a category, but some do and appear in the "subblogs", e.g.: http://bits.debian.org/dif/ for the debian in the field posts.

* add tag for translators identical to "authors", it will appear in the translated posts

* add feeds for translations

* workflow + documentation for translators

* Have translations line added in the RSS line (so they're visible from planet and RSS agregators)