Carlos Camacho
2004.11.09, 12:35 AM
Today, a concerned developer who is entering uDevGames for the first time, took time to write to me. Since he took the time to comment on uDevGames, and sense there might be other newcomers to iDevGames and uDevGames, I thought I would go through his comments to help provide a perspective on uDevGames. Perhaps by doing so, we can see where we have come from, and even consider, where we must go.
uDevGames, the registration, the management, the downloads page, and
In the first year of uDevGames, 2001, we kicked off the contest wondering if anyone would join. The prize pool was very small, and most of the dev community didn't have it on their radar. At that time, we used our own Content Management System, out together by our, then, guru webmaster Griggs. If memory serves me right, the only true functioning section for contest management was the voting system. For the most part, everything else was done by sending emails. Developers couldn't edit their own game's info, etc. I was a great bottlekneck.
In 2002, our webmaster improved the uDevGames system. I know had the ability to add the content pages without uploading html to the server. The voting system was improved a bit as well. But if I recall, there was a bug which was keeping us from getting the correct vote results. In the end, I managed to patch Grigg's code, and we got the results. Griggs was in the middle of leaving us, so this had a profound impact on the management of the site -- his CMS was good, but working on it for anyone else required a good amount of effort.
In 2003, our assistant webmaster, Josh took over. He learned the API of Grigg's code, and added some features to our backend. We added the "Entrant Login System", which finally allowed developers to manage their own downloads. We had bugs along the way, but somehow managed to get the contest finished. Though I realize that our backend system, and CMS was really killing us.
It was in 2003, when we were plagued with server problems. Not being a guru system administrator, and not being able to spend 24/7 (this is a HOBBY after all) were sure signs that we were in for trouble. Sure enough, trouble came our way, and the contest was hit by various delays.
Some time later I made a choice to get away from a proprietary CMS, and after a great deal of research settle on Mambo. It is far from perfect, but with many active developers, it meant that I could find various components (like plugins) to handle my needs, rather than waiting for a lone coder to write it, as we did before.
Now to cover 2004. Our main site was using Mambo. However, migrating all our downloads (for example the past uDevGames, and postmortems) was a bit of work. This work was often interupted when I moved the server from my home, to this place, and that place. A site, or shall I say a permanent home for uDevGames was suggested by the community. Up until then, all our moving was playing havoc with links to various content, and placing a backlog on getting content up. In the summer of 2004, we had a very long downtime period. So long, that once the site was back up, I was nearly 2 months behind in contacting sponsors. With so much to do to just get the site back up, and being behind schedule, I talked about not having uDevGames this year. One side issue in the summer was my own personal problem with a health problem, someone brought on my stress from the attacks, and running uDevGames.
After iDevGames was back, but really without having iDevGames up in a way that made the site complete, I decided to not to disappoint the community, and not to lose our momentum of the contest (2003 was a record breaking year for prizes, and coverage) and run uDevGames 2004. So the site was set up (after first starting off as a sub-domain.) The credit goes to many people in the community for helping with proofing, creating a mascot, to tweaking the CSS. This has always been a great point of uDevGames -- when the community was most threatened with extinction, and turmoil, people stepped up and lent a hand. (Very true in 2003.) That said, and I take nothing away from the people who help, uDevGames remains a one man operation. THIS is the main problem.
We have had threads in this forum on dividing work. Some of its has worked out, and some has, to my disappointment, gone no where. Some people have helped behind the scenes (you know who you are), and they have commented that it is a tremendous amount of work. It really really is. Imagine in 2001 when we were in the stone age, and I had to walk 100 miles, in the snow, barefoot, just to deliver the prizes. ;) (Strike up th violins for the next part) I want to stress that I have given up a great many weekends, and time with my wife, and even battled 3 flus each year at the end of uDevGames.
Ok, enough about me, and the terrible burden I carry like poor little Frodo.
The uDevGames site is based Mambo 4.5. As I said, Mambo isn't perfect, but I have yet to use better CMS. Speaking of which, CMSs are popping up each day. To me, this "technology" is very young, immature, but a godsend to busy people like me. Mambo has moved on to 4.5.1 but I dare not upgrade during the contest.
When building th uDevGames site, myself and other people who came with their tools to help build it, looked at what we needed. We needed an Entrant System, a Download System, a Voting System. First, we looked at components from the Mambo community, so we wouldn't have to reinvent the wheel -- especially since we were extremely behind schedule. Joseph D., got the Entrant List working, and Justin got th sponsors section working, based on such code. For other sections, I was faced with needing to purchase a component, for example to handle forms. In the end, I picked a free form tool that got the job done, though it isn't perfect.
Last two items were voting and downloads. There are two download components for Mambo. Both of which have good and bad points. I tried and tried to tweak them to our needs over the course of the contest. As a backup, I posted third party download systems we should check out. Outside of two people, I don't recall much help. I suppose this isn't a web forum, so I shouldn't expect everyone to be a LAMP guru. No problem. In the case of our voting system, I pretty much followed the same path of the Downloads. Looked for Mambo solutions, that would integrate well with the backend, found none, tried to adapt something, couldn't, asked people to look into other open source solutions. I think only Justin B responded in this area, but I need to check the thread.
Now time to strike up the violins again. One month ago, my "real world" took a nasty twist. No longer could I devote oodles of time to iDevGames -- its been a real challenge to say the least. Remember, since we lost our Sponsorship Manager, I had to take care of this job during the contest. Which eats up a great deal of time. If not, then we all would be running out and getting $30,000 worth of prizes each day right? ;)
I would guess that 4 weeks ago was about the time I started to look at Voting Systems closely. I made a list, checked it twice. Hence started installation, and testing of everything on my list. It is true that I should have been done 2 weeks prior to the end of the dev cycle for you all. I'll use my work, health and wife as an alibi here. :(
Anyways, over the last few days, a member of the community stepped up -- SkyHawk, a person who has helped tremedously in the past with Matt D in getting out the prizes, and we worked on the Download section and Voting section. It was pretty nerve racking testing, and I think we lost a great deal of time trying to get various scripts to work... hey, this sounds like a postmortem! In the end, I had to make "the call", which was, to purchase a 3rd party download and voting system. The funds came from uDevGames/iDevGames. SkyHawk was "with me" (but on the otherside of the planet) during this hard decision. But I think in the end, I made the only decision that I could. I think it is a good decision. Here is why....
The voting and download system are not part of Mambo. At first, this sounds like a step backwards. However, I see the positive aspect. Mambo is a CMS, which to me, best handles article-type content, links, and such. Downloads and Voting are the most crucial components of uDevGames. By having them outside of Mambo, should we ever need to move to a new version, change CMS, etc, these two systems can continue to function independently. Let me talk about each system now...
The Voting system, from the backend is a DREAM. I think the test that I created looks professional, and best of all, it allows for stable performance. I will also be able to provide results in various formats, like CVS, Excel, etc. The ability and flexibility to make any type of "survey" shouldn't be under estimated. True, the system cost us an arm and a leg (more on that later), but to pay someone to create the same level of usability would cost much more. Some of you might now be saying, but I could have whipped up something... OK. But we needed such volunteering months ago. (And we don't want to end up where we were after Griggs left us!) The Voting System Developers are working on this script for a living. Next year, thankfully, we won't have to scramble for a voting system. That is one thing off our scramble list.
The Download system was a tough challenge itself. Since Joseph has been too busy to continue work on the Entrant List system, we HAD to find an alternative. I would have liked to have kept it within Mambo, but as I said, the two current download systems wouldn't have made you all happy. ie, no mirrors, and features which would have confused people (eg. They tend to have have a star rating which CAN'T be turned off.) The system we have I admit is not nearly as slick as the Voting system (price shows). But of the 100 plus scripts on hotscripts.com, it was the only one within our budget, and that could do what we needed for uDevGames. True, SkyHawk and I cursed the developer 100 times while we tried to figure how to set it up. But in the end, it is working. Next year, you all have accounts, so just a matter of adding your new game to the "Games / 2005" folder. And yes, the 2004 folder will stay up, and when I have time, the 2003, 2002, and 2001 folders will come online. This system doesn't look pretty at the moment, and the navigation is a tad crude. However, once I get better, and have time off, I promise to get it to look as good as sites like macupdate. If you have php skills, and design skills, then you are welcomed to help out. :D (The room grows silent.)
Ok, now for a quick summary. Each year, uDevGames grows up a little more. We add some new features to make it easier for the developers, gamers, and the staff<-- me. Each year, it isn't perfect, but we do out best. Those of you who are long timers, will know how far the uDevGames contest and its supporting systems has come. Of course, the long timers know that uDevGames is like an entry in itself -- trying to make deadlines, having bugs, and so on. Overall, I am happy this year because it looks like we will have a solid period of voting. Knock on wood. And at the end of the voting, we can gather the data, and march on. Unlike in years past.
I expect by next year, the systems that seem to be "taped together" will have a front end that presents a very enjoyable experience.
Now to try my best to answer some of you direct comments...
uDevGames, the registration, the management, the downloads page, and
In the first year of uDevGames, 2001, we kicked off the contest wondering if anyone would join. The prize pool was very small, and most of the dev community didn't have it on their radar. At that time, we used our own Content Management System, out together by our, then, guru webmaster Griggs. If memory serves me right, the only true functioning section for contest management was the voting system. For the most part, everything else was done by sending emails. Developers couldn't edit their own game's info, etc. I was a great bottlekneck.
In 2002, our webmaster improved the uDevGames system. I know had the ability to add the content pages without uploading html to the server. The voting system was improved a bit as well. But if I recall, there was a bug which was keeping us from getting the correct vote results. In the end, I managed to patch Grigg's code, and we got the results. Griggs was in the middle of leaving us, so this had a profound impact on the management of the site -- his CMS was good, but working on it for anyone else required a good amount of effort.
In 2003, our assistant webmaster, Josh took over. He learned the API of Grigg's code, and added some features to our backend. We added the "Entrant Login System", which finally allowed developers to manage their own downloads. We had bugs along the way, but somehow managed to get the contest finished. Though I realize that our backend system, and CMS was really killing us.
It was in 2003, when we were plagued with server problems. Not being a guru system administrator, and not being able to spend 24/7 (this is a HOBBY after all) were sure signs that we were in for trouble. Sure enough, trouble came our way, and the contest was hit by various delays.
Some time later I made a choice to get away from a proprietary CMS, and after a great deal of research settle on Mambo. It is far from perfect, but with many active developers, it meant that I could find various components (like plugins) to handle my needs, rather than waiting for a lone coder to write it, as we did before.
Now to cover 2004. Our main site was using Mambo. However, migrating all our downloads (for example the past uDevGames, and postmortems) was a bit of work. This work was often interupted when I moved the server from my home, to this place, and that place. A site, or shall I say a permanent home for uDevGames was suggested by the community. Up until then, all our moving was playing havoc with links to various content, and placing a backlog on getting content up. In the summer of 2004, we had a very long downtime period. So long, that once the site was back up, I was nearly 2 months behind in contacting sponsors. With so much to do to just get the site back up, and being behind schedule, I talked about not having uDevGames this year. One side issue in the summer was my own personal problem with a health problem, someone brought on my stress from the attacks, and running uDevGames.
After iDevGames was back, but really without having iDevGames up in a way that made the site complete, I decided to not to disappoint the community, and not to lose our momentum of the contest (2003 was a record breaking year for prizes, and coverage) and run uDevGames 2004. So the site was set up (after first starting off as a sub-domain.) The credit goes to many people in the community for helping with proofing, creating a mascot, to tweaking the CSS. This has always been a great point of uDevGames -- when the community was most threatened with extinction, and turmoil, people stepped up and lent a hand. (Very true in 2003.) That said, and I take nothing away from the people who help, uDevGames remains a one man operation. THIS is the main problem.
We have had threads in this forum on dividing work. Some of its has worked out, and some has, to my disappointment, gone no where. Some people have helped behind the scenes (you know who you are), and they have commented that it is a tremendous amount of work. It really really is. Imagine in 2001 when we were in the stone age, and I had to walk 100 miles, in the snow, barefoot, just to deliver the prizes. ;) (Strike up th violins for the next part) I want to stress that I have given up a great many weekends, and time with my wife, and even battled 3 flus each year at the end of uDevGames.
Ok, enough about me, and the terrible burden I carry like poor little Frodo.
The uDevGames site is based Mambo 4.5. As I said, Mambo isn't perfect, but I have yet to use better CMS. Speaking of which, CMSs are popping up each day. To me, this "technology" is very young, immature, but a godsend to busy people like me. Mambo has moved on to 4.5.1 but I dare not upgrade during the contest.
When building th uDevGames site, myself and other people who came with their tools to help build it, looked at what we needed. We needed an Entrant System, a Download System, a Voting System. First, we looked at components from the Mambo community, so we wouldn't have to reinvent the wheel -- especially since we were extremely behind schedule. Joseph D., got the Entrant List working, and Justin got th sponsors section working, based on such code. For other sections, I was faced with needing to purchase a component, for example to handle forms. In the end, I picked a free form tool that got the job done, though it isn't perfect.
Last two items were voting and downloads. There are two download components for Mambo. Both of which have good and bad points. I tried and tried to tweak them to our needs over the course of the contest. As a backup, I posted third party download systems we should check out. Outside of two people, I don't recall much help. I suppose this isn't a web forum, so I shouldn't expect everyone to be a LAMP guru. No problem. In the case of our voting system, I pretty much followed the same path of the Downloads. Looked for Mambo solutions, that would integrate well with the backend, found none, tried to adapt something, couldn't, asked people to look into other open source solutions. I think only Justin B responded in this area, but I need to check the thread.
Now time to strike up the violins again. One month ago, my "real world" took a nasty twist. No longer could I devote oodles of time to iDevGames -- its been a real challenge to say the least. Remember, since we lost our Sponsorship Manager, I had to take care of this job during the contest. Which eats up a great deal of time. If not, then we all would be running out and getting $30,000 worth of prizes each day right? ;)
I would guess that 4 weeks ago was about the time I started to look at Voting Systems closely. I made a list, checked it twice. Hence started installation, and testing of everything on my list. It is true that I should have been done 2 weeks prior to the end of the dev cycle for you all. I'll use my work, health and wife as an alibi here. :(
Anyways, over the last few days, a member of the community stepped up -- SkyHawk, a person who has helped tremedously in the past with Matt D in getting out the prizes, and we worked on the Download section and Voting section. It was pretty nerve racking testing, and I think we lost a great deal of time trying to get various scripts to work... hey, this sounds like a postmortem! In the end, I had to make "the call", which was, to purchase a 3rd party download and voting system. The funds came from uDevGames/iDevGames. SkyHawk was "with me" (but on the otherside of the planet) during this hard decision. But I think in the end, I made the only decision that I could. I think it is a good decision. Here is why....
The voting and download system are not part of Mambo. At first, this sounds like a step backwards. However, I see the positive aspect. Mambo is a CMS, which to me, best handles article-type content, links, and such. Downloads and Voting are the most crucial components of uDevGames. By having them outside of Mambo, should we ever need to move to a new version, change CMS, etc, these two systems can continue to function independently. Let me talk about each system now...
The Voting system, from the backend is a DREAM. I think the test that I created looks professional, and best of all, it allows for stable performance. I will also be able to provide results in various formats, like CVS, Excel, etc. The ability and flexibility to make any type of "survey" shouldn't be under estimated. True, the system cost us an arm and a leg (more on that later), but to pay someone to create the same level of usability would cost much more. Some of you might now be saying, but I could have whipped up something... OK. But we needed such volunteering months ago. (And we don't want to end up where we were after Griggs left us!) The Voting System Developers are working on this script for a living. Next year, thankfully, we won't have to scramble for a voting system. That is one thing off our scramble list.
The Download system was a tough challenge itself. Since Joseph has been too busy to continue work on the Entrant List system, we HAD to find an alternative. I would have liked to have kept it within Mambo, but as I said, the two current download systems wouldn't have made you all happy. ie, no mirrors, and features which would have confused people (eg. They tend to have have a star rating which CAN'T be turned off.) The system we have I admit is not nearly as slick as the Voting system (price shows). But of the 100 plus scripts on hotscripts.com, it was the only one within our budget, and that could do what we needed for uDevGames. True, SkyHawk and I cursed the developer 100 times while we tried to figure how to set it up. But in the end, it is working. Next year, you all have accounts, so just a matter of adding your new game to the "Games / 2005" folder. And yes, the 2004 folder will stay up, and when I have time, the 2003, 2002, and 2001 folders will come online. This system doesn't look pretty at the moment, and the navigation is a tad crude. However, once I get better, and have time off, I promise to get it to look as good as sites like macupdate. If you have php skills, and design skills, then you are welcomed to help out. :D (The room grows silent.)
Ok, now for a quick summary. Each year, uDevGames grows up a little more. We add some new features to make it easier for the developers, gamers, and the staff<-- me. Each year, it isn't perfect, but we do out best. Those of you who are long timers, will know how far the uDevGames contest and its supporting systems has come. Of course, the long timers know that uDevGames is like an entry in itself -- trying to make deadlines, having bugs, and so on. Overall, I am happy this year because it looks like we will have a solid period of voting. Knock on wood. And at the end of the voting, we can gather the data, and march on. Unlike in years past.
I expect by next year, the systems that seem to be "taped together" will have a front end that presents a very enjoyable experience.
Now to try my best to answer some of you direct comments...