OSDev.org

Presuming we want to make a magazine, and presuming people are interrested in making a magazine, this thread is to give the attribution of the different roles of the creators of the magazine. The other thread is to talk about everything else about the magazine. This particular thread is only about giving attribution, what you want to do specifically in the magazine.
1.editor
2 writers
3 feedbacker
etc

I propose I be a writer for the magazine.
I can write about:
paging, scheduling, context switching, legacy macos, and various tidbits.
I can also write about other things but I don't see, for now what.
Do you accept my proposition?

Given that you're named after a very famous troll... perhaps you should find a new name first?

jerryleecooper wrote:I propose I be a writer for the magazine.

Everyone is a writer. All you have to do is submit your work.

Alboin wrote:

jerryleecooper wrote:I propose I be a writer for the magazine.

Everyone is a writer. All you have to do is submit your work.

True, a detail forgotten.
As for the name, I don't have an idea which name I can choose. jerryleecooper is correct on this board, but I don't think the real jerryleecooper, when he will stand up, will appreciate that someone else say that this or that operating system exist and doesnt need windows to run. You are right Brynet, I will change my name, but to what?

jerryleecooper wrote:You are right Brynet, I will change my name, but to what?

Is your own name currently broken or something?

As I previously said, I'll write when I have time. No guarantees though, I have a difficult math class to keep up with.
EDIT: If too many people want to do one thing, we may have to hold an election

-JL

piranha wrote:I have a difficult math class to keep up with.

An off topic word of advice: Something is only difficult if you say it is. If you say it's easy, then it is.

Why not have an online self-maintaining system. e.g. We write a document, submit a copy in PDF/PS/etc. There will have to be a consistency in style guideline that entries must follow.

At the end of the month, all those documents get appended to the end of each other, then an editor comes in, adds a page number to the bottom, writes up a table of contents, and makes a fancy cover page.

Of course, you can categorise the entries into sections in the magazine:
- Operating System Reviews (e.g. reviews of random hobby OSes from this site, larger OS's and/or commercial OS).
- Operating System Study Cases (talk about how something specific e.g. - Device Management in FreeBSD)
- Technology Reviews (e.g. EXT2 - theory on how it works, i-nodes, how to read, how to write, etc)
- Operating System Development (e.g. GUI theory)

1) It's not just OSDev. It's low level computer science.

2) PDFs are really hard to modify. If I was the editor, I'd rather have a word document than a PDF. It would also be almost impossible to get a consistent look across all document, unless everybody uses exactly the same LaTeX settings, or the exact same version of Word.

Have a look at XML based formats such as docbook. These are dead easy to write and can be converted into damn near anything, and extremely smartly, via XSLT templates.

I propose to be art and sometimes a writer.

I've never done a mag so I don't know how great my art will be I'll think on this.

Hi ,

May i propose plain text files ... because they can be redily viewed without any externel viewer .... My opnion probly baised coz first tutorials
i read were text files and i have developed an attachment to them ...
I would like to contribute as a writer ... but the problem is time .....
So much to learn .... so much to prepare .... I have to finish my main project before the deadline ... so that i can pass my btech exam and join my job as a developer .....

Regards
Sandeep Mathew

I think we've decided on HTML as the intermediate format.

There's too many threads that are overlapping!

Im writing my current article in Word, will copypaste in notepad, do some basic formating for html and it will be what it will be. no html tag, no body tag, no css, and no jabascript of course.