[Foresight-distro] Re: [Foresight-devel] Re: Re: Re: Monthly News Release

[Ken VanDine]

The nice thing about using a blog engine for it is the rss feeds.  So
not only can we build the feed into liferea, but we can integrate
content from it into other places with rss.  We could perhaps have a
page on the site that pulls content from the rss.

--Ken

On 3/27/07, António Meireles <sbin at reboot.sh> wrote:
> Hi,
> food for though...
>
> a) Confluence (which will be upgraded and moved to a brand new box, like
> JIRA, later this week), is a good fit to this. It has a news module, and
> allows easely to track changes, manage content and has builtin i18n.
> IMHO, we don 't need a  full CMS  unless someone really assures full
> time maintenance of it.
> b) regarding the F newsletter we should have two core audiences - end
> users, namely switchers - either from closed OSs, either from second
> rate distros, and power users. Regarding tech savy users the goal should
> be seduced then enough to get them involved in the foresight, either in
> development, either in advocacy. The keyword should be 'community
> building'. We won't be to far off reality if we claim that we have one
> of most friendly online communities (of all distros) around. A monthly
> edition seems fair, while allowing extra editions, in between, if
> motives arouse. Also, we could time the newsletter, with monthly ISO
> respins of the install media.
> c) regarding the forums, i would consider merging them with the wiki (as
> soon as it gets moved and has a standalone IP (that will solve  the SSL
> issues)). This will allow for much more content reuse, and should be a
> bit more manageable.
>
> António, aka doniphon
>
>
> Thilo Pfennig wrote:
> > Ok giving you quick feedback.
> >
> > * I am for monthly because we can do this now without any headaches. Monthly
> > is better than nothing. And also better than if we try weekly and we fail.
> > We can make this more often if we feel that we can. Lets do it monthly at
> > least twice (now and in one month)
> >
> > * I just had the idea if we could combine this with something like release
> > notes. So if we post what is new and what has happened this could at least
> > help in writing release notes.
> >
> > 2. I need feedback on the wiki page to make sure we have agreement on the
> >
> >> topics.
> >>
> >
> >
> > I also think about what the focus should be. What the target users? I mean
> > dowe focus more on the technical terms or do we talk to the user. I would
> > like to consider the last. I like this one summarizing blog posts, irc and
> > mailing list discussions. it should contain recommendations to what the
> > normal user should do. I also would like to suggest that we add some tips &
> > tricks. Pointers to wiki pages, things to test out, especially GNOME stuff.
> >
> >
> > 3. Are we agreed on using a blog engine to post the content?
> >
> >
> > I like your initiative and have proposed such a thing in the past. But I
> > also like to habe a news channel that can be used to announce everything
> > immediately. Maybe we can import this blog in a new page in Drupal where we
> > collect some sources. Security 1)Announcements - 2)Newsletter - 3)Foresight
> > News.
> >
> >
> >
>
> _______________________________________________
> Foresight-devel mailing list
> Foresight-devel at lists.rpath.org
> http://lists.rpath.org/mailman/listinfo/foresight-devel
>