OSDev.org

glauxosdev wrote:Maybe I will request a hosting server. The ideal solution would be chase to host it, though.

Or you could use GitHub, including GitHub pages. It's the most popular platform out there and you can easily host sites.

muazzam wrote:What about a traditional html/css/js/php site (written from scratch) instead of things like WordPress?

Why do you want a dynamic site? I don't see any need for non-static contents.

no92 wrote:

muazzam wrote:What about a traditional html/css/js/php site (written from scratch) instead of things like WordPress?

Why do you want a dynamic site? I don't see any need for non-static contents.

Dynamic site for comments, reviews and perhaps, contribution.

Contributing: GitHub repo
Reviews: osdev.org forums
Comments: Disqus (JavaScript-based, no PHP/ruby/etc. needed)

Do you still see any need for dynamic pages? That's why GitHub (Pages) is perfect for that purpose - there are no issues with dynamic sites. It's plain static.

no92 wrote: Comments: Disqus (JavaScript-based, no PHP/ruby/etc. needed)

I think, having your own software for that purpose would be better.

muazzam wrote:

no92 wrote: Comments: Disqus (JavaScript-based, no PHP/ruby/etc. needed)

I think, having your own software for that purpose would be better.

Why?

no92 wrote:Contributing: GitHub repo
Reviews: osdev.org forums
Comments: Disqus (JavaScript-based, no PHP/ruby/etc. needed)

Do you still see any need for dynamic pages? That's why GitHub (Pages) is perfect for that purpose - there are no issues with dynamic sites. It's plain static.

That would be a good setup. I would suggest the same.

Roman wrote:

muazzam wrote:

no92 wrote: Comments: Disqus (JavaScript-based, no PHP/ruby/etc. needed)

I think, having your own software for that purpose would be better.

Why?

I assume that people here are hobbyists. They're developing their "own" operating system, but Why? The reason to have your own website and the reason to have your own operating system, is same; for fun, and to have full control over system.

So? Why would we do the boring code monkey stuff when we could work on an OS?

muazzam wrote:I assume that people here are hobbyists. They're developing their "own" operating system, but Why? The reason to have your own website and the reason to have your own operating system, is same; for fun, and to have full control over system.

As someone who dealt a lot with Web App development, this is just complete bullshit. The negatives of having your own dynamic comment system outweigh any positives by far. For any PHP/Ruby/etc. hosting you have to pay. The load times are longer. Do you have any experience with designing secure applications (SQL-Injection protection, XSS protection, etc.)? It's a pain in the @$$. It's a big don't for me, especially when designing a site, that is, except for comments, entirely static.

To sum up, where will we host the final issue?

Regards,
glauxosdev

Your baby, your choice.

But I think that first you need to concentrate on getting quality material for the first issue. Worry about where to host it when you have something worth hosting.

Hi,

You are absolutely right, iansjack, but others pushed me to talk about hosting. Do you have any ideas for material? You, being experienced, could you tell me some ideas?

Regards,
glauxosdev

I'm afraid that I have no idea as to what would be suitable material for such a hypothetical magazine. I don't personally see it as a good format for hobby OS developers. I'd say that something along the lines of a Wiki and discussion forums was a more appropriate format as you are really dealing with long-term reference material (Wiki) and discussions, or questions, about particular aspects of the subject (forums).

But you must have had some ideas in mind when you came up with the idea of producing a magazine. Perhaps talk to those who have expressed an interest in the project and get them to contribute.

EDITED:
I suggest the following way of developing our osdev magazine using The Wiki:
Lets suppose we;re writing Issue <put a number here> of the magazine.
We want it to contain the following articles:

• X (an article present on the wiki)
• Y (an article not present on the wiki)
• Z (an article not present on the wiki)

We write article Y and article Z.
Then we create an article called "Issue <put a number here>" an put in a category with all the other issues.
In this article we write a short preamble, table of contents, an finally...
...we use the MediaWiki (as the OSDEV Wiki runs on MediaWiki) transclusion function to embed the contents of articles in this article (Yo Dawg )
This article is now the issue of our magazine.
Now we can use another MediaWiki feature called Collection Creator to Create PDF's, EPUB's, ODF's from it or even print it with pediapress.
Advantages:

• The Wiki is the central place for the OSDEV Community
• We avoid duplicates of Magazine Articles and Wiki articles as we don't copy&paste articles from the wiki, but embed|symlink them.
• Every issue adds new articles to the Wiki
• Everybody an account on a Wiki can contribute
• Basiclly everything

I worked for a small Magazine just for clients from a certain healthcare institute. So, here are my 2cents based on experience.

Don't do a monthly magazine. You're underestimating the effort in writing, editing and publishing. Articles from the wiki are nice but it won't be enough for something like a magazine. You'll quickly be looking at featured projects or interviews to fill the pages and make it worthwhile for people to read.

Every three or six months would be more feasible. It's also something you can't do alone. You'll need a team with each they're own speciality. We worked with a close team of four that put the magazine together and about six writers. It's not that all six wrote articles for every magazine that came out, it takes time to think of and write good articles. Sometimes they all had articles and we had to shelve some for a later edition. Because at other times, we had no articles coming in.

I think it's a wonderful idea if done right.... but to get from now to the first edition takes allot of planning and effort.

It might be easier to just write an OS