CyberArmy University | Open Source Institute | CyberArmy Intelligence & Security | CyberArmy Services & Projects

[CyberArmy] Feedback Digest - January 2006


[Reply] [View by Thread] [Help]
[Back To Article Discussion Forum]

Posted by Author icklenewt On 2007-04-29 10:02:22




View and vote on the article here: Feedback Digest - January 2006


Feedback Digest - January 2006

Category
CyberArmy
Summary
Near the beginning of January the Projects system was released. When large changes are made or new sections are added to the site, there are always bugs to be filtered out and ideas for improvements. Due to this, we received an influ
Body
Near the beginning of January the Projects system was released. When large changes are made or new sections are added to the site, there are always bugs to be filtered out and ideas for improvements. Due to this, we received an influx of requests this month relating to /projects. As such, submissions relating to the project system are listed in separate categories for this month's Feedback Digest.

Project System Features
  • BBCode: This has now been enabled for project descriptions.
  • Project Categories: Initially the projects were primarily categorized by brigades. After receiving a suggestion via Feedback, this has now been altered. The categories now provide a better indication of what projects entail, e.g. Multimedia, administration, security. You can still easily recognize which brigade a project is under as the title uses the relevant brigade color.
  • Public Profile: Due to a suggestion via feedback, the projects a user is a member or leader of are now displayed in their public profile.
  • Projects News Admin: We received a request to add a preview option for this feature. This has now been implemented.
  • New member notification: Project leaders now receive a cMS informing them when a member has joined their project.
  • Secondary Leaders: A user suggested allowing secondary leaders to a project (like X/Os). This will not be implemented at this time, but will be reconsidered in the future.
  • Deleting a Project: In /projects, you can't delete projects. Deletion can only be done via the brigade command panel. It shall remain this way as only project admins can delete a project, so at present it is sensible to leave this as it is.
  • cMS All: Originally, the project leader and admin were not included in the 'cMS all' feature (available on the project admin page). A user requested the inclusion of these types of members, and this has now been implemented.
  • Project Leader: People from all over CA can join a project, but the project leader could only be someone from inside your brigade. It was suggested that any member should be able to be the leader. This has now been implemented. When you 'edit' a project you can set any member as the leader.
  • Project ToDos: Originally, a project leader could add a task to a member's ToDo list; however, they could not view these or remove them. The ToDo system has now been updated. Project leaders can now see and delete the ToDo tasks added to each member. Members have their own personal ToDo list which works the same as always, but if you get a Task added by a project admin, you will see a 'Project ToDo list', categorized by project (in case you are a member of many). Only project leaders can delete these ToDos.
  • ToDo All: It was suggested that a project leader may wish to add a task to all members' ToDo lists. This has now been implemented.
  • Request Discharge: A user pointed out that the 'Join this Project' link is unsuitable for those already in a project, and suggested it be replaced with a 'Request Discharge' option. This will be implemented shortly.
Project System Bugs
  • Description Wrapping: Long descriptions for projects were not wrapping correctly. This has now been fixed.
  • Description Spacing: New lines were getting stripped, leading to the bunching together of paragraphs. This has now been fixed.
  • Link Exchange: Feedback received a submission from a representative of another website proposing an exchange of links between the sites. If your site is interested in something similar, please submit a proposal via Public Relations.
  • Logs: The logging available to Project leaders was broken. This has been fixed.
  • Member Listing: A comma was being appended to the end of the list of project members. This has now been corrected.
  • [admin] link: An [admin] link was displaying to all users, even though they were then unable to access that section. This has now been removed (unless you have the necessary access).
  • Invite List: A user's nickname was not being removed from the invite list after joining. This has been fixed.
  • Project Description: A user informed us that if the [code] tag is used in the project description, then it may cause the width of the table to expand and the lines will not wrap. This is not a bug. Lines of code are not meant to be wrapped and should only have new lines where they originally did. As such, this will not be altered, but we do ask users not to use the [code] tag if it is not suitable for their purposes.
  • Empty Categories: All categories were being displayed even if they contained no projects. Empty categories are now hidden.
  • Remove Member: There were some problems removing users from a brigade, giving the error that they were a project leader (and had to be removed from this position before being discharged). This has now been fixed.
Features
  • Honorary listings in brigade structure: One feedback submission suggested creating a more official way to display honorary members of a brigade in the brigade tree. It was felt that this is no longer necessary as the new project system helps address this issue. (Note: This submission was received prior to the project system's release.)
  • CA Header: A member pointed out that the header on CyberArmy is getting full, and suggested removing (or moving) some of the links. This will not be done as the issue is addressed by the new CyberArmy design that is being created. If you are interested in helping out on this project, or viewing the progress, take a look at Dinah Design.
  • Start New Thread: A user requested moving the 'start new thread' link to the bottom of a forum's MOTD. This is due to some forums having a long MOTD. We will be adding an additional link below the MOTD.
  • Personality Test: One member suggested creating a test for users to take to tell them which brigade would be of best interest to them. It is felt that this is not practical at this time, and hence shall not be implemented.
  • Rank Reformat: We received a suggestion to aid users' identification of new members in CA. The idea is to give new members the rank 'Recruit'. When such a member joins a brigade or project, they will automatically be promoted to Trooper. It was felt that this would be a useful improvement to the current ranking system, and shall be implemented shortly.
Other/Miscellaneous
  • Rank Thumbnails: Currently the original rank images are resized to a smaller version in various places. A user suggested creating thumbnails instead, to improve the quality. This is already being worked on.
Report A Bug
  • Brigade Structure: Along with the arrival of the new projects system, the display of brigades was altered. Initially, some sections were not indented correctly. This has been fixed.
  • Sered HoF: The Sered Hall of Fame is currently not available to those not logged in. This has been added to the coder's ToDo list to be fixed.
  • Wrong banner redirection: One of the CA banners was pointing to the wrong address. This has been corrected.
  • Images Not Loading: When viewing via https, some images were not loading since they came from unsecured links (http). This has been corrected.
  • Search Forum: A value in the search form was incorrect. This has been corrected.
  • Time Since Last Post: We received a submission indicating an occurrence where nothing was given in the field indicating the time since a post was made on /forum. It was deduced that the time since the last post in question had been 0 seconds. In such an event, the code that finds the difference between the current time and time of last post returns nothing rather than indicating 0, hence giving a blank field. This has now been corrected, '0s ago' will be displayed in future cases.
  • cMS Preview: If, when replying or forwarding a cMS, you previewed before sending it, the message it was replying to or forwarding would not be correctly marked (the small arrows that appear beside messages indicate this). This has been fixed.
  • /command/logs bug: The /command section (available to staff members only) contained a link error in the log feature. This has been corrected.
  • /includes browsable: The /includes directory on CA was browsable to all. This has now been changed.
  • Banner Transparency: When viewing CyberArmy using Internet Explorer, the transparency on some of the banners displays incorrectly. This will be fixed soon.
Thank you for all your feedback. Every submission is considered and discussed. Please expect to wait up to several weeks to receive details regarding the outcome of your feedback. If you have yet to hear back regarding a request or report you made, please don't hesitate to cMS me (icklenewt) and I'll chase it up and reply to you with its status.

Remember, if you wish to be contacted in response to your feedback, or are requesting assistance, ensure contact details are enclosed.


This article was imported from zZine. (original author: icklenewt)


There are no replies to this post yet.



Guest:
Subject:
Message:
Signature:
Optional Image Link:
http://

CyberArmy::Forum v0.6
Generated In 0.01725 seconds


About Us | Privacy Policy | Mission Statement | Help