Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=226187 --- Comment #14 from Jason Tibbitts <tibbs@xxxxxxxxxxx> 2010-01-07 16:30:51 EDT --- Honestly I'm not sure what the best course of action would be. The current situation is something we want to get away from; we don't want to be maintaining the source directly inside the Fedora package. We really don't like pointless forking and all the "Fedora doesn't work with upstream" grousing that comes with it, and we've worked very hard to avoid that kind of thing. Stopping short of filing a bunch of upstream tickets for each of our patches, how hard would it be to let upstream know that regardless of what's happened in the past, Fedora would like to reduce or eliminate the current divergence and show them the current set of patches we're carrying? If they reject or ignore the attempt at contact then we can at least get a quick fedorahosted project set up so that there's some public source for what's in this package. Alternately, I'm happy to open a FESCo ticket and ask them for guidance. They could grant an exception, but more likely they'd recommend something not much different than I detail above. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review