Disabling BZ `fedora_requires_release_note` flag
by Ben Cotton
I intend to disable the `fedora_requires_release_note` flag in
Bugzilla. These days, the Release Notes are mostly built via issues
against the Release Notes repo[1] on Pagure. Removing unused flags
simplifies the BZ experience for users and prevents the Docs team from
having to look in multiple places. pbokoc said it's okay, but I wanted
to run it by a wider audience just in case.
I see one open bug with the flag granted and none with it requested.
Five bugs closed in 2020 had the flag granted. One of those was a test
bug and two were for Change tracking bugs, which get Release Notes
issues as part of the process.
I will disable the flag on Friday 16 April unless there's a good
reason to keep it.
[1] https://pagure.io/fedora-docs/release-notes/issues
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years
- 1
- 1
Docs at https://docs.pagure.org/docs-fedora/ ?
by Ankur Sinha
Hi folks,
Someone referenced a document from here on AskFedora:
https://docs.pagure.org/docs-fedora/
I've not seen these before, and they don't seem to have the same content
as the quick-docs do either. Are they meant to be used (and are they
maintained by the community: last updated 2018)?
If not, we should look at disabling these so that users don't end up
here.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
3 years
- 2
- 3
Proposed update of Fedora's default content license
by Ben Cotton
Hi everyone,
I'm sending this to several lists that might care about the default
content license.
The Fedora Council is considering an update of the default *content*
license for Fedora contributions to the Creative Commons Attribution
Share-Alike 4.0 (CC BY-SA 4.0) license. Currently, it is CC BY-SA 3.0.
This license applies to content (not code) submitted to Fedora that
does not have an explicit license attached. It does not override the
explicit license choices of contributors or upstream projects.
For more information about the improvements in this license, see the
Community Blog post[1]. The Council will begin voting on this on 16
April in accordance with the Policy Change Policy[2].
To keep the discussion unified, please discuss this proposal in the
Discussion thread[3].
As a reminder, the Council posts proposed *policy changes* to
discussion.fedorapoject.org and communityblog.fedoraproject.org.
[1] https://communityblog.fedoraproject.org/policy-proposal-update-default-co...
[2] https://docs.fedoraproject.org/en-US/council/policy/policy-change-policy/
[3] https://discussion.fedoraproject.org/t/policy-proposal-update-default-con...
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years
- 1
- 0
- ← Newer
- 1
- Older →