From Fedora Project Wiki
There is a page named "ISV" on Fedora Project Wiki. See also the other search results found.
Page title matches
- ...about your software license and compatibility with Fedora standards? The ISV SIG can help. # Join the [http://www.redhat.com/mailman/listinfo/fedora-isv-sig-list mailing list].2 KB (291 words) - 21:50, 17 September 2016
- [[ISV Welcome|Welcome]]. This is the independent software vendors (ISV) special interest group (SIG). If you are considering packaging your ISV software for Fedora, read [[Fedora for ISVs]].5 KB (799 words) - 17:35, 5 November 2021
Page text matches
- ...about your software license and compatibility with Fedora standards? The ISV SIG can help. # Join the [http://www.redhat.com/mailman/listinfo/fedora-isv-sig-list mailing list].2 KB (291 words) - 21:50, 17 September 2016
- ...defunct|See [https://gregdekspeaks.wordpress.com/2012/01/06/why-the-fedora-isv-sig-never-caught-fire/ Greg DeKoenigsberg's excellent postmortem blog post] If a security problem is discovered then the ISV will fix it in the next release or will provide an update mechanism as part5 KB (804 words) - 20:46, 19 September 2016
- [[ISV Welcome|Welcome]]. This is the independent software vendors (ISV) special interest group (SIG). If you are considering packaging your ISV software for Fedora, read [[Fedora for ISVs]].5 KB (799 words) - 17:35, 5 November 2021
- {{Anchor|ISV-IHV-Perspective}} === ISV/IHV Perspective ===5 KB (855 words) - 16:13, 8 September 2021
- {{Anchor|ISV-IHV-Perspective}} === ISV/IHV Perspective ===6 KB (890 words) - 20:05, 6 January 2022
- ...://www.kolabsys.com Kolab Systems AG] || Not Public (yet) || Packaging for ISV products4 KB (597 words) - 12:05, 28 May 2022
- === Independent Software Vendor (ISV) === The ISV can be anything from a one- or two-man shop to a software design and develo0 members (0 subcategories, 0 files) - 12:50, 28 May 2020
- === Independent Software Vendor (ISV) === [[SIGs/ISV | ISV SIG]]0 members (0 subcategories, 0 files) - 01:25, 21 February 2018
- === Independent Software Vendor (ISV) === The ISV can be anything from a one- or two-man shop to a software design and develo134 members (10 subcategories, 0 files) - 16:02, 15 August 2023
- === Enterprise and ISV Developer - Systems of Innovation - Ben === === Traditional ISV ===22 KB (3,318 words) - 17:24, 16 August 2016
- ** '''no''' : SIGs/ISV/Join6 KB (859 words) - 21:17, 29 November 2015
- ** '''no''' : SIGs/ISV/Join6 KB (878 words) - 01:14, 13 September 2019
- ...ny cases develop their own methods for managing their SELinux policy. The ISV experience should improve significantly with the SELinux Modularity effort ...e as policy can be branched and managed per-application/module, and higher ISV/third-party involvement as policy development/packaging becomes easier.27 KB (4,083 words) - 20:03, 19 March 2018
- * Building an ISV ecosystem, including [[EPEL|EPEL]].7 KB (985 words) - 14:46, 18 September 2016
- ** '''no''' : SIGs/ISV/Join7 KB (631 words) - 21:52, 29 November 2015
- == What if my ISV/IHV wants to maintain a package in EPEL? == ...EPEL. For more information, read the [[About EPEL#ISV.2FIHV_Perspective| ISV/IHV Perspective]].24 KB (3,877 words) - 20:01, 6 January 2022
- ...raded on a rolling basis or as needed based on other requirements e.g. new ISV application needing a new glibc and a desire from users to deploy that in t8 KB (1,356 words) - 05:39, 3 November 2017
- ** '''não''' : SIGs/ISV/Join6 KB (996 words) - 15:13, 30 November 2021
- ...fers a range of software and hardware certifications including third party ISV applications. Rebuilds often have a substantial [http://lwn.net/Articles/3411 KB (1,659 words) - 11:29, 9 October 2021
- Formal ISV certification is available for Red Hat Enterprise Linux, which shares many54 KB (1,575 words) - 14:22, 31 July 2015