Code Project Project(s) Update [long but important]
-
I was going to put my WTL Porting Project Idea into the vote but I don't think that is what you meant. I also don't think it will be one of the top three either. John
No, I have only put in the top 10. Your idea was voted a 2.8 which meant it was probably in the top 15. Keep your idea handy though, since eventually Chris is going to allow anyone to make an actual project rather than an article. Can't say how long thats going to be though.
Jason Henderson
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
-
Idea submittal and voting have come to a slow crawl or stopped altogether so we'll just say its time to chose the final three projects. We could go just by the current voting result (see below), but I think its only fair that we re-evaluate what we would really like to do. Before doing so, I'd like to give you my opinion of what we should do and I know at least Paul and Marc will agree with me. I'm not going to endorse a particular project, but rather an ideal for our first stab at this. Its called... KISS (keep it simple stupid) Whatever project(s) we choose to do, it's/their scope needs to be somewhat limited (initially for release 1.0). Rome was not built in a day and CPPs are sure to fail if we try to do too much too soon. Heck, the infrastructure for large group projects isn't even in place yet. So we have a lot of thinking to do before we "dive right in." Here is how I propose we proceed: 1) Decide on 3 projects via voting (now until Tuesday) which gives us 24+ hours 2) Pick a project leader for each project (preferrably, the originator of the idea AND someone with experience writing articles and managing a herd of cattle ;)) 3) If you want to, we can pick a CPP coordinator who will look after these first 3 projects, but I doubt we'll need one. 4) Divide up into teams (I have an idea on how to do this but we'll discuss later). There may be lopsided teams. 5) Start an article for each project. NOT QUICKLY THOUGH! I'd like to see us decide on a standard layout and "features" in our project article. Its going to have to be different somehow than a standard article (I see tables :~ ). 6) Project leaders and team members will then need to define the scope and timeline for the project. A design document would be very nice. Anyone have a nice Design Doc template? 7) Here's where the fun begins. Start coding. Project leaders should be good delegators. 8) Try to stay within the scope and timeline, giving frequent updates and screen shots. If you have any different ideas, please discuss them by replying to this message. Below this message you will see a thread for PROJECT VOTING. Within that thread are 10 messages with the title of each project. Please give a vote for each message using the message voting system. The top 3 after Tuesday morning will be our beginning proje
A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line.
- What is the official name that the projects will be published under?
- Are we working on a logo of some sorts? (the kind that can be put in an About box)
- I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects
Jason Henderson wrote: 3.8 Defect Tracking/Source Versioning (16) Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS.
Paul Watson
Bluegrass
Cape Town, South AfricaChris Losinger wrote: i hate needles so much i can't even imagine allowing one near The Little Programmer
-
A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line.
- What is the official name that the projects will be published under?
- Are we working on a logo of some sorts? (the kind that can be put in an About box)
- I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects
Jason Henderson wrote: 3.8 Defect Tracking/Source Versioning (16) Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS.
Paul Watson
Bluegrass
Cape Town, South AfricaChris Losinger wrote: i hate needles so much i can't even imagine allowing one near The Little Programmer
Paul Watson wrote: A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line. Thank you. Its a lot like herding cats (for more info, see a super bowl commercial from a couple years back). Paul Watson wrote: What is the official name that the projects will be published under? Good question. Got any ideas? Paul Watson wrote: Are we working on a logo of some sorts? (the kind that can be put in an About box) If we publish under a single group entity, we need a logo. We need a cool one! Paul Watson wrote: I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects I really can't do anything about people starting other projects outside of our 3. I do think that they will fail completely if they don't follow the methods we come up with here. How do you manage 50 developers around the world??? :~ Paul Watson wrote: Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS. Heck if I know. :) We'll let the teams decide how their respective projects work.
Jason Henderson
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
-
Paul Watson wrote: A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line. Thank you. Its a lot like herding cats (for more info, see a super bowl commercial from a couple years back). Paul Watson wrote: What is the official name that the projects will be published under? Good question. Got any ideas? Paul Watson wrote: Are we working on a logo of some sorts? (the kind that can be put in an About box) If we publish under a single group entity, we need a logo. We need a cool one! Paul Watson wrote: I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects I really can't do anything about people starting other projects outside of our 3. I do think that they will fail completely if they don't follow the methods we come up with here. How do you manage 50 developers around the world??? :~ Paul Watson wrote: Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS. Heck if I know. :) We'll let the teams decide how their respective projects work.
Jason Henderson
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
Jason Henderson wrote: How do you manage 50 developers around the world??? Going to be bloody difficult and noone is going to stop nuts from splintering off. But you have handled it well so far and you have a firm but fair hand which is ideal. Splinters should be coerced back into the project, but if they turn out to be impossible then leave them be in their dark corners. Jason Henderson wrote: Got any ideas? The Code Project Army. I can imagine the logo that goes with it; Rank upon rank of little Bobs fading off into to the distance all marching in step. (p.s. this is Chris' real purpose with CP, he wants to indoctrinate us all into the Maunder Liberation Force and then take over the world.) If I think of anything decent I will mention it. We can make it part of the whole process, that of finding a name and (maybe) voting on the ideas. (Obviously Chris will have to ok the name) Jason Henderson wrote: for more info, see a super bowl commercial from a couple years back hehe, my buttered kittens metaphor was a different take on that very same advert. Classic ad, and yes even us South Africans have seen it. :)
Paul Watson
Bluegrass
Cape Town, South AfricaChris Losinger wrote: i hate needles so much i can't even imagine allowing one near The Little Programmer
-
A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line.
- What is the official name that the projects will be published under?
- Are we working on a logo of some sorts? (the kind that can be put in an About box)
- I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects
Jason Henderson wrote: 3.8 Defect Tracking/Source Versioning (16) Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS.
Paul Watson
Bluegrass
Cape Town, South AfricaChris Losinger wrote: i hate needles so much i can't even imagine allowing one near The Little Programmer
Paul Watson wrote: I would think defect/bug/issue tracking falls under something like PMS. I'm sure the women-folk would agree! Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files" -
A few questions, but first; Great job so far Jason, you have cracked that whip and kept what to me looks like a bowl full of buttered kittens in line.
- What is the official name that the projects will be published under?
- Are we working on a logo of some sorts? (the kind that can be put in an About box)
- I vote you as overall high commander of the... I mean CPP Coordinator. I think it is something we will need as people splinter off and try to start more than three projects
Jason Henderson wrote: 3.8 Defect Tracking/Source Versioning (16) Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? I would think defect/bug/issue tracking falls under something like PMS.
Paul Watson
Bluegrass
Cape Town, South AfricaChris Losinger wrote: i hate needles so much i can't even imagine allowing one near The Little Programmer
Paul Watson wrote: Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? If you have a Source Control/Versioning and a Defect Tracker that work together, bugs can be attached to different versions of sourcecode and so on... You might see it as 2 different projects, and it might as well be that, but is you make it one project, you can make the "2 parts" work together (integrated). The other thing is that there is something to do for everyone to do on that project, all the way from you web-dudes, and to native C++ on the server. And yes, the project is my idea :-O - Anders Money talks, but all mine ever says is "Goodbye!"
-
Paul Watson wrote: Oh and finally; How the heck does Source Versioning (CVS, VSS etc.) and Defect Tracking work together? If you have a Source Control/Versioning and a Defect Tracker that work together, bugs can be attached to different versions of sourcecode and so on... You might see it as 2 different projects, and it might as well be that, but is you make it one project, you can make the "2 parts" work together (integrated). The other thing is that there is something to do for everyone to do on that project, all the way from you web-dudes, and to native C++ on the server. And yes, the project is my idea :-O - Anders Money talks, but all mine ever says is "Goodbye!"
Anders Molin wrote: If you have a Source Control/Versioning and a Defect Tracker that work together, bugs can be attached to different versions of sourcecode and so on... My sources all have their own bugs. :omg: Attaching a bug to different source code versions makes fixing too easy ;P
Off to Brazil in a few days
-
I hope this forum is open for discussions once the voting is over? I mean like a normal message board where you can start threads at the top. Every time I press "Next" in this forum, it takes many minutes before I see the next page. jhaga CodeProject House, Paul Watson wrote: ...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner. ...Good heavens!
What happened to your suggestion for a bioinformatics project? I was really looking forward to that being on the list. :-(
-
What happened to your suggestion for a bioinformatics project? I was really looking forward to that being on the list. :-(
There are not enough people here interested in biology, sorry. We had one Gene Detection and one Medical visualization idea. To get a project going we need at least 10 very interested people. jhaga CodeProject House, Paul Watson wrote: ...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner. ...Good heavens!
-
Idea submittal and voting have come to a slow crawl or stopped altogether so we'll just say its time to chose the final three projects. We could go just by the current voting result (see below), but I think its only fair that we re-evaluate what we would really like to do. Before doing so, I'd like to give you my opinion of what we should do and I know at least Paul and Marc will agree with me. I'm not going to endorse a particular project, but rather an ideal for our first stab at this. Its called... KISS (keep it simple stupid) Whatever project(s) we choose to do, it's/their scope needs to be somewhat limited (initially for release 1.0). Rome was not built in a day and CPPs are sure to fail if we try to do too much too soon. Heck, the infrastructure for large group projects isn't even in place yet. So we have a lot of thinking to do before we "dive right in." Here is how I propose we proceed: 1) Decide on 3 projects via voting (now until Tuesday) which gives us 24+ hours 2) Pick a project leader for each project (preferrably, the originator of the idea AND someone with experience writing articles and managing a herd of cattle ;)) 3) If you want to, we can pick a CPP coordinator who will look after these first 3 projects, but I doubt we'll need one. 4) Divide up into teams (I have an idea on how to do this but we'll discuss later). There may be lopsided teams. 5) Start an article for each project. NOT QUICKLY THOUGH! I'd like to see us decide on a standard layout and "features" in our project article. Its going to have to be different somehow than a standard article (I see tables :~ ). 6) Project leaders and team members will then need to define the scope and timeline for the project. A design document would be very nice. Anyone have a nice Design Doc template? 7) Here's where the fun begins. Start coding. Project leaders should be good delegators. 8) Try to stay within the scope and timeline, giving frequent updates and screen shots. If you have any different ideas, please discuss them by replying to this message. Below this message you will see a thread for PROJECT VOTING. Within that thread are 10 messages with the title of each project. Please give a vote for each message using the message voting system. The top 3 after Tuesday morning will be our beginning proje
Jason, I am sure you know what you are doing, but I found this and might help everyone http://www.construx.com/survivalguide/test.htm[^] I am going to use it for my HAI project, i think. Later,
JoeSox
www.humanaiproject.org "Dream as if you'll live forever; live as if you'll die tomorrow." - James Dean(ISTP) -
Jason, I am sure you know what you are doing, but I found this and might help everyone http://www.construx.com/survivalguide/test.htm[^] I am going to use it for my HAI project, i think. Later,
JoeSox
www.humanaiproject.org "Dream as if you'll live forever; live as if you'll die tomorrow." - James Dean(ISTP)That may be helpful. I'll look at it a little more closely over lunch.
Jason Henderson
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
-
There are not enough people here interested in biology, sorry. We had one Gene Detection and one Medical visualization idea. To get a project going we need at least 10 very interested people. jhaga CodeProject House, Paul Watson wrote: ...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner. ...Good heavens!
Hmmm, why 10? :-)
-
First of all, I hope I'm not doing the wrong thing by replying here. Second of all, here's my thoughts: Jason Henderson wrote: Idea submittal and voting have come to a slow crawl or stopped altogether so we'll just say its time to chose the final three projects. My thoughts exactly. Jason Henderson wrote: Universal Gui LibrarY (UGLY) Please, not UGLY! That's the opposite of what we want! How about SUIT - SmartUI Toolkit. Also, if we do a UI Library first, then it's easy to start out simple - do it one control at a time :) . We can stop any place along the way. Jason Henderson wrote: Divide up into teams (I have an idea on how to do this but we'll discuss later). I have an idea too... later. :) Jason Henderson wrote: Project leaders and team members will then need to define the scope and timeline for the project. A design document would be very nice. Anyone have a nice Design Doc template? I have some ideas and questions - where shall we discuss it? GOOD JOB, JASON!
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhijdunlap wrote: Please, not UGLY! That's the opposite of what we want! How about SUIT - SmartUI Toolkit. But that's the reason we like it...it's funny. :-D
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
-
Idea submittal and voting have come to a slow crawl or stopped altogether so we'll just say its time to chose the final three projects. We could go just by the current voting result (see below), but I think its only fair that we re-evaluate what we would really like to do. Before doing so, I'd like to give you my opinion of what we should do and I know at least Paul and Marc will agree with me. I'm not going to endorse a particular project, but rather an ideal for our first stab at this. Its called... KISS (keep it simple stupid) Whatever project(s) we choose to do, it's/their scope needs to be somewhat limited (initially for release 1.0). Rome was not built in a day and CPPs are sure to fail if we try to do too much too soon. Heck, the infrastructure for large group projects isn't even in place yet. So we have a lot of thinking to do before we "dive right in." Here is how I propose we proceed: 1) Decide on 3 projects via voting (now until Tuesday) which gives us 24+ hours 2) Pick a project leader for each project (preferrably, the originator of the idea AND someone with experience writing articles and managing a herd of cattle ;)) 3) If you want to, we can pick a CPP coordinator who will look after these first 3 projects, but I doubt we'll need one. 4) Divide up into teams (I have an idea on how to do this but we'll discuss later). There may be lopsided teams. 5) Start an article for each project. NOT QUICKLY THOUGH! I'd like to see us decide on a standard layout and "features" in our project article. Its going to have to be different somehow than a standard article (I see tables :~ ). 6) Project leaders and team members will then need to define the scope and timeline for the project. A design document would be very nice. Anyone have a nice Design Doc template? 7) Here's where the fun begins. Start coding. Project leaders should be good delegators. 8) Try to stay within the scope and timeline, giving frequent updates and screen shots. If you have any different ideas, please discuss them by replying to this message. Below this message you will see a thread for PROJECT VOTING. Within that thread are 10 messages with the title of each project. Please give a vote for each message using the message voting system. The top 3 after Tuesday morning will be our beginning proje
Jason Henderson wrote: Idea submittal and voting have come to a slow crawl People just arn't finding these new threads, after all it took me a while and I'm quite keen. Maybe we should get some kind of email update going... Or a cover article on the CP front page.**
*¨¨`) ¸¸.·´ ¸.·*¨¨`) (¸¸.·* ¸ .·* ¸¸.·* (¸¸.~~> Joel Holdsworth.
**
-
Paul Watson wrote: I would think defect/bug/issue tracking falls under something like PMS. I'm sure the women-folk would agree! Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files":-D My boss actually wrote his own Project Management System and named it PMS...some of the women around the office saw it and got a little upset. :)
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
-
jdunlap wrote: Please, not UGLY! That's the opposite of what we want! How about SUIT - SmartUI Toolkit. But that's the reason we like it...it's funny. :-D
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
UGLY is just the opposite of what we want - we want something that looks nice. Would you buy a toolkit that's called "UGLY"??? I think we should have a vote on this one.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi -
Idea submittal and voting have come to a slow crawl or stopped altogether so we'll just say its time to chose the final three projects. We could go just by the current voting result (see below), but I think its only fair that we re-evaluate what we would really like to do. Before doing so, I'd like to give you my opinion of what we should do and I know at least Paul and Marc will agree with me. I'm not going to endorse a particular project, but rather an ideal for our first stab at this. Its called... KISS (keep it simple stupid) Whatever project(s) we choose to do, it's/their scope needs to be somewhat limited (initially for release 1.0). Rome was not built in a day and CPPs are sure to fail if we try to do too much too soon. Heck, the infrastructure for large group projects isn't even in place yet. So we have a lot of thinking to do before we "dive right in." Here is how I propose we proceed: 1) Decide on 3 projects via voting (now until Tuesday) which gives us 24+ hours 2) Pick a project leader for each project (preferrably, the originator of the idea AND someone with experience writing articles and managing a herd of cattle ;)) 3) If you want to, we can pick a CPP coordinator who will look after these first 3 projects, but I doubt we'll need one. 4) Divide up into teams (I have an idea on how to do this but we'll discuss later). There may be lopsided teams. 5) Start an article for each project. NOT QUICKLY THOUGH! I'd like to see us decide on a standard layout and "features" in our project article. Its going to have to be different somehow than a standard article (I see tables :~ ). 6) Project leaders and team members will then need to define the scope and timeline for the project. A design document would be very nice. Anyone have a nice Design Doc template? 7) Here's where the fun begins. Start coding. Project leaders should be good delegators. 8) Try to stay within the scope and timeline, giving frequent updates and screen shots. If you have any different ideas, please discuss them by replying to this message. Below this message you will see a thread for PROJECT VOTING. Within that thread are 10 messages with the title of each project. Please give a vote for each message using the message voting system. The top 3 after Tuesday morning will be our beginning proje
-
UGLY is just the opposite of what we want - we want something that looks nice. Would you buy a toolkit that's called "UGLY"??? I think we should have a vote on this one.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhijdunlap wrote: buy a toolkit that's called "UGLY"??? Ummm....I thought this was going to be a CP thing...and thus free. :~ Besides, we're all coders...we all have a sense of humor. If we see a GUI toolkit that's called UGLY, we're gonna take a look at it just to see what it's like anyway.
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
-
Joel Holdsworth wrote: I prefer SUIT myself THANK YOU!!! I hope David Stone doesn't convince people not to have a vote.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi -
:-D My boss actually wrote his own Project Management System and named it PMS...some of the women around the office saw it and got a little upset. :)
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
:laugh: David Stone wrote: some of the women around the office saw it and got a little upset. Everyone is so touchy nowadays. I wish the acronym PC could have remained "Personal Computer". But no, I now I have tell people that I'm an ego-challenged, politically disenfranchised, monetarily weakened, non-available single citizen of the earth involved in a heterosexual relationship. X| Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
Sensitivity and ethnic diversity means celebrating difference, not hiding from it. - Christian Graus
Every line of code is a liability - Taka Muraoka
Microsoft deliberately adds arbitrary layers of complexity to make it difficult to deliver Windows features on non-Windows platforms--Microsoft's "Halloween files"