Why are you all jerks?!

Posted by firestormx on Oct. 24, 2010, 11:30 a.m.

Canadonian just posted a blog entry about v3, and you're all mocking his efforts! Even the mods! What kind of stupid site not only has mods that do not stick up for members, but joins in the mocking?!

plz dont flame me.

Anyway, in my v3 update to you guys (well, to those with server access), Matt and I are porting over v2's code into v3's design. It's easier for us to just do it (and we're making a lot of headway), because we can sit in the same room, and he can design, and I can code, and we can communicate our ideas immediately to each other.

Once this stage is done (in another week or two), I'll be sending out an email to the devs again so that they can come in and start adding the new features.

Speaking of new features, there's very little that is actually set in stone for new features. Matt and I have a large list of features that we want to add in, but they're mostly just our interpretation of how a feature should work. Every so often, I guess I should mention a new feature we're working on, and ask how you want it to work. (I believe there's a general suggestion thread for v3 features in the forum. go find it)

Today's concept for a feature (that a lot have seen coming): Team Pages.

Teams are a little fuzzy in my mind as to what kind of scope they should give. A team page will be sort of like your user. You have a front end where you post your news/blogs for the team, a file manager, a little discussion area, etc.

So if you had a section of the site reserved for your team, what would you want to be able to do? Even in a general sense.

For EXAMPLE, I would like a team to have a front page specifically for their team related news. From there, there are links to each of the team's projects.

Within the projects there are:

- blogs/updates for the public

- profile page for the public, which shows who is working on this project

- file manager for internal use

- forum for internal use

- to do/bug list for internal use

A team's projects could then be "published" as a game on the site, just like a single user would, with a slight differentiation to show it came from a team. (Matt and I have already worked this part out)

Post your ideas.

Edit: Thanks to Kilin planting the seed, and F1ak3r driving it home with the suggestion, Matt and I decided that instead of making team pages, we'll only make "projects". Very similar to team pages, so keep your suggestions coming, except that instead of having an overall team page, the projects will be a group of users working towards a single project, rather than a slew of projects.

Comments

Castypher 13 years, 6 months ago

Quote:
Team Pages
If we could get a little collaboration going, I think that'd be a really good addition. But I think the site is a bit too personal right now, and it feels like team pages would do better in a less personal environment. Kind of like YYG I guess. Not to say I don't want to give it a try. Team projects are always a bit touchy in indie development.

Glad to see V3 is getting some more work done on it. I got too busy to keep doing my own work so I haven't had a chance to even open FireFTP for 64Digits.

firestormx 13 years, 6 months ago

I'm hoping that team pages will help to get people to collaborate and motivate each other to keep going with their projects. It should also help to bring more people to 64D as well (if one person joins and starts a team, they'll want to bring their friends from other sites to 64D to be part of the team.

It'll also be useful for officially giving multiple people credit for a game (ie "Adrenaline" has bryan, OL, and things like that)

F1ak3r 13 years, 6 months ago

Maybe a project-orientated system is worth considering. Teams that work on multiple games… don't often exist.

firestormx 13 years, 6 months ago

Actually, that's a really good point, and it makes things a lot simpler for me.

So rather than team pages, I'll just make projects. If a group of people want to work another game together, they'll just make another project.

Thanks!

F1ak3r 13 years, 6 months ago

Great. While my ideas are being used, I don't think I ever showed you the FAQ I wrote. Sure, V3 will probably invalidate most of it, but maybe you could put it up for now - it's a good deal more current than the current FAQ.

flashback 13 years, 6 months ago

OH NO CRITICISISISIMS IMMA HAVE TO BANHAMMER YOU

firestormx 13 years, 6 months ago

Do it flashback, do it! Finally someone who cares about how they treat members around here!

flak: thanks. Since I've got the FTP open, I updated the FAQ with your new stuff. =)

I hope it's all correct, 'cause everyone knows I didn't read it first.

Castypher 13 years, 6 months ago

Quote:
Killin
You keep getting my name wrong, you dick. >=[

If the team projects page is versatile, it might spark more collaboration, like you said. For example, you might have a "team leader," who recruits users or accepts applications to the projects. You might have a member list that shows their roles. Then have a few other pages regarding the actual game.

Team leaders might be touchy, but it's the only way I could think of making those examples.

Now all we have to do is get people inspired to work together more.

firestormx 13 years, 6 months ago

Killin: No I don't. Where? lies. Stop lying killin. Maybe I should just change your name to "lying killing". My blog mentions your name with only one "l"

I think we'll keep it with just projects for now. Less work for me. It can easily be expanded into teams at a later time though, if I plan this right.

sirxemic 13 years, 6 months ago

Quote:
Canadonian just posted a blog entry about v3, and you're all mocking his efforts!
Oh, come on… several people have tried to finish and launch V3 for several YEARS and then when another someone says he is working on it you expect us to take it seriously instantly?

It's a great idea (finishing V3), but the credibility of anyone stating to finish V3 is kinda small now.

Also, great tips:

- try to use divs + css as much as you can and tables as few as you can

- try to make the code as clear as possible (shouldn't be a problem while being sober instead of being drunk [which was the case when V1/V2 was written I've heard?])

- if possible, review the database. Like, fix the different styles ampersands, apostrophes etc are escaped.