|
If someone is in for it... i too am the buyer 
|
|
|
|
|
One thing that you can do is get people to vote on your articles. I voted 5 on each one, and not because you're a regular, but because they deserved it. Maybe you just gotta make more noise, like I do. 
BTW, the CP Vanity article is absolutely great.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
modified on Tuesday, March 23, 2010 8:53 AM
|
|
|
|
|
Yhanks John.
And I'll consider that. 
|
|
|
|
|
John Simmons / outlaw programmer wrote: One thing that you can do is get people to vote on your articles
Please go through my articles too and put your precious vote!
John Simmons / outlaw programmer wrote: Maybe you just gotta make more noise, like I do
How do you do this... help me out! 
|
|
|
|
|
Thanks again for the votes. That has seriously upped my author rep and halved my gold gap.
I also changed sigs, not very noisy yet, but getting there. Any way to add sound to them?
|
|
|
|
|
I've approved your article here:
CP Vanity[^]
The Articles Needing Approval list was created to help combat the "article quality" issue. These days it serves more as a way for new authors to get feedback from seasoned authors to bring their articles up to the standards Code Project members come to expect.
This doesn't apply to you. If you can see this list, you might not have seen your article there because the list only displays the most recent five articles. Since we get about 20 or sometimes 30 articles a night, it's possible that in the submission onslaught one the Gold level article members or Code Project staff might miss an obvious gem in the rough for a few hours if you post it in the evening.
I like the idea of a link or explanation within the article about what Pending status means though. The estimated time of posting would mostly be effected by when I go sleep ... "Sean is sleeping, will be awake in 6 hrs 38 mins on average" or "Sean is driving, it is unsafe to approve articles at this time. 20 min wait on average"
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Sean Ewington wrote: estimated time of posting would mostly be effected by when I go sleep ... "Sean is sleeping, will be awake in 6 hrs 38 mins on average" or "Sean is driving, it is unsafe to approve articles at this time. 20 min wait on average"
Would be nice to read so
|
|
|
|
|
How is automatic posting enabled with regards to the new reputation system? He has eight *highly rated* articles posted, and over 54000 authority points. How is it that his articles aren't automatically posted?
Maybe the overage score of a users articles should be considered as well as the number of articles. So, if a user has between five and ten (inclusive) approved articles posted, and his average article score is above 3.5 (with at least 10 votes per article), his articles should be automatically posted. If he has more than ten articles posted, the average rating is no longer considered, and his articles are auto-posted. If he has fewer than five approved articles approved, heis new articles go into the pending queue.
Following that rule, Luc wouldn't have to wait.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
 Sounds good and appropriate...
|
|
|
|
|
John Simmons / outlaw programmer wrote: How is automatic posting enabled with regards to the new reputation system? He has eight *highly rated* articles posted, and over 54000 authority points
Auto-moderation (ie not needing to have articles moderated) kicks in at Gold. Luc is so, so close... (though I think we should change it to silver)
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thanks Sean.
I was aware of the articles-needing-approval list; some, maybe all, of my earlier articles didn't go through there either because it wasn't in place yet or because I had gold (old, overall gold) based on account age if nothing else.
But then, yesterday, I could see the articles-needing-approval list, it did contain exactly one article for most of the evening/night (as was confirmed by DaveyM69), and that one article I could not open as it wasn't approved yet, so my complaint really goes a couple of ways:
1. no feedback
my new entry was not to be seen in any list; if it is in the "articles-needing-approval" list, I do understand the home page only shows a limited number, however there should be a way to see all the entries listed somehow, no matter how many they are, so an author can at least check it is there.
2. no explanation
I could only guess what was happening, there wasn't much of a clue what I did wrong or omitted;
3. probably not enough approvers
I think you should assign approval rights to more people. If only gold authors can see and approve new entries, that is absolutely wrong IMO, as there used to be thousands of overall gold members before, and there are only an estimated 71 gold+platinum authors now (ADDED: and 134 when including silver). That would be way too restrictive, and an unnecessary bottleneck. I would suggest approval to use a voting mechanism, so an entry can get approved in several ways. An example: approval needs 10 points, a voter has (non-cumulative):
- 8 votes when he is platinum author
- 4 votes when he is gold author or platinum authority
- 2 votes when he is silver author, or gold authority
- 1 vote when he is silver authority
4. way too severe
the approval mechanism is way too severe; it was meant for screening beginners; I do remember it had (maybe still has?) an instruction along these lines: "if you think the author made a reasonable effort, by all means, do approve the article". Well, that is not supported by the mechanism you have now in place. Someone having more than 3 articles (real ones, not T&T) should not be subjected to all this anymore.
[ADDED]
5. articles not properly rewarded
the rep points earned by writing articles and collecting votes on them, does not relect the effort it takes. I can churn out ten messages in programming forums in a matter of minutes, and collect over 100 points on them. It takes a couple of days to provide a decent article. The balance is screwed.
[/ADDED]
conclusion:
I ask you to reconsider and improve the situation; I really don't feel like publishing another article under the current circumstances.
|
|
|
|
|
Luc,
Thanks for the comments.
Firstly, I'm sorry if awarding and recording reputation points now makes you feel that you no longer wish to write articles. My goal with reputation was to award those who were starting to motivate them, and to recognise those who are established to show they are true experts in the eyes of the commnunity. The reputation system was never meant to be the reason for someone posting an article: Authors should still post based on their desire to share and educate, not to simply gain a badge.
Also, the reputation system is based on small rewards from lots of users.. You wrote "I can churn out ten messages in programming forums in a matter of minutes, and collect over 100 points on them. It takes a couple of days to provide a decent article. The balance is screwed". It is correct in terms of the time taken vs rep points, but the system works over time, not instantly.
You post 100 messages and you get 100 points. Your messages are voted, maybe, and you may get more points, or if you post 100 peices of rubbish then your 100 points erodes. You post a single article and then from then on each time a member reads and up-votes your article you get points. Your article will be read and voted on way, way more than a message and so will, over time, get far more than it's initial 100 points.
This is why upvoting an article is worth far more than upvoting a message: we've designed it so that someone who posts 10 crap articles will never stand a chance of getting the points of someone who posts 10 gems. The motivation for this? It was too easy to achieve gold and platinum.
Other Points:
1,2: I have been away and so have not had enough time to review what happened. I'm jumping in here halfway through (and have not yet followed up with Sean) but my feeling is this is a usability issue our end. We will improve this
3 - no enough approvers. We've had the opposite complaint: too many approvers so that the only articles an approver sees are the poor ones. We then limited it so that poor articles, after sufficient "poor" votes, drop off the list.
4 - way too severe:. You are correct. It was too easy to get Silver before, so we chose gold. The rejigging of the system means Silver is now more appropriate. I will adjust
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Hi Chris,
yes, I have missed you being omnipresent these last couple of days.
I understand and agree with most of what you say on rep points and votes.
However, offering instant points will influence instantaneous behavior.
FYI: messages accumulate votes over time too; I have quite a collection of standard replies, and every time a fitting question pops up, I dump a standard reply and collect votes on that!
I wish to write articles and I won't stop (I have several in the works); all I said is I won't publish them on CodeProject right now as it is too much pain, I would rather spend my time on content rather than on fighting the system.
Changing the gold requirement to a silver one (for avoiding the approval list) would solve it for me, not for people who have even fewer author points (fewer articles) so far. The fundamental problem here is you try and use rep points as a quality filter, however rep points are to a large extent quantitative, they reward the number of articles; yes they also reward votes, hence quality, but that only works over time, as you just pointed out; so a recent author has a choice of creating more articles and going through the painful process for each of them, or just sit and wait for votes until he reaches the right color, then write more. That can not be what you intended? IMO you want something that measures quality from the start. Here is my suggestion:
needNoApproval=articleCount>=5 || (averageVote>=4.0 && coloredVoteCountOverall>=5)
where coloredVoteCountOverall could be the total number of unweighted up-votes by silver/gold/platinum authors and authorities (i.e. excluding new accounts and backroom debators).
The formula means a single article, appreciated by the community, is enough to open the gates; and getting 5 articles published is also good enough no matter their rating (you might bring in a rejection ratio here, however I'm not sure it is available nor necessary).
Please remember, you want to stimulate article writing, and the approval scheme got introduced to avoid the real crap. Your sentence said something like "...if the author made an effort, by all means, approve". IMO your current system does not really fit the original goals.
Chris Maunder wrote: We've had the opposite complaint: too many approvers so that the only articles an approver sees are the poor ones
We have had this conversation before. It still is my opinion that your approval scheme is completely flawed. You want to discourage and hide bad articles, and the only immediate tool you offer is an approval button. Well, if one uses that, the better articles disappear from the list and the lesser ones remain. Normally, the quality assurance department has a "reject" stamp, yours has the opposite.
Due to this situation, I have chosen to install AdBlocker and hide the articles-needing-approval list from my CP home page, as that list is tempting but always ended in a disappointing waste of time lacking the right tools. Give me a reasonable way to judge entries, and I will be happy to participate though.
IMO the major problem with unrighteous approvals is caused by historic golds. All it took to get approved was a single old account willing to click the button. I suggest you increase the number of approvers, install a voting system, and make sure not a single person (except maybe platinum) is capable of approving or disapproving. Hence my 10-point suggestion.
|
|
|
|
|
Hi Luc,
Just curious about one thing you said: "the only immediate tool you offer is an approval button." What about the Report button? Or do you not see that?
If in fact you don't see the Report button, then that is shocking. Rep points, silver, gold, platinum, etc., emit warm fuzzies, but if a serious CP member doesn't have access to a key feedback mechanism like the Report button, then this should be addressed immediately, with divine intervention if necessary.
|
|
|
|
|
Hi Hans,
I am fully aware of the report button, however:
1. it isn't clear what it does, I'm just guessing it sends a notification to the editors; and whatever it does, there is no immediate result. When voting on an article or forum message, the vote count goes up, the average gets adapted, so as a reader you have several options and see some, albeit minor, result. Other readers also see the updated average vote. Clicking "report" on an article entry has no immediate or noticeable effect.
2. it is rather extreme, and I would use that with care; to me it means "I absolutely don't want this article to appear" which is quite a strong statement; as is the "I approve" button, which basically says "no matter what others think, this article now becomes public".
|
|
|
|
|
Chris Maunder wrote: You post a single article and then from then on each time a member reads and up-votes your article you get points
Luc wrote: I can churn out ten messages in programming forums in a matter of minutes, and collect over 100 points on them. It takes a couple of days to provide a decent article
I have to agree with Luc here. Some articles can take a long long time to produce. I have a few in progress that are serious works that I have, believe it or not, spent many months working on, one of them has been over a year in progress already - meant as a study subject for myself but with a view to CP publication from the outset.
I will post them here at CP because I love the site and the philosophy - not because I want a pretty colour on my profile page! However, we have the pretty colours because they do mean something so should accurately reflect what they are rewarding. An article in itself without any votes should be worth more than 100 points. Maybe a stronger reduction if downvoted would be required to restore a balance if it's garbage if it were changed.
Dave
Binging is like googling, it just feels dirtier. (Pete O'Hanlon)
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Why are you using VB6? Do you hate yourself? (Christian Graus)
|
|
|
|
|
|
When we first released the beta version of the reputation system back in August there was a lot of discussion on the topic of how to award points on an article based on the effort put into it. It's impossible to say "an article is worth 100 times a forum posting" because one person may whip up an article in an hour, and another (like yourself) may spend months. We have no "How long did you spend on this article" field in the article wizard, and scoring an article by its length would not be realistic.
The discussions centered around trying to realistically reward authors for their actions, and the only method I could see that was fair was to have the community - those who actually use your articles - award you. If we increase the base award for articles then that applies to all articles, even the crud that gets submitted after final exam time. I, personally, don't think it's fair that an author churning out rubbish has a chance at Gold or Platinum status. It should simply be impossible for them to get it. Having the automated, one-size-fits-all award be modest means this is less likely, since the true value of the article will be in the votes, not the initial post.
This raises another side issue: what if an author spends a great deal of time on an article but it's simply of no value? It could be a long, well formatted article written over 3 months, but it could be simply the worlds most convoluted Hello World app. Our system can't (and should no) make s judgement call on this article. The readers who actually read and use the article should make the call.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Since we're now talking about metaphysical reality, how about giving each CP editor (I mean employees here) 10000 points per month, to award to articles as they see fit? Sort of like "editor's choice" rep points. Presumably, these would be awarded based on actual usefulness and merit.
|
|
|
|
|
Why not just give each Editor's choice article 250 points?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Too limited, lacks flexibility. I'm sure your editors all have different opinions, and they each see something different in an article, concerning its relative merits. Why not just trust their judgments?
|
|
|
|
|
OK, so instead of fixed points, they can vary the points?
Hmm, I dunno. I'm prefer to have those who use the articles vote on them, instead of an editor pinning a start on, say, 5 articles a month while another 20 of equal value go unrewarded. My thinking is that a jaded editor will only award an article if it's really special, and will award big. Editors only get to briefly view all the articles that come in during any given month so the combination of running out of points and missing some deserving ones will mean it's uneven coverage.
Just seems fraught with potential for lots of emails begging to have points awarded to an author's articles.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I know it's complicated, Chris - that's why you get the big bucks.
I can't give you any solid proof for this, but I'm coming to the conclusion that many CP members vote on articles based on whether it's useful to them at the present time. Maybe they think that by voting that way, they can influence what articles get written? I don't know, but I think that the CP editors will have better judgment than these idiots.
I'm sure that CP editors each have different opinions, and letting them award points separately makes sense. They are also more likely to consider the whole package: code, article text, screenshots, and design issues/background.
Yes, it's possible that an editor might overlook some articles, but by forcing the selection of only a single article, you're overlooking a lot of articles. You can still keep the present system's net result: the article with the most editor points is the editor's choice.
|
|
|
|
|
What if we could agree upon a number of articles you want awarded each month, and each editor kept putting them on a list and we collectively decided how to award points from a single pool of editors points, thereby balancing each other's jadedness out?
I am only swayed by envelopes filled with tater tots, not e-mails
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
It's the word 'collectively' that gives me pause. This is your show, but personally I would suspect that group-think begins if you all get in a meeting and try to come to a consensus. All I'm saying is, let each editor get a number of points to award as he/she wants. Or don't you think that would work?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
