Re: Beats and Changes - Writers wanted!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Original Message -----
> Hello,
> 
> Beats for Fedora 20 Release Notes are open. Take a look at
> https://fedoraproject.org/wiki/Category:Documentation_beats?rd=Docs/Beats ,
> find something that interests you, and take a beat!  If you do sign on,
> be sure to add your name to the appropriate column of the tracking
> table. More than one writer per beat is good, especially if they
> communicate, but zero writers for a beat is bad. You might also want to
> pick up the Changes bugs that apply in your beat, a new process for this
> release.
> 
> I've created a number of bugzilla tickets to help track Changes in the
> next version of Fedora. Please pick some up!  The Change process is
> outlined at https://fedoraproject.org/wiki/Changes/Policy and the
> current accepted proposals are at
> https://fedoraproject.org/wiki/Releases/20/ChangeSet .
>
> The are three tickets for each Change listed below: the Change tracker
> bug (CH), the bug for representing the change in the Release Notes (RN),
> and a bug against docs-requests to track impact of the Change on other
> guides.

Hi Pete,
thanks a lot. Btw. could you please send it to the devel-announce too - 
at least summary of the process. Some people asked me what these bugs
are about and if they have to take care about it.

Jaroslav
 
> So, here's the process. Each Change page on the wiki has a "release
> notes owner" - that's us.  Pick up the RN bug, and you are now the
> Release Notes contact for the Change. You'll be responsible for writing
> the changes into a beat on the wiki or directly to git, and ideally
> reviewing the copy with the Change owner. I like to make sure that the
> information is as actionable as possible, or at least refers the reader
> to actionable information.
> 
> The Changes will also impact our existing Guides. Ideally, the same
> person taking the RN bug will take the DR bug as well. You'll be
> responsible for identifying sections of currently maintained guides that
> need updating because of the Change in question.  I'm thinking a few
> choice grep invocations through your directory of docs repos should work
> in most cases. If you find something, open a new bug against the guide
> in question.
> 
> The first round of tickets are those identified as System Wide Changes:
> ============================================
> 
> ARM as Primary Architecture
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998560
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001329
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001330
> 
> AppInstaller
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998562
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001335
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001336
> 
> Migrate to Bluez 5
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998563
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001338
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001339
> 
> Boot 1.54 Uplift
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998564
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001341
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001342
> 
> Kdump with Secure Boot
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998565
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001343
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001344
> 
> SELinux Labeled NFS Support
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998566
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001345
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001346
> 
> NetworkManager Bonding
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998567
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001347
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001348
> 
> NetworkManager Bridging
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998568
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001349
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001352
> 
> No Default Sendmail
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998571
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001353
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001354
> 
> No Default Syslog
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998573
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001355
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001356
> 
> Python-setuptools update to 0.7
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998574
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001358
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001359
> 
> Ruby on Rails 4.0
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998578
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001361
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001362
> 
> Unversioned Docdirs
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998579
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001364
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001365
> 
> Visible Cloud
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998582
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001367
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001368
> 
> Web Assets
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998583
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001371
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001374
> 
> Perl 5.18
> CH: https://bugzilla.redhat.com/show_bug.cgi?id=998584
> RN: https://bugzilla.redhat.com/show_bug.cgi?id=1001375
> DR: https://bugzilla.redhat.com/show_bug.cgi?id=1001377
> --
> -- Pete Travis
>  - Fedora Docs Project Leader
>  - 'randomuser' on freenode
>  - immanetize@xxxxxxxxxxxxxxxxx
> 
> 
> 
> --
> docs mailing list
> docs@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/docs
-- 
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux