Differences between revisions 1 and 2
Revision 1 as of 2008-04-08 14:56:41
Size: 2390
Comment:
Revision 2 as of 2008-04-08 20:44:45
Size: 3871
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
## [[TableOfContents(2)]] [[TableOfContents(2)]]
Line 15: Line 15:
== Send interesting news == = Send interesting news =
Line 24: Line 24:
=== What you should send ===

Generaly speaking: Everything which might have an noticable impact on
== What you should send ==
Generally speaking: Everything which might have an noticeable impact on
Line 32: Line 31:
   noticable impact (e.g. License Discussion, scheduled transition from    noticeable impact (e.g. License Discussion, scheduled transition from
Line 34: Line 33:
 * Smaller announcements from subprojects:  * Smaller announcements from sub projects:
Line 42: Line 41:
 * Debian related reviews / tests / articles in other media / websites / mailing lists / blogs  * You got interviewed about your work on Debian
* Debian related reviews / tests / articles in other media / web sites / mailing lists / blogs
Line 45: Line 45:
Things you don't need to report
 * Debian release -- we probably know it allready ;)
== Things you don't need to report ==
 * Debian release -- we probably know it already ;)
Line 50: Line 50:
websites, blogs and everything else. So it's very valuable to report web sites, blogs and everything else. So it's very valuable to report
Line 54: Line 54:
Keep in mind, that one of the main purpouse from our side beside keeping
our users informed is to show them that we are a living, working community!
That things are done, that Debian is alive!

= Help by native speakers =

Currently the main editor is not a native English speaker. He knows it, you
probably have noticed it, too. So one thin you can help as a native speaker
is to fix his en_DE to proper English. That's very easy; just look at
[:ProjecNews/Issues/Current: the current issue] and fix spelling mistakes
and the like.


= Becoming an editor yourself =

If feel you are capable of writing small articles for ProjectNews yourself,
feel free to join the team. We assume you have allready subscribed to the
debian-publicity mailing list at http://lists.debian.org/debian-publicity?

A good idea would be to subscribe to the wiki-Pages of the category
["CategoryProjectNews"].

Then you are ready to start: Take a look at the list, and if we got a proposal,
examine it -- or find something interesting yourself. Do you think it should be
added to the weekly news? Do you feel capable of summarizing it in a objective
way? Then do so! Just add your news to
[:ProjectNews/Issues/Current:the current Issue].

We put up some guidelines [:ProjectNews/Guidelines:here].

If you are unsure, if you got it written up properly, feel free to send your article
first to the publicity list.

[:DebianWiki/EditorGuide#translation:Translation(s)]: none

(!) [:/Discussion:Discussion]


This page explains HOWTO contribute to ProjectNews and what YOU can do to help it.

?TableOfContents(2)

HOWTO contribute

Contributing to ProjectNews is easy but depends on your skills and the amount of time you can spare.

Send interesting news

The easiest way to help us is to inform us about interesting things happening in the Debian universe. Debian is a quite big project, and we don't have the manpower to monitor every mailing list, blog, news site for content we might want to add to our ProjectNews. So tell us, if you noticed something interesting happening. You can usually to this by sending an E-Mail to debian-publicity@lists.debian.org.

What you should send

Generally speaking: Everything which might have an noticeable impact on the Debian Project at large and it's user base in special.

Some ideas:

  • Discussion taking place on a mailing list, which will have an
    • noticeable impact (e.g. License Discussion, scheduled transition from Project foo to Project bar, discussion about General Resolutions, etc.)
  • Smaller announcements from sub projects:
    • debian installer about to release beta3, testing requested
    • French debconf translations reach 100%
    • cdrkit capable of burning blue ray discs
    • ...
  • Interesting Bug Reports (ever looked at http://bugs.debian.org/245047?)

  • You represent Debian at a conference or exhibition (with a booth, talk, workshop, etc.)
    • You wrote an report after having represented Debian at a conference or exhibition
  • You got interviewed about your work on Debian
  • Debian related reviews / tests / articles in other media / web sites / mailing lists / blogs
  • ...

Things you don't need to report

  • Debian release -- we probably know it already ;)

Of course the above list is far from beeing complete. Especially we would like to point out, that the we can't monitore other media, web sites, blogs and everything else. So it's very valuable to report anything you think fitting to the ProjectNews to our mailing lists debian-publicity@lists.debian.org.

Keep in mind, that one of the main purpouse from our side beside keeping our users informed is to show them that we are a living, working community! That things are done, that Debian is alive!

Help by native speakers

Currently the main editor is not a native English speaker. He knows it, you probably have noticed it, too. So one thin you can help as a native speaker is to fix his en_DE to proper English. That's very easy; just look at [:ProjecNews/Issues/Current: the current issue] and fix spelling mistakes and the like.

Becoming an editor yourself

If feel you are capable of writing small articles for ProjectNews yourself, feel free to join the team. We assume you have allready subscribed to the debian-publicity mailing list at http://lists.debian.org/debian-publicity?

A good idea would be to subscribe to the wiki-Pages of the category ["CategoryProjectNews"].

Then you are ready to start: Take a look at the list, and if we got a proposal, examine it -- or find something interesting yourself. Do you think it should be added to the weekly news? Do you feel capable of summarizing it in a objective way? Then do so! Just add your news to [:ProjectNews/Issues/Current:the current Issue].

We put up some guidelines [:ProjectNews/Guidelines:here].

If you are unsure, if you got it written up properly, feel free to send your article first to the publicity list.


CategoryProjectNews