--- Tyler Larson <fedora-config@xxxxxxxxxxx> wrote: > Which brings me to my next question: once you create a new project, > how > do you set it all up officially? You know, project spec, CVS > repository, > project maintainer, etc? Brent, this seems like something you could > help > us with. Sourceforge is always available. > I'd be willing to work as a maintainer if no one else wants the job. > I > have a pretty extensive understanding of networks, protocols, and > iptables, so this project is right up my alley. But like a number of > us > here, this is my first time ever using python, gtk, et al., and I've > never created RPM before or any of that jazz. I'm very familiar with Python and somewhat proficient with GTK, RPM, and firewalls. I can't promise too much, but especially during the next month, I can probably be of some assistance. I can be especially helpful if you give me clear requirements: I don't want to lead the project, but I wouldn't mind using my PyGTK framework to churn out some nice code. Just to reiterate, we're building a simple firewall tool for personal use. We're not trying to reinvent Firewall Builder, or anything else, eh? What's wrong with the "Security Level" configuration utility? > Finally, I was wondering how we're supposed to handle communication > relating to specific projects that we're working on. Should the bulk > of > the communication be routed through the mailing list, or is the list > just for communication about configuration tools in general? Do we > set > up little project-specific mailing lists, or how does this all work? Again, I think the mailing lists that come with a Sourceforge account could be used. I'm guessing that this list is for talk about the "Fedora" part, whereas a Sourceforge list would be more for the "application domain" part. Have fun, -jj __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/