Today we created a new, permanent, location for pykickstart: https://github.com/pykickstart/pykickstart/ And I've agreed to be the new maintainer. I've been involved with Anaconda and pykickstart since I joined Red Hat in 2010 so this isn't a new experience for me :) My general philosophy for this is going to be "don't break it". I consider pykickstart to be one of the best examples of how to write a python library, especially one that has to support so many different features and versions so I have no plans to make fundamental changes. I consider it primarily to be in maintenance mode, driven by bugfixing and requests from Anaconda. Recently there have been some requests to add features to pyks for the livecd-creator project that don't have (and never will) support in Anaconda. I've been trying to come up with a way to make everyone happy -- and haven't. At the moment I think the best way to proceed is to require that new features need to have patches, and be accepted by, Anaconda. Anything else is just going to lead to a fractured user experience, confusing documentation, difficult to debug problems, etc. Since Anaconda is the primary user for pyks it makes practical sense to have the installer team's input on new features. I also will *not* be re-reviewing any old closed requests. If the previous maintainers declined to add something I am not going to re-open it. -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
