Issue #1745: Hosting Request for "Fedora Security Spin" - fedora-infrastructure

fedora-infrastructure

#1745 Hosting Request for "Fedora Security Spin"

Closed: Fixed None Opened 14 years ago by jsimon.

Project Name: Fedora Security Spin

Project Short Summary: providing a fully functional livecd based on Fedora for use in security auditing, forensics, and penetration testing

SCM choice (git/bzr/hg/svn): git

Importing from another SCM? NO

Project admin Fedora Account System account name: lmacken, maxamillion, jsimon

Trac Instance? Yes

Mailing List(s)? No

nigelj commented 14 years ago

Sorry, clarification required:

What content are you planning on putting on Fedora Hosted, we already provide some infrastructure for Fedora Spins via the Spins SIG.

Refer to https://fedoraproject.org/wiki/SIGs/Spins

So my question is: What gap needs to be filled that isn't filled by the Spins SIG?

jsimon commented 14 years ago

Replying to [comment:1 nigelj]:

Sorry, clarification required:
What content are you planning on putting on Fedora Hosted, we already provide some
So my question is: What gap needs to be filled that isn't filled by the Spins SIG?

The Spins SIG is the right place to set common rules for spin development and also come in game if the "product" is finished. There is https://fedorahosted.org/spin-kickstarts but this is nothing we use for early state ks files, artwork things or status updates on the wishlist or documentations. Right now all this stuff is dispersed across multiple platforms wiki(https://fedoraproject.org/wiki/SecuritySpin), artwork ... to have a place where we can move tracking things from the wiki - and to join all this resources and keep track on further development.
https://fedorahosted.org/fedora-electronic-lab is a perfect example.

chitlesh commented 14 years ago

Well there is a difference between SPIN SIG and SPIN maintainers(+community).

The spin sig formalizes the process of promoting the "product" developped by spin maintainers. However the spin sig does not interfere with what will be the new features of the spin along as the software is among fedora repositories.

Unlike general fedora distribution which has a clear predefined feature list for every upcoming release, most spins doesn't not have a clear goal except general packaging of popular software of their field.

Hence I support Joerg's request for a trac instance which can help him create a community around his spin and work with this community to establish features for F-N release or even F-N+1 release.

Take FEL for example, https://fedorahosted.org/fedora-electronic-lab/report/1
We get lots of request from users who only want to use the spin. But having file a ticket following their request those users feel they are heard and in my experience most of them give more feedbacks during testing. We have already started working on F-13 and an university is helping us for testing of one of our F-13 features.