should we create an OS development magazine?
- Steve the Pirate
- Member
- Posts: 152
- Joined: Fri Dec 15, 2006 7:01 am
- Location: Brisbane, Australia
- Contact:
Because a wiki is completely different from a magazine. They require completely different styles of writing - factual and concise vs. creative.tsp wrote:I haven't followed this topic very closely but instead of own magazine or blog why don't you just use your work effort to update the OSDev wiki to contain the material you have in your mind?
Hi,
I would really like to have a magazine, it's just nicer and if you print it out you have something to read when you are offline. But maybe for coordinating it is a good idea to use an IRC channel or a mailing list.
Is there anyone responsible for the magazine or how should we organize? I really get interested in this thing with time
Are there any articles in for the first issue yet? If not I'd just start with my article about VFS.
I would really like to have a magazine, it's just nicer and if you print it out you have something to read when you are offline. But maybe for coordinating it is a good idea to use an IRC channel or a mailing list.
Is there anyone responsible for the magazine or how should we organize? I really get interested in this thing with time
Are there any articles in for the first issue yet? If not I'd just start with my article about VFS.
- Steve the Pirate
- Member
- Posts: 152
- Joined: Fri Dec 15, 2006 7:01 am
- Location: Brisbane, Australia
- Contact:
http://system-call.org/issues/2008-01.pdf
Thanks to all involved. Sorry for the epic lateness.
Edit: Fanfare? What's that?
Thanks to all involved. Sorry for the epic lateness.
Edit: Fanfare? What's that?
great read.
just a few gramatical errors;
in Compiler Defined: "Most of the compiler convert.." should be "compilers"
in the last column of the first page of Memory Managment: Disgress should be Digress.
thats all I could find through one pass.
I really liked the compiler article, i look forward to the other parts.
just a few gramatical errors;
in Compiler Defined: "Most of the compiler convert.." should be "compilers"
in the last column of the first page of Memory Managment: Disgress should be Digress.
thats all I could find through one pass.
I really liked the compiler article, i look forward to the other parts.
Website: https://joscor.com
- Brynet-Inc
- Member
- Posts: 2426
- Joined: Tue Oct 17, 2006 9:29 pm
- Libera.chat IRC: brynet
- Location: Canada
- Contact:
First let me say congratulations for a successful release. I'm reading it at the moment and it is quite informative. Let me give a +1 of something to the contributors.
Now on to the "constructive" criticism. (to be fair my comments are mostly focused on the layout).
1. The columns
The columns have too few words per line make it a bit weird to read. The large font size also makes the page look cramped. This could probably be improved by shrinking the font size and increasing the spacing between columns a little.
2. Text flow
On the first page of "Understanding the FAT filesystem" there is a fairly lare diagram which splits the text across the page. Unfortunately it makes reading more awkward than it should because of the readers natural tendancy to go from the bottom of the first column (just above the diagram) to the top of the next column (which happens to be mid sentance).
3. Inconsistent capitalisation
This mostly applies to the front page.
edit: Just thought I'd add something else. The system call logo with the ugly drop shadown on the first page of "Practical compiler development" seems really out of place and quite random. That and it's just ugly.
Anyway - good job with the zine.
Now on to the "constructive" criticism. (to be fair my comments are mostly focused on the layout).
1. The columns
The columns have too few words per line make it a bit weird to read. The large font size also makes the page look cramped. This could probably be improved by shrinking the font size and increasing the spacing between columns a little.
2. Text flow
On the first page of "Understanding the FAT filesystem" there is a fairly lare diagram which splits the text across the page. Unfortunately it makes reading more awkward than it should because of the readers natural tendancy to go from the bottom of the first column (just above the diagram) to the top of the next column (which happens to be mid sentance).
3. Inconsistent capitalisation
This mostly applies to the front page.
edit: Just thought I'd add something else. The system call logo with the ugly drop shadown on the first page of "Practical compiler development" seems really out of place and quite random. That and it's just ugly.
Anyway - good job with the zine.
The cake is a lie | rackbits.com