Hi Ashutosh & co., We'd like to schedule the buildah article to publish but there are a few rough edges that need help: * The first section doesn't give enough introduction to buildah. The only thing a reader knows is they're not using a daemon. Why should they care about that? Feel free to get help from Tom or William to add some introduction. It doesn't need to be more than a short paragraph or two. But readers should understand why the Magazine is suggesting they use this utility. * The second section with the httpd use case works pretty well, but it's a good idea to start the section by introducing the example. * Don't use "we," "us," "I," or "me" in articles. The Magazine doesn't speak using the first person. You often don't even need to use "you," although that's fine if it makes text clearer. Paul On Tue, Apr 17, 2018 at 02:02:47PM +0530, Ashutosh Bhakare wrote: > Hello Tom, > Its up and runnig, I guess you need fedoramagazine login details for > this > > Regards > Ashutosh > On Mon, 2018-04-16 at 10:39 -0400, Tom Sweeney wrote: > > Hi Ashutosh, > > > > I tried pulling up the page via the link below, but it's returning a > > 404 > > error. Has it moved? > > > > t > > > > On 04/15/2018 02:09 PM, Ashutosh Bhakare wrote: > > > Hi Paul, > > > > > > Thanks for approving !! Its was great help by refering Tom's and > > > William blogs. Cheers :) > > > > > > I have drafted the article as below, please have a look and do > > > suggest > > > if any changes or editing required. > > > https://fedoramagazine.org/?p=20945&preview=true&preview_id=20945 > > > > > > I could see that builah, podman, skopeo are very vast tools, i have > > > wrrtten the draft considering "intermediate" level of audience on > > > buildah. If given a chance i would love to write a next level > > > article > > > on buildah which may cover a topic like "creating a image from > > > scratch" _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx
