<div dir="ltr">As an example like the ones given above (Gnome, KDE, etc..), I would like to add symfony.<br><br>Their developpement politic is discutible, but their comunication with the comunity is just awesome :<br>see <a href="http://www.symfony-project.org/">http://www.symfony-project.org/</a> and <a href="http://www.symfony-project.org/blog">http://www.symfony-project.org/blog</a><br>
<br>Thomas<br><br><br><div class="gmail_quote">2008/10/7 Kostis Anagnostopoulos <span dir="ltr"><<a href="mailto:ankostis@gmail.com">ankostis@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Excellent and creative post Alex about the resposibilities of an Editor!<br>
<br>
Just a thought along your lines:<br>
<br>
- We do not need a PR Manager to *insualte* the community from the enginners.<br>
- We need an Editor to ease communications among those 2 groups.<br>
<font color="#888888"><br>
Kostis<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Mon 06 Oct 2008 11:11:20 Alex Osborne wrote:<br>
> Steve Mosher wrote:<br>
> > Question: what functions do you see a community<br>
> > manager performing. Write his job spec.<br>
><br>
> As I see it there's two main points that Risto and others have usually<br>
> brought up on this topic, communication and leadership.<br>
><br>
> Communication<br>
><br>
> This is the big point that everyone always mentions. You can't have<br>
> leadership without first a way to communicate effectively. In my<br>
> opinion, the wiki is being covered pretty well now and is becoming a<br>
> really good _reference_. So what is missing?<br>
><br>
> News! News! News! The engineering updates are excellent once you've<br>
> discovered them. The community updates by Steve leading up to the<br>
> release of the FreeRunner were also good. The planet, as several people<br>
> have mentioned is a mixed bag, now and then there's good blog posts by<br>
> various people but there's too much off topic or personal stuff that<br>
> shouldn't be there and it's in desperate need of a way to filter by<br>
> language. Sadsammy also pointed out in a reply to Risto's "Lost<br>
> Openmoko Community" blog post that these guys are doing fantastic job:<br>
><br>
> <a href="http://onlinedev.blogspot.com/search/label/openmoko" target="_blank">http://onlinedev.blogspot.com/search/label/openmoko</a><br>
><br>
> But they're not even in the planet! (I just filed a bug to<br>
> admin-trac). There's also not enough stuff from within Openmoko itself<br>
> in the planet, it should be a central place to look for news.<br>
><br>
> How is news handled elsewhere? For small specialised projects a mailing<br>
> list and the lead developer's blog is fine. But the Openmoko community<br>
> is extremely diverse covering lots and lots of different bases and is<br>
> rapidly growing in size. It's not just a single software package, heck<br>
> it's not even a single distro! So lets look to the big diverse<br>
> communities. For general Linux stuff there is the absolutely fantastic<br>
> Linux Weekly News [1]. In addition to that, virtually all the large<br>
> community-style projects have their own newsletters, either weekly,<br>
> bi-weekly or monthly: Debian [2], Gentoo [3], Ubuntu [4], Fedora [5],<br>
> Mozilla [6] and so on. GNOME [7] and KDE [8] have a continuous<br>
> planet-style news rather than a newsletter, but they are edited by real<br>
> humans and serve much the same purpose and have recurring feature articles.<br>
><br>
> Lets look at what they have in common:<br>
><br>
> * Visibility: If not directly on the front page, then a big fat link at<br>
> the start of the navbar "News". Not hidden away in some mailing list<br>
> (although usually mirrored or announced on lists).<br>
><br>
> * Well edited: Typically they have one *human* editor who puts<br>
> everything together in a consistent easy to read way and filters out the<br>
> rubbish.<br>
><br>
> * Sections: The details vary a bit between the projects but in some<br>
> form they usually have the following. Theses don't have to be<br>
> particularly long. A paragraph or two on each section would do.<br>
><br>
> - Table of contents with highlights of the most important stuff from<br>
> the other sections.<br>
><br>
> - "Corporate" news: What's happening in the core company (Mozilla),<br>
> council (Gentoo) or core developers (Linux kernel). These decisions<br>
> have been taken. This is the new policy for X. We're opening a new<br>
> t-shirt store. We're looking to hire a community manager and two kernel<br>
> hackers. We will be having an IRC or real-life meeting to discuss issue<br>
> X at this time and place. John Smith has moved to the Foobar team will<br>
> now be working on X. This should help a little to give a voice to the<br>
> company, what are its interests and where it is going.<br>
><br>
> - Special features: Two or three more in-depth articles on a<br>
> particular topic. This could be a review of a new program, discussion<br>
> on a debate about a particularly tricky technical problem or a round-up<br>
> from a recent conference or event with a few photos. It would be good<br>
> to have maybe one or two by the newsletter's editor and then some<br>
> good-quality articles by guest authors. If there's a good article on<br>
> some random person's blog, ask them whether you can include it.<br>
> Offering some incentives (merchandise, gear or even a small sum of money<br>
> like LWN) could help encourage people to submit good articles.<br>
><br>
> - Development news: Digest of the more interesting commits to the<br>
> repositories of core projects. Bug tracker statistics (list of fixed<br>
> bugs, how many news ones etc). LWN has the mailing list quote of the<br>
> week, which often mixes a few funnies (whatever creative way Linus has<br>
> told someone their code stinks this week) with rather interesting<br>
> mailing list threads worth reading.<br>
><br>
> - Software release notices: Generally submitted from the community,<br>
> but edited, or at least with a policy of how they should look to be<br>
> accepted. Kept short and to the point. One sentence description of<br>
> what the project is (maybe a little longer if its a new project), list<br>
> of big changes, link to the project's website or install instructions.<br>
><br>
> - Community events/announcements: OpenMoko community get-together<br>
> in Sydney. Upcoming mobile computing conference in Denmark. New users<br>
> group in Italy looking for members.<br>
><br>
> - Tips and tricks: This is not so general, but something I noticed<br>
> in Gentoo's newsletter and may be useful at this stage where we don't<br>
> have obvious GUI methods for doing everything. We get useful hints on<br>
> how to do stuff all the time in the mailing list. Just aggregate some<br>
> of the good ones with an attribution. This could also be a could<br>
> oppurtunity to add them to the wiki as well for later reference.<br>
><br>
> This might be completely different to what you were thinking, but in my<br>
> opinion we need more of an editor than a "manager".<br>
><br>
> Cheers,<br>
><br>
> Alex<br>
><br>
> [1] <a href="http://lwn.net/" target="_blank">http://lwn.net/</a><br>
> [2] <a href="http://www.debian.org/News/project/" target="_blank">http://www.debian.org/News/project/</a><br>
> [3] <a href="http://www.gentoo.org/news/en/gmn/" target="_blank">http://www.gentoo.org/news/en/gmn/</a><br>
> [4] <a href="https://wiki.ubuntu.com/UbuntuWeeklyNewsletter" target="_blank">https://wiki.ubuntu.com/UbuntuWeeklyNewsletter</a><br>
> [5] <a href="http://fedoraproject.org/wiki/FWN" target="_blank">http://fedoraproject.org/wiki/FWN</a><br>
> [6] <a href="http://developer.mozilla.org/devnews/" target="_blank">http://developer.mozilla.org/devnews/</a><br>
> [7] <a href="http://news.gnome.org/" target="_blank">http://news.gnome.org/</a><br>
> [8] <a href="http://dot.kde.org/" target="_blank">http://dot.kde.org/</a><br>
><br>
> _______________________________________________<br>
> Openmoko community mailing list<br>
> <a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
> <a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br></div>