On Wed, Feb 12, 2020 at 9:42 AM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > On Wed, Feb 12, 2020 at 9:37 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > > > The nuance is usually that ISVs often are forking packages and > > maintaining their own fixes without being a regular contributor to > > Fedora. > > Okay. So are: > > > 38. As an ISV developer who contributes to Fedora, I can fork a dist-git repo via mirroring, make changes, and submit them back to Fedora as applicable so that I can contribute to Fedora. > > 39. As a distro developer, I can fork dist-git repos via mirroring, make changes, and submit them back to Fedora from my Git server so that I can contribute to Fedora. > > distinct from a requirements perspective? It seems like 38 could > either be a part of 39 or of a general contributor workflow, depending > on how the ISV developer is working. It's not clear that 38 provides > any additional information other than another persona. > They could probably be folded into one requirement, rewording the first clause to be "As an independent software or distro developer,". -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
