|
|
Reputation System, is now in Beta mode only, Hope many more to come. 
|
|
|
|
|
| Yes, we can certainly add it. cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Cheers,
The reporter should get +points for reporting something that is acted on by the staff/admins.
However they should get -points for something that is not deemed reportable (i.e. within the rules of the site/forum) and no action is taken. This is to stop somebody just reporting everything they see out of spite.
[Edit: Can anything that has been 'Report'ed be flagged someway, e.g. text added next to the 'Report' link to say 'This item has been reported and is queued for review'.]
|
|
|
|
|
|
I'm not exactly sure what this would look like, but I'd like to see an area on CP that would allow people to find each other to collaborate on work.
I've done quite a bit of work on a charting library (based off of zedgraph), and would like to collaborate with someone who has a lot of experience with statistical analysis (i.e. linear regression, correlation, etc). My end goal would be to use my innovations with usability, and the experience of someone with a math background to make sure I'm properly preparing the data. At the end, we both benefit from the shared code ... and perhaps write an article together.
Thoughts?
|
|
|
|
|
| We've been thinking about that for years and have a few ideas (turn articles into projects, our membership group system, adding an issue tracker) but I'd like to hear what features you feel would be the minimum to get you up and running. Once we have something you can use then we'll refine and add more features. cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris, thanks for replying to this. I hadn't noticed the Collaboration/Beta Testers section before. Looks like that forum could be a segway into a full fledged collaborative environment.
Anyway, here are a few random thoughts about development collaboration:
- A source code repository would be crucial. (think sourceforge).
- The person who started the project would be the 'owner', and responsible for granting access to the
project to other. (May also designate another user as an 'admin')
- I think it would be appropriate that CP members would be able to read the repository, but only authorized users could modify the repository.
- I'd like to see somekind of 'CP Ranking' to be enforced on allowing a CP member to create a collaboration project. (Gold member or something ... wait, am I gold? Yes, ok that's fine)
- Perhaps require that an article is written within (?? months) of creating a collaboration project. This would help you ensure that people aren't using your resources to host their own work, and help motivate them to get the work done. Some projects would be larger than others, but I think for the type of collaboration I'm interested in, max project length would be 1 month.
- Make is easy for collaboration members to share contact info (securely) with each other, so IM and/or phone calls could be exchanged as necessary.
- A message board, unique to the project, so that general questions can be asked, responded to, and not mixed with other areas of the web site.
I guess all in all, this is kind of 'SourceForgey', but to enable this to be done within codeproject would be fantastic.
If I have any other thoughts on this, I'll post. Likewise, if you have any questions/comments/feedback just let me know.
-- one other thing. As specific needs/expertise are needed on the project, allow some kind of 'Current Project Needs' section, that could be viewed for a single project, or all projects ... so CP members could check it out, and see if there's anything they could contribute on.
-- it would also be cool to allow collaborating members to rank the contribution of others.
|
|
|
|
|
| Great ideas. Thanks. cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
By the way, congrats on THE hockey game of the century.
|
|
|
|
|
| Unfortunately I didn't even get to watch the game. The entire country seemed to hold its collective breath though. It was great being here when it happened though. LOTS of happy the next day! cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Something like this would be very cool - can you imagine some of the projects that might appear as a hybrid of the coding skills of some of our notable members? Awesome!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)
|
|
|
|
|
- Integrating it with the article system, so that all that the author of an article with a corresponding project would have to do to upload the new source, is upload it and have the changes cascaded through to the article (i.e. download links automatically updated.)
- A proper diff system, so that things are easier to compare. Something which is more like the Wiki style, with line breaks.
- The ability to buy extra space. I assume that if everybody decided to create a repository, space would fill up quite quickly, so you'd have to set a reasonable limit. Offering extra space to people who need it might alleviate some of the space concern.
- Similar projects list. If somebody's looking at a text editor project, they might want to look at others.
- Project and source file rating. If a particular code file is put together very elegantly, I'd like to be able to tell them that. By averaging the scores for the code files in a particular directory, it'd be possible to provide a general rating for that directory.
- Sub-projects. The major problem with having only one repository is that if there are other repositories which use the code inside that initial repository, there would be no standardised way of telling the user that.
- Project takeover. Every 6 months or so, send out an email to the person in charge of the project, asking them to verify that they're still active; after there hasn't been any reply for a while, put the project onto a list which somebody can take over, keeping it active.
- Cross-referencing, both of source code and of articles. A pre element could be able to link to a part of a file in an article's attached repository, so that the article always has the most up to date code. Likewise, a file could link to an article which covers the theory in more detail
- Per-file permissions. It'd be an interesting way of assigning responsibilities in the repository, and would let contributors submit patch files (which would be another good addition)
That's all that I can think of for now; if I think of any more, I'll edit this post
|
|
|
|
|
Good suggestions. Thanks for you insights, and I hope Mr. Maunder has this up and running soon.
|
|
|
|
|
How would you handle contributed code?
Would the original author be required to validate/okay contributions?
The current project "lead" should be able to surrender his lead status and allow someone else to take the lead spot.
Should membership status somehow dictate who can be lead and who can't?
Should the article wizard have a new checkbox labeled "Make this a project"?
Should projects be worth more (or less) than articles in terms of reputation points?
Should project leads be awarded more points for being the lead?
Should contributors receive points for contributing?
Should the project lead be able to determine the value of a contribution (1-5), and the site award points accordingly? This would prevent someone from merely making a spelling corrcection from earning as many points as someone that fixes a bug or adds a feature.
Should contributers be limited to silver or higher? (maybe according to the combined/averaged "authority", "author", and "organizer" reputation scores).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
|
|
|
|
|
|
If I'm not mistaken that status display is still calculated with the old system.
I'm sure it will be changed to the new system soon enough
|
|
|
|
|
What was the old system?
If you have details. please provide that to me.
|
|
|
|
|
don't remember the exact numbers but your message count isn't enough to get to silver under the old system. Hence the 'none' status.
Don't worry to much about it the CP team will get it updated soon enough.
|
|
|
|
|
If I remember it right, these things are calculated once every week.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
| We're in the process of moving over to the new reputation system fully. If all goes to plan you'll see your updated status today. cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
so it is this today, not yesterday's; minor slip of plan 
suggestions:
1. apply background colors to color names in the FAQ's table explaining the statuses.
2. make that table a lot smaller and more readable, by using a simple matrix:
rows: author, authority, ...
columns: bronze, silver, gold, platinum (with background color)
cell content: points needed
3. put actual numbers under the (colored) statuses on the Who's Who page.
4. support sorting on each of the rep numbers (author, ..., total) on the Who's Who page.
PS: oh no, all rep gone again...
|
|
|
|
|
Thanks for rep numbers on personal page. Much better.
Two minor suggestions:
- you could still fit all seven of them on one line
- I would prefer alphabetical order here too (Debator is off, as it was for a while in the rep graph legend)
|
|
|
|
|
|
| Fixed. Thanks cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
