text:
Wikipedia talk:Collaboration of the week/Archive 3

This page contains old talk from 12 August to 29 September 2004, archived from Wikipedia talk:Collaboration of the week (previously known as Wikipedia talk:Article of the week).

Results of vote
Completely forgot about the votes which ended on 18 August.

Results

 * "Collaboration of the week" has won with 15 votes.
 * "Project of the week" obtained 10 votes, with the others much further behind.

Comments

 * The consensus is not entirely clear, particularly as multiple voting was permitted. Before making the move, would anyone who strongly objects to moving to changing the name of "Article of the week" to "Collaboration of the week" comment below.  Absent a signifiant number of strong adverse views, I would suggest that the move takes place when the next candiate is chosen at 18:00 UTC on Sunday 22 August. -- ALoan (Talk) 13:41, 20 Aug 2004 (UTC) [Some minor corrections by PFHLai 14:18, 2004 Aug 20 (UTC)]
 * Agree. -- PFHLai 14:21, 2004 Aug 20 (UTC)
 * Completely disagree. The name change will be to Collaboration because it beat even the 2nd place by a convincing number.  Votes such as the above would be agonisingly pointless and frustrating if we meet these sorts of objections time after time and nothing would ever get done on a structural level.  Incidentally, I found this page too late to vote and I think "Collaboration of the week" is an ugly, yuck title.  But I rapidly accept I am in the minority. --[[User:Bodnotbod| bodnotbod  »  .....TALK Q uietly  )  ]] 17:56, Aug 20, 2004 (UTC)
 * Er - you are in favour of the move, yes? I am not proposing another vote: Wikipedia operates on consensus, and a straight vote cut across that unless there is a clear majority.  In this case, 15:10 is hardly a convincing majority (3:1 would be a lot better).  I just want to make sure that there are no good reasons not not to make the move, and the next day or two gives us the opportunity to fund out (unless you are proposing to move the page yourself now?  Incidentally, I am away from this evening, so someone else will have to do the moves :) -- ALoan (Talk) 21:23, 20 Aug 2004 (UTC)
 * I'm in favour of the move on the basis that it won the vote. --[[User:Bodnotbod| bodnotbod »  .....TALK Q uietly  )  ]] 18:39, Aug 24, 2004 (UTC)

Results

 * "Seniority" (the status quo) has won with 13 votes.
 * "Extension" (mostly for 1 extra day / 24 hours) received 11 votes.

Comments

 * Again, the consensus is hard to determine. In order to respect everyone's views, I would suggest that the official policy ought to be to extend the deadline for 24 hours, and then to decide by seniority.  If anyone strongly objects, please comment below.  Absent a signifiant number of strong adverse views, I would suggest that the policy change becomes effective when the AotW (soon to be CotW) is chosen at 18:00 UTC on Sunday 22 August. -- ALoan (Talk) 13:41, 20 Aug 2004 (UTC)
 * Agree. Perhaps extensions, if any, should be announced at the VillagePump ? -- PFHLai 14:24, 2004 Aug 20 (UTC)
 * Excellent idea, PFHLai. —[[User:Siroxo| siro χ  o

—siroχo]] 18:51, Aug 24, 2004 (UTC)
 * Thank you, Siroxo. -- PFHLai 07:27, 2004 Aug 25 (UTC)

The add a vote or comment link
I used that link for the first time just now and was disappointed that it took me to an edit of the whole page. For me that makes the editing harder than the section editing.

Now, I suspect someone will say "ah, it's there for the new users who do not understand your wise section editing ways". Well, come on, those section edit links are pretty clear. I would have faith in new potential editors with a view to share to see that edit link and be able to intuit what it will let them do.

So, on that basis, I think the "helpful" link currently leads new users into a more difficult situation than they would otherwise be in without it. --[[User:Bodnotbod| bodnotbod »  .....TALK Q uietly  )  ]] 17:51, Aug 20, 2004 (UTC)

 * Excuse me, User: Bodnotbod, where is this "helpful" link ? It's not here on Wikipedia talk:Article of the week, right ?  Please point me to the right place.  Maybe we can fix it. Thanks.  -- PFHLai 01:38, 2004 Aug 21 (UTC)

 * No, sorry, it's on the project page itself, not this talk page. --[[User:Bodnotbod| bodnotbod »  .....TALK Q uietly  )  ]] 18:36, Aug 24, 2004 (UTC)

 * Oh, that one.... I don't like it, either. Maybe better to replace that bad link with a link that jumps to the bottom of the page.  Does anyone have any idea how to do this ?  -- PFHLai 07:33, 2004 Aug 25 (UTC)
 * I've just removed that bad link. -- PFHLai 07:49, 2004 Aug 25 (UTC)

AOTW -> COTW
I have just executed the name change and moved AOTW to COTW. Can someone check if I have missed any other pages in Wikipedia that needs editing as a result of this re-naming, please ? Thanks. -- PFHLai 14:26, 2004 Aug 23 (UTC)

Increasing needed votes per week?
At the moment we have almost 30 candidates on this page, and most of them are far from being pruned. The collaboration of the week seems to get much more attention (and therefore votes) that it got just a few weeks ago, so maybe we should increase the needed votes per week to 5 to "balance this out" a bit? --Conti|✉ 19:28, Aug 24, 2004 (UTC)

 * I agree. Furthermore, five is a better number to count. (I can't count...) However, I'd wait till after September before changing anything. We may lose a number of younger voters when their summer vacation is over.  I hope they stay, though .... then, we may need 6 votes per week ?!? -- PFHLai 20:02, 2004 Aug 24 (UTC)

 * Maybe a soft transition: old candidates keep 4 votes/week limit and candidates after day x need 5 (or 6) votes/week? Or is it a bit unfair? --Farside 21:59, 24 Aug 2004 (UTC)

 * I like this. 5 votes/week from now on, 4 votes/week for the existing nominations. Ambi 07:48, 25 Aug 2004 (UTC)

 * Oh, and one other thing I forgot. I think we need to set some sort of anti-sockpuppet guidelines. I'm inclined to suspect that a couple of these nominations have been bumped over the line a few times thanks to the use of sockpuppets. Get rid of sockpuppet votes, and I think we'll see a drop in the survival rates of nominations. Ambi 09:53, 25 Aug 2004 (UTC)

 * I agree with the 5 and the soft transition, though I'm not sure it'll make much of a difference. I don't think it's so much an issue of sock puppets keeping stuff alive as just that people see that something needs just a few more votes that day to stay in and sort of pities it another week. I've noticed surges with some of my own nominations right at the cut-off mark. Sarge Baldy 19:35, Aug 25, 2004 (UTC)

Hmm, we could increase the needed votes per week to 5 on September 1, so people will have a little more time to add to this discussion (and because it's the start of the month :-P ). --Conti|✉ 23:40, Aug 25, 2004 (UTC)

 * That's 2 days from today. Does anyone object ? -- PFHLai 02:25, 2004 Aug 30 (UTC)
 * Sounds good to me. • Benc • 17:27, 31 Aug 2004 (UTC)

I increased the needed votes per week to 5 on the CotW page now. --Conti|✉ 21:03, Aug 31, 2004 (UTC)

 * Does the new pruning policy apply to existing nominees ? Or are they under a 'grandfather clause' to continue with 4 votes per week ?  In other words, when I update the header for History of feminism, the first candidate on the COTW page right now, should it be changed to "Week 7: need 28 votes by September 8" or "Week 7: need 29 votes by September 8" ?  I suggest the latter, to speed things up.  I am now more concerned with nominated articles outgrowing their "stubbiness" after 6, 7 or even 8 weeks of voting, than with losing voters when kids go back to school. (If I don't see any objections posted here at the end of today and no one has updated the headers yet, I'll update them by adding 5.) -- PFHLai 02:40, 2004 Sep 1 (UTC)

 * If we apply the new pruning policy to existing candidates, then "History of feminism" would have needed 30 votes until today and therefore would get pruned. As proposed above, I like the soft transition, only candidates nominated after today need 5 votes per week. --Conti|✉ 10:47, Sep 1, 2004 (UTC)

 * I agree with ContiE. It's unfair to those otherwise. Ambi 11:50, 1 Sep 2004 (UTC)

 * Ah - look what happens when you go away for a week :) Yes, I was concerned that the pruning threshold would need increasing before I went away: I think the threshold should continue to be 4 votes/week for candidates nominated before 1 September but should become 5 votes/week for candidates nominated on or after 1 September. -- ALoan (Talk) 14:09, 1 Sep 2004 (UTC)

Two articles per week?
Another possibility to consider is picking two collaborations of the week. I know this was discussed earlier, but CotW traffic has increased since then. If we have enough CotWers, we might as well give them a choice of articles to work on. Livestock took 56 days to get voted up; that's a pretty good indicator that we have a glut of good candidates. One article per week may not be fast enough to prevent a continued increase in time lag. If we run short of candidates (not likely), we can eventually go back to one article per week. • Benc • 17:27, 31 Aug 2004 (UTC)

 * I am concerned with diluted attention. The quality may go down. Then, we'll have more old COTW articles for the 'Fix-it' week (below). -- PFHLai 03:05, 2004 Sep 1 (UTC)

 * I agree - I'd rather wait and see how things pan out over the next few weeks, rather than risk diluting attention. -- ALoan (Talk)

 * I'm sure I remember replying to this yesterday. I think we just can't afford to dilute what attention we do have, or we'll never get anything featured as a part of COTW. We've had some successes, but we're not there yet, and to split the effort at this stage would be the death of this. Ambi 00:09, 2 Sep 2004 (UTC)

 * The more attention the page gets and more nominations, the more likely we'll get an COTW article that will attract the maximum amount of editors - increasing the likelihood of featured status of the end result. Davodd 18:30, Sep 5, 2004 (UTC)

The tag
Should the tag be placed on the talk page of a candidate article (current policy), or on the article ? I think we should move it to the article to increase visibility. Comments, anyone ? -- PFHLai 18:23, 2004 Aug 28 (UTC)

 * Keep it on the talk page. We must remember that articles are created primarily for readers, and not editors.  There is thus a longstanding policy against adding material only relevant to editors in the article namespace. - SimonP 20:11, Aug 28, 2004 (UTC)
 * What about the tags ?  They are almost 'ubiquitous'.  It's a way to invite readers to participate in improving what they read by becoming editors. I don't see much problem with having one extra line on the article. It's temporary, anyway. -- PFHLai 21:29, 2004 Aug 28 (UTC)
 * How about modifying the tag for a COTW candidate ? -- PFHLai 21:46, 2004 Aug 28 (UTC)
 * I agree that if the message is directed at editors, it can still go in the article space as it could well turn readers into editors... and isn't that what we want to do wherever possible? TPK 05:20, 29 Aug 2004 (UTC)
 * Hmm... I'm generally opposed to tagging articles except when absolutely necessary. OTOH, there will only be one article with on it at a time. I don't see the harm; why not? • Benc • 17:30, 31 Aug 2004 (UTC)

 * I am aware of the policy against adding materials in the article namespace for the sake of the readers. But, if there are lots of things to read, the article won't be a stub and won't be a candidate for COTW.  I think it's okay to put one line there without bothering the readers.  I am thinking of a new  tag to be place in the article namespace, right after the  tag.  Together they may expand to :
 * ''This article is a stub. You can help Wikipedia by expanding it.
 * This stub is also a candidate for collaboration of the week. Please visit that page to support or comment on the nomination.
 * I can also merge the two lines and form a new tag. Comments, anyone ?  -- PFHLai 03:02, 2004 Sep 1 (UTC)
 * I would prefer to have two separate messages, and  rather than another special stub message (just look at Template messages) but yes, adding the  flag to the article page rather than the talk page - like  would be a good idea, I think. -- ALoan (Talk) 14:09, 1 Sep 2004 (UTC)

 * Whoa ! I didn't know that we have so many different Stub tags now. .....
 * Anyway, i would like to see more support (here, please) before I start moving the tag out of the talk pages and into the article page.  Are there many silent supporters of User:SimonP's view (please see above) ? -- PFHLai 00:37, 2004 Sep 3 (UTC)

 * Personally, I don't see the need for "special" stub messages for every eventuality, but there we are. If you want more support/dissent, it would be worth asking on Village Pump. -- ALoan (Talk) 10:25, 3 Sep 2004 (UTC)

Fix-it week
I was glancing over the trophy page and noticed that we have a rather abysmal track record — out of the 16 CotWs we've finished, only 2 of them are featured articles!

The main reason for this is probably that we simply forget to submit finished CotWs to Featured article candidates. However, some of the articles might not quite be feature-quality yet.

I'm was planning to look into this more and work on any CotW graduates that need it. However, I thought of a better idea: one week soon, instead of picking the article with the most votes, let's have a "Fix-it week". (Better name suggestions welcome.) The goal of this week would be to get all of these articles up to snuff, then submitting all of them to FAC.

We could work with FAC on this one, adding a notice to the top of the page to the effect of: CotW will be submitting 14 articles at once a week from now, want to help smash out the kinks early?

What do you think? • Benc • 17:45, 31 Aug 2004 (UTC)

 * I think we should submit them all anyway. Let the reviewers there help us identify the kinks in each article.  :-)
 * Then we'll know exactly what to do during the "Fix-it week".
 * BTW, shall we make it a policy to submit a COTW to Featured article candidates right after its week of collaborative makeover ? We don't need to go thru' a round of internal review, eh ? ..... -- PFHLai 03:14, 2004 Sep 1 (UTC)

 * Plenty of the finished AOTWs are far from featured article standard, and thus, are not worth submitting. However, there's several that we've done (such as Renaissance) which probably are, and I think we should get around to submitting them ASAP. There's enough of us on hand to fix up any issues that are raised. Ambi 11:55, 1 Sep 2004 (UTC)

Now, of the ones that are of potentially suitable length:

 * Diplomacy isn't bad, but it still seems a little brief
 * Medieval warfare has a poor lead section, as well as "to-do" details throughout the article
 * Cairo has a good history section, but is still so short on everything else as to be barely worth considering
 * Iranian Revolution is probably our best bet at the moment, but needs a decent lead section and pictures
 * Soup has potential, but is going to need some more fleshing out
 * but most of all, Renaissance could be nominated now, I think - it's fantastic

All the others are still significantly short of featured article length, so IMO, are no longer worth worrying about as part of this project. Ambi 12:02, 1 Sep 2004 (UTC)

Hello all - I agree that we should submit any previous AOTWs/COTWs that are up to scratch as Featured article candidates. At the moment, I should have thought that Renaissance is the best bet, but Iranian Revolution, Cairo, Baghdad, Jean-Paul Sartre, Pravda are also reasonably good, and Livestock is also looking to be good by the end of the week. Medieval warfare, Soup, Diplomacy need some work. Having just taken my first FA through the process a couple of weeks ago, I'm willing to propose one of the above - anyone else? -- ALoan (Talk) 14:09, 1 Sep 2004 (UTC)

 * I suggest proposing Renaissance now, and Iranian Revolution as soon as someone writes a lead section and finds a picture. It's pointless to nominate it before addressing things that would otherwise become inevitable objections.

 * Of the rest of the ones you mentioned, I don't think Cairo and Baghdad are suitable, for the reasons I mentioned above, and Pravda is still, while a nice article, far too short. Ambi 14:35, 1 Sep 2004 (UTC)

 * Well, first things first. I'm currently assisting with cricket on Featured article candidates, but I'll propose Renaissance if no-one else wants to.  I've added a longer lead section for Iranian Revolution - please edit at will! - but it needs pictures (there must be some of the protests, or the exit of the Shah, or return of Khomeini).

 * I agree that Baghdad and Cairo are not perfect - perhaps Peer review for them, and Medieval warfare, Soup and Diplomacy? Pravda is small but well-formed - is there more to say?  Jean-Paul Sartre?  -- ALoan (Talk) 15:25, 1 Sep 2004 (UTC)

 * I agree that it's well formed, but still, too short. It's a difficult one to expand without some serious research, however. Ambi 00:14, 2 Sep 2004 (UTC)

Yeah, let's definitely submit any articles that are ready to go. I don't think we should submit them all to FAC en masse as is. A lot of them will be sent straight to Peer Review, which is already stuffed to the brim with articles needing review.

On second thought, a "fix-it week" might not be such a great idea since, as pointed out above, there are at least 10 articles needing lots of work. Working on them all at once might be a disorganized Sisyphean mess.

I'll start working on some of the ones that need a little bump to get to featured-quality in a day or two. Maybe we could add a one-liner for each article listed on /History, a brief statement about the approximate amount of work needed to get it featured? I'd really like to improve our collective brag list. • Benc • 15:34, 1 Sep 2004 (UTC)

 * That is a good idea - the two featured articles already have an extra line, so line setting out the status of the others would be a good idea.

 * We should make sure in future that appropriate ex-COTWs are proposed on WP:FAC or WP:PR immediately after they have been the COTW. -- ALoan (Talk) 16:01, 1 Sep 2004 (UTC)

 * I like ALoan's idea, but I'd caution against submitting them all to FAC. That's just going to annoy a lot of people, seeing we only have one (very nearly two) ready to go.

Okay, third time's the charm. I came up with a new idea, which I've implemented: Collaboration of the week/To do, which is just a concatenation of all the CotW articles' to-do lists. Actually, none of them had to-do lists, so I created boilerplates to be filled in by whomever feels like peer reviewing. I'll start peer reviewing within a couple days, myself — then start actually improving the articles' text. • Benc • 20:11, 1 Sep 2004 (UTC)

 * Excellent idea. :) Ambi 00:14, 2 Sep 2004 (UTC)

Well, I nominated Renaissance on WP:FAC last night: if it gets through, I will then nominate Iranian Revolution (assuming that someone finds a picture); if not, I'll try to deal with any unresolved objections. I suggest we concentrate on the next few best articles with a view to submitting to WP:PR and then WP:FAC. -- ALoan (Talk) 08:44, 2 Sep 2004 (UTC)

 * One thing that is sadly lacking in Renaissance is a proper discussion "literature and poetry" (currently section 3.5) - if anyone can flesh it out, I'd be grateful (it is also in the to do list). -- ALoan (Talk) 13:57, 3 Sep 2004 (UTC)
 * I'll do I've done what I can could, though I'm no expert. • Benc • 01:43, 4 Sep 2004 (UTC)

Changing headings
I propose that we change the headings of the CotW page. The ToC looks very confusing and is pretty big at the moment, so I propose that we merge the title of the nomination and the date when it will be pruned. I also propose to tally the needed votes to avoid pruning immediately and not weekly. So "July 21 (Week 7: needs 28 votes by September 8)" and "History of feminism" would be merged into "History of feminism (needs 32 votes by September 15)". As the candidate already has 28 votes by now the heading should be changed accordingly. Another example would be "Gestapo (needs 40 votes by October 21)". It already has 37 votes, and I don't really see why the heading should still say that it might get pruned in a few days when it is clear that that won't happen. The drawback of this would be that every candidate needs to get its own individual heading, even when they are started on the same day. What do you think? --Conti|✉ 01:06, Sep 4, 2004 (UTC)

 * Good idea. I agree that the headings are an eyesore as is. I support your proposal to do away with the "September X (Week Y: needs Y*Z votes by September X+Y*7)" section headers. (Where Z = 4 or 5, depending on when the article was nominated.) However, I don't think we need the "(needs Y*Z votes by September X+Y*7)" in the header at all. Pruners have to scroll down to the section to see the vote count anyway, so why not keep the section headers clean?

 * To illustrate, instead of this:

 * Let's do this:

 * I'm okay with the idea of tallying the votes at any time as part of the pruning process, though this shouldn't be mandatory. In any case, pruning will remain a daily task, right? The votes will always be re-tallied then anyway. Instant tallying seems like a little bit of extra work — arguably a form of instruction creep, which is a Very Bad Thing (TM). • Benc • 02:00, 4 Sep 2004 (UTC)

 * Side note: removing the pruning date from the section header would make the page cleaner, but a small bit harder to prune. However, pruners can simply search for "September 9" (Ctrl-F on IE) to find all articles needing pruning that day. • Benc • 02:26, 4 Sep 2004 (UTC)

 * I also propose deprecating the practice of adding "Reason for removal: Lack of votes after Y weeks. ~ ", in favor of simply adding "(X votes over Y weeks)" or "(not a stub)" to the section header. Less work for pruners. • Benc • 02:39, 4 Sep 2004 (UTC)

 * This sounds ok too, but do we really need to mention on which week the candidate is and how many votes it needs per week? Usually every candidate needs the same amount of votes per week, so this doesn't really needs to be mentioned IMHO. I agree that tallying shouldn't be mandatory, everyone who wants to tally the votes if needed should feel free to do so though. I also agree on the proposed procedure for the removed candidates. --Conti|✉ 12:25, Sep 4, 2004 (UTC)

 * Implemented. To avoid confusion, I think we should still mention how many votes each candidate needs per week, at least until all the pre-September 1 candidates are either promoted or pruned. • Benc • 01:06, 9 Sep 2004 (UTC)

 * Sounds ok to me. If no one objects, I'll tally the nominations that have enough votes to survive this week. No one should feel obliged to tally on sight, but it can't hurt either IMHO. --Conti|✉ 16:14, Sep 9, 2004 (UTC)

Increased growth of this page
We're starting to see rather significant growth in nominations, and more than that, rather significant growth in votes. This page is going to become very, very long if all these current articles hang on, and with the way they're going, I can't see many of the new ones getting pruned soon. I think it might be time to look at upping the pruning limit to six. Ambi 08:43, 10 Sep 2004 (UTC)

 * 4 new nominations just today, 43 nominations at the moment.. Although we just increased the pruning limit, I strongly agree. --Conti|✉ 13:40, Sep 10, 2004 (UTC)
 * Perhaps a nomination should be required to get 10 votes the first week, then 5 votes per week thereafter to sustain the nomination? Davodd 14:44, Sep 10, 2004 (UTC)
 * I've been worrying about this, there are far too many - and the entire thing is working too well, articles are taking so long to win the vote that they're being expanded well beyond stub status. I suggest we seriously crack down on the articles nominated, make it so articles HAVE to be stubs or they'll be withdrawn immediatly (no "this section needs expanding" or "this article isn't quite good enough"). Tom- 14:55, 10 Sep 2004 (UTC)
 * How do we define a stub? A paragraph or less of information? Davodd 16:42, Sep 10, 2004 (UTC)

 * Yes, the page is essentially serving its purpose, in that it attracts attention to articles needing help, but then they often don't need help (or at least not help that the "average Wikipedian" could provide without major research) once they win the vote. The Find or fix a stub page defines a stub as generally one paragraph, and also suggests a threshold of 200 characters (which seems REALLY short to me). Maybe we could be a little more lax on CotW candidates -- if they grow beyond two paragraphs / 1000 characters they are "real" articles and not needing the kind of help they'd get as a CotW? -- Mpolo 16:57, Sep 10, 2004 (UTC)

 * I like it that non-stubs can become COTW as well (like Gestapo). I think it would be better to raise the pruning limit, maybe even to 7 or more. --Conti|✉ 17:31, Sep 10, 2004 (UTC)
 * I tend to agree with Conti. So long as the articles aren't on for too many weeks, then they won't grow so much, and people can vote or not vote on the basis of the length and standard of the article without it growing and improving much before it becomes a CotW. Warofdreams 17:52, 10 Sep 2004 (UTC)
 * If it's not enforced, then we should remove the phrase, "This is a specific topic which either has no article or a basic stub page," from the main project page. Still, my vote is for the requirement that the article either be a stub (2 paragraphs or less or fewer than 1000 characters) or non existant at time of nomination be enforced. The idea, if I'm not msitaken, of COTW is for us to bring a stub or non article up to featured-quality in one week. Other projects already exist for non-stubs or articles that need attention or expansion. this project needs strict guidelines to set it apart from other WP projects and needs to enforce them or it will continue to become more and more out of hand and spill over into the territory of existant WP projects. Davodd 19:41, Sep 10, 2004 (UTC)

How about reducing the length of time articles are worked on? Two articles a week, or an article of the day? Warofdreams 17:57, 10 Sep 2004 (UTC)
 * Doesn't WP already have a featured daily article linked on the Main Page that anyone can improve upon? Davodd 19:41, Sep 10, 2004 (UTC)
 * Yes, but that article has to already be of a high standard. I like the suggestion below, though. Warofdreams 15:59, 11 Sep 2004 (UTC)

I'm for 1 article lasting 7 days to get maximum input from the WP community (many of whom only contribute on weekdays/weekends or once a week). I also believe that the bar should be raised on nominations (but not too high). Since most of the new nominations will never make it as far as Feminism or Space race, we should help that weeding process along by making the inital bar higher. My fear is if we set the weekly goal too high, for some quality nominations, 80 votes may not be enough to keep from being - wheras the folowing week an arictle with fewer nominations may be chosen as COTW. My proposal: The nomination must be a stub or non-existant at time of nomination and must get 10 votes or more the first week. After that, 5 votes a week to stay in the running. Also, if an article has the most nominations on the page - even if it fails to get enough weekly votes, it should not be eliminated from the running. -- Davodd 18:46, Sep 10, 2004 (UTC)

 * I think this is the best way to go. That would solve most of the issues. I also think that in most cases, we should stick to the stub rule. There's some cases, however - like Gestapo, where it's such a massive hole, particularly with top Google rank, that we really needed action. Ambi 00:34, 11 Sep 2004 (UTC)

 * I'm not completely sure about this, but let's give it a try. :-) --Conti|✉ 14:39, Sep 11, 2004 (UTC)

 * I guess there is no reason to be anal about the rules all the time... especially if no one objects to occasional bends in the rules. :) Davodd 15:29, Sep 11, 2004 (UTC)

Maybe if no-votes were added too, and after x no-votes or when there are more noes than yesses the article would be pruned. --Farside 04:49, 13 Sep 2004 (UTC)
 * We don't have any "no" votes per se — there's just those occasional comments that explain why individual users didn't vote. I don't think we should add an "oppose" section, either: (1) it would bloat the page and (2) it would make the process more political. The COTW is one of the most idealistic places on Wikipedia; it would be best to keep it that way. :-) • Benc • 06:22, 13 Sep 2004 (UTC)

How about changing 'votes' to 'committments to contribute'? Anyone posting a page would be commiting to contributing to the article if it becomes COTW and everyone voting for it ditto. This should reduce both postings and votes and ensure that the winning article has a pool of folk willing to work to improve it. Filiocht 07:59, 13 Sep 2004 (UTC)

Recent date changes

 * I've reverted the recent date changes made to this page, since its only September 10 (or maybe 11 UTC now). Somewhat confusing to have to think that far into the future.  — siro  χ  o  00:13, Sep 11, 2004 (UTC)

 * It was discussed above that such tallying should not be a problem. (I did it myself without getting reverted :) ) --Conti|✉ 00:25, Sep 11, 2004 (UTC)

 * Actually, I liked those. Allows you to see just how long it's going to survive for unless it receives more votes. Ambi 00:31, 11 Sep 2004 (UTC)

 * Note for the future: When you revert editors' edits, it is good manners to tell them so on their talk page. Not everyone is as amicable as me when they find their work reverted - especially when they have followed established procedure. Thanks for keeping the reader in mind, though. Davodd 00:34, Sep 11, 2004 (UTC)

Other COTWs
At Irish wikipedians' notice board we've begun our own "Irish COTW", with a view to perhaps having one each week. Currently it's Culture of Ireland. I created a Template:Current_Irish_COTW, emulating the format here. Now I don't know whether people approve of this or not (it's only an experiment), but I think if other interest groups were to do so also, we could expand Wikipedia "gaps" at a much faster rate than with just the main COTW.

Any opinions? zoney ♣ talk 14:52, 20 Sep 2004 (UTC)

 * Clearly, as I kind of kicked off the Irish idea, I think it's great. But it also links to thoughts I've been having about COTW in general. Currently COTW is too big and too many minority interest articles get lost after a week or two. I would propose having a number of sub-pages: COTW/Science/Arts and literature/Popular culture/History and politics/Biography for example. Then each page could set its own weekly minimum for commitments to contribute (note:not votes). That way, a lot more articles would get improved, the management of each subpage would be easier, and types of articles that currently have no hope of being COWT would be in with a shout. Also, it would reduce the number of passing interest votes by getting people to say 'I think this needs improving and I'm willing to help.' rather than 'Why not.'. Filiocht 15:03, 20 Sep 2004 (UTC)

 * I support the sub-cotw idea, it sounds great and could work very well. But I most strongly oppose the "commitment to contribute" thing. Wikipedia works because its volunteers contribute as much as they can, without having to feel guilty for "not doing enough". It's an endless bog of "he shouldn't be allowed to vote, he voted last week and didn't contribute at all and blah blah" and feeling bad for not contributing "enough". --Farside 17:37, 20 Sep 2004 (UTC)

 * It appears you are faulting COTW voting process for doing what it was designed to do - weed out topics of limited appeal. The idea behind COTW is to find topics that are very broad and appeal to the largest number of editors. That said, I do not think you need COTW to do what you want to do. But I do think that WP needs an easy way for folks who have an interest or strengths in certain areas to find each other. I believe that's why we have Wikiprojects - to address topics that appeal to a smaller segment of editors. There is nothing stopping you from having a project of the week in the Wikiprojects area dedicated to your wubject of interest. As for sub-English-language COTWs linked from this project, I oppose that idea - just as I would not support an Irish Picture of the Week process or an Irish Peer Review. Any Balkanization of primary WP projects would be detrimental to everyone. Davodd 21:30, Sep 20, 2004 (UTC)

 * I oppose balkanization of this as well, BUT concentrating a WikiProject on a particular article for a period of time is a good idea, as part of that. Just don't link it here/make it official. Ambi 21:56, 20 Sep 2004 (UTC)

Frankly, COTW is not working as it is. The stated aim is to bring articles up to featured standard, but only two winners have made it so far. So something has to change. I think what I'm suggesting is not balkanization but diversification and I suspect it will help achieve the stated COTW aim more effectively. Filiocht 07:37, 21 Sep 2004 (UTC)
 * I think the solution is simple - by supporting something, you are pledging to do significant (that is, non-trivial) amounts of editing should the article become the COTW - should be do this, we'll have to devise some kind of enforcement mechanism. Also, I think another thing that would help is if you realize that the only two articles to become featured so far were Academia and Siege, and that (a) they were really good COTWs because they are generic (that is, not requiring a lot of research - knowledgable people can write it off the top of their head), but not too broad, and (b) they had people actively pushing to make them FAs (I looked after seige personally). →Raul654 07:47, Sep 21, 2004 (UTC)
 * This is what I mean by commitment to contribute: not voting for other people to do work, but saying 'I want this article to meet FA standard and am willing to work with others to make that happen.' And these two article, benefitting from that attitude, became really good FAs. Filiocht 08:07, 21 Sep 2004 (UTC)

Getting more from COTW
I know that some of you will think this is instruction creep, as it popularily called, but listen. Our collaboration projects that run each week should have better planning. Each COTW proposal that looks like it will be selected for next week should prepare a plan on the article's talk page. This plan should be useful for the writers of the article and to make people aware of what there is to do. Also should we try to keep track of the Wikipedia orientation -- related articles, consistency of facts, gaping holes and lots of red links.

A proper plan could include a to-do list, but also all kinds of draft section structures, image sources, perhaps a list of books related, that if lucky some wikipedian has read.

Yes, I know, this is a lot to do, but you can do what ever you want out of it. I think this will take our projects farther, if we update the plan as the week progresses. Also, we have noted that not all (ehrm..) COTWs end up as featured articles; the plan should make it clear what is critically missing. ✏ Sverdrup 15:22, 21 Sep 2004 (UTC)

Let's require that all COTW nominees have a to-do list on the talk page. It's a useful tool. [[User:Neutrality|Neutrality (talk)]] 16:00, Sep 21, 2004 (UTC)

 * I agree, and should they survive, as it looks like they will, will do this for my two nominations. I think this could help us get more out of topics. Ambi 21:53, 21 Sep 2004 (UTC)

 * Disagree. Rule creep  should be kept to a minimum. Davodd 19:49, Sep 24, 2004 (UTC)
 * As I said, this is very little work for each selected COTW (only one article/Week, not every nominee). And I think it's worth it. ✏ Sverdrup 18:10, 25 Sep 2004 (UTC)
 * As many articles as possible should have a todo list when important and identifiable information is missing. To require it, however, may deter people from nominating a cotw because it involves more work. violet/riga (t) 10:36, 27 Sep 2004 (UTC)

Boldly pruning outside of established COTW guidelines
The follow pruning of topics: http://en.wikipedia.org/w/wiki.phtml?title=Wikipedia%3ACollaboration_of_the_week&diff=6113297&oldid=6113291

happened before the 7-day limit was up for these nominations and appears to be in violation of the established pruning guidelines for this project. Is it OK for an invididual editor to arbitrarily decide which nominations have merit and which do not, delete them, and not note reason why in this forum or here: Collaboration_of_the_week/Removed? Do we need to update guidelines to accomdate this sort of pruning activity or should these nominations be restored? -- Davodd 20:03, Sep 24, 2004 (UTC)

 * I've restored three of the four nominations I deleted and apologize; this was done improperly. However, I have not restored penectomy, as it was very clearly not suitable for COTW. [[User:Neutrality|Neutrality (talk)]] 20:19, Sep 24, 2004 (UTC)

 * Why is penectomy not suitable for CotW? It clearly won't become CotW imho, but that shouldn't be a reason. --Conti|✉ 22:36, Sep 26, 2004 (UTC)

 * On a similar point, and not pointing fingers, please could I encourage everyone who prunes to check the date and time when a candidate was proposed for CotW - unless unsuited to CotW (not nonexistent or a stub at time of nomination), articles should only be pruned after 7 days (14 days, etc) have passed - I interpret that as meaning the same time, 7 days (etc.) after nomination (please comment if you disagree with this interpretation).

 * In the last week or two, some candidates have been pruned before (sometimes significantly before) the deadline - for example:

 * Obstetric ultrasonography was nominated at 10:37, 17 Sep 2004 but was pruned after 1 week at 10:08, 24 Sep 2004 (29 minutes early, needing 3 votes to remain);
 * Roald Dahl was nominated at 19:06, Aug 6, 2004 but was pruned after 6 weeks at 17:29, 16 Sep 2004 (1 hour 37 minutes early, needing 2 votes to remain);
 * Abbey Theatre was nominated at 07:50, 10 Sep 2004 but was pruned after 1 week at 17:29, 16 Sep 2004 (over 12 hours early, needing 1 vote to remain);
 * Navy was nominated at 00:00, 10 Sep 2004 but was pruned after 1 week at 17:29, 16 Sep 2004 (over 6½ hours early, needing 1 vote to remain)

 * It also makes it easier to check that things were not pruned too early if the pruner adds a ~ timestamp on the /Removed page (I know "reasons for removal" are deprecated above, but I don't think it is overly burdensome to ask pruners to cut and paste a short reason and add a timestamp). -- ALoan (Talk) 02:17, 25 Sep 2004 (UTC)

 * To me, counting minutes or even hours is silly -- four weeks is four weeks, and not x hours, y minutes and 0.00 seconds. As long as the margin is less than 12 hours this is nothing, and 24-12 hours is acceptable in all cases except when it's bordeline (needs one vote more). ✏ Sverdrup 20:03, 26 Sep 2004 (UTC)

 * Exact makes more sense to me, and gives articles an equal time frame to work with. I also don't believe any article should be pruned before its time expires, I don't think it's up to anyone to decide if something is "worthy" of a nomination, so long as the item is an acceptable topic for a Wikipedia article at all (premature prunes being limited to nominations for things such as My Dear Great Aunt Bessie or of course doesn't meet the CotW guidelines). Sarge Baldy 01:03, Sep 27, 2004 (UTC)

Well, four weeks is 28 days is 672 hours is 40,320 minutes - you have to start and stop counting at a definite date and time, and article quite often get one or two votes in the hour or two just before a deadline passes. In principle, articles should not be pruned until the time for meeting a particular level of votes has passed. As it happens, some of these only needed one or two more votes to avoid being pruned - I've added details above. I doubt that any of these article would have become CotW, but we should be consistent (and NPOV regarding "worthiness") in applying the rules. -- ALoan (Talk) 10:20, 27 Sep 2004 (UTC)

 * I agree. I nominated Abbey Theatre and it soon became clear that it was never going to make COTW, so I went ahead and edited it myself. Nevertheless, I was quite annoyed to see it pruned early. To say 'four weeks is four weeks' is to state that this unit of time should be exactly the same for every candidate, surely? Filiocht 10:28, 27 Sep 2004 (UTC)

By way of contrast, I have just deleted Havana, which obtained 8 votes in 2 weeks (it needed 10). However, when I deleted it, it had 10 votes because two people voted for it after the two weeks were up, my thinking being that it should not have been on the list when the last couple of votes were cast, so the late votes should not retrospectively resurrect it. Comments? -- ALoan (Talk) 21:06, 28 Sep 2004 (UTC)

 * Havana should be reinstated. We should give votes for articles the benefit if the doubt, and NOT delete "by the 28th" nominations until after the "29th" starts. Sure, some nominess will be on the list longer than others, but I think it avoids voter confusion to wait until the following "day" to actually prune. - Davodd 00:38, Sep 29, 2004 (UTC)
 * I just re-added Havana. It should be the DAY of the month that counts - not the TIME of day for deadlines. Davodd 00:49, Sep 29, 2004 (UTC)

 * Well, I disagree with your reasoning (as explained above, I think articles should be pruned 7, 14, etc days after the time and date that it was nominated), but I won't delete Havana again unless the consensus is that it should go. -- ALoan (Talk) 11:10, 29 Sep 2004 (UTC)
 * I agree it would be more precise to use the time of day, but then this would need to be included in the text that says how many votes the candidate needs by when. Often people vote last-minute to get a candidate over the threshold, so the deadline needs to be specified correctly. However, I wonder whether we need to be so precise about this rule anyway -- it's just some mechanism for pruning the list of candidates, and if someone feels strongly that something should stay around despite one or two votes being a couple of hours late, why not let it stay around and prune it if it fails to get enough votes a week later. If it does get them, fine, it was just having a bad week in between. Fpahl 14:42, 29 Sep 2004 (UTC)

 * I actually commited an act of self-pruning (Duck and Cover) after I was told it wouldn't work because it wasn't a stub. -Litefantastic 14:50, 29 Sep 2004 (UTC)

Space Race tally
So far, this topic attracted the most edits and the most editors of any of the COTW.

 * 1) September 19 2004: Space Race (46 votes over 28 days)
 * 2) * 132 edits made by 43 editors (including 7 anonymous IPs)
 * 3) *Size increased from 25 bytes to 73 bytes (size for entire HTML source).

Not only that, but much of the generic space content added to Space Race but not germane to the topic was moved to space exploration. See how that article also was transformed by COTW here.

Wasn't vinegar listed here yesterday?
It seemed like a do-able project. Another do-able suggestion, although sadly also US-centric, is the broad and deep topic of the Federal Bureau of Investigation. jengod 01:45, Sep 29, 2004 (UTC)
 * Never mind. Found /Removed. jengod 01:47, Sep 29, 2004 (UTC)


text:
Danny Morrison (cricketer)

Daniel Kyle Morrison (born 3 February 1966) is a New Zealand cricket commentator and former cricketer. He specialized as a pace bowler with a useful outswinger. He made his test debut for New Zealand in 1987 at the age of 21 against Australia.

International career
His most notable bowling accomplishment occurred on 25 March 1994, when he took a hat-trick in a One Day International (ODI) against India. He is one of only three New Zealanders and twenty-two players worldwide to have taken an ODI hat-trick.

On 28 January 1997, Morrison made his final appearance for his national team, and contributed 14 runs in a 106-run partnership with Nathan Astle for the tenth wicket against England, to save the match. He was dropped from the team after the match.

During his international career, Morrison played for New Zealand in three Cricket World Cups - 1987, 1992 and 1996.

After cricket
Since his departure from international cricket, Morrison has been employed in numerous cricket-related positions. These include:
 * Commentator of TVNZ, Sky Sports and Fox Sports
 * Commentator of the Indian Premier League
 * Commentator of the Bangladesh Premier League
 * Commentator of the Pakistan Super League
 * Commentator of the Caribbean Premier League
 * Commentator of the Abu Dhabi T10 League
 * Host of Sky Sports "Cricket Company" show for 7 years
 * Host of radio show on Radio Sport for 6 years
 * Charity work including the 'Fight for Life' – Meningitis appeal
 * Involved in coaching for schools and clubs
 * Guest speaker
 * Batter/Bowler for the official New Zealand Beach Cricket team in 2008 and 2009

Personal life
Morrison currently lives on the Sunshine Coast, Australia, moving there in 2006 with his wife, Kim Morrison and children, Jacob and Tayla.

Autobiography
Morrison released an autobiography after his retirement named Mad As I Wanna Be that was published in 1997. This received generally positive reviews although outspoken New Zealand Cricket commentator Richard Whiting described the overall tone of the book as 'mental'. He has also written a book called the Danny Morrison Junior Cricket Diary as an aid for aspiring young cricketers.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Danny Morrison (cricketer)


text: User talk:138.232.1.229

title: User talk:138.232.1.229


text:
John Houghton (physicist)

Sir John Theodore Houghton (30 December 1931 – 15 April 2020) was a Welsh atmospheric physicist who was the co-chair of the Intergovernmental Panel on Climate Change's (IPCC) scientific assessment working group which shared the Nobel Peace Prize in 2007 with Al Gore. He was lead editor of the first three IPCC reports. He was professor in atmospheric physics at the University of Oxford, former Director General at the Met Office and founder of the Hadley Centre.

He was the president of the John Ray Initiative, an organisation "connecting Environment, Science and Christianity", where he has compared the stewardship of the Earth, to the stewardship of the Garden of Eden by Adam and Eve. He was a founding member of the International Society for Science and Religion. He became the president of the Victoria Institute in 2005.

Biography
Born in Dyserth, John Theodore Houghton was the second of the three sons of Sidney and Miriam (née Yarwood) Houghton. His older brother, David (died 2015), became a meteorologist. The third and youngest brother, Paul Houghton, became a lecturer in engineering and was treasurer and company chairman of the John Ray Initiative, connecting the environment, science and Christianity.

The family moved to Rhyl when John was two, and he attended Rhyl Grammar School where he discovered his interest in science. He continued his education at Jesus College, Oxford, gaining a BA in 1951, MA (Oxon) and DPhil in 1955.

He was brought up as an evangelical Christian by devout Christian parents and believed in science and Christianity as strengthening each other, as well as Christianity and environmentalism. Houghton's evangelical Christianity combined with his scientific background made him a significant voice in evangelical Christian circles. He was a supporter of and advisor to the international Christian relief and development agency Tearfund. He was also an elder at Aberdovey Presbyterian Church.

In 1962, Houghton married Dr Margaret Broughton, daughter of a mill owner in Colwyn, Lancashire, and they had two children and seven grandchildren. Following her death from cancer in 1986, he set up the Margaret Houghton Memorial Fund, a research unit on medical nursing in her memory. His second wife, Sheila, became his companion for almost thirty years.

Posts include:
 * a Member of the UK Government Panel on Sustainable Development (1994–2000)
 * Chairman, Royal Commission on Environmental Pollution (1992–98)
 * Chairman or Co-Chairman, Scientific Assessment Working Group, Intergovernmental Panel on Climate Change (1988–2002)
 * Director General (later Chief Executive), UK Meteorological Office (1983–91)
 * Director Appleton, Science and Engineering Research Council (also Deputy Director, Rutherford Appleton Laboratory)(1979–83)
 * Professor of Atmospheric Physics, Oxford University (1973–83).

He was knighted in 1991. Houghton was an Honorary Scientist of the Hadley Centre for Climate Prediction and Research at the Met Office (since 2002); Honorary Scientist at the Rutherford Appleton Laboratory (since 1991); a Trustee of the Shell Foundation (since 2000); Chairman of the John Ray Initiative (since 1997) and in 2013 was announced as an Advisory Board member for Sure Chill Technology. He moved back to Wales and lived in Aberdyfi. In 2007 he criticised the controversial documentary The Great Global Warming Swindle for its inaccuracies.

He died of complications from COVID-19 on 15 April 2020, aged 88.

Awards and honours

 * Albert Einstein World Award of Science (2009)
 * Japan Prize (2006)
 * International Meteorological Organization Prize (1998)
 * American Meteorological Society, Honorary Member (1998)
 * Gold Medal of the Royal Astronomical Society (1995)
 * Global 500 Award, under the United Nations Environmental Programme (1994)
 * Bakerian Lecture of the Royal Society (1991)
 * Knight Bachelor (1991)
 * Symons Gold Medal, Royal Meteorological Society (1990)
 * Richard Glazebrook Medal and Prize, Institute of Physics, (1990)
 * William Gaskell Medal of the Royal Meteorological Society, (1983)
 * The Chree medal and prize (1979)
 * President of the Royal Meteorological Society (1976–1978)
 * Elected Fellow of the Royal Society (1972)

He received Honorary Doctorates of Science from the Universities of Wales (1991), Stirling (1992), East Anglia (1993), Leeds (1995), Heriot-Watt (1996), Greenwich (1997), Glamorgan (1998), Reading (1999), Birmingham (2000), Gloucestershire (2001), Hull (2002) and Dalhousie (2010). He was an Honorary Fellow of Jesus College, Oxford, University of Wales, Aberystwyth and of University of Wales, Lampeter and was also a Founding Fellow of the Learned Society of Wales.

Legacy
A metal sculpture of Sir John Houghton was erected in Rhyl in 2013, together with figures of two other local celebrities, Don Spendlove and Mike Peters.

Selected publications

 * Does God Play Dice? 1988, Intervarsity Press
 * Global Warming, the Complete Briefing, 1994, Lion Publishing (2nd edition 1997, Cambridge University Press; 3rd edition 2004, Cambridge University Press; 4th edition 2010, Cambridge University Press; 5th edition 2015, Cambridge University Press)
 * The search for God; can science help? 1995, Lion Publishing
 * Physics of Atmospheres, 1977. 2nd edition 1986, 3rd edition 2002, Cambridge University Press.
 * Climate Change, the IPCC Scientific Assessment, eds J.T. Houghton, G.J. Jenkins and J.J. Ephraums, 1990, Cambridge University Press
 * Climate Change 1992, the Supplementary Report to the IPCC Scientific Assessment, eds. J.T. Houghton, B.A. Callander and S.K. Varney, 1992, Cambridge University Press
 * Climate Change 1994, Radiative Forcing of Climate Change and an Evaluation of the IPCC IS92 Emission Scenarios, eds. J.T. Houghton, L.G. Meira Filho, J. Bruce, Hoesung Lee, B.A. Callander, E. Haites, N. Harris and K. Maskell, 1994, Cambridge University Press
 * Climate Change 1995, the Science of Climate Change, eds. J.T. Houghton, L.G. Meira Filho, B.A.Callander, N. Harris, A. Kattenberg and K. Maskell, 1995, Cambridge University Press
 * Climate Change 2001, The Scientific Basis, eds J.T. Houghton, Y. Ding, D.J. Griggs, M. Noguer, P.J. van der Linden, X. Dai, K. Maskell, C.A. Johnson, 2001 Cambridge University Press

Misquotation
In a November 2006 article in Australia's The Daily Telegraph, journalist Piers Akerman quoted Houghton as saying "Unless we announce disasters, no one will listen", attributing the quotation to his 1994 book Global Warming, The Complete Briefing. This has since been quoted by many deniers, including Benny Peiser and Christopher Monckton, and is listed at the top of the front page of Christopher Booker's The Real Global Warming Disaster. However, the quotation does not appear in any edition of Houghton's book. Houghton never said any such thing and believed the opposite. The publishers of The Real Global Warming Disaster, The Continuum International Publishing Group, apologised for the reference to that quotation, confirmed (in addition to Booker's confirmation) that it will not be repeated, and agreed to place a corrigendum in any further copies of the book.

In an article which appeared in The Sunday Telegraph on 20 February 2010, Christopher Booker purported to correct the misquotation contained in The Real Global Warming Disaster but this article contained yet further inaccuracies. As a result, Houghton referred the matter to the Press Complaints Commission (PCC Reference 101959). Following the PCC's involvement, The Sunday Telegraph published on 15 August 2010 a letter of correction by Houghton stating his true position. An article supportive of Houghton also appeared in the edition of 21 May 2010 of New Scientist.

The correct quotation was, "If we want a good environmental policy in the future we'll have to have a disaster. It's like safety on public transport. The only way humans will act is if there's been an accident."

title: John Houghton (physicist)


text:
Project team

In a project, a project team or team is defined as "an interdependent collection of individuals who work together towards a common goal and who share responsibility for specific outcomes of their organizations". An additional requirement to the original definition is that "the team is identified as such by those within and outside of the team". As project teams work on specific projects, the first requirement is usually met. In the early stages of a project, the project team may not be recognized as a team, leading to some confusion within the organization. The central characteristic of project teams in modern organizations is the autonomy and flexibility availed in the process or method undertaken to meet their goals.

Most project teams require involvement from more than one department, therefore most project teams can be classified as cross-functional teams. The project team usually consists of a variety of members often working under the direction of a project manager or of a senior member of the organization. Projects that may not receive strong support initially often have the backing of a project champion. Individual team-members can either be involved on a part-time or full-time basis. Their time commitment can change throughout the project depending on the project development stage.

Project teams need to have the right combination of skills, abilities and personality types to achieve collaborative tension. Teams can be formulated in a variety of ways. The most common method is at the discretion of a senior member of the organization.

There are many components to becoming a top-performing team, but the key is working on highly cooperative relationship. The job of management is to foster a relaxed and comfortable atmosphere where members can be themselves and are engaged and invested in the project work. All team members are encouraged for relationship building. Each member is responsible to give constructive feedback, recognize, value and utilize unique strengths of each other. The whole team is tuned trust and cooperation.

title: Project team


text:
Deborah Coddington

Deborah Leslie Coddington is a New Zealand journalist and former ACT New Zealand politician.

Pre-political career
Coddington, born in Waipukurau, worked from 1973 to 1984 as a magazine journalist, but in 1985 moved to Russell, a town in the Bay of Islands, where she owned and operated a café and restaurant. In 1989, she returned to journalism, writing for the Metro and North & South magazines. In 1993, she became a broadcaster, working for the BBC World Service's New Zealand operation. She then returned to magazines, becoming senior feature writer for North & South. In 2002, she won the Qantas Senior Feature Writer of the Year Award for her work.

From 1978 to 2004, her partner was the controversial publisher Alister Taylor, with whom she had three children.

Entry into politics
Coddington first became involved in politics in the context of the Libertarianz party, and in the 1996 election and the 1999 election, the Libertarianz ranked her second and third, respectively, on their party list.

At the 1998 local elections she stood for a seat on the Auckland Regional Council in the Auckland Isthmus Ward ward as an Auckland Now ticket candidate, but was not elected.

Member of Parliament
Later, however, Coddington transferred her support to the ACT New Zealand party, which ranked her sixth on its party list in the 2002 election, high enough for her to enter Parliament as a list MP.

Many New Zealanders know her as the compiler of a register of sex-offenders which aims to publicly identify those convicted of sex-crimes. This register, first published in 1996, generated considerable criticism from those who alleged it breached the rights of criminals named in it. She has also published a registry of convicted child molesters in Australia. Coddington has also had a high amount of media interest in her personal life – early in 2004 journalists widely canvassed the financial problems of Alister Taylor, her partner (and her subsequent split from him), and later the same year, the media reported Coddington's distress about attention received from Roger Kerr, the executive director of the New Zealand Business Roundtable. Kerr allegedly chased her drunk, across the grounds of parliament. Coddington described the media's portrayal of events as "wildly overblown".

On 15 April 2005, Coddington announced that she would not seek re-election in 2005. In the announcement, she said that she did not regret entering politics, but said that she was no longer as eager to fight political battles. Coddington attributed her change in perspective primarily to her recent marriage to Wellington lawyer, Colin Carruthers QC.

Return to journalism
Coddington returned to journalism, writing for the Herald on Sunday and North & South. In 2019, Coddington was a judge for the Voyager Media Awards.

Controversy
In November 2006, Coddington published an article, "Asian Angst", in North & South magazine, questioning immigration and referencing the high profile of "Asian" crime, talking of a "gathering crime tide" and an "Asian menace". Coddington's article attempted to justify this language by pointing to a 53% increase in police arrest figures for "Asians" over the last 10 years. However she neglected to mention that the corresponding overall "Asian" population had increased by more than 100% in that time and that the arrest rate among that "Asian" population (which was already very low compared to the general population) had halved. A member of the general population was now four times more likely to be arrested than an "Asian".

Outraged reaction swiftly followed, and formal complaints to New Zealand Press Council came from the Asia New Zealand Foundation, the head of Journalism at Massey University and a consortium of mostly academics, journalists and ethnic Asian community leaders led by Tze Ming Mok.

The following month, the New Zealand Press Council condemned Coddington's article and ordered North & South to print an apology.

The Press Council found the language of the article "misleading" and "emotionally loaded". The Council stated that even though journalists are "entitled to take a strong position on issues they address ... that does not legitimise gratuitous emphasis on dehumanising racial stereotypes and fear-mongering and, of course, the need for accuracy always remains".

Coddington called the New Zealand Press Council's decision "pathetic".

title: Deborah Coddington


text:
Reuthe

Reuthe is a municipality of the Bregenzerwald, in the westernmost Austrian state of Vorarlberg. It is located in the district of Bregenz. Its main industry is tourism.

Geography
One of the smallest towns in Vorarlberg, with respect to population and geography, Reuthe has an area of 10.24 km2. 53.4% of the community area is forested, 11.6% is alpland.

Culture
The '''parish church Hl. Jakobus''' was built in 1248. In 2002 a new organ was installed. Reuthe is part of the Bregenzerwald Umgang (literally "Bregenzerwald Walking Tour"). This walking tour offers insights into the architecture and community planning of 12 traditional villages in the Bregenzerwald. While walking over various landscapes, visiting public buildings, homes and everyday objects, walkers gain a comprehensive overview of typical Bregenzerwald architectural styles as they developed throughout the ages.

title: Reuthe


text:
Talk:Branch point

Re: Changed Formula
A point about the now-changed formula

 * $$F(z) = \sqrt{z} \sqrt{1-z}$$

is that it is no innocent difference, to take the square root of each factor separately; each then has a different domain of definition, so that F is actually defined a priori on the intersection of the domains. Which is to confuse the point being made with the example, really.

Charles Matthews 11:05, 15 Oct 2004 (UTC)

Mistake
Is the statement:

 * A point z0 is a branch point for a holomorphic function f(z) if and only if its derivative f ′(z) has z0 as a simple pole (i.e., a pole of order 1) − see mathematical singularity.

correct? The function $$\sqrt{z}$$ seems to be a counter example. 0 is a branch point, but its derivative is 1/2$$\sqrt{z}$$ which also has a branch point at zero, not a pole of order 1.

 * It's a strange thing to say. Branch points basically are places where the inverse function theorem fails, in this setting. So they are associated with zeroes of the derivative of the function to be inverted. Charles Matthews 09:55, 16 Jan 2005 (UTC)

 * That's funny, because I found your statement strange. :) I see your point, and I understand what you are trying to say. However, let us be rigurous.

 * Err?! The derivative of $$\sqrt{z}$$ is $$1/(2\sqrt{z})$$ which does have a simple pole at zero. —Preceding unsigned comment added by 129.97.218.32 (talk) 03:13, 4 April 2008 (UTC)

 * A branch point is not a place where the inverse function theorem fails. For the function z->z2 the inverse function theorem fails at 0, but 0 is in no way a branch point for this function. A branch point, according to what the article says, is a point where the function is multi-valued, like log z at 0.

 * The inverse of z->z2, which is the square root, does have 0 as a branch point. However, the derivative of the square root does not have 0 as a pole.

In short, there is some connection between branch points and poles, but the statement

 * A point z0 is a branch point for a holomorphic function f(z) if and only if its derivative f ′(z) has z0 as a simple pole (i.e., a pole of order 1) − see mathematical singularity.

is still wrong. I am talking wrong mathematically, that statement cannot be proved to be right, because I gave a counterexample (the second item above). Oleg Alexandrov 17:23, 16 Jan 2005 (UTC)

You are correct, of course. I was trying to put the ramification concept into quite elementary language. Charles Matthews 19:18, 16 Jan 2005 (UTC)

?
perhaps a definition? —The preceding unsigned comment was added by Rsjyufoih (talk • contribs).

Confused by Square Root Example
I find the example for the square root to be confusing. The example says that a branch point of sqrt(z) is zero, but the suggested domain ("a circle of radius 4 centered at 0") never passes through zero. The suggested domain seems to be z=4*e^(i*theta). The values of the square root for this domain trace a semicircle of radius 2 centered at 0" -- z=2*e^(i*theta/2) -- which, likewise, never passes through zero.

Elsewhere in the article: "it is customary to construct branch cuts in the complex plane, namely arcs out of branch points". This seems to suggest that the shape of the arc is determined by selecting branch points individually. Would it be accurate to say that a branch point is an intersection of the value and/or domain of the function with a branch cut?

Which would be the branch point(s) in the given example for the square root: "4+0*i" (a point in the domain) and/or "2+0*i" (a value of the function)?

Using the same subscript throughout the following statement suggests that a branch point z0 is necessarily at the origin: "a branch point may be informally thought of as a point z0 at which a 'multiple-valued function' changes values when one winds once around z0." Ac44ck 03:55, 29 May 2007 (UTC)

 * There's no "suggested domain" at all. The circle of radius 4 centered at 0 is not suggested to be the domain.  Rather, it is used for the purpose of showing why 0 is a branch point.  If you go around 0, following this path, the value of the function when you get back to your starting point is no longer what it was when you started.  That's why 0 is a branch point. Michael Hardy 21:27, 29 May 2007 (UTC)

 * The discussion in another section of this talk page seems to say, "A branch point .. is a point where the function is multi-valued." This suggests to me that there is a branch point _on_ the circle of radius 4. The article mentions a branch point only at zero.

 * The mention elsewhere in the article that branch cuts are constructed from "arcs out of branch points" suggests that it is common for a function to have several branch points.

 * If the center of the circle is the branch point in the given example, then such would seem to be the case for a circle of any radius -- and there is only one branch point for the square root function: at zero. Is this what the example is showing?
 * Ac44ck 04:26, 16 June 2007 (UTC)

That 0 is a branch point of the square root function is what it is saying. It stops short of explicitly saying "only", although "only" would be correct. Any circle that goes once around the origin will do; the number 4 was chosen for numerical convenience. Michael Hardy 00:10, 23 September 2007 (UTC)

 * Mathworld seems to say that there are an infinite number of branch points:

 * http://mathworld.wolfram.com/SquareRoot.html

 * "the complex square root function has a branch cut along the negative real axis."

 * According to the current article, branch cuts are constructed from "arcs out of branch points".

 * It seems to me that the branch point for the circle of radius 4 occurs where that circle intersects the negative real axis -- not at the origin.

 * -- Ac44ck 08:18, 23 September 2007 (UTC)

 * Some confusion here. A point on a branch cut will be a kind of jump point, but is not what is known in the trade as a "branch point". The branch cut is in any case a somewhat arbitrary line: after following the negative real axis for a bit, it could suddenly head off south-west. This would be an awkward way to define "square root", but would be well-defined. And the points at which the square root function then could not be made continous would be different. A branch point, on the other hand, has a meaning intrinsic to the squaring function we are trying to invert. The point 0 is a branch point because of the geometry there of squaring. Charles Matthews 09:58, 23 September 2007 (UTC)

What does this mean?
If you can explain what the following means, then probably the section is alright:
 * A point z in the domain of f is said to be a branch point of f if the value of f at z differs depending on its argument. That is, z is a branch point of f if and only if for two particular arguments θ1 and θ2 of z, the value of f at z is different for each.

However, please be aware that a holomorphic function of the complex variable z must necessarily have the same value whether one chooses θ or θ+2π for the argument of z. So until this matter is cleared up, the definition is unclear and non-rigorous. I suggest that it be removed, or at least clarified. In the present state, it is utterly nonsensical. siℓℓy rabbit (  talk  ) 20:58, 10 December 2008 (UTC)

Copied from silly rabbit's talk page:

OK. I will remove the first definition. The second definition probably explains it in a more formal manner.

Topology Expert (talk) 21:13, 10 December 2008 (UTC)

Better? I removed everything that is disputed and kept what is not. When we sort the issue out, we can add back what is correct. I have to sleep now so I will respond to comments tomorrow. If you still think that there are problems with this definition, please explain them. Tomorrow I will clarify definition 1 and 'holomorphic' (and anymore issues).

Topology Expert (talk) 21:18, 10 December 2008 (UTC)

Good night.

Topology Expert (talk) 21:18, 10 December 2008 (UTC)

The definition seems alright but I will have a proper look at it now.

Topology Expert (talk) 09:29, 11 December 2008 (UTC)

Some questions
Just a few questions. The formal definition section associates branch points with the original function, but the examples section associates the branch points with the inverse maps. There is a note explaining this in the formal definition section (which is helpful), but we should probably be consistent in how we introduce the branch points, do you think? For example, in the first example we could introduce the function ƒ:C -> C by ƒ(x) = x^2, deduce that 0 is a branch point, and leave some notes about the square root function. Maybe we should extend this example to the Riemann sphere, since this could easily double up as a Riemann surfaces example then too, and note that $$\infty$$ is a branch point too. I'm happy to do this if you all agree, but this brings me to my next question.

In example 2, we can't deduce that 0 is a branch point of the logarithm function using the method explained in the formal definition section, since the logarithm function isn't even defined at 0. So I'm wondering if we should modify the formal definition section a bit too? Maybe even have a complex analysis section replace this section? Then we can have examples fleshed out from each of complex analysis, Riemann surfaces and algebraic geometry, though I can't help with the last two.

In Forster's 'Lectures on Riemann Surfaces' (GTM 81), he gives the definition of a branch point as follows: Suppose X, Y are Riemann surfaces, p : X -> Y a non-constant holomorphic map. A point y in Y is called a branch point or ramification point of p, if there is no neighbourhood V of y such that p|V is injective. Looking at the Riemann surfaces section of this article and the local coordinates article, I see some similarities, but in particular, Forster doesn't seem to differentiate between ramification points and branch points. This is a bit different to our formal definition too, so I'm wondering if maybe this Forster definition isn't so widepsread? Or if it is, maybe this should be noted at some point? Cheers, Ben (talk) 12:27, 11 December 2008 (UTC)

 * Hi Ben. You make some excellent points and I must say I'm sorry that I apparently missed this thread in all of the hullabaloo.  Unheeded, I had some of these things in mind while editing this evening, and so I have probably at least partially cleared up some of the ambiguities here (although some confusion still seems to remain: see the next thread).  If it isn't too much to ask, perhaps you would care to examine the article once more with the same critical eye?

 * With regard to your last point, the Forster definition is equivalent to the one in the Riemann surfaces section. It is somewhat simpler however, and so probably should be included in the article, and stated before the more sophisticated definition involving the ramification index.  The distinction between branch points and ramification points is a fairly common one, although not universal.   siℓℓy rabbit  (  talk  ) 01:56, 12 December 2008 (UTC)

Logarithm
The singularity of the logarithm does not qualify as a branch point according to most definitions. It is not in the domain of the function, and doesn't come from any good ramified cover. It is of a special enough kind that it deserves some treatment, but separately from the main cases. However, most of the examples in the article are logarithmic branch points. I think this should be fixed. siℓℓy rabbit (  talk  ) 12:44, 11 December 2008 (UTC)
 * So what do you call a thing like that if not a branch point? Are you saying something is not a branch point unless it's in the domain, i.e. it gets mapped to some finite complex number? Michael Hardy (talk) 13:15, 11 December 2008 (UTC)

 * Domain also generally includes poles. The term "branch point" typically means what some would call "algebraic singularity" (see for instance Ahlfors).  I have heard the singularity of the logarithm referred to as a "logarithmic branch point".  It is, of course, an essential singularity rather than an algebraic pole.   siℓℓy rabbit  (  talk  ) 13:26, 11 December 2008 (UTC)

 * I don't agree with this--- the log singularity is only special because you get infinitely many values when you go around. With square root branch cuts you get two values, but
 * $$ \sqrt{x} = e^{\log(x)/2}$$

 * and exp is analytic. So the square-root branch cut (the "joe sixpack" of branch-cuts) is exactly the same as the log branch cut after some analytic gluing.Likebox (talk) 19:13, 11 December 2008 (UTC)

 * But exp is a covering map, not a ramified cover, so there is no branch point in the sense that is usually meant. Of course, there is monodromy (and so one can talk about branch cuts), but branch cuts are a different thing.  siℓℓy rabbit  (  talk  ) 19:25, 11 December 2008 (UTC)

 * The only difference between the two is that there are infinitely many values when you go around the log "branch point". The rational exponent branch points have a finite number of values, so they are special--- they can be "unwound" with a rational map. The log branch point requires a transcendental map which has an essential singularity at infinity. This is a difference, but it is not so important a difference in my opinion to declare that "log" doesn't have a branch cut.

 * If you separate the two cases, then you would also make a huge distinction between x^\alpha for \alpha rational and \alpha irrational. In the rational case, you have a ramified cover, and in the irrational case, you have the same log-singularity. When people say "branch cut" in the physics literature, they mean a continuum of poles, and the two cases are never separated--- they are both "cuts".

 * For purposes of algebraic geometry, I agree that the two cases should be separated. The right way, I think, is to give names to the two cases: finitely ramified branch cuts and logarithmic branch-cuts. The separation is like that between rational and irrational numbers, for certain idealized properties, the two are very differnt, but for applied mathematics the two continuously blend together.Likebox (talk) 23:06, 11 December 2008 (UTC)

 * I think we may actually be in agreement, then. I am not saying that logarithms do not belong here, but that they should be kept separate from the algebraic case, and that there is no need to try to give a general definition which will simultaneously address all concerns.  I think the definition for algebraic singularities is the simplest, and should go first.  Transcendental singularities seem to require the machinery of analytic continuation, and so should be second.  This also gives the article some time to motivate the introduction of analytic continuation and global analytic functions to begin with.   siℓℓy rabbit  (  talk  ) 23:37, 11 December 2008 (UTC)

(deindent) Root branch cuts also need analytic continuation, and I personally think logs are simpler. But whatever floats your boat. I think the current wording is decent.Likebox (talk) 23:54, 11 December 2008 (UTC)

 * Actually, algebraic branch points only require the notion of a covering: a branch point is the image of a ramification point. Analytic continuation is not required.  The first section of the article, after the lead, defines a branch point without any reference at all to analytic continuation.  siℓℓy rabbit  (  talk  ) 01:13, 12 December 2008 (UTC)

 * And how do you define the function on the cover? By analytic continuation from some known values. It's exactly the same in the case of the log function. You can define the Riemann surface of a "spiral staircase", and a projection onto the complex plane, and the log is single valued. There's really no difference of principle, the only difference is that you can't straighten out the singularity algebraically.Likebox (talk) 02:01, 12 December 2008 (UTC)

 * I agree that one needs analytic continuation to define the function via branch cuts. However, note that I am here only talking about the branch points.  (Isn't that what the article is supposed to be about?)  While a complete description of constructing the analytic continuation of a function in terms of its function elements is probably beyond the scope of this article, a section should probably be added somewhere on how to define analytic continuations via branch cuts.   siℓℓy rabbit  (  talk  ) 02:16, 12 December 2008 (UTC)

 * I see. Thanks.Likebox (talk) 02:20, 12 December 2008 (UTC)

Holomorphic at the branch point?
The article now says:
 * Algebraic branch points most commonly arise from functions in which there is an ambiguity in the extraction of a root, such as solving the equation z = w2 for w as a function of z. Here the branch point is the origin, because the analytic continuation of any solution around a closed loop containing the origin will result in a different function: there is non-trivial monodromy. Despite the algebraic branch point, the function w is defined and, in an appropriate sense, is holomorphic at the origin.
 * Algebraic branch points most commonly arise from functions in which there is an ambiguity in the extraction of a root, such as solving the equation z = w2 for w as a function of z. Here the branch point is the origin, because the analytic continuation of any solution around a closed loop containing the origin will result in a different function: there is non-trivial monodromy. Despite the algebraic branch point, the function w is defined and, in an appropriate sense, is holomorphic at the origin.

This seems to say that the square root function is holomorphic at the origin. In what sense is that true? Michael Hardy (talk) 23:25, 11 December 2008 (UTC)

 * I mean that the branched covering map z=w2 is defined and holomorphic over the origin as well, which is the chief feature distinguishing between the algebraic and non-algebraic cases. I'll give it another go tomorrow.   siℓℓy rabbit  (  talk  ) 00:59, 12 December 2008 (UTC)

Expert attention: branch point $$z_0$$ or $$f(z_0)$$?
There seems to be an inconsistency in the Algebraich branch points section. In the second paragraph $$z_0$$ is said to be a ramification point and $$f(z_0)$$ is said to be a branch point, whereas the third paragraph speaks of "a branch point $$z_0$$ of $$f$$". This may or may not be related to the abuse of language mentioned in the third paragraph. If it is, it needs to be made much clearer which function we are talking about at which point, and ideally different symbols should be used for points in the domain of $$f$$ and points in the domain of $$f^{-1}$$. Joriki (talk) 07:37, 10 April 2009 (UTC)
 * An anonymous user has since made some helpful improvements, but problems remain, so I've added the expert attention template again (this time for the article, since the problems are partly in the relationship between the sections). Some remaining problems are:

 * "Then g is said to be a transcendental branch point" makes no sense (g is a function) -- this should probably be either $$z_0$$ or $$g(z_0)$$.
 * The use of the term "branch point" still seems inconsistent between the sections "Algebraic branch points" and "Transcendental and logarithmic branch points". It's one thing to note that often no distinction is made between branch points and ramification points in the literature, and another to use the terminology introduced in the article within the article with a different meaning than was introduced.
 * Joriki (talk) 12:02, 19 April 2009 (UTC)
 * The use is consistent between the two sections. One speaks of branch points of the square root, for instance, and ramification points of the squaring function.  I have also removed the "expert" tag and corrected the grammatical lapse that you objected to in your first bullet point.  71.182.187.38 (talk) 11:26, 24 April 2009 (UTC)

Branch points in fields?
I'm a bit confused about the lead section of this article; to me it seems to indicate that branch points is something that only exist in complex functions. But what about scalar or vector fields? Don't branch points exist in those too? —Kri (talk) 10:38, 28 August 2016 (UTC)

Definitions are wrong, or at best imprecise
The definition in the lead makes no sense. One can say that a single-valued function is discontinuous at a point (i.e., not continuous there), but what does it mean to say that a multi-valued function is "discontinuous when going around a circuit"? Also, the definition for Riemann surfaces given later is too limited since it requires both $X$ and $Y$ to be compact. Better references need to be found. Ebony Jackson (talk) 18:15, 23 January 2021 (UTC)

 * just changed the the definition in the lead you've mentioned. this one might still be slightly imprecise and could use an expert's second opinion but it I think it's at the very least using well defined statements and much less imprecise partly because of it. Axiomatic Ginger (talk) 20:41, 27 April 2022 (UTC)

title: Talk:Branch point


text: File:Starship Troopers - movie poster.jpg