Sep 7th 2010, 18:28:30
[repost of what I had on API users, since there wasn't a lot of activity there :p]
well, more accurately, replacing it with a fresh system now that we have a good, reliable data setup. It's been something I've been wanting to start on for a while, but I've been busy with other project (such as EE, my thesis and work :p)
I'll be overseeing the project and TC will remain as the server host, but since, as I mentioned, I have a lots of other work to do (and I'd rather focus my 'hobby' time on EE), I thought I'd see if any folks are interested in working on this project. QZ, Slag, and Nuk may be involved as well
As far as what we'll be doing, here is the 30 second rundown
- Linux/Apache/MySQL/PHP
- We'll be using a similar system as EE in terms of permissions and how pages are served to users
- It will be a public service that will eventually replace Boxcar (including migrating existing data from Boxcar and other hosting sites)
- It won't be a part of EE, but it may have opportunities to be tied into it -- Boxcar was what I always used to build Game to Site API's before I made them live, so this site would replace that in that context
There are a couple of conditions for those interested...
- If you are part of this project, it should be in favour of your current one, meaning that this will be the priority hosting site project for everyone involved. Obviously, there will still need to be support for old sites while it's being built, but the eventual goal should be for all of the developers to phase out their existing sites. I know this is a dealbreaker for a lot of folks, but I want to make sure that everyone is going to give their all and not just stay peripherally involved because their alliance is hosted elsewhere.
- Anything you write should be made available to all alliances in some form. We can write specific API's that link to 'proprietary' tools like war bots and stuff, but specific alliances should not get features other alliances don't get just because a developer plays there. Features undergoing testing can be tested by developers' alliances.
- All developers will need to be vetted and not be affiliated with people who have broken the EE rules. This is a necessity because there is so much data available.
- This can't be a "learning" project for anyone. I did that with Boxcar and that's why I'm so unhappy with it :p I didn't know a line of PHP when I started, and even though I've updated a TON of stuff, it's still detrimental to be working on that codebase. If you're new to PHP or web programming, that's great... but we may not be able to take on those folks at the moment.
So if you're interested in getting involved, let me know in some manner and we can discuss!
well, more accurately, replacing it with a fresh system now that we have a good, reliable data setup. It's been something I've been wanting to start on for a while, but I've been busy with other project (such as EE, my thesis and work :p)
I'll be overseeing the project and TC will remain as the server host, but since, as I mentioned, I have a lots of other work to do (and I'd rather focus my 'hobby' time on EE), I thought I'd see if any folks are interested in working on this project. QZ, Slag, and Nuk may be involved as well
As far as what we'll be doing, here is the 30 second rundown
- Linux/Apache/MySQL/PHP
- We'll be using a similar system as EE in terms of permissions and how pages are served to users
- It will be a public service that will eventually replace Boxcar (including migrating existing data from Boxcar and other hosting sites)
- It won't be a part of EE, but it may have opportunities to be tied into it -- Boxcar was what I always used to build Game to Site API's before I made them live, so this site would replace that in that context
There are a couple of conditions for those interested...
- If you are part of this project, it should be in favour of your current one, meaning that this will be the priority hosting site project for everyone involved. Obviously, there will still need to be support for old sites while it's being built, but the eventual goal should be for all of the developers to phase out their existing sites. I know this is a dealbreaker for a lot of folks, but I want to make sure that everyone is going to give their all and not just stay peripherally involved because their alliance is hosted elsewhere.
- Anything you write should be made available to all alliances in some form. We can write specific API's that link to 'proprietary' tools like war bots and stuff, but specific alliances should not get features other alliances don't get just because a developer plays there. Features undergoing testing can be tested by developers' alliances.
- All developers will need to be vetted and not be affiliated with people who have broken the EE rules. This is a necessity because there is so much data available.
- This can't be a "learning" project for anyone. I did that with Boxcar and that's why I'm so unhappy with it :p I didn't know a line of PHP when I started, and even though I've updated a TON of stuff, it's still detrimental to be working on that codebase. If you're new to PHP or web programming, that's great... but we may not be able to take on those folks at the moment.
So if you're interested in getting involved, let me know in some manner and we can discuss!
-=Pang=-
Earth Empires Staff
pangaea [at] earthempires [dot] com
Boxcar - Earth Empires Clan & Alliance Hosting
http://www.boxcarhosting.com
Earth Empires Staff
pangaea [at] earthempires [dot] com
Boxcar - Earth Empires Clan & Alliance Hosting
http://www.boxcarhosting.com