Hi everyone,
I've got a first draft up for part 1 of the Backing up series. Please read, follow and give me feedback. There are definitely areas that can be improved.
Also, I don't want to publish until all three articles are done. I need to make sure that parts two and three (duply and deja-dup, respectively) will work seamlessly with the backup created in part one. This may mean significant edits to this part one.
Please provide feedback!
https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880
~link
On Tue, Jun 27, 2017 at 10:40:11PM -0700, Link Dupont wrote:
Hi everyone,
I've got a first draft up for part 1 of the Backing up series. Please read, follow and give me feedback. There are definitely areas that can be improved.
Also, I don't want to publish until all three articles are done. I need to make sure that parts two and three (duply and deja-dup, respectively) will work seamlessly with the backup created in part one. This may mean significant edits to this part one.
Please provide feedback!
https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880
The coverage of this article is absolutely spot-on. It's easy to follow and gives clear directions.
I recommend you make a pass over it, though, and try to shorten and simplify sentences. A good rule of thumb is to minimize the use of the verb "to be," along with gerunds ("-ing" words). For example:
FROM: "Backups are only as good as how often they are run. Backups need to be scheduled and run regularly in order to keep adding new data and pruning off old data."
TO: "Backups only help if you run them often. Schedule and run them regularly to keep adding new data and prune off old data."
This might seem nitpicky, but writing becomes stronger when you make sentences short, and use a declarative or commanding tone. Don't labor over it too long though! ;-) Do what you can and I'll be glad to help tune it later.
On Mon, 2017-07-03 at 14:47 -0400, Paul W. Frields wrote:
On Tue, Jun 27, 2017 at 10:40:11PM -0700, Link Dupont wrote:
Hi everyone,
I've got a first draft up for part 1 of the Backing up series. Please read, follow and give me feedback. There are definitely areas that can be improved.
Also, I don't want to publish until all three articles are done. I need to make sure that parts two and three (duply and deja-dup, respectively) will work seamlessly with the backup created in part one. This may mean significant edits to this part one.
Please provide feedback!
https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880
The coverage of this article is absolutely spot-on. It's easy to follow and gives clear directions.
I recommend you make a pass over it, though, and try to shorten and simplify sentences. A good rule of thumb is to minimize the use of the verb "to be," along with gerunds ("-ing" words). For example:
FROM: "Backups are only as good as how often they are run. Backups need to be scheduled and run regularly in order to keep adding new data and pruning off old data."
TO: "Backups only help if you run them often. Schedule and run them regularly to keep adding new data and prune off old data."
This might seem nitpicky, but writing becomes stronger when you make sentences short, and use a declarative or commanding tone. Don't labor over it too long though! ;-) Do what you can and I'll be glad to help tune it later.
-- Paul W. Frields http://paul.frields.or g/ 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 _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Oh, I was about to edit this but I now get a 404 error on the link.
On Tue, Jul 4, 2017 at 1:09 PM, Link Dupont link@sub-pop.net wrote:
On Mon, 2017-07-03 at 14:47 -0400, Paul W. Frields wrote:
On Tue, Jun 27, 2017 at 10:40:11PM -0700, Link Dupont wrote:
Hi everyone,
I've got a first draft up for part 1 of the Backing up series. Please read, follow and give me feedback. There are definitely areas that can be improved.
Also, I don't want to publish until all three articles are done. I need to make sure that parts two and three (duply and deja-dup, respectively) will work seamlessly with the backup created in part one. This may mean significant edits to this part one.
Please provide feedback!
https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880
The coverage of this article is absolutely spot-on. It's easy to follow and gives clear directions.
I recommend you make a pass over it, though, and try to shorten and simplify sentences. A good rule of thumb is to minimize the use of the verb "to be," along with gerunds ("-ing" words). For example:
FROM: "Backups are only as good as how often they are run. Backups need to be scheduled and run regularly in order to keep adding new data and pruning off old data."
TO: "Backups only help if you run them often. Schedule and run them regularly to keep adding new data and prune off old data."
This might seem nitpicky, but writing becomes stronger when you make sentences short, and use a declarative or commanding tone. Don't labor over it too long though! ;-) Do what you can and I'll be glad to help tune it later.
-- Paul W. Frields http://paul.frields.or g/ 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 _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in. _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org
Those preview links expire after 24 hours IIRC.
Link, I don't necessarily think you need to restructure. More info is better when it comes to these articles. I like the ones that don't assume too much knowledge on the part of the user.
Paul
On Tue, Jul 4, 2017 at 3:39 AM, Stuart Brady sbrady1215@gmail.com wrote:
Oh, I was about to edit this but I now get a 404 error on the link.
On Tue, Jul 4, 2017 at 1:09 PM, Link Dupont link@sub-pop.net wrote:
On Mon, 2017-07-03 at 14:47 -0400, Paul W. Frields wrote:
On Tue, Jun 27, 2017 at 10:40:11PM -0700, Link Dupont wrote:
Hi everyone,
I've got a first draft up for part 1 of the Backing up series. Please read, follow and give me feedback. There are definitely areas that can be improved.
Also, I don't want to publish until all three articles are done. I need to make sure that parts two and three (duply and deja-dup, respectively) will work seamlessly with the backup created in part one. This may mean significant edits to this part one.
Please provide feedback!
https://fedoramagazine.org/?p=17880&preview=true&preview_id=17880
The coverage of this article is absolutely spot-on. It's easy to follow and gives clear directions.
I recommend you make a pass over it, though, and try to shorten and simplify sentences. A good rule of thumb is to minimize the use of the verb "to be," along with gerunds ("-ing" words). For example:
FROM: "Backups are only as good as how often they are run. Backups need to be scheduled and run regularly in order to keep adding new data and pruning off old data."
TO: "Backups only help if you run them often. Schedule and run them regularly to keep adding new data and prune off old data."
This might seem nitpicky, but writing becomes stronger when you make sentences short, and use a declarative or commanding tone. Don't labor over it too long though! ;-) Do what you can and I'll be glad to help tune it later.
-- Paul W. Frields http://paul.frields.or g/ 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 _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in. _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e67b
…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e67b…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link
On Thu, 2017-07-06 at 16:13 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e67b…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject. or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
I finished up Part 1 and Part 2. I'd greatly appreciate an editorial eye; I made a number of changes late tonight, and I know my error count goes up significantly the later in the evening I write.
Also I'd like it if someone could follow the steps to make sure I didn't make any assumptions about software on my system.
~link
New preview links (I hope).
Part 1: https://fedoramagazine.org/?p=17880&preview=1&_ppp=8de1fb8558 Part 2: https://fedoramagazine.org/?p=17929&preview=1&_ppp=3115e531ea
On Thu, 2017-07-06 at 23:03 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 16:13 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e67b…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraprojec t. or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject. or g
I finished up Part 1 and Part 2. I'd greatly appreciate an editorial eye; I made a number of changes late tonight, and I know my error count goes up significantly the later in the evening I write.
Also I'd like it if someone could follow the steps to make sure I didn't make any assumptions about software on my system.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Hello Link,
I checked the first article for readability (I'm sorry but I don't have time to do any more today). I made a few suggestions in the Google Doc below. Please understand these are only suggestions.
Oh, and this is a more general thing, are we cool with using Google Docs? TBH it's my go to when I'm editing stuff as Libre is significantly inferior and I couldn't find anything else on Gnome Software.
Here is the link:
https://docs.google.com/document/d/1UK7V3cgPsl3wvJlZb3ObrKIs8Mwzqspl-QY aW5G9ovg/edit?usp=sharing
Regards,
Stuart Brady
On Thu, 2017-07-06 at 23:07 -0700, Link Dupont wrote:
New preview links (I hope).
Part 1: https://fedoramagazine.org/?p=17880&preview=1&_ppp=8de1fb8558 Part 2: https://fedoramagazine.org/?p=17929&preview=1&_ppp=3115e531ea
On Thu, 2017-07-06 at 23:03 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 16:13 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e6 7b
…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject.or g To unsubscribe send an email to magazine-leave@lists.fedoraproj ec t. or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraprojec t. or g
I finished up Part 1 and Part 2. I'd greatly appreciate an editorial eye; I made a number of changes late tonight, and I know my error count goes up significantly the later in the evening I write.
Also I'd like it if someone could follow the steps to make sure I didn't make any assumptions about software on my system.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject. or g
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.or g
Cool. I like a few of those edits, but it appears I can't edit the article anymore after moving it to Pending Review. One of the editors will have to pick it up, I suppose.
We can definitely move the gpg --list-keys line to a <pre> block so the double-dashes are move obvious.
On Sat, 2017-07-08 at 09:13 +0900, sbrady1215@gmail.com wrote:
Hello Link,
I checked the first article for readability (I'm sorry but I don't have time to do any more today). I made a few suggestions in the Google Doc below. Please understand these are only suggestions.
Oh, and this is a more general thing, are we cool with using Google Docs? TBH it's my go to when I'm editing stuff as Libre is significantly inferior and I couldn't find anything else on Gnome Software.
Here is the link:
https://docs.google.com/document/d/1UK7V3cgPsl3wvJlZb3ObrKIs8Mwzqspl- QY aW5G9ovg/edit?usp=sharing
Regards,
Stuart Brady
On Thu, 2017-07-06 at 23:07 -0700, Link Dupont wrote:
New preview links (I hope).
Part 1: https://fedoramagazine.org/?p=17880&preview=1&_ppp=8de1fb85 58 Part 2: https://fedoramagazine.org/?p=17929&preview=1&_ppp=3115e531 ea
On Thu, 2017-07-06 at 23:03 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 16:13 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote:
Perfect feedback. I'll give that a pass. Do you think there's too much time spent on setting up AWS? I was thinking about a slight restructuring of the article to focus more on duplicity, and leave most of the AWS stuff up to the user. Basically writing the article assuming that the user has their AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY already and just telling them to plug them in.
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e6 7b
…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject. or g To unsubscribe send an email to magazine-leave@lists.fedorapr oj ec t. or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.or g To unsubscribe send an email to magazine-leave@lists.fedoraproj ec t. or g
I finished up Part 1 and Part 2. I'd greatly appreciate an editorial eye; I made a number of changes late tonight, and I know my error count goes up significantly the later in the evening I write.
Also I'd like it if someone could follow the steps to make sure I didn't make any assumptions about software on my system.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraprojec t. or g
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject. or g
Thanks for the reply Link. Regards the gpg, I had to go through all those articles you linked to - haha!
Anyway, I really enjoyed reading your work and I'm actually quite envious of your knowledge and ability to explain quite a lengthy and involved process.
All the best with the finished piece,
Stuart On Sat, Jul 8, 2017 at 10:31, Link Dupont link@sub-pop.net wrote:
Cool. I like a few of those edits, but it appears I can't edit the article anymore after moving it to Pending Review. One of the editors will have to pick it up, I suppose.
We can definitely move the gpg --list-keys line to a <pre> block so the double-dashes are move obvious.
On Sat, 2017-07-08 at 09:13 +0900, sbrady1215@gmail.com wrote:
Hello Link,
I checked the first article for readability (I'm sorry but I don't have time to do any more today). I made a few suggestions in the Google Doc below. Please understand these are only suggestions.
Oh, and this is a more general thing, are we cool with using Google Docs? TBH it's my go to when I'm editing stuff as Libre is significantly inferior and I couldn't find anything else on Gnome Software.
Here is the link:
https://docs.google.com/document/d/1UK7V3cgPsl3wvJlZb3ObrKIs8Mwzqspl- QY aW5G9ovg/edit?usp=sharing
Regards,
Stuart Brady
On Thu, 2017-07-06 at 23:07 -0700, Link Dupont wrote:
New preview links (I hope).
Part 1: https://fedoramagazine.org/?p=17880&preview=1&_ppp=8de1fb85 58 Part 2: https://fedoramagazine.org/?p=17929&preview=1&_ppp=3115e531 ea
On Thu, 2017-07-06 at 23:03 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 16:13 -0700, Link Dupont wrote:
On Thu, 2017-07-06 at 21:39 +0000, Justin W. Flory wrote:
On 07/03/2017 11:09 PM, Link Dupont wrote: > Perfect feedback. I'll give that a pass. Do you think > there's > too > much > time spent on setting up AWS? I was thinking about a slight > restructuring of the article to focus more on duplicity, > and > leave > most > of the AWS stuff up to the user. Basically writing the > article > assuming > that the user has their AWS_ACCESS_KEY_ID and > AWS_SECRET_ACCESS_KEY > already and just telling them to plug them in. >
Hey Link,
This came up during the meeting today. We remembered that you wanted to wait until all three articles in the series were complete before you published them. However, in the release upgrade article…
https://fedoramagazine.org/?p=17971&preview=1&_ppp=0dcd79e6 7b
…we briefly mention about taking backups, and point to a PkgDB link for deja-dup. What do you think about publishing the first one on Monday, and then cross-linking this in the upgrade instruction article? This might help give the series a long shelf-life since the upgrade article gets a lot of traffic for a couple months after an upgrade (so ideally, people might discover the whole backup series by looking up instructions on how to upgrade).
However, we wanted to check with you if you want to do this first. We could always go back later and edit the link to your series once all the drafts are up. What do you think?
Fedora Magazine mailing list -- magazine@lists.fedoraproject. or g To unsubscribe send an email to magazine-leave@lists.fedorapr oj ec t. or g
Echoing what I said in #fedora-magazine. It looks like part 3 (deja- dup) *won't* build (technically) on top of part 1 (duplicity) like I originally thought. Part 2 (duply) can definitely build on top of part 1 though. So I'd like to have part 1 and 2 finalized before publishing so that the full backup created in part 1 is detected by duply in part 2.
Both articles do exist in draft form. I'm currently editing the commands in part 2 to make sure the output is correct, and the duply profile detects the full backup created with duplicity. Both articles are mostly complete. Once I've given them another pass over to make sure the commands are correct, they'll still need an editorial review. If someone can possibly edit them over the weekend, then we could probably publish part 1 on Monday.
They both articles also will need feature images. I had hoped to try one on my own, but maybe Ryan should crank out one for Part 1 so it's ready for publishing on Monday.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.or g To unsubscribe send an email to magazine-leave@lists.fedoraproj ec t. or g
I finished up Part 1 and Part 2. I'd greatly appreciate an editorial eye; I made a number of changes late tonight, and I know my error count goes up significantly the later in the evening I write.
Also I'd like it if someone could follow the steps to make sure I didn't make any assumptions about software on my system.
~link _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraprojec t. or g
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject. or g_______________________________________________
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@lists.fedoraproject.org
magazine@lists.fedoraproject.org
-
Justin W. Flory -
Link Dupont -
Paul Frields -
Paul W. Frields
-
sbrady1215＠gmail.com -
Stuart Brady