Patch sharing or start a new upstream?Most distributions contain packages where upstream is completely dead or very close to it, yet there still is a significant user group for the packages in question, be it directly or through other packages depending on them. But even when upstream is alive, packages often needs some additional patching.All distributions seem to end up carrying some custom distro grown patchset, with some patches being shared and other patches being unique per distro. Clearly not an ideal situation and one which most distributions try to avoid by feeding all necessary changes upstream and aiming for having packages which use the upstream provided code as is.Clearly the usual model of sharing code fixes / integration work done at the distribution level between distributions by pushing it upstream does not work for projects where there is no upstream. And even with upstream around, distributions sometimes needs to fix bugs in versions that upstream no longer care about or fix bugs that are not important/considered feature upstream and it may take a long time to get them fixed there. In the end we can't avoid all patching. But we can try to avoid duplicating the work by better sharing the results.The plan for this sessions is to give a short presentation sketching the problem, show two possible approaches to help solving this problem together with few generally helpful ideas. After presenting these hopefully somewhat structured discussion with the audience about this topic is planned.