Thread: Any help needed?

Almost.

Now it's time to explain some extra details.

There are two version of the mod: v1 and v2

v1 is what the TF2 server is using right now, and it's what your link points to. v1 is more of a "first try" at making the mod, and was never open-source. This version was also completely C++

v2 was a port of v1 to python (for various reasons) and was planned from the beginning to be open-source. v2 isn't technically out yet, because I just got done with an alpha version of the port this last weekend. This week we've been alpha testing it trying to get rid of any bugs we find. Once that's done (this weekend hopefully), it will turn into "beta 1" and be a download on this site. I plan on each release contianing both the prebuilt binary AND the source code, which is how I plan on the public-at-large getting access to the source code.

The current private subversion server TTP has is, well, private, and it doesn't allow for anonymous access, which is one of the big reasons the source will be shipping with each release. You guys won't have access to the subversion server.

I also plan on doing the "release-early, release-often" kind of release schedule. I also don't expect TTP to migrate to any particular release just because it's released. They need to make sure their servers are stable, so TTP might be a release or two behind while the mod team works out any kinks introduced in new features.

For now, while you're waiting for beta1 to be released, go through the python tutorial in the sticky. Trust me, it'll help.

How do you plan on the community to provide bug fixes / new features if you aren't going to have svn accounts for them?

For people that have an un-established history with the project: patches (posted in the forums, or emailed to me)

For people that have history with the project (they're devoted, they've submitted a lot of a good quality patches, and they work well with the rest of the team): we'll specifically give them a subversion account.

I hope you understand the situation I'm in: I have a lot of people volunteering, but I have no idea how they will pan out. It just makes sense to be defensive and let people prove themselves before giving them unrestricted access to the code base (i.e. a subversion account).

Even if you don't have a subversion account, you can still use subversion to generate patches of your changes instead of checking them in.

Optimally this would involve you checking out the code anonymously, and then making your changes, and then having subversion make a patch out of your changes.

Unfortunately as we don't have anonymous access to our subversion server at the moment, this more likely will involve making your own personal private repo, importing the code base, and then using that as the "anonymous code store" to generate patches against. If this is unclear, I can do a write-up of it. It's pretty easy to do.

I'm looking into anonymous svn access isolated to the LoneStar project (so that you can do the optimal way of making patches above), but I make no guarantees on when/if this is going to happen at this time.

Sounds good. Just curious how you planned to handle it. I think what you outlined above makes good sense. I look forward to seeing the source.

As a side note, you may want to put together a requested features list non-svn users can sign up to, as to give a way to participate and stay on track.

Yeah hopefully this weekend I'll be able to get to things like that.

I took a year of C++ if that gives me enough knowledge to help at all

It's open to all at any skill level. Download the source, look at it, and see what you can do. Start small, and when you get more comfortable with modifying things, try to add a new command or feature we currently done have.

And feel free to ask questions on this forum.

ALERT!

Someone has tried to register using the IP Address 121.207.162.127 which is MATCHED IN THE RBL DATABASE of the proxies.dnsbl.sorbs.net RBL.

This registration attempt has been allowed and the account has been permanently banned.

Registration Details: shcdi4Ggong ( sunglassestom@gmail.com )