View and vote on the article here: Issue #1 : CyberArmy Staff Digest Sep 2004
Issue #1 : CyberArmy Staff Digest Sep 2004| Category | | | Summary | | The CyberArmy Staff Digest is a collection of topics that have been discussed in the past month on the CyberArmy staff forums. It is hoped that by sharing this information with the rest of the CyberArmy community that their thoughts and concerns can be ad |
| | Body | This past month has been fairly slow on the Staff forums. This is most likely the result of the summer coming towards a close and people taking vacations and spending time with friends and family before school and work start to pick up again in the fall.
Instead of going in chronological order this Staff Digest will be organized by topic.
CyberArmy Backend
- Dinah Code Release
Before the release could be finalized a license still had to be decided on and the challenge code taken out (don't want any cheaters, now do we). This in itself is a fairly complicated task and for the moment various svndumpfilter abuses are being tested to strip out the challenge code without screwing up the revisions/history/etc too much. These topics are still being addressed.
- Preferred license for CA source releases
One of the biggest topics was the discussion about code licensing. There are many licenses to choose from including closed source, GPL, BSD, modified Apache, etc. One of the goals of CyberArmy is to release Open Source software, but at the same time we wish to respect each contributor's rights to his or her own code. When it comes to the topic of the CyberArmy backend code this debate becomes even more heated because some people have put so much work into it that they don't want it just being ripped off by anyone on the internet. The final decision seems to be pretty much summed up in this post by wa1800z:
"as long as the contribution is for the website directly, that includes dinah code, art and brigade work (including, reports, articles, forum posts, etc?), we use an ASF Contributors license derivative.
For projects being worked on by cyberarmy members (using cyberarmy facilities, I guess), nothing special needs to be done, beside the fact that it should be an OSI [www.opensource.org] approved license"
Though this issue seems to be resolved for the moment expect that it will be reopened again in the future and you can expect a wiki to be created shortly.
CyberArmy Website
- CyberArmy Files Access
Access to the CyberArmy files tree will be set up similar to that of the forums where there can be an administrator was well as access given to specific groups. It also allows access control and moderation features to keep everything under control. This will come in handy for different brigades or projects that need to have separate storage facilities.
- Projects Wiki Update
The projects wiki really came together with the help of a few staff members, most notably Ker Hisim. The structure and some content were added, but the real advantage of the wiki is in letting it grow naturally by having other contributors. As the CyberArmy projects plan moves forward expect this wiki to really take off.
- Chaldev
The challenge development team had been stalling and the leading member had gone LOA so more leadership was requested and with Gen ToTaL coming back to the CA community it was thought he might be a good candidate for his experience with the development of other challenges. He agreed to take on the job. Lets hope for some good things from them.
Important Issues
- zZine
Although already an issue on the member's forum, the restructuring of the zZine sub-brigade was thought to be interfering with other brigade's to an even greater extent then just the public arguments. For this reason C/Os were asked to disregard these issues for the time being until it was better understood where zZine was headed as a whole.
- Update on moderation issues
Some of the moderation issues talked about in the last staff digest, which includes extending the CyberArmy code of conduct across all CyberArmy mediums, were brought up again to see if there were any comments, thoughts, or additions. It seems that everyone is in agreement with the original post and so far the thread has no responses and so the code of conduct will remain applicable to all areas of CyberArmy and a release should be made about it by Moderation members on the main forums shortly.
- Staff input required
CAU requests that members start going through the Knowledge-Bank and start rating some articles. This will improve the efficiency of the up coming CAU search engine that will include ratings in its evaluation. Although some staff members were up to the job to start pumping some out, it is a good idea for all CyberArmy members who have a free moment to check it out because it will eventually benefit everybody.
Misc
- Asmodai back on staff?
Gen Asmodai was brought back onto staff after a short vote. He had been retired due to time constraints but now he is back.
- Security Forum update
Header information was updated on the security forum, it seems some of the links had gone bad.
That's it for this month and remember that if you have any comments or concerns that you don't want to bring up on the forum you can always submit ideas through the feedback form.
|
|
This article was imported from zZine. (original author: SamSpade)
There are no replies to this post yet.
|