[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org
Great! I'm looking forward to the report. I have a Google Alert set up but that's going to be delayed by indexing (and is a little crude). I can tell you that we had nice write ups in Dutch and Catalan :) Amir On 11 Dec 2013, at 10:21, Lars Kurth <lars.kurth.xen@xxxxxxxxx> wrote: > Adding publicity > > > On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth <lars.kurth.xen@xxxxxxxxx> wrote: > Amir, > > seems we got quite good coverage indeed. I will send the media report to the > list (and to the Advisory Board). > > You and others may want to sign up to publicity@xxxxxxxxxxxxxxxxxxxx via > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use this > to coordinate blog posts, articles on Linux.com, LWN.net, ... , other PR, etc. > > It is also entirely acceptable to re-post the same content in several places. > Typically what you do is to change the title slightly for SEO reasons. For > example we frequently post some content on the xen blog first and then copy > to the wiki, or publish something on Linux.com and then repost on the blog. > > Regards > Lars > > > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry <amirmc@xxxxxxxxx> wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a > bunch of posts to describe the system and help people (and each-other) get to > grips with it. > > This will effectively form some of the documentation so it's more than just > blog posts and wiki pages -- getting this content in written form is > important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts > Anil/Dave think are needed and also some people who could write them. If > you're ok with the list please say so on the issue's comments. The idea is > that once we've agreed on *what* posts we need, we'll create a *separate* > issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip > and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@xxxxxxxxxxxxxxxxxxxx > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > Publicity mailing list > Publicity@xxxxxxxxxxxxxxxxxxxx > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |