Re: Systemd series -- need writers!

2015-10-19 Thread Jon Stanley 
On Mon, Oct 19, 2015 at 12:40 AM, Ryan Lerch  wrote:
> Someone must have already granted you access -- you are listed as an author,
> so you should be able to edit away!

Cool, thanks! Apparently that is now part 5. Can someone take a look
and make sure that I'm on the right track here? It's slightly more
than I thought that it would be, since I'm going into fairly
considerable detail. Some of it may be covered by other parts of the
series, and some may just be me pontificating on how great systemd is
:). I just want to make sure general style is OK before I flesh out
other parts of the article.
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: Systemd series -- need writers!

2015-10-19 Thread Paul W. Frields 
On Sat, Oct 17, 2015 at 07:58:29PM +0530, Ashutosh Bhakare wrote:
> Hello All
> 
> http://fedoramagazine.org/?p=10411&preview_id=10411
> 
> I have drafted the systemd article (part 6). Please suggest if any
> correction or additional points need to be covered in this article
> considering this as my first article :) 

Hi Ashutosh, thank you for drafting this article.  A couple points:

* We provided starter descriptions for each article in the "drafts"
  list.  For instance, this masking article has a starter here:
  

  It looks like you started a new post instead.  That's not a big
  problem by any means.  But in the future, pleased look for the
  original pitch or draft rather than starting a new article, since
  the URLs are often used in our meeting notes and we want them to be
  traceable over time.

* You don't need to worry about any banner graphic.  Our resident
  designer Ryan will be happy to provide one as part of our series.
  That way all the articles will have a similar look and feel to the
  graphic.

* Please flesh out the article with: introductory information about
  stopping a service, disabling a service, and the difference between
  those and masking.

* If you can, provide an example of *why* one would mask a service.
  If you don't know an example immediately, do some web searching to
  see if you can find a reliable use case that would serve well.  (In
  this case, remember not to copy text from other articles unless
  their licensing permits, and in that case observe any requirements
  for attribution.)

Also, this is not relevant to the Magazine, but when you respond to a
digest article, please trim it to the single post you're responding
to.  I invite you to read our mailing list guidelines, which will help
you make better use of it over time:

https://fedoraproject.org/wiki/Mailing_list_guidelines
(for instance, 
https://fedoraproject.org/wiki/Mailing_list_guidelines#Replying_to_Digests)

Also, I know you are on an APAC time zone, but feel free to contact us
on IRC in your early morning or later at night and we can help you in
real time.  This will also help avoid any confusion or wasted effort.
Thank you again and talk to you soon.

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

G11n Test Days post scheduled

2015-10-19 Thread Paul W. Frields 
I finished editing the G11n test days post, and I've set a featured
image and scheduled it for tomorrow morning (wee hours US-EDT, which
should be in afternoon/evening APAC time).

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: [Magazine] Closing comments on old articles?

2015-10-19 Thread Lord Drachenblut 
Is there any way to give authors of an article the choice for how long to
allow comments?

On Mon, Oct 19, 2015, 2:56 PM Gabriele Trombini 
wrote:

> Il giorno lun, 19/10/2015 alle 09.55 -0400, Paul W. Frields ha scritto:
> > On Fri, Oct 16, 2015 at 03:19:31PM -0400, Justin W. Flory wrote:
> > > On 10/16/2015 03:15 PM, Gabriele Trombini wrote:
> > > > Il giorno ven, 16/10/2015 alle 14.55 -0400, Paul W. Frields ha
> > > > scritto:
> > > > > How do folks feel about time-limiting open comments on
> > > > > articles?
> > > > > We often see comments coming in on old articles.  We can't
> > > > > reasonably expect authors to monitor these forever.  It seems
> > > > > to
> > > > > me like 30 days should be enough time to allow comments,
> > > > > considering the curve of hits we see on the articles.
> > > > >
> > > > > What do other folks think?
> > > >
> > > > good point, sometimes I'm really bored about seeing comments on
> > > > old
> > > > posts; but there are some evergeen post we should leave open (e.g
> > > > [1][2][3]) or open for a long time.
> > > >
> > > > IMO posts not related to the release or a specific version of
> > > > software
> > > > should be open for more than 30 days.
> >
> > How long?  90 days?  180?  Forever?
> > And what would you, as a commenter, a reader, or an editor, expect to
> > happen with the comments left after a certain period?
> >
> > > > Is there a way (e.c. categories) to handle these terms? Are we
> > > > able to
> > > > distinguish amongst posts? Also, are we able to remind to the
> > > > author
> > > > his post is going to be closed, so he can ask to leave open if he
> > > > considers that its cycle is not ended?
> > > >
> > > > [1]http://fedoramagazine.org/make-github-pages-blog-with-pelican/
> > > > [2]http://fedoramagazine.org/how_we_translate_fedora/
> > > > [3]http://fedoramagazine.org/use-fpaste-share-problem-reports/
> > > >
> > >
> > > I think having a category or some kind of tag to mark articles as
> > > time-sensitive is a good idea - I also think there are some
> > > articles that
> > > might be better for a longer commenting period and others that are
> > > useful
> > > only for a specific window of time (as mentioned with specific
> > > Fedora
> > > releases). I think this also depends on the author's activity with
> > > the
> > > magazine too.
> >
> > The built-in function in Wordpress is global.  Either comments are
> > open, disabled on articles after a certain time period, or closed.
> >
> > I found a plugin that accomplishes what we want on an individual post
> > basis:  https://wordpress.org/plugins/comment-expirator/
> >
> > We should probably test that elsewhere before trying on the site.
> >  The
> > plugin has a pretty low uptake, although it looks simple enough.
> >
> > --
> >
> I'm guessing about categorized  articles:
>
> A) general (like mine a couple of years ago [1], "how do you Fedora"
> series[2] or groups related [3] and similar [4]-> no closing terms;
>
> B) events (Fudcon, Flock and so on) -> closed when new events happen (a
> year?);
>
> C) election, meetings and so on - manually(?) closed when things are
> over;
>
> D) Fedora/n: -> automatically closed every new release;
>
> E) Software, hardware, howtos and so on: -> manually(?) closed when
> updated or rewrote;
>
> This is very hard to handle; it needs almost an admin manual check, so
> I think we should determine deadlines for each category we would
> maintain.
>
> On different perspective, I expect to happen:
>
> - as commenter: fill in a comment, waiting for author reply and going
> on if we might discuss; guessing how long it can last it's really hard.
> But probably those kind of comments become obsoletes when points D) and
> E) above happen.
> - as reader: the same of as commenter, difference is small. In this
> case I'm only following the discussion amongst other people.
> - as editor: I'm expecting a lot of people send me thanks for the
> article and I'd be really glad to start a discussion and if it's a
> generic article, seeing other's point of view and sometimes change my
> opinion or change people's opinion.
>
> Either fedmag is a resource to browse, study, read, deepen and view as
> a Fedora living historic memory or make it a sort of feed reader just
> setting up a cold expiration date everywhere.
>
> That's what I think.
>
> Thanks Gabri
>
>
> [1] http://fedoramagazine.org/we-are-everywhere-you-need/
> [2] http://fedoramagazine.org/major-hayden-how-do-you-fedora/
> [3] http://fedoramagazine.org/about-fedora-infrastructure/
> [4] http://fedoramagazine.org/join-fedora/
>
> >
> --
> marketing mailing list
> marketing@lists.fedoraproject.org
> List info or to change your subscription:
> https://admin.fedoraproject.org/mailman/listinfo/marketing

-- 

Cheers

Matthew "Lord Drachenblut" Williams
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: [Magazine] Closing comments on old articles?

2015-10-19 Thread Gabriele Trombini 
Il giorno lun, 19/10/2015 alle 09.55 -0400, Paul W. Frields ha scritto:
> On Fri, Oct 16, 2015 at 03:19:31PM -0400, Justin W. Flory wrote:
> > On 10/16/2015 03:15 PM, Gabriele Trombini wrote:
> > > Il giorno ven, 16/10/2015 alle 14.55 -0400, Paul W. Frields ha
> > > scritto:
> > > > How do folks feel about time-limiting open comments on
> > > > articles?
> > > > We often see comments coming in on old articles.  We can't
> > > > reasonably expect authors to monitor these forever.  It seems
> > > > to
> > > > me like 30 days should be enough time to allow comments,
> > > > considering the curve of hits we see on the articles.
> > > > 
> > > > What do other folks think?
> > > 
> > > good point, sometimes I'm really bored about seeing comments on
> > > old
> > > posts; but there are some evergeen post we should leave open (e.g
> > > [1][2][3]) or open for a long time.
> > > 
> > > IMO posts not related to the release or a specific version of
> > > software
> > > should be open for more than 30 days.
> 
> How long?  90 days?  180?  Forever?
> And what would you, as a commenter, a reader, or an editor, expect to
> happen with the comments left after a certain period?
> 
> > > Is there a way (e.c. categories) to handle these terms? Are we
> > > able to
> > > distinguish amongst posts? Also, are we able to remind to the
> > > author
> > > his post is going to be closed, so he can ask to leave open if he
> > > considers that its cycle is not ended?
> > > 
> > > [1]http://fedoramagazine.org/make-github-pages-blog-with-pelican/
> > > [2]http://fedoramagazine.org/how_we_translate_fedora/
> > > [3]http://fedoramagazine.org/use-fpaste-share-problem-reports/
> > > 
> > 
> > I think having a category or some kind of tag to mark articles as
> > time-sensitive is a good idea - I also think there are some
> > articles that
> > might be better for a longer commenting period and others that are
> > useful
> > only for a specific window of time (as mentioned with specific
> > Fedora
> > releases). I think this also depends on the author's activity with
> > the
> > magazine too.
> 
> The built-in function in Wordpress is global.  Either comments are
> open, disabled on articles after a certain time period, or closed.
> 
> I found a plugin that accomplishes what we want on an individual post
> basis:  https://wordpress.org/plugins/comment-expirator/
> 
> We should probably test that elsewhere before trying on the site. 
>  The
> plugin has a pretty low uptake, although it looks simple enough.
> 
> -- 
> 
I'm guessing about categorized  articles:

A) general (like mine a couple of years ago [1], "how do you Fedora"
series[2] or groups related [3] and similar [4]-> no closing terms;

B) events (Fudcon, Flock and so on) -> closed when new events happen (a
year?);

C) election, meetings and so on - manually(?) closed when things are
over;

D) Fedora/n: -> automatically closed every new release;

E) Software, hardware, howtos and so on: -> manually(?) closed when
updated or rewrote;

This is very hard to handle; it needs almost an admin manual check, so
I think we should determine deadlines for each category we would
maintain. 

On different perspective, I expect to happen:

- as commenter: fill in a comment, waiting for author reply and going
on if we might discuss; guessing how long it can last it's really hard.
But probably those kind of comments become obsoletes when points D) and
E) above happen.  
- as reader: the same of as commenter, difference is small. In this
case I'm only following the discussion amongst other people.
- as editor: I'm expecting a lot of people send me thanks for the
article and I'd be really glad to start a discussion and if it's a
generic article, seeing other's point of view and sometimes change my
opinion or change people's opinion. 

Either fedmag is a resource to browse, study, read, deepen and view as
a Fedora living historic memory or make it a sort of feed reader just
setting up a cold expiration date everywhere.

That's what I think.

Thanks Gabri


[1] http://fedoramagazine.org/we-are-everywhere-you-need/
[2] http://fedoramagazine.org/major-hayden-how-do-you-fedora/
[3] http://fedoramagazine.org/about-fedora-infrastructure/
[4] http://fedoramagazine.org/join-fedora/

> 
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: systemd series dates

2015-10-19 Thread Paul W. Frields 
On Mon, Oct 19, 2015 at 08:48:13AM -0400, Justin W. Flory wrote:
> Just noticed I was tagged for Article #7 for creating unit files - while I
> would love to have the opportunity to write the article, I don't think my
> technical experience with systemd is proficient enough to write the article.
> I believe I could probably better utilize my time working on other articles
> in areas I'm more comfortable with.
> 
> Would there be anyone else who has the time to write that article? If
> needed, I can spend the time to write the article and do a little homework,
> but if there's someone else who already knows enough to write the full
> article and has the time, I think that might be the better option.

My mistake Justin -- I thought I'd seen you put a hand up for this
one elsewhere.  Revised list:

Article (# - topic)   Author  Draft dueTo be 
published
  --  ---  
---
1 - Intro Ryan Lerch  (done)   
2015-Oct-21
2 - Unit filesBryan S 2015-Oct-21  
2015-Oct-28
3 - Unit dependencies and orderingBryan S 2015-Oct-28  
2015-Nov-04
4 - Using the journal Paul F  2015-Nov-04  
2015-Nov-11
5 - Converting SysVinit scripts   Jon S   2015-Nov-11  
2015-Nov-18
6 - Masking units Ashutosh B  2015-Nov-18  
2015-Nov-25
7 - Creating unit files   ?   2015-Nov-25  
2015-Dec-02
8 - Remote loggingPaul F  2015-Dec-02  
2015-Dec-09



-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: Magazine posts to G+ Page

2015-10-19 Thread Paul W. Frields 
On Mon, Oct 19, 2015 at 02:10:04PM +, Lord Drachenblut wrote:
> I've been going back on some of the magazine posts to the G+ page and
> adding to them when I can who the author was and linking to their g+
> profile and fedora wiki pages.
> 
> I think this helps give people more information about the article and gives
> credit to the authors.  I was hoping that this could be made to be a part
> of posting a magazine article instead of it being added after the fact.

I like this idea!  Thanks for doing this, Matthew.

Can I suggest building a wiki page that shows people how exactly to
post the right details per social media feed?  It wouldn't need to be
a very long page.  Examples showing how to make each post as effective
as possible would be helpful.  This way we can scale out a little more
effectively, with participants feeling like they are "doing it right."

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: [Magazine] Closing comments on old articles?

2015-10-19 Thread Paul W. Frields 
On Fri, Oct 16, 2015 at 05:41:08PM -0400, Joe Brockmeier wrote:
> On 10/16/2015 02:55 PM, Paul W. Frields wrote:
> > What do other folks think?
> 
> I think 30 days is a bit aggressive. There are also a number of articles
> where a reply after even a year might be useful (e.g. - an article about
> Technology Foo is high in Google Ranking and the piece is outdated and
> better information lives elsewhere now, thus a commenter wants to ensure
> other folks have some idea what is currently true).
> 
> No, I wouldn't expect a reply from an author a long time after a piece
> is published - but that doesn't *necessarily* mean comments will no
> longer have value.
> 
> Older pieces can be a major target for spam, so if this is something we
> need to do in order to retain sanity from moderating spam, then I'd be
> reluctantly +1.

Do you think 90 or 180 days (or some other number) is a more useful
window?  I think we should be open to alternatives -- including not
limiting at all.  I like the idea of doing this by category, so that
non-time limited articles wouldn't be closed as aggressively (or
ever?) compared to, say, specific release-related articles.

Perhaps a good solution might be:

* A shorter window for certain short-lifespan articles --
  e.g. security update for an app, likely subsumed or obsolete within
  a few months (maybe 90 days is as short as it should get?)

* A default window of some period, maybe 180 days

* An unlimited window for concept pieces that will apply for a long
  time (like our upcoming systemd series)

My concern is more about picking up random comments with little value,
as opposed to spam.  As Ryan pointed out elsewhere, we have fairly
decent (sometimes a tad aggressive) spam filtering in place.  There's
a constant pressure on any article comment section to serve as
substitute help forum, often for unrelated topics.  I doubt it does
readers good when we create an expectation their comments will be
answered over a very long span.

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Magazine posts to G+ Page

2015-10-19 Thread Lord Drachenblut 
I've been going back on some of the magazine posts to the G+ page and
adding to them when I can who the author was and linking to their g+
profile and fedora wiki pages.

I think this helps give people more information about the article and gives
credit to the authors.  I was hoping that this could be made to be a part
of posting a magazine article instead of it being added after the fact.

Cheers

Matthew Williams
-- 

Cheers

Matthew "Lord Drachenblut" Williams
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: [Magazine] Closing comments on old articles?

2015-10-19 Thread Paul W. Frields 
On Fri, Oct 16, 2015 at 03:19:31PM -0400, Justin W. Flory wrote:
> On 10/16/2015 03:15 PM, Gabriele Trombini wrote:
> >Il giorno ven, 16/10/2015 alle 14.55 -0400, Paul W. Frields ha scritto:
> >>How do folks feel about time-limiting open comments on articles?
> >>We often see comments coming in on old articles.  We can't
> >>reasonably expect authors to monitor these forever.  It seems to
> >>me like 30 days should be enough time to allow comments,
> >>considering the curve of hits we see on the articles.
> >>
> >>What do other folks think?
> >
> >good point, sometimes I'm really bored about seeing comments on old
> >posts; but there are some evergeen post we should leave open (e.g
> >[1][2][3]) or open for a long time.
> >
> >IMO posts not related to the release or a specific version of software
> >should be open for more than 30 days.

How long?  90 days?  180?  Forever?

And what would you, as a commenter, a reader, or an editor, expect to
happen with the comments left after a certain period?

> >Is there a way (e.c. categories) to handle these terms? Are we able to
> >distinguish amongst posts? Also, are we able to remind to the author
> >his post is going to be closed, so he can ask to leave open if he
> >considers that its cycle is not ended?
> >
> >[1]http://fedoramagazine.org/make-github-pages-blog-with-pelican/
> >[2]http://fedoramagazine.org/how_we_translate_fedora/
> >[3]http://fedoramagazine.org/use-fpaste-share-problem-reports/
> >
> 
> I think having a category or some kind of tag to mark articles as
> time-sensitive is a good idea - I also think there are some articles that
> might be better for a longer commenting period and others that are useful
> only for a specific window of time (as mentioned with specific Fedora
> releases). I think this also depends on the author's activity with the
> magazine too.

The built-in function in Wordpress is global.  Either comments are
open, disabled on articles after a certain time period, or closed.

I found a plugin that accomplishes what we want on an individual post
basis:  https://wordpress.org/plugins/comment-expirator/

We should probably test that elsewhere before trying on the site.  The
plugin has a pretty low uptake, although it looks simple enough.

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing

Re: systemd series dates

2015-10-19 Thread Justin W. Flory 
Just noticed I was tagged for Article #7 for creating unit files - while 
I would love to have the opportunity to write the article, I don't think 
my technical experience with systemd is proficient enough to write the 
article. I believe I could probably better utilize my time working on 
other articles in areas I'm more comfortable with.


Would there be anyone else who has the time to write that article? If 
needed, I can spend the time to write the article and do a little 
homework, but if there's someone else who already knows enough to write 
the full article and has the time, I think that might be the better option.


Thanks!


Cheers,


Justin W. Flory
jflo...@gmail.com

On 10/16/2015 03:42 PM, Paul W. Frields wrote:

Here is what I have right now for assignments for the Magazine's
systemd series.

* If any of these are wrong, just let us know obviously
* If you want to volunteer, please reply to the list
* If you have more ideas, please post them as pitches or ideas


Article (# - topic)   Author  Draft dueTo be 
published
  --  ---  
---
1 - Intro Ryan Lerch  (done)   
2015-Oct-21
2 - Unit filesBryan S 2015-Oct-21  
2015-Oct-28
3 - Unit dependencies and orderingBryan S 2015-Oct-28  
2015-Nov-04
4 - Using the journal Paul F  2015-Nov-04  
2015-Nov-11
5 - Converting SysVinit scripts   ?   2015-Nov-11  
2015-Nov-18
6 - Masking units ?   2015-Nov-18  
2015-Nov-25
7 - Creating unit files   Justin F2015-Nov-25  
2015-Dec-02
8 - Remote loggingPaul F  2015-Dec-02  
2015-Dec-09






signature.asc
Description: OpenPGP digital signature
-- 
marketing mailing list
marketing@lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing