From Fedora Project Wiki

(Update the purpose statement)
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
===Condor's Notes===
<!-- This is a comment! -->
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action! Asking myself, "What should be the next step?" ]]
[[File:fedora_notebook.jpg | thumb | 400px | Decison making tools in action: What should be the next installation? ]]
<br/>
<br/>
==Introduction==
----
<p>
This content concerns community involvement starting with comprehending Fedora Quality Assurance
practices and protocols related to being friendly. Looking above Quality Assurance my first observation
is the importance of the current release schedule and the nature of [https://fedoraproject.org/wiki/Releases Fedora's Hybrid Release Schedule]. These observations are of the release of Fedora 33 in October 2020.
</p> 
<p>


</p>


==f34 current while f35 is under development==
==f33 current while f34 is under development==




{| class="wikitable"
[https://en.wikipedia.org/wiki/Digital_signal_processing Digital Signal Processing] ->
! Ordinal Coordinate || Task Name  || Description
[https://fedoraproject.org/wiki/Test_Day:2021-03-03_Audio_Test_Day Pipewire Testing]</br>
|-
[https://fedoraproject.org/wiki/Test_Day:2021-03-17_Fedora_34_GNOME_40  Gnome 40 Testing]</br>
|
<p>Writing an evaluation before the end of the procedure seems odd, but sometimes we need
1
to take a breath and collect our thoughts. This is only the second release cycle I'm
||
following closely and I'm making decision on the move. For instance, the delicate Win 10
'''Activity Log'''
installation that's been my laptop's internal hard drive has been removed and the ancient
||
60 GB SATA drive I've used for testing is now the laptop's internal hard drive.</p>
[[user: condor/dribble | Activity Log ]
|-
|
2
||
'''Fedora Flock 2015'''
||
[[user: condor/flock | Flock Itinary ]] 
|-


<p>It seems best to base testing on what is important when using a production installation in a
production role. It also good practice to continue testing the features previously tested
as part of the lead up to new testing. Hence, looking at btrfs, ARM, and pipewire, before
on to test Gnome 40.</p> 


<p>Early adopters of the next release need the new software to be production quality ASAP.</p>
==f32 current while f33 is under development==


|3
==F33 -> F34==
||
2/9/21</br>
'''Purpose Statement'''
Applications</br>
||
OpenSCAD</br >
The purpose of my Fedora Project involvement is to remain on the bleeding, leading edge of the Gnu/Linux family of technologies; to ever increase my technical knowledge of the Fedora ecosystem including methodologies as they are advanced.  These purposes are achieved by networking within the community, actively using Fedora,  and promoting Fedora to the general public. 
Gazebo</br>
|-
FreeCAD</br>
|4
Synfig (New Interest)</br>
|| Schedule in principle
||


{| class="wikitable"
1/9/21</br>
! Day Of Week || Task  || Description
Once again communications channels.</br>
|-
|
Monday
||
# '''Career Development'''<BR />
# '''CONDOR Activities'''<BR />
# '''Fedora QA'''
||
Description Body
|-
|
Tuesday
||
'''Typical day off'''<BR />
||
Description Body
|-
|
Wednesday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Thursday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Friday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Saturday
||
# '''The Day Gig.'''
||
Description Body
|-
|
Sunday
||
'''Typical Day Off (with nothing scheduled)'''
||
Description Body
|}
|-
|5
||Important Links
||


==F32 -> F33==
12/08/2020
IRC Chat, Telegram, Matriix</br>
Rebasing Silverblue</br>
My first Silverblue installation went belly up this morning,</br>
therefore 12/15/2020 is declared a Fedora involvement.</br>


==Release Schedule==
[https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle The Life Cycle of a Fedora Release]


[https://lists.fedoraproject.org/pipermail/test/ Test Mailing List Archive]<BR />


[http://lists.gnu.org/archive/html/help-bash/ Bash Help List Archive]<BR />
==Test Days==
[http://lists.gnu.org/archive/html/bug-bash/ Bash Bug List Archive]<BR />
===F34 Testing===
[http://fedoraproject.org/wiki/Fedora.next Fedora Next]<BR />
<BR />
[https://lists.gnu.org/archive/html/qemu-devel/ Qemu Devel List]<BR />
<BR />


[https://lists.fedoraproject.org/pipermail/test/2014-May/121247.html May Test Matrix]<BR />
[https://fedoraproject.org/wiki/Test_Day:2021-01-04_Kernel_5.10_Test_Week Kernel 5.10 ]
[https://lists.fedoraproject.org/pipermail/qa-devel/ QA Devel Mailing List Archive]


|-
virt-manager test</br>
|6
SilverBlue test</br>
||Miscellany
Raspberry Pi test</br>
||
----
[[user:condor/notes | Top Level of my notes]]<BR />
[http://docs.fedoraproject.org/en-US/index.html Fedora Documentation]<BR />
[[User:Condor/Networking-notes | (Preliminary) Networking Notes]]
|}




===F33 IoT Test Day===
----
====Initial====
[http://fedoraproject.org/wiki/Test_Day:2020-09-30_Fedora_33_IoT_Edition IoT Test Announcement Day]


Visit me here: [http://www.josephpesco.info/qaz My Wiki ]
[https://testdays.fedorainfracloud.org/events/95 IoT Edition Result Page]
====Resources====
===F33 Btrfs By Default Test Week===
----
====Initial====
Install to Previous KVM
====Release-blocking (x86_64)====
====Desktop====
====Modularity====
====Guided Storage Configuration====
====Exploration====
====Resources====
[https://btrfs.wiki.kernel.org/index.php/Main_Page btrfs home page @ kernel.org]
 
==Resources==
----
<div>
Visit me here: [http://englishgrammar.josephpesco.info My Personal Blog ]
 
[https://meetbot.fedoraproject.org/ Fedora Meeting Bot]
 
[https://fedoraproject.org/wiki/QA/Join#release-validation release-validation]


[[Help:Wiki_syntax_and_markup | Local Wikimarkup cheat sheet]]
[[Help:Wiki_syntax_and_markup | Local Wikimarkup cheat sheet]]


[https://www.mediawiki.org/wiki/Help:Formatting  Mediawiki help]
[https://en.wikipedia.org/wiki/Btrfs English Wikipedia Btrfs Article]
[https://bugzilla.redhat.com/page.cgi?id=bug-writing.html Red Hat Bugzilla Bug Writing Guidelines]
[https://docs.fedoraproject.org/en-US/project/code-of-conduct/ Code of Conduct]
[https://fedoraproject.org/wiki/Legal:PrivacyPolicy?rd=Fedora_Project_Wiki:Privacy_policy Privacy Policy]
</div>
<!-- ==================================== -->
<!-- ==================================== -->


<!-- https://fedoraproject.org/wiki/User:Condor/Networking-notes  -->
<!-- https://fedoraproject.org/wiki/User:Condor/Networking-notes  -->

Revision as of 19:17, 21 March 2021

Decison making tools in action: What should be the next installation?



Introduction


This content concerns community involvement starting with comprehending Fedora Quality Assurance practices and protocols related to being friendly. Looking above Quality Assurance my first observation is the importance of the current release schedule and the nature of Fedora's Hybrid Release Schedule. These observations are of the release of Fedora 33 in October 2020.

f34 current while f35 is under development

f33 current while f34 is under development

Digital Signal Processing -> Pipewire Testing
Gnome 40 Testing

Writing an evaluation before the end of the procedure seems odd, but sometimes we need to take a breath and collect our thoughts. This is only the second release cycle I'm following closely and I'm making decision on the move. For instance, the delicate Win 10 installation that's been my laptop's internal hard drive has been removed and the ancient 60 GB SATA drive I've used for testing is now the laptop's internal hard drive.

It seems best to base testing on what is important when using a production installation in a production role. It also good practice to continue testing the features previously tested as part of the lead up to new testing. Hence, looking at btrfs, ARM, and pipewire, before on to test Gnome 40.

Early adopters of the next release need the new software to be production quality ASAP.

f32 current while f33 is under development

F33 -> F34

2/9/21
Applications
OpenSCAD
Gazebo
FreeCAD
Synfig (New Interest)

1/9/21
Once again communications channels.

F32 -> F33

12/08/2020 IRC Chat, Telegram, Matriix
Rebasing Silverblue
My first Silverblue installation went belly up this morning,
therefore 12/15/2020 is declared a Fedora involvement.

Release Schedule

The Life Cycle of a Fedora Release


Test Days

F34 Testing

Kernel 5.10

virt-manager test
SilverBlue test
Raspberry Pi test



F33 IoT Test Day


Initial

IoT Test Announcement Day

IoT Edition Result Page

Resources

F33 Btrfs By Default Test Week


Initial

Install to Previous KVM

Release-blocking (x86_64)

Desktop

Modularity

Guided Storage Configuration

Exploration

Resources

btrfs home page @ kernel.org

Resources