Slackware on AWS EC2 - New how to on SlackDocs
 

Hi all,

It has been a week ago I have had published my first tutorial on The Slackware Documentation Project: Slackware on AWS EC2.

It's an attempt to fill in the gaps on the subject and to provide comprehensive, detailed documentation on how one can have a Slackware up and running at AWS EC2 cloud, starting from nothing.

I have made no AMI publicly available from the method of this how to I wrote neither I intent to. This should not be a problem at all, as it provides you with all the knowledge to create your own images, which is far more secure. Besides, anyone can create an AMI and just set it public.

This how to was published to SlackDocs and I made the announcement to the SlackDocs editors in the mailing list. Aside from some good criticism over the intro text (thanks Chris Abela), there aren't any other comment from editors. I suppose it's fine for a public announcement here.

Best,

I'll send the editor team a gentle reminder to evaluate your article as well as Didier's on internationalization.
Your articie is fine, and hopefully will benefit Slackers who want cloud presence.
After more in-depth review, your article will probably get a few updates (syntax/spelling), and I am still pondering a split into multiple articles, but the editor team has been very quiet indeed.

Eric, while you are at it could you please request a review of this one (also in French) as well. I'm sure there are remaining typos and room for enhancement.

Thanks in advance.

Hi Didier

I had sent a request to review your new article to the editor team two weeks ago. The lack of response to that, and to Deny's request, pissed me off so much that I sent the team a poll - who still feels involved as an editor and who needs to move to pasture.

Your article will get review.

I confess I've neglected my duties as an editor, and have resigned.

Dear Alien Bob, Didier Spaier, brianL et all,

With all my deepest respect to you, this topic is about Slackware on AWS EC2 and the process of building it up, make it work and so on as it was extensively described in the how to.

The comment I made in the first message about no replies from SlackDocs editors was to justify why I decided to announce it publicly here. There are no value judgments implied.

Could you please refrain to discuss SlackDocs internal affairs here and leave the topic for what it's intent for? There could be more appropriated channels for that SlackDocs matter elsewhere.

Thank you very much.

Best,