User:Maury Markowitz/Infobox mainframe computer

Documentation[view] [edit] [history] [purge]

This template uses Lua:

Usage edit

This infobox is intended to document mainframe computer systems like the IBM System/360 Model 30. It should be used to replace the more general "information appliance" infobox where appropriate. Related infoboxes include minicomputer, microcomputer and game console.

This user is an administrator on the English Wikipedia. (verify)

2002
UID 2175

I have been editing Wikipedia since 2002-05-31,22 years and 4 months ago ([1])

50,000+

This user has made more than 50,000 contributions to Wikipedia.

en

This user is a native speaker of the English language.

Dad

This user is a father and proud of it!

This user comes from the
City of Toronto.

This user runs macOS.

This user contributes using Safari.

This editor is a
**Master Editor II**
and is entitled to display this Platinum
Editor Star.

This user has been editing Wikipedia for more than twenty years.

I award you the *Aviation Barnstar* in recognition of your knowledgeable contribution to aviation articles. -Bzuk

I can't decide, am I a Wikipedia:WikiSloth or a Wikipedia:WikiDragon?

Leela: Hmmm. I've been looking for a way to serve the community that incorporates my violence. Let's do it!

Fry: You'll barely regret this.

The quick-n-dirty description of me is "coding physicist" - I took physics in U, and like so many others of my era, today I'm a programmer. Eh, I don't mind that too much. I'm also a pilot, so unsurprisingly most of my edits are on science, tech or aircraft.

I hail from Toronto, specifically the Christie Pits area close to downtown. I have what used to be a "right sized" house until the girlfriend and I broke up, and now it's just plain too big. Still, I got it for a great price, so the cheapie in me won't let me sell it. Of course that leads to other problems, like the neverending upgrades you always forget about when you buy a place.

I work at a medium-sized (for Canada) hedge fund during the day, primarily writing the program they use to enter and track orders. I'm formerly a Mac guy, but holding a day job pretty much means you've got to work on the PC, and so I do. I can't say I really mind it though, and I have to admit that Microsoft Access does the job well.

I got into programming in a roundabout way, originally working in tech support for FirstClass. That was one odd company; there were the programmers, and then "everyone else", the peons. I never managed to break into programming there, the barrier to entry was just too high. Then back in '97 Apple Computer announced it was buying NeXT and using OpenStep as the next Mac OS X. So I started looking into OS and got completely hooked, posting about it a lot on the UseNet. Then one day I got a email from a developer in Toronto who wanted to hire me to help him write a program on OpenStep, but I declined, saying I liked my job and didn't really have that much experience anyway. The next day I got laid off. The day after that I worked for him. The rest, so it goes, is history.

I'm an avid cyclist and do about 200k a week on average, at least during the warmer months, which takes up my afternoons and any free weekends. I've started doing some longer distance day ride this year, 100-120 typically and a century ride every so often. Right now I'm gearing up for the Donut Ride, which I hope to try this weekend.

I have a fairly wide group of friends, some of whom have even ended up here on the wiki, like User:Pandora and my buddy Nick (missing in action).

Me and the Wiki edit

I've been a wikipedian for a while now, my first edits go back to the March 2002 time-frame. I guess that makes me one of the old-timers. Since then I've made a little under 10,000 edits, and created or rewritten perhaps 1,000. Before registering for this account I made a number of edits using User:216.94.11.2. As of April 2007 I have over 12,500 mainspace edits, and over 15,000 in total.

Some of these turned out to be really interesting when the people I was writing about would later see the article and write me. For instance I got a really nice letter from the author of the ZGRASS, who was impressed that I managed to piece together so much of the history. Admittedly I did a lot of legwork on that one, photoblasting a couple of articles at the Toronto Reference Library for background. I also came across a mention of the Lotus Improv article on someone's blog. He was convinced that I worked at Lotus because of all the "insider history" I gathered, but I have to admit I got most of it from an old NeXTWorld article.

I have only one "wikiwhine". In May I spent about a week trying to get several pictures of the IBM 1360 from Berkeley, only to succeed and then find they were summarily deleted because I uploaded just after the May 19th cutoff. This was particularly frustrating because there was no notice on the wiki about this cutoff, I only noticed it when I went back to the page and noticed a deletion tag. Poorly handled, IMHO. It's doubly frustrating in this case because the machines in question were all destroyed.

Something new edit

One of my pet peeves in the software industry is good ideas that simply disappear into the ether. I'm always annoyed when I try out some new package and it's missing some painfully obvious feature they could have just lifted directly out of another older package. That's why a lot of my writing is on older software, like Lotus Improv, FullWrite Professional.

And following that line of thought, I've decided to try a little experiment. I have started a new collaborative effort I call the Manifesto for a Better Word Processor, in which I hope to collect up ideas from all and sundry on the features they would like to see in the ideal word processor.

And a new one too: ObjC wishlist

My favourites edit

Here's a few of my articles I'm particularly proud of.

Article lists edit

Everyone seems to do this, but it got so long I had to break it up.

Multi-licensed with the Creative Commons Attribution Share-Alike License versions 1.0 and 2.0
I agree to multi-license my text contributions, unless otherwise stated, under Wikipedia's copyright terms and the Creative Commons Attribution Share-Alike license version 1.0 and version 2.0. Please be aware that other contributors might not do the same, so if you want to use my contributions under the Creative Commons terms, please check the CC dual-license and Multi-licensing guides.

{{Infobox mainframe computer
| name         = 
| title        = 
| aka          = 
| logo         = 
| image        = 
| caption      = 
| manufacturer = 
| family       = 
| type         = 
| release date  = {{Start date|YYYY|MM|DD}}
| lifespan     = 
| discontinued = 
| units shipped = 
| price        = 
| os           = 
| memory       = 
| platform     = 
| compatibility= 
| predecessor  = 
| successor    = 
| related      = 
| website      = {{URL|example.org}}
}}

Parameters edit

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:Maury Markowitz in articles based on its TemplateData.

TemplateData for Maury Markowitz

No description.

Template parameters
This template prefers block formatting of parameters.
Parameter		Description	Type	Status
Name	`name` `Name` `Title`	Name of the computer. Default it the article name. However it is a required parameter as it does not accept null. Default PAGENAME	String	optional
Logo	`logo`	File name of the logo to be appeared at the top of the infobox	String	optional
Logo size	`logo_size`	Size of the logo. Default is 250px. Must not normally be changed. Default 250px	String	optional
Logo upright	`logo_upright`	Size of the logo, scaling per user preferences. Default is 1. Must not normally be changed. Default 1	String	optional
Logo alternative text	`logo_alt`	Alternative text for the logo, used when the web browser cannot display the image or when a visually-impaired person uses a screen reader.	String	optional
Logo caption	`logo caption`	Caption for the logo. Must only be used to provide anything far more important than 'This is the logo of X'. e.g. used for inserting {{ffdc}} or {{deletable image-caption}}.	String	optional
Image	`image` `Image` `photo` `Photo`	File name of the image of the computer that will appear at the top of the infobox.	String	optional
Image size	`image_size` `ImageWidth`	Image size. Defaults to 300px. The best practice is to ensure the image is displayed at the default resolution. Hence, use of this parameter is discouraged. Default 300px	String	optional
Image upright	`image_upright`	Size of the image, scaling per user preferences. Default is 1. Default 1	String	optional
Image alternative text	`alt`	Alternative text for the image (used by the blind and when web browsers cannot or do not load the image)	String	optional
Image caption	`caption`	Caption for the image of the computer.	String	optional
Also known as? ("AKA")	`aka`	System nicknames	String	optional
Manufacturer	`manufacturer`	Name of the manufacturer, if applicable	String	optional
Family	`family`	Product family	String	optional
Type	`type` `Type`	Type of the device; mainframe, supercomputer, etc.	String	optional
Release date	`release date` `releasedate` `first_release_date` `Released` `Introduced`	Date introduced	String	optional
Base price	`baseprice` `baseprice` `price` `MSRP`	Base price or MSRP (manufacturer suggested retail price) of the appliance at its initial release. Per [[WP:NOTCATALOGUE]], "An article should not include product pricing information unless there is an independent source and a justified reason for the mention. Encyclopedic significance may be indicated if mainstream media sources (not just product reviews) provide commentary on these details instead of just passing mention.	String	optional
Discontinuation date	`discontinued` `discontinued` `discontinuation_date`	Date of when the appliance was discontinued / pulled from sale.	String	optional
Units shipped	`units shipped` `unitsshipped`	Number of units shipped	String	optional
Operating system	`os` `OS` `operatingsystem`	Operating system bundled with the product	String	optional
Type of memory	`memory` `Memory` `RAM`	Type of memory used (core, DRAM, etc.), and base amount if applicable	String	optional
Compatibility	`compatibility`	Details of backward compatibility with the appliance's predecessor(s).	String	optional
Predecessor	`predecessor`	Name of the system's predecessor, if applicable.	String	optional
Successor	`successor`	Name of the system's successor, if applicable.	String	optional
Related	`related`	Names of any sibling systems.	String	optional
Website	`website` `Website`	URL of the official website, in a printer-friendly form. (consider using the {{URL}} template for cleaner URL output)	String	optional

Important notes edit

Under WP:NOPRICES, "product prices should not be quoted in an article unless they can be sourced and there is a justified reason for their mention". Use of the "price" field should therefore be the exception rather than the norm.

In addition to the tracking category below, using this template without including at least one of parameters besides "title", "image", and "caption" will add the page to Category:Articles using infobox templates with no data rows.

Microformats edit

The HTML mark-up produced by this template includes an hCalendar microformat that makes event details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

Classes used

The HTML classes of this microformat include:

attendee
contact
description
dtend
dtstart
location
organiser
summary
url
vevent

Please do not rename or remove these classes
nor collapse nested elements which use them.

The HTML mark-up produced by this template includes an hProduct microformat that makes a product's details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

If the product has a URL, use {{URL}} to include it.

Classes used