View and vote on the article here: Behind the Scenes of Sered
Behind the Scenes of Sered| Category | | | Summary | | For those who are new to CyberArmy, I shall give you a little background information on Sered. Sered was the proposed name for the new set of challenges to replace the old Zebulun challenges, which were CyberArmy's main focus before the rank split and br |
| | Body | For those who are new to CyberArmy, I shall give you a little background information on Sered. Sered was the proposed name for the new set of challenges to replace the old Zebulun challenges, which were CyberArmy's main focus before the rank split and brigade system were implemented.
First off, let's look at how far Sered got in terms of its development. From the account given by zZine's source for this article (a member of the original Sered development team) Sered had a complete storyline, a detailed level schema and the first couple of challenges coded (the code was never integrated into the site as development of Dinah and the Sered GUI was still underway at the time).
So what happened to Sered? In simple terms, it failed. But why?
The development team was under a great deal of pressure from both CA Staff and the member base as a whole. Although not the primary reason for the resignation of the challenge development team, a few key members felt that both the staff and the membership were not seeing the whole picture, despite constant attempts at reassuring members that the challenges were progressing. Some members, on the other hand, became agitated by the continued demand for the challenges and information on the challenges.
Sered was to be released once everything was complete rather than in stages, so it would take a considerable amount of time to get to a finished release. Chaldev members also felt that there was little help from the CyberArmy Staff regarding these matters, but as the team and project were then largely classified to all except Executive Staff, this situation should have been somewhat expected.
After some discussions, and a lot of time, the issues although not fully solved, have at least reached somewhat of a compromise and the members have become present to an extent within the community once more, however the code still remains in their hands. There are currently no plans to use the Sered code, and a new set of challenges is under development.
The decision to take the code was originally made out of frustration. From the core team's prespective, why provide a set of challenges to those who did nothing but make demands? The team did, however, develop CyberArmy's current temporary challenge, Alphaplex, which at the time of writing this article, has not been passed in over a year. This raises some interesting questions, which I will leave the reader to ponder at their leisure. |
|
This article was imported from zZine. (original author: xayto)
There are no replies to this post yet.
|