Re: [Audit-test-developer] RHEL-7.1 audit-test suite pushed as rhel7_1

[Cyril H. <ch...@su...>]

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 would have to confirm if it's okay to release the patches and locate
the git repository but I suppose that this would be doable at least.

> 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.

The biggest problem would be locating these in the pile of, quite often
unclean, patches.

> > 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?

To be completely honest here, I do have enough on my plate with
maintaing LTP upstream. Hence unfortunately I do not have any resources
for doing patch review for another upstream project.

> 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.

Given that there are upstream repositories for audit and selinux it
would probably makes sense to reuse these for the certification purposes
in the long term.

-- 
Cyril Hrubis
ch...@su...