<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Promoting your project</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>Recent changes to Promoting your project</description><atom:link href="https://sourceforge.net/p/forge/documentation/Promoting%20your%20project/feed" rel="self"/><language>en</language><lastBuildDate>Fri, 06 May 2022 17:40:31 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/forge/documentation/Promoting%20your%20project/feed" rel="self" type="application/rss+xml"/><item><title>Promoting your project modified by SourceForge Support</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v7
+++ v8
@@ -1,16 +1,16 @@
 # Promoting your project #

-There are many different ways that you can promote your project, and this is by no means a comprehensive list.
+There are many different ways to promote your project, and this is by no means a comprehensive list.

 ## Project Summary Page ##

-Your project summary page is often the first impression that anyone has of your project, you should, at a minimum:
+Your project summary page is often the first impression anyone has of your project. You should, at a minimum:

-* Provide a **project summary statement**. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement. This is what we use when we tweet about your project.
+* Provide a **project summary statement**. State what your project is in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement. This is what we use when we tweet about your project.
 * Have an **icon**. A distinctive icon makes your project stand out in a list.
-* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your **project description**. This is what we use if we write a blog post about your project, or feature you on the [front page](http://sf.net/)
-* If appropriate, provide one or more **screenshots** showing off the more interesting parts of your product. People respond much more quickly to pictures than to text.
-* Write a bullet-list of main **features**. Highlight what makes you distinctive.
+* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your **project description**. 
+* If appropriate, provide one or more **screenshots** showing off the more exciting parts of your product. People respond much more quickly to pictures than to text.
+* Write a bullet list of main **features**. Highlight what makes you distinctive.
 * Release early, release often. **Frequent releases** state loudly that your project is alive.

 ## Project Blog ##
@@ -19,18 +19,14 @@

 ## Project Web Site ##

-Whether you host your project website on SourceForge or not, be sure to link to it from your project summary page.
+Whether you host your project website on SourceForge or not, link to it from your project summary page.

 ## Discussion Lists and Forums ##

-You need a place where users of your software can come talk. If you don't have a discussion forum, you are telling people that you're not interested in what they have to say, and they'll find another project that is. Discussion forums are a great place to figure out what your users want in the product, to find new developers who want to help you, and just to get a pat on the back for a job well done.
+It would help if you had a place where users of your software could talk. If you don't have a discussion forum, you are telling people that you're not interested in what they have to say, and they'll find another project that is. Discussion forums are a great place to figure out what your users want in the product, find new developers who want to help you, and get a pat on the back for a job well done.

 Open Source is about community. From good communities comes good code. Be sure to give your community a place to talk with one another.

-## SourceForge Blog, Podcasts, and Mailing Lists ##
+## SourceForge Help Wanted ##

-If you want to promote your project via any of the SourceForge communications - our [blog](http://sf.net/blog/), [podcasts](http://sf.net/blog/category/podcast), or our [monthly mailing](http://sourceforge.net/blog/newsletter-july-2012/) - just [tell us](mailto:communityteam@sourceforge.net). We're always looking for projects to write about, or interview, and who better to talk about it than you?
-
-Also, each month, our community mailing features projects that are looking for new developers, either to rejuvenate a project, or to fill specific gaps in the team. We'd love to feature your project there, too.
-
-Our podcasts are 10-20 minute conversations, conducted over Skype, about whatever you want to say about your project. We try to do one a week, but we depend on you to provide that content. Don't hesitate to contact us.
+If your project is looking for new developers, either to rejuvenate a project or fill specific gaps in the team. Visit our [help wanted forum](https://sourceforge.net/p/forge/helpwanted/) where you can find like-minded creators that are willing to help out with your project.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">SourceForge Support</dc:creator><pubDate>Fri, 06 May 2022 17:40:31 -0000</pubDate><guid>https://sourceforge.neta6214df2257a7b72f3ac60c03305fdde3131d64d</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;--- v6
+++ v7
@@ -29,6 +29,8 @@
 
 ## SourceForge Blog, Podcasts, and Mailing Lists ##
 
-If you want to promote your project via any of the SourceForge communications - our [blog](http://sf.net/blog/), [podcasts](http://sf.net/blog/category/podcast), or our [monthly mailing](http://sourceforge.net/blog/newsletter-july-2012/) - just [tell us](mailto:communityteam@sourceforge.net). We're always looking for projects to write about, or interview, and who better to talk about it than you.
+If you want to promote your project via any of the SourceForge communications - our [blog](http://sf.net/blog/), [podcasts](http://sf.net/blog/category/podcast), or our [monthly mailing](http://sourceforge.net/blog/newsletter-july-2012/) - just [tell us](mailto:communityteam@sourceforge.net). We're always looking for projects to write about, or interview, and who better to talk about it than you?
+
+Also, each month, our community mailing features projects that are looking for new developers, either to rejuvenate a project, or to fill specific gaps in the team. We'd love to feature your project there, too.
 
 Our podcasts are 10-20 minute conversations, conducted over Skype, about whatever you want to say about your project. We try to do one a week, but we depend on you to provide that content. Don't hesitate to contact us.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 06 Sep 2012 15:06:25 -0000</pubDate><guid>https://sourceforge.net278d91f252d63dc3889fe7029e01124d5a5de4dd</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;--- v5
+++ v6
@@ -6,12 +6,12 @@
 
 Your project summary page is often the first impression that anyone has of your project, you should, at a minimum:
 
-* Provide a *project summary statement*. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement. This is what we use when we tweet about your project.
-* Have an icon. A distinctive icon makes your project stand out in a list.
-* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your project description. This is what we use if we write a blog post about your project, or feature you on the [front page](http://sf.net/)
-* If appropriate, provide one or more screenshots showing off the more interesting parts of your product. People respond much more quickly to pictures than to text.
-* Write a bullet-list of main features. Highlight what makes you distinctive.
-* Release early, release often. Frequent releases state loudly that your project is alive.
+* Provide a **project summary statement**. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement. This is what we use when we tweet about your project.
+* Have an **icon**. A distinctive icon makes your project stand out in a list.
+* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your **project description**. This is what we use if we write a blog post about your project, or feature you on the [front page](http://sf.net/)
+* If appropriate, provide one or more **screenshots** showing off the more interesting parts of your product. People respond much more quickly to pictures than to text.
+* Write a bullet-list of main **features**. Highlight what makes you distinctive.
+* Release early, release often. **Frequent releases** state loudly that your project is alive.
 
 ## Project Blog ##
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 15:35:22 -0000</pubDate><guid>https://sourceforge.net4d8d2fa8ec8cb3b1280fbf2c2ef20de5116c7545</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 15:07:29 -0000</pubDate><guid>https://sourceforge.net66565a738a8ae4e9eaad390b7dfa1e042e07e929</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;--- v3
+++ v4
@@ -6,9 +6,9 @@
 
 Your project summary page is often the first impression that anyone has of your project, you should, at a minimum:
 
-* Provide a project summary statement. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement.
+* Provide a *project summary statement*. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement. This is what we use when we tweet about your project.
 * Have an icon. A distinctive icon makes your project stand out in a list.
-* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your project description.
+* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your project description. This is what we use if we write a blog post about your project, or feature you on the [front page](http://sf.net/)
 * If appropriate, provide one or more screenshots showing off the more interesting parts of your product. People respond much more quickly to pictures than to text.
 * Write a bullet-list of main features. Highlight what makes you distinctive.
 * Release early, release often. Frequent releases state loudly that your project is alive.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 15:07:29 -0000</pubDate><guid>https://sourceforge.net180ea5c904ee66fca4562cebde323f1944f6656d</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;--- v2
+++ v3
@@ -26,3 +26,9 @@
 You need a place where users of your software can come talk. If you don't have a discussion forum, you are telling people that you're not interested in what they have to say, and they'll find another project that is. Discussion forums are a great place to figure out what your users want in the product, to find new developers who want to help you, and just to get a pat on the back for a job well done.
 
 Open Source is about community. From good communities comes good code. Be sure to give your community a place to talk with one another.
+
+## SourceForge Blog, Podcasts, and Mailing Lists ##
+
+If you want to promote your project via any of the SourceForge communications - our [blog](http://sf.net/blog/), [podcasts](http://sf.net/blog/category/podcast), or our [monthly mailing](http://sourceforge.net/blog/newsletter-july-2012/) - just [tell us](mailto:communityteam@sourceforge.net). We're always looking for projects to write about, or interview, and who better to talk about it than you.
+
+Our podcasts are 10-20 minute conversations, conducted over Skype, about whatever you want to say about your project. We try to do one a week, but we depend on you to provide that content. Don't hesitate to contact us.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 14:56:07 -0000</pubDate><guid>https://sourceforge.net54e266fb5feacbf827ef80b2126a9a3027285490</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description>&lt;pre&gt;--- v1
+++ v2
@@ -6,10 +6,23 @@
 
 Your project summary page is often the first impression that anyone has of your project, you should, at a minimum:
 
-* Provide a project summary statement. State what your project is, in 70 characters or less.
+* Provide a project summary statement. State what your project is, in 70 characters or less. [See this blog post](http://sourceforge.net/blog/again-half-as-long/) for some tips on writing your summary statement.
 * Have an icon. A distinctive icon makes your project stand out in a list.
-* Describe in more detail what your project does.
-* If appropriate, provide one or more screenshots showing off the more interesting parts of your product.
-* Write a bullet-list of main features.
+* Describe in more detail what your project does. [See this blog post](http://sourceforge.net/blog/what-does-it-do/) for some tips on writing your project description.
+* If appropriate, provide one or more screenshots showing off the more interesting parts of your product. People respond much more quickly to pictures than to text.
+* Write a bullet-list of main features. Highlight what makes you distinctive.
 * Release early, release often. Frequent releases state loudly that your project is alive.
 
+## Project Blog ##
+
+SourceForge projects have the option of a blog. You may already have a blog for your project, but we encourage you to post to your project blog on SourceForge as well - particularly when you do a new release. This brings your release to the attention of the Community Team, which then triggers various promotion activities on our side, including mentioning you on Twitter.
+
+## Project Web Site ##
+
+Whether you host your project website on SourceForge or not, be sure to link to it from your project summary page.
+
+## Discussion Lists and Forums ##
+
+You need a place where users of your software can come talk. If you don't have a discussion forum, you are telling people that you're not interested in what they have to say, and they'll find another project that is. Discussion forums are a great place to figure out what your users want in the product, to find new developers who want to help you, and just to get a pat on the back for a job well done.
+
+Open Source is about community. From good communities comes good code. Be sure to give your community a place to talk with one another.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 14:52:36 -0000</pubDate><guid>https://sourceforge.netdfef9be6478925f63fd0d5efff38f113c4b41c50</guid></item><item><title>WikiPage Promoting your project modified by Rich Bowen</title><link>https://sourceforge.net/p/forge/documentation/Promoting%2520your%2520project/</link><description># Promoting your project #

There are many different ways that you can promote your project, and this is by no means a comprehensive list.

## Project Summary Page ##

Your project summary page is often the first impression that anyone has of your project, you should, at a minimum:

* Provide a project summary statement. State what your project is, in 70 characters or less.
* Have an icon. A distinctive icon makes your project stand out in a list.
* Describe in more detail what your project does.
* If appropriate, provide one or more screenshots showing off the more interesting parts of your product.
* Write a bullet-list of main features.
* Release early, release often. Frequent releases state loudly that your project is alive.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 26 Jul 2012 14:45:42 -0000</pubDate><guid>https://sourceforge.net56216553dca15a4c7111b9b39d3837f72e3172c6</guid></item></channel></rss>