Hello.
I would like to highlight some random information from around the
community.
- The new Fedora translation platform is up and running:
https://translate.fedoraproject.org/
You can start translating, and you can contact friends and other
community members speaking your language, and organize a team (if the
localization team for your language is no more active).
Probably, the more important bits until the release of F32 are the
strings related to the website and the release notes.
- Elections for Fedora 32 supplemental wallpapers is undergoing and
will close on April, 30
https://apps.fedoraproject.org/nuancier/elections/
Only Fedora contributors can vote. A contributor is defined by someone
having an account on FAS, having signed the FPCA and being in one
additional group (CLA+1).
- Fedora 32 Upgrade Test Day will take place from April 2 to April 6.
If you have a spare hardware to use for testing the upgrade, or a
virtual machine, you are welcome to participate. You can find more
information here:
https://communityblog.fedoraproject.org/fedora-32-upgrade-test-day-2020-04-…
- A brief article from the Fedora Project Leader about the Fedora Code
of Conduct (CoC):
https://communityblog.fedoraproject.org/on-being-part-of-the-fedora-communi…
- April, 21 is the preferred target date for the release of Fedora 32
Bye,
A.
Here's an excellent opportunity to contribute to the Fedora 32 release,
and learn lots about Fedora while we do it!!
----- Forwarded message from Petr Bokoc <pbokoc(a)redhat.com> -----
> Date: Fri, 13 Mar 2020 00:45:37 +0100
> From: Petr Bokoc <pbokoc(a)redhat.com>
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Subject: Fedora 32 release notes are waiting for your contributions!
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
> Thunderbird/68.4.1
>
> Hi everyone!
>
> Today's F32 Beta Go/No-Go meeting earlier today resulted in a no-go status, but
> nevertheless, it's about time we started working on F32 release notes. As
> usual, we aim to cover notable Changes[0]. Ben Cotton has been tracking those
> in the relnotes repo's issues for us, which allows us to grab a list of
> everything that needs to be documented[1].
>
> Some of you are already familiar with the process, so go ahead and grab some
> issues; branch f32 is waiting for you. For those of you who are new or need a
> refresher, here's how it works:
>
> 1. Pick one or more issues in the list linked above.
>
> 2. Open each issue you picked, and click the Take button on the right to claim
> it. (If you claim an issue but later find out you don't have time to write
> about it, remove yourself from the issue ASAP so others can see it's free and
> take it!)
>
> 3. Find some information about the issue. A lot of them have plenty of info in
> them already; if not, find out who's responsible for the change, and talk to
> them on IRC or via mail. Of course it's always better if you try to do research
> before you ask questions. Note that you might not always be able to reach the
> owner in a reasonable timeframe; in that case just do your best, I'll be
> reviewing PRs, so if we publish something wrong, it's on me.
>
> 4. Write a release note about the issue. If you're not sure how exactly a
> release note looks, check out some of the previous releases for inspiration. We
> don't want any long, overly technical texts, the release notes are meant to
> highlight changes, not to tell people how to use something.
>
> 5. Now the workflow diverges based on your permissions and technical skills:
>
> 5a. If you know how to use git and asciidoc, we'd appreciate if you wrote up
> the release note and sent a pull request[2] against the main repo, branch
> "f32". Your contributions should go into one of the files in "modules/
> release-notes/pages/", which one exactly depends on the contents of the change
> you're documenting. Use the "build.sh" and "preview.sh" scripts in the
> repository root to preview your changes locally; see the repository README for
> specific instructions. If you can't see the section where you added your
> contributions at all, make sure it's included in "modules/release-notes/
> nav.adoc".
>
> 5b. If the above sounds like gibberish to you, it's fine: just add a comment
> with your text into the issue, and ping me on IRC/Telegram or through e-mail;
> I'll mark it up for you and make sure your contribution appears in the final
> document.
>
> If anyone has any questions, go ahead and ask either here on the list or on IRC
> /Telegram, I'm happy to help. The current schedule[3] gives us until April 14
> (see line 9), after that we'll be handing the release notes to the localization
> team. This gives us a month, which should be enough to cover the 55 open
> issues.
>
> Happy writing!
>
> Petr
>
> [0] https://fedoraproject.org/wiki/Releases/32/ChangeSet
> [1] https://pagure.io/fedora-docs/release-notes/issues?status=Open&
> search_pattern=F32&close_status=
> [2] https://docs.pagure.org/pagure/usage/pull_requests.html
> [3] https://fedorapeople.org/groups/schedule/f-32/f-32-docs-tasks.html
>
> _______________________________________________
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
> 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/docs@lists.fedoraproject.org
----- End forwarded message -----
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
Hello!
There are still a lot of quick-docs that were automatically converted
from wiki pages that have not yet been reviewed for correctness. If you
have a few minutes, please pick one and check it to see if the
information is correct and up to date.
https://docs.fedoraproject.org/en-US/quick-docs/
I've opened some tickets that folks can take up, mostly for newcomers.
https://pagure.io/fedora-docs/quick-docs/issues
There are lots of pages that I've not created tickets for yet. If you
take one of those up, please open a ticket to let folks know that you
are working on it.
Honestly, most of these are so simple, 5 minutes is all it'll take!
You'll get a cookie from me on IRC as a reward!! A whole cookie!! :D
For any questions, please head to the docs channels/mailing list:
#fedora-docs, docs(a)lists.fedoraproject.org
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
Hi folks,
If you are on Fedora 31 or can run a test Fedora 31 machine, please test
upgrading to Fedora 32 to see how it is going. Please reply to the
thread on the -devel list if you see any errors.
We'd like our users to have a smooth upgrade experience, and this is a
simple way to help!
----- Forwarded message from Miroslav Suchý <msuchy(a)redhat.com> -----
> Date: Wed, 4 Mar 2020 16:24:58 +0100
> From: Miroslav Suchý <msuchy(a)redhat.com>
> To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
> Subject: Donate 1 minute of your time to test upgrades from F31 to F32
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
>
> Do you want to make Fedora 32 better? Please spend 1 minute of your time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> sudo dnf --releasever=32 --setopt=module_platform_id=platform:f32 \
> --enablerepo=updates-testing --enablerepo=updates-testing-modular \
> distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal potential problems. You may also run `dnf
> upgrade` before running this command.
>
>
> If you get this prompt:
>
> ...
> Total download size: XXX M
> Is this ok [y/N]:
>
> you can answer N and nothing happens, no need to test the actual upgrade.
>
> But very likely you get some dependency problem now. In that case, please report it against the appropriate package. Or
> against fedora-obsolete-packages if that package should be removed in Fedora 32. Please check existing reports first:
> https://red.ht/2kuBDPu
>
> Thank you
>
> --
> Miroslav Suchy, RHCA
> Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> 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/devel@lists.fedoraproject.org
----- End forwarded message -----
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London