Difference between revisions of "Project management suggestions"

Revision as of 01:29, 2 February 2010

This page is intended as a collaborative repository for suggestions on how to improve the social site. Create a new section for each specific suggestion or related group of suggestions. Feel free to discuss them to some extent on this page, but bear in mind that discussions should be refactored every once in a while into a summary of the idea - the purpose of this page is to consolidate discussion into a more easily-referenced form.

See social site suggestions for other subject areas.

Project "progress" status

It is too hard to tell if a project is done or in progress or abandoned.

There is no filter option or way to mark your project as completed and ready for use. It would be nice if projects could be given a completion attribute (i.e. planning, building, alpha testing, beta testing, released, etc).

Abandoned projects clutter up the list enormously. Projects should be automatically disabled or flagged if there is no activity in them for some threshold criteria length of time and they remain incomplete/never started.

I'd throw in that it should be activity from the project owner themselves, since here's a good example of a popular long abandoned project that still has people posting comments all the time - http://social.bioware.com/project/602/. The owner has already so much as said in the comments that they now hate the game and have abandoned it. Yet the project is now more like a petition than anything else I suppose.

Other project filter options

Advanced Filter Options button. Currently the drop-down boxes for filtering are all independent of one another. If you want to browse in the groups there are 4 lists. Would be nice to have an advanced filtering options button that will pop up a little dialog box where you can make all your selections at once and then say GO!

• Would be nice to be able to filter out completely all those projects with fewer than X members.
• Would be nice to be able to filter out completely all those projects that haven't had any activity at all for X days.
• I would also like to see the author of the project without opening it up.

When you click on projects the list can only be viewed 10 items at a time, which is way to few.

Redundant filters: Some of the drop down options are not something anybody would be interested in listing them by or are duplicated by others (e.g. popularity? most views? what is the difference between those two?). Ordering by most views is unlikely to generate a significantly different ordering than sorting by last updated or popularity. All the older projects are likely to have more views than the any of the newer ones, so ordering by create date isn't going to be significantly different than ordering by most views. This isn't a major problem, frankly more options are better than fewer, but the ones you really need (which projects are "the best" and which are "not worth the effort", which are done which are still in progress) aren't there.

Rating projects

Problems with the current rating system

• The modules that have been around the longest will have the most "+" while a brand new awesome module may never get noticed. This encourages builders to do a rush job just so they can be one of the first ones out there. Perhaps a weighted rating system, so that a very large/old mod can sit up their with a brand new smaller mod of equal caliber that just hasn't garnered the high amount of ratings yet.

• Provide a checkbox on a project that a host can check when he/she considers the content "done" and ready to be ranked with the others. This would allow you to post work-in-progress downloads to gather feedback, without the concern of getting low ranks because it is not done yet.

• Once you have given a project a "+", there is no way to remove that again, even if you discover later that the project didn't deserve it at all.

Variation and changes to the current rating system

• Have two ways to rate projects -- one similar to the NWVault's rating system (is it a good idea, do people like it, etc), and another where people could rate the "buggyness" or "stability" or "ease of setup" type things about the project.?

• Or perhaps just a screen with two or three categories to rate that get computed into some overall rating (e.g. Design/Idea 1-10, Stability/Ease of Use 1-10, Something Else 1-10). For me it would be far more useful to be able to filter and sort on these kinds of peer judged criteria than by "most views" or a generic "popularity" with unclear basis.

• Maybe projects need a sex rating system similar to what hollywood does (e.g. G, PG, PG13...XXX).

• NWVault has a rating system where you give a 0-10 score, but the rating is hidden until a specific minimum number of people have rated the project. The average number may be meaningless - in NWNvault, an absurdly high percentage of modules have a rating above 9.0, but still the relative ranking is pretty good - a module with a high score and a high download count is probably worth looking at..

Download counting

You cannot update a file without losing the download count - it gets reset back to zero. This would need to be fixed - the ideal solution would be to count the number of people downloading files from the project, but at the very least allow people to update files without losing the download count. As it is, the download count is pointless and actually discourages builders from updating their files.

Project classification

• If a project got incorrectly classified originally, or if a more appropriate category is added later, there is no way to re-classify the project. Allow module owners to change the category of their projects.

• The list of classifications is a mess, with builder-to-builder and builder-to-player categories mixed up. Also, the categories are not well chosen - the NWN modules category is just a pointless waste of space and several categories seem to be missing.
  • Add more project categories (areas, scripts, machinima, tutorials, music, and so on)
  • Separate builder-to-player content from builder-to-builder content. The biggest hurdle to mod creation is creating levels, so a level category would be particularly useful.

Categories to potentially remove or change:

• NWN module
• It is a bit confusing to have "Dragon Age Addons" as well as "DA Gameplay mods", as to most people those categories overlap.

• Replace the one-big-list project page with a splash page with links to separate categories. Include an "all mods" button so we can still get to the huge list if we want to. And allow mods to be in more than one category.

The list of project categories, in order, at the time of writing is

• Dragon Age addons
• NWN Modules
• Builder - DA Mods
• Builder - DA Textures
• DA Playable Modules
• Builder - DA Utilities
• Builder - DA VO files
• DA Gameplay Mods
• DA Item/Armor/Weapon Mods
• DA Character Mods

Whether or not these names are final, and even though it may not be all that relevant at the moment, I think the list should be sorted either by category or game, in alphabetical order, and that games only be represented in their short form. E.g.

• ...
• Modules - DA(:O)
• Modules - NWN
• ...
• Textures - DA(:O)
• ...

or

• ...
• DA(:O) - Modules
• DA(:O) - Textures
• DA(:O) - Utilities (what are those anyway?)
• DA(:O) - VO Files
• ...
• NWN - Modules
• ...

Alternative approach to classification: tags instead of categories

Too many/too unspecific categories can cause similar projects to be categorized differently because they fit under too many categories. I would suggest only a very general level of categorization and leave the specifics to tags. For instance, allow only a single category for game modules but let the author assign Gameplay, Item, and Character (and any other) tags as applicable.

Two things that would definitely have to be considered for such a solution are:

• if the tags are gathered in one global list, some tags will not make any sense whatsoever for certain projects. On the other hand, category exclusive lists seems like a lot of database bloat, and what do you do when the tag(s) you're looking for are not (yet) in the category your project is in?

• if only the author can assign tags, risk of vandalism is greatly reduced, not to say eliminated. Meanwhile, allowing all users to add/remove tags to/from projects greatly increases the likelihood of the average project being more appropriately categorized (tagged).

Subscribed projects view

Under View, add "Subscribed projects" - once I have found projects that are sufficiently interesting to want to follow them, I want to be able to find them again easily. Not everyone knows of http://social.bioware.com/user_bw_projects_subscriptions.php

Project Comments

The comments on Projects is horrible. If they can be made so you can have more than 10 per page and be able to jump to any page in the comments they'd be much better.

Please show the latest comments first. Currently when you go to view comments under a project, it shows the very first comments. It is supposed to show the newest comments first. In the case of a project that has 190 comments, for example, that means one has to click Next Page 19 times!

Captchas in project forums

Could we drop having to solve a captcha to post in a project forum? It ties into the problem above about the comment system, which is all the captcha system probably reinforces, and seems kind of pointless given how somebody could just spam up the comments anyway.

Extend valid file types for projects

I created (what is now) a DA Playable Modules project. In addition to uploading the module (DAZIP) file I want to upload the builder-to-builder (DADBDATA) file and the art resources (in this case just LVL files) so that the community could see how we made the module. However the valid types for a DA Playable Modules project do not allow these file types. I am loathe to made another project simply to accommodate these additional file types so I am requesting the project's file types be extended to allow all extensions associated with Dragon Age and ZIP/RAR in addition to the ones already allowed.

See: Red Riding Hood Redux for the example

Project/Group "Discussions"

Project and Group discussion areas should be replaced with full "Forum" functionality. The owner of the Group/Project should have the ability to assign Moderators. They should be able to set up Forum Areas, Sticky Posts, Moderate, and do all other things that a Moderator might otherwise be able to do. This would allow for a lot more flexibility and "site stickiness" for groups of people that do things together. Also, any upgrades to the forums functionality could be added to this construct at the same time, thereby eliminating the need for two sets of codebase for what is virtually the same activity.