From: Jiri J. <jja...@re...> - 2018-05-17 09:44:13
|
On 05/16/18 23:48, Paul Moore wrote: > On Tue, May 15, 2018 at 8:46 AM, Cyril Hrubis <ch...@su...> wrote: >> Hi! >>> It seems a shame that we can't combine efforts to maintain a common >>> repository. Personally I think moving away from a common repository, >>> even if it is one with distro-specific branches, is a big step >>> backwards. >>> >>> What would it take to get folks to start contributing again? Is it as >>> simple as moving to GH? >> >> I guess that it's too late for past releases, I doubt that anybody would >> allocate resources for merging SLE12 related changes to upstream at this >> point. > > What if we simply created a SLE12 specific branch in the upstream repo? > > I admit that it is unlikely anyone will spend a significant portion of > time towards merging the entire set of changes, but there is always > the possibility that there could be some smaller changes which are > easy to merge and generally applicable. If nothing else it > consolidates everything in one place which I think would be beneficial > for everyone. > >> For the record we tried to upstream at least some of the changes but we >> have given up because there was no real upstream. What we need is a >> someone who reviews and applies patches and maybe then we can get most >> of the fixes upstream when we start working on next certification. > > Ask not what you upstream can do for you, ask what you can do for upstream. ;) > > Would you be willing to work with Jiri to help reinvigorate the > upstream effort? At the very least, what about distro/release > specific branches? Jiri, what do you think? I unfortunately don't think I have the time needed to do upstream work for the project. I also don't think it's really worth putting the effort in - these days, you have things like https://github.com/SELinuxProject/selinux-testsuite https://github.com/linux-audit in addition to LTP and other projects. Keeping a project that exist as a blend of everything for the only and sole purpose of doing EAL4 alive as upstream is IMHO not realistic. Anyone who would like to help the overall Linux testing effort in general will likely contribute to LTP instead. That being said, the pushed RHEL-7.1 changes are only a very small portion of the work I've done on the suite and I have about 260 commits "sidestepping" it for generic Fedora testing. In that branch, I rewrote the entire network-server logic using a modular TCP server with proper locking logic everywhere in the suite, re-did the syscall relevancy logic and generally updated the whole suite to be more relevant to bleeding-edge distros. I'll see if I can get that published somewhere (here or on my github account), for posterity and code copy/pasting if nothing else. Jiri > > I'm trying to avoid the situation we had in the early days of the > Linux CC effort where test development was done in private and there > was a *lot* of duplicated effort. > |