text:
User talk:Remember the dot/Archive/5
|This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
- 1 Removal of Foundation copyrighted images
- 2 Image source problem with Image:Wikipedia-banner0002.png
- 3 Diagram of the constitution of the United States as proposed by Thomas Paine
- 4 Foundation images .. other image nonsense
- 5 JPEG crusader bot?
- 6 Welcome message
- 7 @icon sushi
- 8 PNG crusade bot
- 9 Image:Wikipedia book.jpg
- 10 TfD nomination of Template:Cite newspaper
- 11 PNG Crusade
- 12 Re: admin
- 13 Image:Juno_icon.png
- 14 Your GA nomination of World Community Grid
- 15 Here you go
- 16 RFA oddity?
- 17 Updating the historical template
- 18 Comment on RFA
- 19 Your RFA was unsuccessful
- 20 Your RfA
- 21 Comment about your RFA
- 22 RfA
- 23 Reply to reply to RfA reply
- 24 RfA
- 25 Ignoring Rules and modifying policy
- 26 PNG Crusadebot processing JPGs
- 27 Disputed fair use rationale for Image:Blood Water Mission Know Love Act.png
- 28 Your RfA
- 29 Jargon/Opera
- 31 Priest
- 32 Disputed fair use rationale for Image:Vista slow file system operations.png
- 34 Re: My (Remember the Dot)'s RfA
- 35 RE: Disputed fair use rationale for Image:Kifaya-2005-06-09.jpg
- 36 PNG Crusade Bot
- 37 Harry Meshel
- 38 Tweak cite web
- 39 NW Helsinki 0048 image
- 40 Image:Childers big.jpg
- 41 Template:ShouldBeSVG
- 42 Image:Abc wnt jennings2 050405 t.jpg
- 44 It wasn't a test.
- 45 Re: Your RFA
- 46 FFA icon
- 47 9/11 page
- 48 Image:Swucampus-pic1.gif and 2
- 49 Pan Am Cockpit 4 image
- 50 Image:Kyushu J7W Shinden.jpg
- 52 Village Pump proposal re: dates
- 53 autoformatting of full dates
- 54 Image:Kutuzov Belarus-Slovenia 2005.jpg
- 55 firefox svg
- 56 Re re RFA
- 57 Congrats on FA status for Opera
- 58 Wrong approach to the image patrol
- 59 Further work
- 60 Oprah Winfrey bust
- 61 Notification of image deletion
- 62 Template testing
- 63 Image Proposals
- 64 IE8 Acid2 - Pass/Fail?
Removal of Foundation copyrighted images
Hi, could you explain this edit? I'm not aware of any consensus that prohibits the use of Foundation copyrighted images in userspace. Any discussions I have seen suggests that they should not be treated the same as other unfree images. I'm not aware there has either been a change in local consensus or any directive from the Foundation prohibiting their use... WjBscribe 04:15, 3 October 2007 (UTC)
- In the name of free content, we remove and delete all sorts of images that pose no legal threat to us. The foundation's logos are kept on the Commons for convenience, not because they are free to use. —Remember the dot (talk) 04:19, 3 October 2007 (UTC)
- This matter has arisen before. The community has determined that the use of such images in userspace is acceptable and the Foundation has voiced no complaint about their use. Unless that changes, I don't think your edits are supported by consensus and would recommend you avoid editing other people's userspace without their permission. WjBscribe 04:22, 3 October 2007 (UTC)
Thanks for the note on my talk page, but that's not my image -- I just reverted some vandalism on it years ago. :) The listed uploader is User:SimonMayer who may be inactive, and the upload is marked as a public domain update of User:Nohat's Wikipedia logo. --brion 20:10, 3 October 2007 (UTC)
(what he said, and also): Are you using a script or suchlike to send these messages? If so you might set it to ignore people who only reverted the image. —Charles P._(Mirv) 08:18, 7 October 2007 (UTC)
Diagram of the constitution of the United States as proposed by Thomas Paine
There are issues exporting as SVG with Dia. Hopefully, the problem will be resolved in the version of Dia packaged in Ubuntu 7.10. -- Mathieugp 22:37, 3 October 2007 (UTC)
- this is the fastest reply I've seen in Wikipedia by the way!
- I am not at home right now, so I cannot check. However, if I remember correctly, there were font problems and other small glitches. I am on vacation in France right now, but in 3 weeks I'll be back and the new Ubuntu will be out. I am crossing my fingers. : -) -- Mathieugp 22:44, 3 October 2007 (UTC)
Foundation images .. other image nonsense
The use of images containing foundation logos, while they are indeed copyrighted, is permissible in userspace, even while other non-free images are not. It would indeed be quite absurd to suppose that a website's use of its own logo could violate its copyright on that logo. Each of the many, many times this issue has been raised, the consensus of the board and of Wikipedia has been that use of WMF-copyrighted logos in userspace is appropriate. Additionally, screenshots of a tool for Wikimedia, be the tool released under a free license or not, for the purpose of illustrating the software in question on its appropriate project page or discussion page are permissible on those pages by simple common sense. While the screenshots were mis-tagged, I should think it a far better use of your time to retag them or contact me to ask for an explanation of copyright than to go spam me with three redundant templates and mark the images for deletion. Tagging is a job for a bot, not a person. AmiDaniel (talk) 05:50, 4 October 2007 (UTC)
- If Wikimedia logos, which violate no copyright, are permitted, then why would Mozilla logos (like the Firefox logo), which also violate no copyright, be prohibited? This makes no sense.
- Aside from the Wikipedia logo issue, which I am not pressing, screenshots of non-free software are typically non-free. I looked at User:AmiDaniel/VandalProof#License and found that VandalProof is not under a free license, and therefore screenshots of it would also be non-free. However, since you have clarified that you have released copyright over the user interface elements present in the two screenshots, there is no longer a problem. So, thank you for clarifying! —Remember the dot (talk) 18:44, 4 October 2007 (UTC)
JPEG crusader bot?
I was curious - have you ever considered a JPEG crusader bot to convert photographic GIFs that should be JPEG format? Or are you strictly a PNG fan? :) Videmus Omnia Talk 19:19, 6 October 2007 (UTC)
- No, I have not, because that would lose a bunch of image quality on top of the massive quality loss by saving photographs in GIF in the first place. —Remember the dot (talk) 19:21, 6 October 2007 (UTC)
Welcome message
Why on earth would you welcome an editor that has been here for considerably longer than you? It is one of the shortfalls of using templates blindly. Your edit to Joseph Smith did nothingto improve the article so I don't see why you would issue a warning for "deleting information". You might want to review the purpose of using warning templates and use better judgement in when to apply them. You did no harm, but it is just an annoying approach to editing. --Storm Rider (talk) 06:35, 7 October 2007 (UTC)
@icon sushi
I've added a {{prod}} template to @icon sushi, suggesting that it be deleted according to the proposed deletion process. I've done this as it's been previously deleted based on Wikipedia:Articles for deletion/@icon sushi. I can't find any news articles or other assertion of notability - if you disagree please remove the prod template, drop in some references or drop me a line - Peripitus (Talk) 10:31, 10 October 2007 (UTC)
PNG crusade bot
Dot, would you mind unleasing the bot? The conversion categories are getting a little backlogged...also, had a quick question - are black & white photos usually better off in PNG than JPG format? Thanks... Videmus Omnia Talk 08:12, 12 October 2007 (UTC)
- Done. But unfortunately, the bot is encountering errors trying to convert specific images, and I don't know why. As far as black & white photos, JPEG is probably best, but as always, use a high quality setting. I typically set the GIMP to the 95% quality setting. —Remember the dot (talk) 00:35, 18 October 2007 (UTC)
Image:Wikipedia book.jpg
Mmm, It seems to me that the {{Non-free Wikimedia logo}} tag is a license. The original author apparently put a GFDL tag for his part of the work that was removed. To be honest I don't know... -- lucasbfr talk 14:56, 12 October 2007 (UTC)
TfD nomination of Template:Cite newspaper
Template:Cite newspaper has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for Deletion page. Thank you. — Conrad T. Pino 08:26, 13 October 2007 (UTC)
PNG Crusade
Is it really a good idea to convert, e.g. JPEG directly to PNG? If someone uploads a logo in JPEG form, it may have visible artifacts. In that case, someone should convert the source image (probably a bitmap or vector image) directly to PNG. If you convert the JPEG, the artifacts would still be in the PNG. This isn't usually an issue for GIF, but in some cases creating a GIF loses colors, since GIFs can only represent 256 colors. So if you have a BMP image with more than 256 colors, BMP->PNG is better than BMP->GIF->PNG. I don't think file size really outweighs these concerns at the present. Superm401 - Talk 15:50, 16 October 2007 (UTC)
- Like you said, the PNG crusade bot can't remove artifacts. But, where a JPEG->PNG conversion would decrease the file size despite keeping the artifacts, it will do it. This helps avoid introducing new artifacts if a new version of the image is uploaded, and makes it easier to clean the image of artifacts later and upload in PNG because all the file history has already been copied. —Remember the dot (talk) 18:35, 16 October 2007 (UTC)
Re: admin
Alright, if you wish to run now then I'll nominate you. Lemme just look through your contribs and the like. I should have the nom up in a day or two for you to finish. Wizardman 02:06, 18 October 2007 (UTC)
I have tagged Image:Juno_icon.png as {{no rationale}}, because it does not provide a fair use rationale. If you believe the image to be acceptable for fair use according to Wikipedia policy, please provide a rationale explaining as much, in accordance with the fair use rationale guideline, on the image description page. Please also consider using {{non-free fair use in|article name}} or one of the other tags listed at Wikipedia:Image copyright tags#Fair_use. Thank you. Rettetast 21:13, 18 October 2007 (UTC)
Your GA nomination of World Community Grid
The article World Community Grid you nominated as a good article has failed , see Talk:World Community Grid for reasons why the nomination failed. If or when these points have been taken care of, you may apply for a new nomination of said article. If you oppose this decision, you may ask for a reassessment. Cheers, CP 04:01, 18 October 2007 (UTC)
Here you go
Wizardman 15:40, 20 October 2007 (UTC)
RFA oddity?
Hey, what happened here? SQL(Query Me!) 10:27, 23 October 2007 (UTC)
- It looks like I accidentally pressed Ctrl+V a couple times...oops. —Remember the dot (talk) 18:22, 23 October 2007 (UTC)
Updating the historical template
Hi, seeing that you are the user that most recently made edits to the historical template On my sub-page (User:Cocoaguy/historical alt) i created a version using the ambox template, maby we could update the main one too. -- (Cocoaguy ここがいい contribstalk) 22:17, 23 October 2007 (UTC)
- I'm afraid that ambox is only for templates in the article namespace. There is not currently consensus to use it in any other namespace, so using it for {{historical}} is out for now. —Remember the dot (talk) 22:33, 23 October 2007 (UTC)
Comment on RFA
- Copied from your RFA.
I have never supported that argument. Using a non-free image when a better free image could be created is not acceptable. It diminishes portability for no good reason. And I've seen many articles copied from the Encyclopedia Britannica, and that's fine. We should use them until we have something better. —Remember the dot (talk) 16:08, 26 October 2007 (UTC)
- I am sure you misspoke there. Articles copied from Britannica would be copyright violations. You may want to rephrase and/or strike some of that. I think others should give you time to do so before responding, since it seems like just a slip of the tongue. — Carl (CBM · talk) 16:58, 26 October 2007 (UTC)
Your RFA was unsuccessful
I have closed your RFA. I am afraid there was no consensus to promote you. Please address the concerns that were raised, and feel free to reapply in the future. Good luck. --Deskana (talk) 23:16, 28 October 2007 (UTC)
Your RfA
Aw... Better luck next time. — Edokter • Talk • 23:22, 28 October 2007 (UTC)
- I just wanted to drop by and give my sincere good wishes and, if necessary, apologies for anything that might have been overly caustic. I do understand your position, and I don't think I disagree with you about the nature of the project. I do think we disagree about the importance of images overall, and about the importance of the quality of an image (as opposed to the information it contains) in particular. You worried that my opposition was set in stone, but I actually have no particular opposition to you; on the contrary, you're obviously an excellent editor. But the continuous, strident defense of relatively trivial images (I don't mean by you, I mean in general) has hardened some of us, and I do hope you understand why that would be the case. Chick Bowen 23:47, 28 October 2007 (UTC)
- To be honest, I don't know. When you decide to go up again (and be patient, 'cause the regulars--I'm not one--hate it when people go up again to soon), let me know and maybe we can have this thing out by e-mail or some such. Chick Bowen 00:10, 29 October 2007 (UTC)
- I'm sorry your RfA was not successful. I'm sure it will succeed next time. Cheers, :) Dlohcierekim 02:29, 29 October 2007 (UTC)
Comment about your RFA
First, let me express my deepest regrets that your RFA did not pass this time around. The reason I opposed was about your answer to question #8. Also, as Daniel pointed out, the lack of knowledge between a block and a ban. I hope that why I opposed does not affect your opioion of myself, and Wikipedia as a whole! Not everyone gets lucky on there first RFA attempt. I see people on there 3rd, or 4th passing and becoming admins. Take all opposeing and supporting votes comments into what you do, and try again soon!
PatPolitics rule! 02:52, 29 October 2007 (UTC)
- Would I support you. I think I would. It was a close RFA, and if you follow the concerns, you will pass. PatPolitics rule! 03:29, 29 October 2007 (UTC)
You asked me for comments on the NFCC stuff. Yes we are here to make an encyclopedia, but note in the logo, its the free encyclopedia. This means that we should be using non-free content at the absolute minimum needed. You were not very clear to me (or to others) what you considered a significant use. Often times we are very able to write an article with only free images. If you have any questions feel free to ask me in a response on my page, or to ask me on IRC (if you use it). Best of luck. —— Eagle101Need help? 04:07, 29 October 2007 (UTC)
- Another thing, you uploaded this image: Image:Earth_2025_country_status_screenshot.png, which has its rational disputed. I don't know if the rational is good or not, I'd tend to not using it, *but* note the image size, at 1920 × 1005 pixels I think its overly large for anything we would use in an article. It should be resized to something less then about 400 x 300 (approx), as thumbnails in articles rarely get any larger then that. All in all, I"d suggest you give NFCC a look over and compare your uploads to it, Non-free content generally should not be larger then the minimum needed to display in an article. —— Eagle101Need help? 04:10, 29 October 2007 (UTC)
- I should also note that firefox is free software, as long as you covered up the logo (which is owned by Mozilla), and the google logo you would be fine in displaying an image of firefox. Microsoft internet explorer is a different matter ;). —— Eagle101Need help? 04:16, 29 October 2007 (UTC)
Scrolling up your talk page, I see you have uploaded Image:Mac_listbox_screenshot.png, which has been tagged as replaceable fair use. It is in this case, we can get a free image of a listbox, open any Linux application that uses them take a screen shot of it. I won't point out any more images unless you ask, but I hope you understand better why I chose to oppose. —— Eagle101Need help? 04:19, 29 October 2007 (UTC)
- Response left at User talk:Eagle 101#My RfA —Remember the dot (talk) 04:42, 29 October 2007 (UTC)
- The google logo is also not free, so blanking it out, with the Firefox logo would be required to have a truely free image of Firefox to display. As far as the images, I'll let the normal deletion process occur. I hope you do understand where I am coming from though. —— Eagle101Need help? 04:53, 29 October 2007 (UTC)
- Sure, you also said you did not upload the images that I mentioned above... you did upload Image:Mac_listbox_screenshot.png, which will be deleted as a replaceable fair use image. As long as you can demonstrate in your next RFA that you know what is and is not replaceable, (perhaps check over the rest of your upload history), I'll be fine. I did not oppose so much for your ideology, but for the fact that there is evidence that you don't quite grasp the image policy. —— Eagle101Need help? 14:29, 30 October 2007 (UTC)
- Right, what I was attempting to get you to do is to review your own upload history, and update/delete the images you did before you had a better understanding. —— Eagle101Need help? 18:15, 31 October 2007 (UTC)
- Sure, you also said you did not upload the images that I mentioned above... you did upload Image:Mac_listbox_screenshot.png, which will be deleted as a replaceable fair use image. As long as you can demonstrate in your next RFA that you know what is and is not replaceable, (perhaps check over the rest of your upload history), I'll be fine. I did not oppose so much for your ideology, but for the fact that there is evidence that you don't quite grasp the image policy. —— Eagle101Need help? 14:29, 30 October 2007 (UTC)
- The google logo is also not free, so blanking it out, with the Firefox logo would be required to have a truely free image of Firefox to display. As far as the images, I'll let the normal deletion process occur. I hope you do understand where I am coming from though. —— Eagle101Need help? 04:53, 29 October 2007 (UTC)
Reply to reply to RfA reply
No promises, but I suspect that you will be more clearly admin material and your readiness will be more apparent to the "RfA cabal." By then you should have an even better grasp of things and should be able to show it. Best of wishes. If I can help you in some way, let me know. Cheers, :) Dlohcierekim 14:12, 29 October 2007 (UTC)
I notice you asked a few opposers for ideas on what could be done differently, so perhaps this info is of interest. I considered voting in your RfA but did not. I'd just mention a couple of reasons why I didn't support:
- Edit summaries: I might have supported if you had indicated you would consistently use edit summaries
- Image policy: This was totally baffling. I couldn't sort out what happens when an admin has differences with image policy but still has to carry out admin tasks according to the rules. Maybe you could have pointed out some other admin who has the same views, but can do his duties anyway.
Since you didn't ask for this feedback, it's fine if you want to delete my comment after you read it. EdJohnston 16:22, 29 October 2007 (UTC)
- I've enabled prompted edit summaries in my preferences, and I would of course provide edit summaries for every administrative action that I take.
- I see now that it was a mistake to allow the RfA to degrade into a debate of my personal views of the purpose behind the non-free content policy. It seems that I was not clear enough that as an administrator, I would have to obey the community's wishes, no matter now much I disagree with them. It would be wrong of me to force my personal opinion on others. In cases where my personal opinion differs from the community's opinion, I will not take any administrative action, but rather leave that to others. This is why I refuse to get involved in most deletion "discussions" revolving around WP:NFCC#10c. —Remember the dot (talk) 18:00, 29 October 2007 (UTC)
- I don't consider your view on edit summaries to be adequate for administrators. Anti-vandalism tools look for edit summaries, and I think that administrators ought to show the way for others. EdJohnston 18:10, 29 October 2007 (UTC)
- I have not once been reverted by an anti-vandalism tool, and like I said, I enabled prompted edit summaries and will be using them more often. —Remember the dot (talk) 18:14, 29 October 2007 (UTC)
Ignoring Rules and modifying policy
Ah I see you answered on 21 october. I have been unexpectedly busy these last few weeks, and should have entered debate with you then. I feel kind of guilty, my apologies ^^;; You did the right thing by replying to my oppose by the way. Jolly good show there. :-)
The reason for my oppose is because you didn't quite grasp the basics of how wikipedia rules work.
Starting out
I think a beginning admin doesn't have to know everything, but the one thing they *should* know is that it's ok to Ignore All Rules. Just do what you think is right, and ask other admins to check you from time to time. As a guide to what is "the right thing", be sure to refer to m:Foundation issues.
In the past the "ask other admins" requirement was less of a problem, since the admin-to-user ratio was somewhat sane, and odds were that another admin would check you anyway. These days, do call attention to anything you're not sure about, and after that things still work like a regular wiki -with consensus and all, basically- At any rate, none of the admin actions can permanently harm the encyclopedia anymore these days, so don't sweat it.
So how are rules actually made?
Past that point there's also a question of "how the rules are made". Well, despite anything others may have told you, The Ignore All Rules policy (irony!) automatically makes everything else a guideline. You *may* follow our guidelines or not, at your discretion, as long as you improve the encyclopedia. If you find that you are acting at odds with some guideline, and other people agree with you that you're actually doing the right thing (ie, there's a consensus), go ahead and edit the guideline to conform with reality. Guidelines are descriptive, not prescriptive.
The opposite approach, of following a guideline to destruction until people get fed up with you and change it, is against the recommendations of the guideline that says you should not disrupt wikipedia to make a point (about the rules).
Act first, compare with guidelines, if guidelines are wrong, fix them.
Of course, after many iterations, the guidelines start to look very polished and sane, but naturally that doesn't mean we should abandon the procedure that made them! What happens if the situation changes somehow? We want to continue to be able to respond in a flexible way.
And that's why things are the way they are, at least, as far as I'm aware. :-)
--Kim Bruning 19:47, 29 October 2007 (UTC)
PNG Crusadebot processing JPGs
Should PNG Crusade Bot be processing BadJPGs? These images need to be remade or heavily cleaned up, not just converted to another format.Doodle77 22:44, 29 October 2007 (UTC)
- The PNG crusade bot only converts images that would benefit from a simple PNG conversion, so very few JPEGs are actually converted. Perhaps I should make the bot add the {{artifacts}} tag to converted JPEGs for good measure. —Remember the dot (talk) 01:02, 30 October 2007 (UTC)
Disputed fair use rationale for Image:Blood Water Mission Know Love Act.png
Thanks for uploading Image:Blood Water Mission Know Love Act.png. However, there is a concern that the rationale you have provided for using this image under "fair use" may be invalid. Please read the instructions at Wikipedia:Non-free content carefully, then go to the image description page and clarify why you think the image qualifies for fair use. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to ensure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If it is determined that the image does not qualify under fair use, it will be deleted within a couple of days according to our criteria for speedy deletion. If you have any questions please ask them at the media copyright questions page. Thank you.BetacommandBot 23:40, 29 October 2007 (UTC)
Your RfA
I'm not sure why you're confused; perhaps you should read my comment more carefully, as you seem to have misquoted it. I expect a certain minimum level of contributions to the Wikipedia namespace. In your case, numerous commenters suggested that you are inexperienced in image issues, among other things. Going forward, I think you'd learn quite a lot by visiting more XfDs, and familiarizing yourself with the various fora that address copyright issues. Best wishes, Xoloz 16:16, 30 October 2007 (UTC)
Hi, i've read the Opera article a couple of times and i can see some jargon. The features section simply doesn't describe what makes Opera different/special and most of what's there is jargon and should be sent to the features page with material coming back the other way. The future releases contains jargon, it shouldn't be moved or deleted and needs to be rewritten. I can and will rewrite that section for FF because i'm familiar with all the concepts, but i cant do that with Opera because i dont use it. I also noticed that there is large mention of Opera's use in portable devices and others. The Wii or cell phones for example. This section could be described as simply unimportant and possibly jargon, because anybody who has tried to surf the net using those devices will know what a mostly pointless time it is. Even PDA's are generally unsatisfying and are good for email and not much else. I've started watching this page so if you want to open a discussion on the talk page about jargon then i'd be generally agreeably, altho i wont be editing the article myself because i dont know enough about the subject. Operating 11:41, 31 October 2007 (UTC)
- In retrospect i should have written my first thought, that i dont see much jargon to worry about, i thought you'd seen some and wanted a discussion in place to add the template and edit what was necessary without reverts and undo's. I can't offer any other suggestions because i dont use the program. Operating 19:12, 31 October 2007 (UTC)
Sorry, don't have any idea what you're talking about. I use Firefox and (occasionally) Opera, and while I have IE on my computer, it's IE7, not IE6. -- John Broughton (♫♫) 12:53, 2 November 2007 (UTC)
- No problem. And it was good advice, even if misdirected. -- John Broughton (♫♫) 23:50, 3 November 2007 (UTC)
Thanks for the save on that Judas Priest image. I guess I mislabelled it. Go figure. Howa0082 01:27, 13 November 2007 (UTC)
Disputed fair use rationale for Image:Vista slow file system operations.png
Yeah.. even I felt the same... We actually don't need a snapshot to illustrate the slow file system operations. The reason I uploaded that file was the original file was a jpg version... full of compression artifacts, to an extent that the text was not readable... so I replaced jpg version of the image to png version... I think, You can "speedy delete" that file...
Mugunth 07:23, 13 November 2007 (UTC)
You're welcome. Better luck on your second attempt. SGGH speak! 08:55, 13 November 2007 (UTC)
Re: My (Remember the Dot)'s RfA
That's fine, don't worry about it. It's a shame you didn't succeed, but I'm sure that, if you take note on all the pointers left down by people participating in your RfA, you're next attempt should be more successful. Best wishes, Lradrama 14:38, 13 November 2007 (UTC)
- Pass? I don't doubt it. Rudget zŋ 16:07, 13 November 2007 (UTC)
- You're welcome for the support. :) With any luck, your next RfA should pass. Acalamari 17:06, 13 November 2007 (UTC)
RE: Disputed fair use rationale for Image:Kifaya-2005-06-09.jpg
http://en.wikipedia.org/wiki/Image:Kifaya-2005-06-09.jpg used to be listed on the Arabic Wikipedia, now they have http://commons.wikimedia.org/wiki/Image:Kifaya-protest-20050508-banner.png on wikipedia commons. Thanx --The Brain 20:54, 13 November 2007 (UTC)
PNG Crusade Bot
Just to let you know, I have tagged many images with either {{badGIF}}, {{badJPEG}}, or {{shouldBePNG}}. However, your PNG crusade bot has been fairly inactive for the past month. Could you please re-activate it to convert the images that I have tagged? ANDROS1337 04:08, 16 November 2007 (UTC)
Harry Meshel
Thanks for alerting me to questions about the image for the Harry Meshel article. Unfortunately, I don't think I can add anything to the rationale already included on the image page. The subject in question was affiliated with a state governmental body rather than a federal one. So, the fact that the image is an official portrait doesn't qualify it as free. The only thing I can argue for is its possible historical value, because it depicts the subject at the height of his political career. Thanks, again, for your message! - twelsht (talk) 04:44, 17 November 2007 (UTC)
Tweak cite web
How will the proposed change affect existing pages? If it means that a mass change of all the article the template is used on, I would certainly oppose it, but I'm not fully up to speed on why you suggested it in the first place. - Mgm|(talk) 09:24, 17 November 2007 (UTC)
- Dates formatted as 2007-11-17 would be automatically wikilinked as 2007-11-17 if they are not linked already. Dates in other formats (which I believe are discouraged under the template's usage guidelines), such as November 17, 2007, are not affected. —Remember the dot (talk) 18:27, 17 November 2007 (UTC)
- "if they are not linked already" was the crucial part. If it doesn't meddle with existing properly linked dates, then I have no objections. - Mgm|(talk) 19:28, 17 November 2007 (UTC)
Nice to see you've been able to get dates linked in a couple of {{cite whatever}} templates! Keep up the good work! RossPatterson (talk) 01:53, 29 November 2007 (UTC)
NW Helsinki 0048 image
Hello, I've added a defense of the above-mentioned image to the image's Talk page. Please reconsider the speedy deletion. Thanks. Nerwen (talk) 21:34, 23 November 2007 (UTC)
Image:Childers big.jpg
Hi, you have marked this image as {{withpermission}}. Do you have some record of the permission? What permission has been granted. If not, its a good case for fair-use ; just remove the tag. John Vandenberg (talk) 06:19, 24 November 2007 (UTC)
What's the use in adding this template to an image?! I suppose the word should always bothers me. I can edit a bitmap but I can't edit a SVG, so converting an image I made means I can't improve it later, which is freakin' annoying, so unless you want to change an image now, forget the stupid template markers. Tom Ruen (talk) 02:26, 27 November 2007 (UTC)
- It is Wikipedia policy to prefer vector images to raster images (see Wikipedia:Preparing images for upload). Most of us use the free program Inkscape to edit SVGs.
- I hope that helps! —Remember the dot (talk) 03:34, 27 November 2007 (UTC)
- I don't have time or motivation to learn inkscape. Does it do anything better than hand-tracing an image? If a source image is rendered as a bitmap, it seems a waste of time and effort to hand-re-trace it. Tom Ruen (talk) 04:01, 27 November 2007 (UTC)
- Yes, Inkscape is a full-featured SVG editor. Again, please read Wikipedia:Preparing images for upload to see why vector images are useful, and do not remove the {{ShouldBeSVG}} tags from any more images. —Remember the dot (talk) 04:22, 27 November 2007 (UTC)
- I WILL remove the tag if I think it's WRONG, and I still don't understand - it's senseless to me to convert a rendered source image to a hand-regenerate SVG. Tom Ruen (talk) 04:48, 27 November 2007 (UTC)
- If you continue to remove the tags inappropriately then you will be blocked for violating Wikipedia policy. If you had read Wikipedia:Preparing images for upload then you would understand that vector images scale better than raster images and are easier to modify. This is why they are preferred.
- Perhaps you don't understand that we will not use a vector image over a raster image simply because it is a vector image. Rather, the vector image must be just as good or better than the raster image before we will switch to it. Does that make sense? —Remember the dot (talk) 05:02, 27 November 2007 (UTC)
- My position is really sympathy for not wasting someone else's time. If I make an image, then I have the greatest incentive to make it SVG. If I can't make an SVG one, then someone else must do almost as much work as me to RECREATE my original image as SVG. And if my original image was not the best layout or whatever then someone else is copying my dumpy work, which is a waste of their time. And if later I want to make a better image, then someone ELSE must again remaking MY work to do so. It is a senseless waste of time if the original image isn't from SVG in the first place. Tom Ruen (talk) 05:45, 27 November 2007 (UTC)
- Often it's worth the effort to vectorize images due to the benefits mentioned above. If an image has a bad layout then the person who's doing the vectorizing would hopefully correct the problem. But you're right: it's best if users just upload images in SVG format to begin with to save us the trouble. —Remember the dot (talk) 07:01, 27 November 2007 (UTC)
- My position is really sympathy for not wasting someone else's time. If I make an image, then I have the greatest incentive to make it SVG. If I can't make an SVG one, then someone else must do almost as much work as me to RECREATE my original image as SVG. And if my original image was not the best layout or whatever then someone else is copying my dumpy work, which is a waste of their time. And if later I want to make a better image, then someone ELSE must again remaking MY work to do so. It is a senseless waste of time if the original image isn't from SVG in the first place. Tom Ruen (talk) 05:45, 27 November 2007 (UTC)
- I WILL remove the tag if I think it's WRONG, and I still don't understand - it's senseless to me to convert a rendered source image to a hand-regenerate SVG. Tom Ruen (talk) 04:48, 27 November 2007 (UTC)
- Yes, Inkscape is a full-featured SVG editor. Again, please read Wikipedia:Preparing images for upload to see why vector images are useful, and do not remove the {{ShouldBeSVG}} tags from any more images. —Remember the dot (talk) 04:22, 27 November 2007 (UTC)
- I don't have time or motivation to learn inkscape. Does it do anything better than hand-tracing an image? If a source image is rendered as a bitmap, it seems a waste of time and effort to hand-re-trace it. Tom Ruen (talk) 04:01, 27 November 2007 (UTC)
Image:Abc wnt jennings2 050405 t.jpg
If you look at Wikipedia:Non-free use rationale guideline it states that "A separate rationale must be provided each time the image is used in an article." and this image does not comply. Using the guideline then any of the images could be used in the infobox provied a rationale was given. CambridgeBayWeather (Talk) 06:29, 27 November 2007 (UTC)
One man's vauge is another's way of thinking. I'd thought better of you. Disappointing. At LEAST do the right thing with such redirects so I don't have to pickup your dirty laundry. // FrankB 18:26, 29 November 2007 (UTC)
- re: http://en.wikipedia.org/wiki/User_talk:CBDunkerson#Procedural_minutia
- Fer Pete's sake, lighten up. I didn't accuse you of a capital crime, just failure to apply {{R to other template}}! Sheeesh! Well, maybe I hit you with a wet noodle for your summary. Saying someone's name sucks is borderline PA, if you think on it a while. This is ALL so-oooo-oo NBD, but it does create a bunch of stuff out there where someone will go look... and find themselves "disconnected". Maybe you don't look at templates from inside preview using {{lts}}, but I do that ALL THE TIME—99 out of 100 at least, and I don't go to the source page, but to the source code... i.e. as 'edit mode' so I can see how it works. With an unecessary name change, I end up looking at the internals of a redirect page... a time waster for me and a distraction. But not the end of the world. Shrug, 'lts' works for me, but I've been coding this or that since the mid-seventies, so seeing under the hood is like a baby and a pacifier! <BSEG>. OTOH, if I hadn't liked YOUR name, then I might have created a redirect to one I liked better... not moved it sans discussion—that I've done at least ten or twelve times—see all the aliases of {{R from alternative capitalization}}, errr capitalisation, errr... other Capitalisation... ad nauseum, but it proves the point, and I'm only counting that as one. Why? Cause I could never remember the EXACT name because that the way some one else associates the world, not me. Same deal with {{R from unicode name}}... whatever that redirects too makes sense to someone witha linguistic education, but what it means in software, is WYSIWYG allows font representations ASCII doesn't. I can relate to that, and haven't a clue on the other.
(Hell, sometimes I can't recall the name of something I wrote... here's a perfect example, inasmuch as I was patching your redirect page, when my brain started farting, so I aliased my own template from two years back, as someone else will probably misremember same as I did just then.) So "Capitalization" (whatever the original is called) kept taking my time to follow three or four links until I could find the correct name spelling, that I still couldn't relate too, a week later... when I was likely already preoccupied by whatever important edit (which is ALWAYS) that led me to discover whatever redirect page I now also need to tag. That's all this is about—a bit of respect for other peoples' way of thinking and not making self-righteous pronouncements that "my mother's army shoes are bigger than yours" (WHO CARES? ALL Opinions are like assholes and stink in equal measure, ditto the names we use). What good comes of saying your name sucks to me? (It does, but I'm not asserting that... I see some sense to it, even if you don't to mine. More appropo, I'll NEVER remember it, which pretty much means I'll never use it. Sorry. As CBD agrees, there was nothing wrong with my name, in the first place.) If you took the bit about "socks" critcally, sorry. I was using what I use for a sense of humor. Poor things about dead anyways. Besides, I didn't pick up your dirty underwear... the usage is still written in the name of the original template. [I've even been known to document a redirect alias on the usage page so people can follow along and hum the same tune when I alias something... which if there be a crime here, is perhaps the note your dirty underwear represent!] Cheers! Life is full of bigger problems. Be well, and nice to talk again... it's been a while. // FrankB 00:31, 30 November 2007 (UTC)
- Fer Pete's sake, lighten up. I didn't accuse you of a capital crime, just failure to apply {{R to other template}}! Sheeesh! Well, maybe I hit you with a wet noodle for your summary. Saying someone's name sucks is borderline PA, if you think on it a while. This is ALL so-oooo-oo NBD, but it does create a bunch of stuff out there where someone will go look... and find themselves "disconnected". Maybe you don't look at templates from inside preview using {{lts}}, but I do that ALL THE TIME—99 out of 100 at least, and I don't go to the source page, but to the source code... i.e. as 'edit mode' so I can see how it works. With an unecessary name change, I end up looking at the internals of a redirect page... a time waster for me and a distraction. But not the end of the world. Shrug, 'lts' works for me, but I've been coding this or that since the mid-seventies, so seeing under the hood is like a baby and a pacifier! <BSEG>. OTOH, if I hadn't liked YOUR name, then I might have created a redirect to one I liked better... not moved it sans discussion—that I've done at least ten or twelve times—see all the aliases of {{R from alternative capitalization}}, errr capitalisation, errr... other Capitalisation... ad nauseum, but it proves the point, and I'm only counting that as one. Why? Cause I could never remember the EXACT name because that the way some one else associates the world, not me. Same deal with {{R from unicode name}}... whatever that redirects too makes sense to someone witha linguistic education, but what it means in software, is WYSIWYG allows font representations ASCII doesn't. I can relate to that, and haven't a clue on the other.
It wasn't a test.
It's just I added an infobox but found it redundant so changed my mind. —Preceding unsigned comment added by Justmeherenow (talk • contribs) 02:03, 9 December 2007 (UTC)
Hmm...OK (yeah, that was stray code from who-knows-where that had got stuck on text I'd cut-and-pasted...). Justmeherenow (talk) 02:45, 9 December 2007 (UTC)
Re: Your RFA
Hello. This is in response to your message of Oct. 27. Sorry for not getting back to you sooner. Apparently I did not notice the message at first (I must have jumped to the next one down and then left the page), and then I went on 'wikibreak' for a few weeks.
I hope this is not seen as a lazy answer, but I did sincerely concur with what Meegs said on the RFA, and I also concur with his response to your later message on his talk page.
Regarding your response to Q7 on the RFA, which I also expressed concerned about, you seemed to suggest that the primary reason for limiting non-free content is portability and ease of re-use. To me this suggested a lack of understanding or belief in free content as a core part of our mission, one with which we do not compromise. Perhaps this is essentially a semantic misunderstanding, or a difference in personal values; to me, freedom is important firstly for its intrinsic moral value, and secondarily for its practical benefits (eg. portability). (See this article by our own Benjamin Mako Hill for a good argument against compromising the "ethical" position of freedom, in this case vis-a-vis Creative Commons)
The fact that taking such a position would seem to put me in the ranks of the "hard-core free content activists" with which you disagree (and to be clear, I'm nothing of the sort) suggests to me that one of the foundation issues is not of primary importance to you. (Kim Bruning opposed the RFA on similar grounds.)
Again, sorry for the late reply, and I wish I had had more time to elaborate on the RFA before it closed. Happy editing, heqs ·:. 17:20, 10 December 2007 (UTC)
- In reply to your message, I feel that we are sort of splitting hairs here, or just plain misunderstanding eachother. I'm sure you know that non-free content is not a core part of our mission. You seem to think that the "balancing act" between free and non-free involves two things of similar importance; that we can "compromise" on the free part. We can't and we don't. We can fiddle with the allowed levels of non-free content because it is of secondary importance, using it judiciously where it suits the project, whereas compatibly licensed free content is always welcome and will always be here. We are not going to legislate a reduction in the use of free content, or revoke the GFDL. That's what I mean by "we do not compromise" with free content. heqs ·:. 21:19, 10 December 2007 (UTC)
FFA icon
The star with the red X has been used for former featured articles for ages. Former featured lists uses the same style (though the X is different) on those articles which have not been converted to the {{ArticleHistory}} framework. The icon you've chosen is the former FAC icon; changing this should really be discussed. Gimmetrow 21:19, 10 December 2007 (UTC)
9/11 page
Its prose is 60KB, not even close to the 100KB max. IMHO it is fine. — BQZip01 — talk 05:33, 11 December 2007 (UTC)
- We really should be shooting for the article, including all references, to be in the 30-50 KB range. The article is currently over 100 KB, making it very unwieldy when I try to edit it. Many of us have slower connections; even many low-end "broadband" connections are insufficient. I know that I could work around the problem by just editing specific sections, but then I wouldn't be able to preview the references very easily (and less technical users wouldn't know how to preview the references during a section edit at all). —Remember the dot (talk) 05:40, 11 December 2007 (UTC)
- Responding here is fine (no need to duplicate on my talk page) and I am responding from my work where I can't log in...wierd. These appear to be your personal preferences and not Wikipedia policy.
- Specifically, WP:SIZE states:
- "In the past...technical considerations prompted a strong recommendation that articles be limited to a maximum of precisely 32 KB in size, since editing any article longer than that would cause severe problems.[1] With the advent of the section editing feature and the availability of upgrades for the affected browsers, this once hard and fast rule has been softened and many articles now exist which are over 32 KB of total text size.
- "Though article size is no longer a binding rule, there remain stylistic reasons why the main body of an article should not be unreasonably long, including readability issues. It is instead treated as a guideline, and considered on a case by case basis, depending on the nature of the article.
- "For stylistic purposes, only the main body prose[2] (excluding links, see also, reference and footnote sections, and lists/tables) should be counted toward an article's total size, since the point is to limit the size of the main body of prose."
- If you want to get this Wikipedia guideline changed (note it is also not a policy, but a guideline), then by all means, more power to you and I wish you the best of luck. — BQZip01 — talk 21:04, 11 December 2007 (UTC)
- The guideline clearly states that readability is not the only factor that determines how long is too long. Read further and you will find When using slow connections, e.g., a desktop computer with an analog modem dial-up or the wireless connection of some mobile devices, long articles can take too much time to load. Not everyone is fortunate enough to have an ultra-high-speed connection. The 32 KB rule is no longer an absolute limit, but that does not mean that technical issues still come into play. —Remember the dot (talk) 05:01, 12 December 2007 (UTC)
Image:Swucampus-pic1.gif and 2
Those files were given to me a long time ago for publicity purposes. I didn't make them, so I can't make them GFDL, but they were intended for this kind of purpose but I am not currently in contact with the person who handed them to me. What license do you suggest? Thanks. Nesnad (talk) 14:11, 11 December 2007 (UTC)
I'll try to track down the person who provided these to me. But if I can't these aren't easily replaceable. This is a closed campus in South Korea. Not the easiest to acquire photos of, unlike what it seems to imply on the photos should we delete asap page. I would appreciate a waiting on the sudden delete action. And in the meantime, I'll try to get in contact with the person who provided these and see if they (or newer ones, its been years now) could be released as public domain. Nesnad (talk) 19:09, 12 December 2007 (UTC)
Pan Am Cockpit 4 image
I intend for the copy on commons to be deleted but for the copy on EN to stay. IMO I don't see how any significant use of that particular image can be lost with a fair use license. WhisperToMe (talk) 14:40, 11 December 2007 (UTC)
- In that case, it needs a more specific tag and a use rationale. —Remember the dot (talk) 05:01, 12 December 2007 (UTC)
Image:Kyushu J7W Shinden.jpg
If I recall correctly, the place I obtained the image from did not give attribution to the copyright holder. I certainly doubt I could find it now; it's been too long. Matthew Brown (Morven) (T:C) 21:02, 11 December 2007 (UTC)
Sorry Not my business I know, but didn't all items belonging to imperial Japan loose copyright after world war two? So isn't the allegation of needing a copyright over active tagging?? Seems that way to me. Nesnad (talk) 19:18, 12 December 2007 (UTC)
- I don't think that that is definitive. As far as US law is concerned, items seized by American forces and brought back to the US are probably PD here, but they probably are not in any other country (I'm going by the similar circumstances of German official photos; PD in the US, not PD in Germany or many other nations). Matthew Brown (Morven) (T:C) 03:56, 13 December 2007 (UTC)
- And I don't think that would hold for images that were not captured, nor photos that were the property of private individuals and not the state. Matthew Brown (Morven) (T:C) 03:57, 13 December 2007 (UTC)
Can I just delete all of these pages blindly, or is there any manual intervention required to determine if it needs deletion? Please reply on my talk page. east.718 at 00:12, December 15, 2007
- Just delete them all. A complete list is at User:ST47/--DUP. These are the pages that previously had WP: prefixes, but are no longer needed due to the merge with the Wikipedia namespace (see Wikipedia:Village pump (technical)#WP: vs WIkipedia:). —Remember the dot (talk) 00:17, 15 December 2007 (UTC)
- Thanks. They'll all be gone in two minutes. east.718 at 00:19, December 15, 2007
Village Pump proposal re: dates
FYI, I've offered a counter to your proposal at the Village Pump. We already have the technology to fix the inconsitency problem for all readers without any article changes, we just need to take advantage of it by setting a default date format. Bugzilla:12318 has been opened requesting this be done. RossPatterson (talk) 21:47, 16 December 2007 (UTC)
autoformatting of full dates
Thanks for your input at MOSNUM. I wonder whether the developer is finally responding to the activity at MOSNUM. Tony (talk) 00:55, 19 December 2007 (UTC)
Begin forwarded message:
From: email@example.com Date: 18 December 2007 1:27:27 PM To: firstname.lastname@example.com Subject: [Bug 4582] Use date format preference on unlinked dates
Brion Vibber <email@example.com> changed:
What |Removed |Added
Status|RESOLVED |REOPENED Resolution|WONTFIX |
--- Comment #73 from Brion Vibber <firstname.lastname@example.com> 2007-12-18 02:27:25 UTC --- Let's keep it open for now and see what happens...
Image:Kutuzov Belarus-Slovenia 2005.jpg
thanks for the notice. I asked site owner to relicense the image to wikipedia under suitable license. Give me few more days, please. --Monk (talk) 07:12, 19 December 2007 (UTC)
firefox svg
source provided
"will only work in browsers that support XHTML (not HTML) and SVG integration."
firefox does not support SVG natively in html - only in xhtml.
thanks LNRyan (talk) 03:00, 23 December 2007 (UTC)
Thanks for the pointer on signing! And thanks for the welcome! LNRyan (talk) 03:00, 23 December 2007 (UTC)
Re re RFA
Please excuse my late reply once again. The answer to your last question is yes; please feel free to notify me if you have another RFA. Cheers, heqs ·:. 11:39, 22 December 2007 (UTC)
TfD nomination of Template:Cite press release/doc2
- re: 'Template:Cite press release/doc2' has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for Deletion page. Thank you. —Remember the dot (talk) 02:39, 23 December 2007 (UTC)
- Thanks Dot... Good catch ferreting that one out... that was an old proposal that didn't fly with the community. I also db-authored a few more, and apologies for not tidying up sooner when the discussion died out on that idea. // FrankB 19:38, 23 December 2007 (UTC)
Congrats on FA status for Opera
Nicely perservered, that looked like a long FA Candidacy! I hope to see more articles of that caliber in the future- Congratulations! --Kiyarrllston 01:04, 24 December 2007 (UTC)
- Thanks! I'm happy about it too, especially since there are relatively few computing-related featured articles. I'm also thinking about how to get Opera Mini up to featured article quality. Do you have any suggestions? —Remember the dot (talk) 01:10, 24 December 2007 (UTC)
- You asked for some feedback on Opera Mini
- "It is offered free of charge, but requires that the mobile device be capable of running Java ME applications." not quite a "but" kind of relationship
- They run Linux and "are massively parallel and massively redundant."[23] - at the very least linking to redundant and parallel - is massively a technical term as well?
- "Opera Mini supports bi-directional text, meaning that it can display text in languages such as Arabic and Hebrew." - [as well as the left to right predominant in western civilization]?
- History should start with Opera Mini's birth not with the relations it had with other browsers. - That's more context or background
- I hope this helps - feel free to ask again. :D
- --Kiyarrllston 23:27, 24 December 2007 (UTC)
Wrong approach to the image patrol
This effectively says that I attached the false license to the image. You should have checked my experience and contributions history before implying that. Also, you failed to notify me of submitting my image for deletion. Anyway, I responded to your deletion proposal at the article talk. In the future, please talk before shooting. And, a friendly advise, this aggressive attitude would unlikely help you in getting the content conscious editors to cooperate with your actions even if they are legitimate. I've seen it all but new editors might be taken aback by such approach. --Irpen 09:27, 24 December 2007 (UTC)
Same criticism about your tagging of Image:Maabarah children.jpg for deletion. You did this as a modification of its legend in the article Jewish refugees. Nothing in the talk page of the article, nothing in the page or talk of the image. Not exactly due process; I reverted it. In the future, please talk before shooting. Emmanuelm (talk) 03:14, 25 December 2007 (UTC)
I looked up what RFA means. Yeah, you'd make a fine Admin, you seem to fit the profile. Emmanuelm (talk) 03:23, 25 December 2007 (UTC)
Further work
Well your proposal went live on the Uploader which is a good thing. I'm still concerned that too many BCB images will get deleted for not having the article= tag in them. Is there some way to make Article= an optional variable in the Image Summary Template? Then the uploader could have it as a visible option, and experienced users would just know that they don't need it for free images. Mbisanz (talk) 07:47, 27 December 2007 (UTC)
- I'm afraid that this really isn't a good option. The problem here is mainly that BetacommandBot tags images for deletion rather than fixing them. The bot really ought to be rewritten to automatically add the Article parameter if it has been omitted. —Remember the dot (talk) 08:11, 27 December 2007 (UTC)
Oprah Winfrey bust
Hi Dot,
Thank you for notifying me of the listing of Image:Winfrey.JPG at Wikipedia:Possibly unfree images. Have I put the wrong licensing tag on the photo? If this is not the problem, what can I do to rectify the situation?
Neelix (talk) 18:19, 27 December 2007 (UTC)
- Hi Dot,
- Thank you for your quick response. Would this apply to Image:Walt Disney.JPG and Image:Danny Thomas.JPG as well?
Notification of image deletion
I happened across three images you tagged for deletion and posted notices to an uploader here. There has been some discussion about image deletion notification on the non-free content page and while Betacommandbot does notify the talk page of the article where an image is currently being used, you don't appear to do this. The advantage being that editors who have such a page on their watchlist may be able to fix the fair-use rationale and so avoid deletion, especially in cases where the original uploading editor is no longer active. This seems to be the case with Jtdirl and for many older uploaded images where the fair-use rationale is an issue. I have often noticed that an image was no longer available on an article page only AFTER it was already gone and only when someone marked the image on the article page as now deleted either by commenting it out or deleting the reference to it. Perhaps you would consider leaving an article talk page notification in future as this might facilitate the rescuing of many images that may otherwise go unnoticed. Obviously not knowing what an image was makes it difficult for any interested editor to decide if it might have been worth while saving by writing or fixing the fair-use rationale or been better to attempt to find a suitable replacement. I reply where I first post). Thanks ww2censor (talk) 14:55, 28 December 2007 (UTC)
- Actually now I dig a little deeper it appears that you tag the image for deletion right on the article page. If you do that every time, it is another great way to get some attention especially when the uploading editor is not active. If it is an occasional thing I would suggest doing it every time in future. Cheers and thanks ww2censor (talk) 15:07, 28 December 2007 (UTC)
- I use Twinkle, which should do that every time, yes. —Remember the dot (talk) 18:16, 28 December 2007 (UTC)
Template testing
My apologies. Larry V (talk | e-mail) 05:21, 29 December 2007 (UTC)
Image Proposals
I'm working on two new image system proposals over here User:Mbisanz/ImageSystemProposal and figured you might be interested in them either commenting or if you know coding. Mbisanz (talk) 05:57, 29 December 2007 (UTC)
IE8 Acid2 - Pass/Fail?
Hi Rtd, my edit in the section for IE8 has nothing to do with the controversy surrounding whether or not IE8 will display sites in standards mode by default, which is what Acid2 requires. The simple fact is, even in standards mode, the IE8 example videos show that IE8's development UI still displays a scroll bar which means it fails the test regardless.
So to clarify, IE8 currently fails Acid2 in both situations. Thus it is wrong for the article to state that "an internal debug build of IE8 passes the Acid2 test in IE8 standards mode" since it clearly does not. See the screencap at [1]. Hope you understand and revert to my previous version. GreyWyvern (talk) 19:57, 31 December 2007 (UTC)
- I took another look at http://www.howtocreate.co.uk/acid/ and saw:
- Note, however, that their video evidence shows a scrollbar, which means it actually fails the test. However, that seems to be a development environment UI, not the normal IE UI. As a result it may show a fail while the main IE 8 UI will pass. It is not possible to say without seeing a real IE 8 UI.
- So, it's really just speculation at this point. —Remember the dot (talk) 20:21, 31 December 2007 (UTC)
- Then if it is all just speculation, why does it say explicitly that IE8 passes? It should really say that the developers claim it passes, because there are reliable sources (the video) which cast doubt on the assertion that it passes. Is there a third party, non-MS source which says IE8 passes? GreyWyvern (talk) 20:41, 31 December 2007 (UTC)


text:
ODT Online
ODT /directory
Police are hunting for the culprits in a drive-by shooting in
Waipukurau at the weekend that left a house significantly
damaged by shotgun fire.
Police said two shots were fired from a vehicle at a home in
Racecourse Rd, Waipukurau, about 6.30pm on Saturday.
Detective Sergeant Heath Jones said a family of three adults
and two children were in the house at the time of the attack
but were all uninjured.
"It's very fortunate that no one was hurt.
"This could have had a catastrophic result."
The shots had caused damage to the exterior, and parts of the
interior, of the house.
Some of the discharge from the shotgun had gone through a
kitchen window.
A Mackie St resident told Hawke's Bay Today she heard the two
gunshots but didn't think anything of them.
"I must admit, I did hear two shots but because we've had so
many duck shooters at Hatuma Lake, it made me disregard
The resident said the house shot in the drive-by was on the
corner of Racecourse Rd and Freyburg Tce.
Mr Jones said police believed the incident was gang related
but the motivation behind the attack was "quite unclear".
Police were taking the incident "very seriously", Mr Jones
They would like to hear from anyone living in the area who
heard or saw a dark-coloured four-door sedan leaving the area
at speed.
Mr Heath said following the attack, the vehicle turned left
into Freyberg Tce and right into Mackie St.
Anyone with information can contact the Waipukurau police, or
call the Crimestoppers line anonymously on 0800 555111.
- Hawke's Bay Today
A name, residential address, and (preferably residential) telephone number is required from readers who comment on ODT Online. These details will not be visible to site visitors.
Login or Register
to add your business to the ODT/directory. Quick link to
Submit your news & photos - Login or
Opinion? Have your say - Login or Register
Submit your
event or notice
Add a photo
Bookmark ODT
Make ODT my
Otago Daily Times print and digital edition, The
Star - Dunedin, The News - Central Otago, The
Ensign - Gore, Southland Express -
Invercargill, Southern Rural Life - Otago and
Southland, The Courier - Timaru, Courier Country - Canterbury and
West Coast, Queenstown Times - Queenstown, Mountain Scene -
Queenstown, The Oamaru Mail - Oamaru, The
Greymouth Star - Greymouth, Hokitika Guardian - Hokitika,
West Coast Messenger - West Coast, The Ashburton Courier -
Ashburton, The News - North Canterbury, Extra! schools
publication, Property
Times South Canterbury

subset: commoncrawl


text:
Top Definition
To make fun of or to bring attention to one's faux pas.
"Did you see Jacks poem about rainbows?"
"Yeah. I Called him on it too."
"Yeah. I Called him on it too."
додав Seaton 19 Липня 2006
Trending Now
mispronounciation of collared
Mmm-MMM I loves me some called greens!
додав Trevbo 13 Липня 2004


text:
the best coffee
Sweet! I love this pic' simple & clean. Good!
Can i use this pic for my design plz?
I really like the angle and the simple background. It really goes nicely with the colour you picked. It makes it look older even though the mug is modern
Beautiful.. serene and inviting. Lovely work.
May I use this picture as a reference for my drawing please??????
I love this, it looks so delicious. I dont personally drink coffee because it is too strong for me, but this artwork makes me want to drink some coffee! I love the simplicity that you have captured here. I can relate to this, because of the book next to the coffee, lol the life of a university student.
so glad that you like it
thanks a lot for the comment &
thanks a lot for the comment &
Hey Sawsan you are welcome! thank you so much for the work you do, keep it coming
If you lose yourself, you lose everything.
If you lose yourself, you lose everything.
The color tone makes the elements so homogenious.
I love it
I love it
i loooooove it
Hi, I just wanted to let you know that this has been featured in this news article:- Coffee, Digital Coffee, Cake and more Food I hope you don't mind, I just love this image so much I couldn't not add it.
I love the monotones of this...very simple, understated... I like it! Nicely done.
very nice ... i love very much the way the book dissapear in the dof ... very soft effect ! very nice !
so simple and so preatty.
lovely !
Tranquilidade, calmaria, beleza. <3
so nice


text:
I am learning Django and wanted to test hosting it on an Ubuntu computer I have. I decided to serve it with Apache and mod_wsgi. I got most things working, but I have one thing puzzling me. I can access the website only from my external IP address, not from say 127.0.0.1 or my 192.168.x.x address.
My django.conf file in /etc/apache2/sites-available is
<VirtualHost *:80>
WSGIScriptAlias / /home/username/project
ServerName my_external_ip
Alias /media/ /home/username/project/media
Alias /static/ /home/username/project/static
<Directory /home/username/project>
Order allow,deny
Allow from all
If I set ServerName to 127.0.0.1 then the page only loads from there. Also I should add, it doesn't exactly "not load" when I access from other locations, it just shows an Apache page titled "Index of /" with no contents.
What is stopping Apache serving pages in all cases, and how can I make it serve pages as 127.0.0.1 etc..? Is there a better way I should host it?


text:
Video Industry News Video Company News Technology Industry News Technology Company News Novelty Industry News Novelty Company News Gay Industry News Gay Company News Legal Industry News All Company News
Released: Jun 01st, 1999
Running Time: 90
Director: Nick Orleans
Company: Ultimate
Distribution Companies: Adam & Eve Pictures
Cast: Mark Davis, Yvonne (I), China Moon, Tina Tyler, Kirsty Waay, Alicia Rio, Mike Horner, Christina Angel, Kylie Ireland, Melissa Monet
Critical Rating: Not Yet Rated
Genre: Film
A decent film for singles and couples who enjoy female masturbation and exploration of fantasies within a science-fiction setting.
Lovely visuals, pleasantly sparse dialogue and good sex can't entirely save this classy but confusing voyeuristic science-fiction sex drama. Maybe you have to have seen Dreamers 1 in order for the plot to make sense. Something about a deal between some humans and some robots and suspended animation and dreams of sex. There's plenty of sex in the dreams, and first thing these characters want when they wake up is some of the real thing. You'd think they'd want a burger or something first, but no. Lots of female masturbation, some threeways and robot suicide. What more could you want?


text:
Easy Blintz Souffle
Total Time
Prep 10 mins
Cook 45 mins
This is an easy version of my regular homemade from scratch blintz souffle.
Ingredients Nutrition
- 2 (6 count) packages cheese blintzes, defrosted
- 1⁄4 lb butter
- 1 1⁄2 cups sour cream
- 1⁄2 teaspoon salt
- 4 eggs, well beaten
- 3 tablespoons sugar
- 1 teaspoon vanilla
- 1 tablespoon frozen orange juice, undiluted (optional)
- Melt butter in an 9"x13" pan.
- Place blintzes over butter in one layer.
- Blend the other ingredients with the eggs and pour over the blintzes.
- Bake 45 minutes at 350°F or until the top starts to brown.
- The souffle can be served with powdered sugar, strawberries, or any other fruit.
Most Helpful
I've made a very similar recipe to this for years. It's great for brunch or to break the fast after Yom Kippur. The orange juice in this is a nice touch. Since my family is not crazy about cheese blintzes, I make it with fruit blintzes. Almost any combination is good. I just made it with one package of blueberry blintzes and one package of cherry. It disappeared in minutes.
Very good! I alternated cheese/apple blintzes in the pan-- and liked the apple best. Very easy and tasty. I only used 1/2 stick butter, and it was fine. I like the fact that it can be breakfast or dessert. Thanks!
It was ok, I think the vanilla was a bit over powering. I think I might have liked it better with a fruit filled blintz. The kids didn't like it at all but DH said it was good. I probably wont make it again.


text:
Only Jon could get an entire commuter train to chant "Ride! Jon! Home!" to get a girl in bed.
You must be Logged in to post a comment
The most interesting man in the world .... He doesnt always get people to shout on the train ... but when he does ... he gets laid
Go Jon!
This must be about Jon Mmmayhem, he's the most charming pervert.


text:
Reviewed by 1 customer
I ordered this piece in September and have been enjoying it in my living room for about two months. For the most part, it is sturdy and well-designed, but I did have an issue with the drawer. The piece of wood supporting the drawer was flimsy and had to be reinforced after it snapped in half (spontaneously, a few days after assembly, with nothing terribly heavy inside it). Also, the instructions were inaccurate for a few of the steps. The descriptions didn't always match what the pictures were illustrating, which was frustrating until I realized that the pictures were actually accurate.
Related Products
Crafted of solid hardwood and packed with features ...
The contrasting colors and textures of our low-profile ...
Featuring adjustable shelves behind paned glass doors, our ...
Recently Viewed Items


text:
Ahh, the memorabilia
The Handbook of Current English still comes in handy
Baby Dani takes a nap before the festivities
Sharon's cute centerpieces
The Kims catch up with Sr. Katharine Ann
A good faculty turnout!
15 out of 35 - we get almost half credit on attendance
Erin accepted a $10 bet to try on the old gym suit
Is Damon praying in the background?
Baby Ben!
The playground kept the kids amused


text:
You are using an outdated browser. Please upgrade your browser to improve your experience.
Recall - Reminders for Recommendations
Hot New Apps Of The Week
Today we're rounding up the best new apps of the week, watch the show to see them in action!
Robin Rhys
| October 16
AppAdvice App Of The Week For October 15, 2012
Keep track of entertainment releases and recommendations and delight some kids with our top app picks of the week!
Christine Chan
| October 15
It's Time To Recall All Of Those Great Recommendations
Can't remember all of those recommendations from your friends? Keep them together with this fantastic new app.
Christine Chan
| October 10


text:
- You'll save an extra 5% on Books purchased from Amazon.ca, now through July 29th. No code necessary, discount applied at checkout. Here's how (restrictions apply)
Learn more
Agile Estimating and Planning Paperback – Nov 1 2005
Amazon Price
|New from
|Used from
Kindle Edition
"Please retry"
"Please retry"
Special Offers and Product Promotions
Frequently Bought Together
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product Details
Would you like to update product info, give feedback on images, or tell us about a lower price?
Product Description
From the Inside Flap
This book could have been called Estimating and Planning Agile Projects. Instead, it's called Agile Estimating and Planning. The difference may appear subtle, but it's not. The title makes it clear that the estimating and planning processes must themselves be agile. Without agile estimating and planning, we cannot have agile projects.
The book is mostly about planning, which I view as answering the question of "What should we build and by when?" However, to answer questions about planning we must also address questions of estimating ("How big is this?") and scheduling ("When will this be done?" and "How much can I have by then?").
This book is organized in seven parts and twenty-three chapters. Each chapter ends with a summary of key points and with a set of discussion questions. Because estimating and planning are meant to be whole-team activities, one of the ways I hope this book will be read is by teams who meet perhaps weekly to discuss what they've read and the questions at the end of each chapter. Because agile software development is popular worldwide, I have tried to avoid writing an overly United States-centric book. To that end, I have used the universal currency symbol, writing amounts such as ¤500 instead of perhaps $500 or €500 and so on.
Part I describes why planning is important, the problems we often encounter, and the goals of an agile approach. Chapter 1 begins the book by describing the purpose of planning, what makes a good plan, and what makes planning agile. The most important reasons why traditional approaches to estimating and planning lead to unsatisfactory results are described in Chapter 2. Finally, Chapter 3 begins with a brief recap of what agility means and then describes the high-level approach to agile estimating and planning taken by the rest of this book.
The second part introduces a main tenet of estimating, that estimates of size and duration should be kept separate. Chapters 4 and 5 introduce story points and ideal days, two units appropriate for estimating the size of the features to be developed. Chapter 6 describes techniques for estimating in story points and ideal days, and includes a description of planning poker. Chapter 7 describes when and how to re-estimate, and Chapter 8 offers advice on choosing between story points and ideal days.
Part III, "Planning for Value," offers advice on how a project team can make sure they are building the best possible product. Chapter 9 describes the mix of factors that need to be considered when prioritizing features. Chapter 10 presents an approach for modeling the financial return from a feature or feature set and how to compare financial returns so that the team works on the most valuable items first. Chapter 11 includes advice on how to assess and then prioritize the desirability of features to a product's users. Chapter 12 concludes this part with advice on how to split large features into smaller, more manageable ones.
In Part IV, we shift our attention and focus on questions around scheduling a project. Chapter 13 begins by looking at the steps involved in scheduling a relatively simple, single-team project. Next, Chapter 14 looks at how to plan an iteration. Chapters 15 and 16 look at how to select an appropriate iteration length for the project and how to estimate a team's initial rate of progress. Chapter 17 looks in detail at how to schedule a project with either a high amount of uncertainty or a greater implication to being wrong about the schedule. This part concludes with Chapter 18, which describes the additional steps necessary in estimating and planning a project being worked on by multiple teams.
Once a plan has been established, it must be communicated to the rest of the organization and the team's progress against it monitored. These are the topics of the three chapters of Part V. Chapter 19 looks specifically at monitoring the release plan, while Chapter 20 looks at monitoring the iteration plan. The final chapter in this part, Chapter 21, deals specifically with communicating about the plan and progress toward it.
Chapter 22 is the lone chapter in Part VI. This chapter argues the case for why agile estimating and planning work and stands as a counterpart to Chapter 2, which describes why traditional approaches fail so often.
Part VII, the final part, includes only one chapter. Chapter 23 is an extended case study that reasserts the main points of this book but does so in a fictional setting.
From the Back Cover
Praise forAgile Estimating and Planning
"Traditional, deterministic approaches to planning and estimating simply don't cut it on the slippery slopes of today's dynamic, change-driven projects. Mike Cohn's breakthrough book gives us not only the philosophy, but also the guidelines and a proven set of tools that we need to succeed in planning, estimating, and scheduling projects with a high uncertainty factor. At the same time, the author never loses sight of the need to deliver business value to the customer each step of the way."
—Doug DeCarlo, author ofeXtreme Project Management: Using Leadership, Principles and Tools to Deliver Value in the Face of Volatility(Jossey-Bass, 2004)
"We know how to build predictive plans and manage them. But building plans that only estimate the future and then embrace change, challenge most of our training and skills. InAgile Estimating and Planning, Mike Cohn once again fills a hole in the Agile practices, this time by showing us a workable approach to Agile estimating and planning. Mike delves into the nooks and crannies of the subject and anticipates many of the questions and nuances of this topic. Students of Agile processes will recognize that this book is truly about agility, bridging many of the practices between Scrum and ExtremeProgramming."
—Ken Schwaber, Scrum evangelist, Agile Alliance cofounder, and signatory to the Agile Manifesto
"InAgile Estimating and Planning, Mike Cohn has, for the first time, brought together most everything that the Agile community has learned about the subject. The book is clear, well organized, and a pleasant and valuable read. It goes into all the necessary detail, and at the same time keeps the reader's burden low. We can dig in as deeply as we need to, without too much detail before we need it. The book really brings together everything we have learned about Agile estimation and planning over the past decade. It will serve its readers well."
—Ron Jeffries, www.XProgramming.com, author ofExtreme Programming Installed(Addison-Wesley, 2001) andExtreme Programming Adventures in C#(Microsoft Press, 2004)
"Agile Estimating and Planningprovides a view of planning that's balanced between theory and practice, and it is supported by enough concrete experiences to lend it credibility. I particularly like the quote 'planning is a quest for value.' It points to a new, more positive attitude toward planning that goes beyond the 'necessary evil' view that I sometimes hold."
—Kent Beck, author ofExtreme Programming Explained, Second Edition(Addison-Wesley, 2005)
"Up-front planning is still the most critical part of software development. Agile software development requires Agile planning techniques. This book shows you how to employ Agile planning in a succinct, practical, and easy-to-follow manner."
—Adam Rogers, Ultimate Software
"Mike does a great follow-up toUser Stories Appliedby continuing to provide Agile teams with the practical approaches and techniques to increase agility. In this book, Mike provides time-proven and well-tested methods for being successful with the multiple levels of planning and estimating required by Agile. This book is the first to detail the disciplines of Agile estimating and planning, in ways that rival my 1980 civil engineering texts on CPM Planning and Estimating."
—Ryan Martens, President and Founder, Rally Software Development Corporation
"With insight and clarity, Mike Cohn shows how to effectively produce software of high business value. With Agile estimation and planning, you focus effort where it really counts, and continue to do so as circumstances change."
—Rick Mugridge, Rimu Research Ltd., and lead author,Fit for Developing Software(Prentice Hall, 2005)
"Finally! The groundbreaking book my clients have been clamoring for!Agile Estimating and Planningdemystifies the process of defining, driving, and delivering great software that matters to the business. Mike's clarity, insight, and experience leap out through every page of this book, offering an approach that is relevant and immediately useful to all members of an Agile project."
—Kert D. Peterson, President, Enterprise Agile Group, LLC
"This isn't yet another generic book on Agile software development.Agile Estimating and Planningfills a gap left by most of the other books and gives you important, practical, down-to-earth techniques needed to be successful on Agile development projects."
—Steve Tockey, Principal Consultant, Construx Software
"Estimation, planning, and tracking is a trinity. If you don't do one of them, you don't need the other two. This book provides very practical knowledge for estimation, planning, prioritizing, and tracking. It should be compulsory subject matter for project managers and their teams, even if they hesitate to call themselves Agile."
—Niels Malotaux, Project Coach
"Effective planning is an important, but often misunderstood, part of any successful Agile project. WithAgile Estimating and Planning, Mike Cohn has given us a definitive guide to a wide range of Agile estimating and planning practices. With his clear and practical style, Mike not only explains how to successfully get started planning an Agile project, but also provides a wealth of tips and advice for improving any team's Agile planning process. This book is a must-read for managers, coaches, and members of Agile teams."
—Paul Hodgetts, Agile coach and CEO, Agile Logic
"Mike's writing style captures the essence of agility-just the right amount of information to bring clarity to the reader. This book provides an excellent guide for all Agile practitioners, both seasoned and novice."
—Robert Holler, President and CEO, VersionOne, LLC
"It is as if Mike took the distilled knowledge regarding planning and estimation of a great Agile developer (which he is) and laid out all he knows in an easily understandable manner. More importantly, he has a great mix of concepts with real-world examples finished off with a case study so the reader can relate the information to their own situation. Unless you are already an expert Agile planner and estimator, this book is for you."
—Alan Shalloway, CEO, Senior Consultant, Net Objectives, and coauthor ofDesign Patterns Explained, Second Edition(Addison-Wesley, 2005)
"Although I had plenty of XP experience before trying out Mike Cohn's Agile planning practices, the effectiveness of the practical and proven techniques in this book blew me away! The book recognizes that people, not tools or processes, produce great software, and that teams benefit most by learning about their project and their product as they go. The examples in the book are concrete, easily grasped, and simply reek of common sense. This book will help teams (whether Agile or not) deliver more value, more often, and have fun doing it! Whether you're a manager or a programmer, a tester or a CEO, part of an Agile team, or just looking for a way to stamp out chaos and death marches, this book will guide you."
—Lisa Crispin, coauthor ofTesting Extreme Programming(Addison-Wesley, 2003)
"Mike Cohn does an excellent job demonstrating how an Agile approach can address issues of risk and uncertainty in order to provide more meaningful estimates and plans for software projects."
—Todd Little, Senior Development Manager, Landmark Graphics
"Mike Cohn explains his approach to Agile planning, and shows how 'critical chain' thinking can be used to effectively buffer both schedule and features. As withUser Stories Applied, this book is easy to read and grounded in real-world experience."
—Bill Wake, author ofRefactoring Workbook(Addison-Wesley, 2003)
"Mike brings this book to life with real-world examples that help reveal how and why an Agile approach works for planning software development projects. This book has great breadth, ranging from the fundamentals of release planning to advanced topics such as financial aspects of prioritization. I can see this book becoming an invaluable aid to Agile project managers, as it provides a wealth of practical tips such as how to set iteration length and boot-strap velocity, and communicate progress."
—Rachel Davies, Independent Consultant
"There has been a need for a solid, pragmatic book on the long-term vision of an Agile Project for project managers.Agile Estimating and Planningaddresses this need. It's not theory—this book contains project-tested practices that have been used on Agile projects. As Mike's test subjects, we applied these practices to the development of video games (one of the most unpredictable project environments you can imagine) with success."
—Clinton Keith, Chief Technical Officer, High Moon Studios
"When I first heard Mike Cohn speak, I was impressed by a rare combination of qualities: deep experience and understanding in modern iterative and Agile methods; a drive to find and validate easy, high-impact solutions beyond the status quo of traditional (usually ineffective) methods; and the passion and clarity of a natural coach. These qualities are evident in this wonderful, practical guide. I estimate you won't be disappointed in studying and applying his advice."
—Craig Larman, Chief Scientist, Valtech, and author ofApplying UML and Patterns, Third Edition(Prentice Hall, 2005) andAgile and Iterative Development(Addison-Wesley, 2004)
"Agile Estimating and Planningis a critical guide on how to successfully provide value to customers of IT services. This book is filled with clear examples that are essential—from project team members to the executive level."
—Lou Thomas, Director, Applications Development, Farm Credit Services of America
"This work is deeply significant in that it articulates and details structured techniques to realize a simple, but profound insight—planning is an iterative quest for value, rather than a perfunctory scheduling of activities. Mike presents processes to converge on this value while reducing risk and uncertainty, supporting decision making, establishing trust, and conveying information. Agile methodologies have shifted the emphasis from plans to planning, but have glossed over many of the finer details of Agile planning. Now, very simply and accessibly, Mike demonstrates how it can be done."
—Sanjiv Augustine, Practice Director, Lean-Agile Consulting at CC Pace, and author ofManaging Agile Projects(Prentice Hall, 2005)
"The techniques described inAgile Estimating and Planninghave helped us tremendously with planning and managing our projects. It provides all you have ever wanted to know about Agile project management."
—Roman Pichler, Engineering Manager, Siemens Communications
"Mike Cohn presents a highly pragmatic and logical approach to making projects successful in a world beset by uncertainty and change. With his trademark clarity and directness, Mike cuts through the management mumbo jumbo to present practical techniques that can be put into use immediately. Put the odds squarely in your favor by making Mike Cohn the planning guru on your next big project."
—Pete Deemer, Vice President, Product Development, Yahoo!
"This book distills the fundamental ideas behind Agile estimating and planning, presenting them in a thoughtful and approachable manner. This is a 'must-have' book that presents clear, unambiguous, and practical advice for anyone who wants to successfully manage modern software development projects."
—Scott W. Ambler, President, Ambysoft Inc.
"How do your projects go? Frustrating changes? Uncertainty? Product missing both the mark and the deadline? With insight and clarity, Mike Cohn shows how to effectively produce software that is of high business value. With agile estimation and planning, you focus effort where it really counts, and continue to do so as circumstances change."
—Rick Mugridge, Rimu Research Ltd., and lead author ofFit for Developing Software
"We are true believers in the agile methods described in this book, and have experienced a substantially positive impact from their implementation and continued use. I would highly recommend this book to anyone who is interested in making their software development more practical and effective."
—Mark M. Gutrich, President and CEO, Fast 401k, Inc.
Detailed, Proven Techniques for Estimating and Planning Any Agile Project
Agile Estimating and Planningis the definitive, practical guide to estimating and planning agile projects. In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies.
Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile.
Using the techniques inAgile Estimating and Planning, you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include:
- Why conventional prescriptive planning fails and why agile planning works
- How to estimate feature size using story points and ideal days—and when to use each
- How and when to re-estimate
- How to prioritize features using both financial and nonfinancial approaches
- How to split large features into smaller, more manageable ones
- How to plan iterations and predict your team's initial rate of progress
- How to schedule projects that have unusually high uncertainty or schedule-related risk
- How to estimate projects that will be worked on by multiple teams
Agile Estimating and Planningsupports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.See all Product Description
What Other Items Do Customers Buy After Viewing This Item?
Kenneth S. RubinCDN$ 52.14
Customer Reviews
Top Customer Reviews
Overall anyone who is interested in agile project management should read this.
Mike Cohn's writing style is fantastic and easy to follow which makes the book a very quick read. I enjoyed each and every chapter.
This is a must read for aspiring SCRUM masters and product owners.
Most recent customer reviews
Look for similar items by category
- Books > Computers & Technology > Computer Science > Software Engineering
- Books > Computers & Technology > Programming > C
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Project Management > PMP Exam
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
- Books > Textbooks > Computer Science & Information Systems > Programming Languages
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering


text:
I am #SOreadytohelp
If you are looking for something to vote on, I'm looking for feedback on the tail end of my answers on Stack Overflow. Look at the lowest-scoring answers; downvotes as well as upvotes appreciated to help me decide what to keep, and what to kill.
The following isn't mine, unfortunately. The image is a clickable link to the original tweet.
0 answers
2 questions
~4k people reached
- iki.fi/era/unix/award.html
- Member for 4 years, 6 months
- 59 profile views
- Last seen Jul 9 at 9:53
Top Posts (2) All Questions Answers | Votes Newest
1 Remove duplicate smart playlists in iTunes Jan 4 '12
Badges (8)
Gold —
Silver 1
Bronze 7


text:
Nordic M&A to Accelerate on Financing, Danske's Boending Says
Nordic mergers and acquisitions, already close to last year's total after four months, will continue to accelerate as takeover financing becomes easier, Danske Bank A/S's corporate finance chief said.
Industrial companies "have come out of the financial crisis stream-lined, with strong balance sheets and are looking at Nordic assets," Anders Boending said yesterday in an interview at Danske's Copenhagen headquarters. "The M&A market is improving, but we're not back to the peak level from before the financial crisis."
In the first quarter, announced Nordic M&A deals doubled in value to $25.4 billion from the year-earlier period, data compiled by Bloomberg show. The value of European deals rose 19 percent to $261 billion and U.S. deals increased 18 percent to $354 billion. Last week, DuPont Co., the third-largest U.S. chemicals maker, said it will complete a $6.36 billion acquisition of Danish food-ingredient maker Danisco A/S.
"Lending is easing and that's benefitting M&A, in particular for private equity," Boending said. Danske, which has 60 people in its corporate finance unit, advised on 11 takeover deals last year ranking it the region's fifth-busiest local bank.
The value of announced Nordic merger transactions so far this year is $61.2 billion compared with $79.1 billion for the whole of 2010.
Fewer IPOs
Fewer Nordic companies will sell shares this year, Boending said. The value of Nordic initial public offerings is $2.82 billion so far this year. In 2010 the region was home to 4 of the 10 biggest share sales in western Europe, according to Bloomberg data.
"We're still talking to clients about IPOs, but the timing will be unpredictable," Boending said. "Global incidents are having a bigger impact on the market than previously."
ISS Holding A/S, the world's biggest cleaning service provider, withdrew a $2.55 billion IPO on March 17, citing a slump in equity markets caused by political unrest in northern Africa and Japan's nuclear disaster.
ISS is still talking with its banks, which include Danske, about the timing of a new IPO attempt, Jeff Gravenhorst, chief executive officer of the Copenhagen-based company, said in a May 12 interview.
Stockholm-based SEB AB advised on the most deals in 2011, with 32 Nordic transactions. The region had a total of 1,051 deals last year.


text:
From Booklist
"Derek Haas is a vivid and cinematic writer and THE RIGHT HAND is a roller coaster of a novel."―Jeff Abbott, author of The Last Minute and Adrenaline
"Screenwriter and novelist Derek Haas confidently strides into espionage with his adrenaline rush The Right Hand. A lean, no-nonsense plot....the vigorous pace never slows as Haas' sparse prose propels the plot that crisscrosses Europe. Haas introduces just enough spycraft to add intrigue, but never to overwhelm his story."―Oline H. Cogdill, South Florida Sun Sentinel
"Cinematic...THE RIGHT HAND never lets up."―Shawna Seed, Dallas Morning News
"Haas has crafted a lean and mean tale laced with wit, mordant insight and, at perfectly judged moments, flashes of sharp prose. He paces his tale with crack action scenes that, however well they read on the page, may soon have film directors calling "Action!" These high-octane scenes, however, never detract from Haas' canny plotting, which is capped by a final, unexpected twist and a poignant fade-out. It's not the game, but how well you play it, and Haas plays it very well indeed."―Kirkus Reviews
"Fast-paced with lots of believable action."―Deadly Pleasures
"Haas spins a riveting page-turner with just the kind of sharp dialogue one would expect from someone who writes for the movies. Readers will want to see more of Austin Clay."―Booklist
"This hard-edged contemporary spy thriller from Haas covers a lot of ground with great narrative economy. Forceful, cinematic scenes show off the lean grace of Hass's prose. Cleverly placed plot twists and spycraft details help make this a standout. Readers will hope to see a lot more of Clay."―Publishers Weekly (starred review)
"Derek Haas knows how to capture your attention with his first sentence and keep you in his thrall until his final words. THE RIGHT HAND is impossible to read in small bites. You devour it like a shark, hungry for more until you've swallowed every gob of flesh, every drop of blood. Haas doesn't know how to write a boring page; THE RIGHT HAND, like a triple shot of espresso, will keep you up all night, eyes darting back and forth, wondering how it's all going to end."―David Benioff, New York Times bestselling author of City of Thieves and The 25th Hour
"A devastatingly cool series."―New York Times Book Review, on THE ASSASSIN TRILOGY


text: I am using the Creativix theme. I would like to change the color scheme on the nav bar, slider (there are two diff color schemes), and the content area where all the articles are. Which template within the editor do I place the hex code? Is there additional code I would need to enter as well?


text:
Available formats: epub mobi pdf rtf lrf pdb txt html
Malcolm McKay has published three novels, THE LACK BROTHERS, BREAKING UP and THISTOWN (for children), as well as being a writer and director for television. His writing has always dealt with extreme behaviour and includes the controversial BBC play AIRBASE which dealt metaphorically with drug abuse on a USAF base in England (the plays was mentioned in Parliament after Prime Minister Thatcher demanded a copy). His work also includes the multi-award winning A WANTED MAN trilogy one of the first television dramas to deal in depth with the arrest, trial and pychology of a serial killer. His stage play, THE PEOPLE'S TEMPLE describes the slow descent of the Californian cult into paranoia and mass suicide. In his film MARIA'S CHILD, he graphically describes a female dancer's decision to abort her child and the subsequent doubts and difficulties of the process. Malcolm Mckay has been a writer for forty years. THE PATH is his first novel to be published as an ebook.


text:
Is there a clean way to have a different side bar, or content in the side bar for a range of pages?
I have a range of 10 products and in the sidebar I want to put the spec for each product.
The only way I can think of is to have a template for each product page and put the spec data in each template - ie. have 10 templates.
Surely there is a better way?