docs April 2018

docs@lists.fedoraproject.org

33 participants
29 discussions

[Fedocal] Reminder meeting : Fedora Docs Weekly Meeting
by bex＠fedoraproject.org 03 May '18

03 May '18

Dear all, You are kindly invited to the meeting: Fedora Docs Weekly Meeting on 2018-04-25 from 15:30:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: An hour of docs folks talking about what they are working on and what they'd like to work on. More information available at: [https://fedoraproject.org/wiki/Docs_Project_meetings](https://fedoraproject… Source: https://apps.fedoraproject.org/calendar/meeting/9196/

2 1

[Fedocal] Reminder meeting : Docs Writing Hour
by bex＠fedoraproject.org 30 Apr '18

30 Apr '18

Dear all, You are kindly invited to the meeting: Docs Writing Hour on 2018-05-02 from 10:00:00 to 11:00:00 US/Eastern The meeting will be about: Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content. There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week. Source: https://apps.fedoraproject.org/calendar/meeting/9195/

1 0

Re: The Docs FAS Group
by Brian (bex) Exelbierd 27 Apr '18

27 Apr '18

On Fri, Apr 27, 2018 at 1:14 AM, Susan Lauber <laubersm(a)gmail.com> wrote: > I'm still lurking but apparently not enough to have caught this before the > cleanup! > > I probably don't need publisher anymore but basic member at least, please. > > FAS ID: laubersm > I've re-added you to the docs group. I look forward to working with you and merging your PRs :) regards, bex > > > > On Wed, Apr 11, 2018 at 12:33 PM, Brian (bex) Exelbierd < > bexelbie(a)redhat.com> wrote: > >> This email has been BCC'ed to all 189 members of the FAS Group (minus a >> few known active people) >> >> In today's docs meeting we were talking about merge permissions. This >> email is going out to determine who in the group still wants to be active >> and help with reviewing PRs. >> >> We'd like to hear back from you, ideally on list, or to me directly, by >> Wednesday April 25. At that time we plan to clean up the list and barring >> objection, add some additional folks (separate email). >> >> If it turns out you were away, let us know and we will happily re-add you. >> >> We look forward to hearing from you. >> >> regards, >> >> bex >> >> -- >> Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com >> Fedora Community Action & Impact Coordinator >> @bexelbie | http://www.winglemeyer.org >> > > > > -- > Susan Lauber, (CCAH, CCSHB, RHCX, RHCA, RHCSS, RHCVA, CISSP) > Lauber System Solutions, Inc. > http://www.laubersolutions.com > gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974 > -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org

2 1

Fedora 28 Final Release Readiness Meeting on Thursday, April 26 @ 19:00 UTC
by Jan Kurik 26 Apr '18

26 Apr '18

Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 28 Final Release Readiness Meeting meeting. The meeting is going to be held on Thursday, April 26, 2018 at 19:00 UTC. Please check the [1] link for your time zone. We will meet to make sure we are coordinated and ready for the Final release of Fedora 28. Please note that this meeting is going to be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but it is by purpose to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information please check the [2] link. [1] https://apps.fedoraproject.org/calendar/meeting/9024/ [2] https://fedoraproject.org/wiki/Release_Readiness_Meetings Thank you for your support, Regards, Jan -- Jan Kuřík JBoss EAP Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

3 3

How to write release notes
by Petr Bokoc 25 Apr '18

25 Apr '18

Hi, I got a question earlier about how to start contributing release notes (or "how to make small contributions", which definitely includes release notes). We still urgently need contributions for Fedora 28, so if anyone wants to start now, even if you want to take one or two issues, it's always appreciated. You can contribute without having to even touch git or any other tools, so go ahead and read on even if you're completely unaware of our process; all you'll need is a Fedora Account System membership so you can comment in pagure. Start by going here: https://pagure.io/fedora-docs/release-notes/issues?status=Open&assignee=0 This is a list of unassigned issues in the release-notes repo. *Be careful here*, many are for Fedora 29 or not tied to any release - don't worry about those now, just get the ones that start with "F28 Change: ". Find an issue you like, and assign it to yourself - when you're logged in using your FAS account, there's a button that says "Take" in the right sidebar, so click that. Next, investigate. Start with the Wiki page linked in the issue description, check any links in that (there should be a link to Bugzilla that might provide additional information), google around, anything. Of course, if there are any comments by the owner in the issue, that's the first (and possibly last) information you'll need. If you're lost, @-mention the owner listed in the issue and ask them what it's about. Once you gain some understanding of the change you're covering, you can do one of two things with it, depending on how much time and technical knowledge you have: * If you're strapped for time, or can't use git (or asciibinder, or asciidoc, ...), just write a release note in the comments. Typically this should be a heading (which will almost always be identical to the issue name), and one or two paragraphs describing the change to Fedora's users. See Release Notes for previous releases for an idea what they typically look like, like here: https://docs.fedoraproject.org/f27/release-notes/sysadmin/Security.html In this link, every heading was originally a separate "Issue" in Pagure. Once you're done, @-mention the person responsible for the change (listed in the issue description on top), and ask them for a review; we'll give them a few days to respond. If they have any feedback, adjust your release note, if they don't respond, oh well. Once you're done (or the couple of days have passed), @-mention me and I'll mark up your release note and create a PR. I'll also check assigned issues from time to time in case someone forgets. * If you want to, you can write your note up in ASCIIDoc (check the repo structure and find a place for it), and submit a pull request against branch "f28" of the main repo. See https://pagure.io/fedora-docs/release-notes/pull-request/148 for a good example; note how the creator of the PR also @-mentioned the owner and asked for a review. Once the PR is merged, the issue it was made for is closed. There's also a boilerplate in each issue that roughly describes the process too. If you have any questions, either reply to the list, or ping pbokoc or bexelbie on #fedora-docs; we're both in UTC+2. Happy writing! -- Petr Bokoc (irc: pbokoc) Technical Writer Engineering Content Services Red Hat Czech, s. r. o. Purkynova 99 612 45 Brno, Czech Republic

1 0

Docs Meeting - 25 April 2018
by Petr Bokoc 25 Apr '18

25 Apr '18

Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2018-04-25/fedora_docs.201… Full log: https://meetbot.fedoraproject.org/fedora-meeting/2018-04-25/fedora_docs.201… -- Petr Bokoc (irc: pbokoc) Senior Technical Writer Customer Content Services Red Hat Czech, s. r. o. Purkynova 99 612 45 Brno, Czech Republic

1 0

Docs FAS Group Results
by Brian (bex) Exelbierd 25 Apr '18

25 Apr '18

I am sending the results of the email I sent out and replying to this conversation, so keep reading :D On Wed, Apr 11, 2018 at 9:40 PM, Matthew Miller <mattdm(a)fedoraproject.org> wrote: > On Wed, Apr 11, 2018 at 04:32:57PM -0300, Eduard Lucena wrote: > > > I'm not sure if community / sub-project docs fit into the scope of > > > needing merge rights to assist. Is this correct? > > I don't think so, because they are under Council Docs, so the council > > should be the permissions' holder > > Although the goal, of course, is for each the actual subprojects to own > their own spaces -- just for the Council to oversee the top level. > Exactly. This FAS group should just control merge rights for the core Fedora Docs. The distributed repositories we use should allow subprojects to directly decide who has commit rights to their docs/information. The Docs team will just publish that data as written to the website (or report that we can't publish because of an error and ideally submit a PR to the original docs to fix the problem). --------------- Reading the responses and thinking about the CI system, I think we should strongly consider moving to a PR based workflow. This will allow the CI to do the checking for us. Lots of people want the FAS designation in order to contribute. Let's make it clear that anyone can contribute by leveraging the CI and the PR concept. What do you think? ----------------- Results of Email: The docs FAS group would be the list of people able to merge those PRs and the entirety of FAS represents the people who can submit those PRs. I've opened a ticket with the results of the email responses. It contains the list of people I believe the FAS group should consist of based on responses. TICKET URL: https://pagure.io/fedora-docs/docs-fp-o/issue/71 I am SUPER MOTIVATED to see that list grow, but I am also glad to have a better feeling about who is active in our community. I'll make these changes after the meeting today, barring changes/discussion. ---------------- For those interested, I sent out 184 emails. I received: 29 "keep me" replies (including 8 new people) 11 "drop me" replies 14 bounces regards, bex

1 0

Fwd: Contributing docs for maintaining and creating a Fedora remix Comments
by Aidan Kahrs 24 Apr '18

24 Apr '18

Forgot this bit. ---------- Forwarded message --------- From: Leslie S Satenstein <lsatenstein(a)yahoo.com> Date: Tue, Apr 24, 2018, 8:51 PM Subject: Re: Contributing docs for maintaining and creating a Fedora remix Comments To: Aidan Kahrs <abkahrs(a)gmail.com> Hi Aidan Thank you for the prompt reply. For the topic I was reading, I was asking questions as if I am a first time Linux user who was told, «go build an ISO file» As I mentioned, I tweaked or rephrased a sentence or two, to make it more useful to non-English speakers. I could also help with the French editing (My French is Québec's version). French is a very very precise language. Any lawyer would tell you that a contract written in French is "tighter", ie, more precise than one written in English. We also must not write to put the reader to sleep. As I mentioned to Bex, I like to see a completed document. I am not too into your writing tools. Years ago I used IBM's gml and took a dislike to the labor involved with repeated "running, reviewing the output, tweaking" until ... I am glad to help Regards * Leslie* *Leslie Satenstein* *Montréal Québec, Canada* ------------------------------ *From:* Aidan Kahrs <abkahrs(a)gmail.com> *To:* For participants of the Documentation Project < docs(a)lists.fedoraproject.org> *Cc:* Leslie S Satenstein <lsatenstein(a)yahoo.com> *Sent:* Tuesday, April 24, 2018 1:29 PM *Subject:* Re: Contributing docs for maintaining and creating a Fedora remix Comments Leslie, Thank you for the suggestions on phrasing. We will certainly consider them and are open to pull requests once the final version has been published. Thank you. Sincerely, Aidan Kahrs abkahrs(a)fedoraproject.org On Tue, Apr 24, 2018, 1:04 PM Brian (bex) Exelbierd <bexelbie(a)redhat.com> wrote: On Tue, Apr 24, 2018 at 6:54 PM, Leslie S Satenstein <lsatenstein(a)yahoo.com> wrote: Brian Is it possible for me to get a "text document or libreoffice word document?" The link https://pagure.io/fedora-docs/remix-building/blob/master/f/remix-ci.adoc leads to an AsciiDoc formatted text document. Asciidoc is described at asciidoctor.org and is the current preferred documentation format. The author starts by saying using Jenkins. What is Jenkins and where can I get it or information about it. Not stated in the draft. Jenkins is a CI system. It is reasonable that readers of this document would know this. https://jenkins.io/ Example of correction: The choice of CentOS was to maximize support time and stay within the RHEL family. The choice of using CentOS was to maximize support time and to stay within the RHEL family. I would have written The decision to use CentOS was to maximize support time and to stay within the RHEL family. I did write you earlier about doing some editing and writing. I would be glad to work with authors to proof their writing. I am sure they would appreciate it. I presume you can accept updates after go-live. I don't see why they wouldn't. I know they would prefer PRs via pagure.io. regards, bex Regards * Leslie* *Leslie Satenstein* *Montréal Québec, Canada* ------------------------------ *From:* Brian (bex) Exelbierd <bexelbie(a)redhat.com> *To:* Development discussions related to Fedora < devel(a)lists.fedoraproject.org> *Cc:* For participants of the Documentation Project < docs(a)lists.fedoraproject.org>; "tigeros(a)ritlug.com" <tigeros(a)ritlug.com> *Sent:* Tuesday, April 24, 2018 5:56 AM *Subject:* Re: Contributing docs for maintaining and creating a Fedora remix On Tue, Apr 24, 2018 at 11:19 AM, Neal Gompa <ngompa13(a)gmail.com> wrote: On Tue, Apr 24, 2018 at 5:03 AM, Brian (bex) Exelbierd <bexelbie(a)redhat.com> wrote: > +devel list to attract feedback from other folks in releng or working on > other remixes and spins > > On Mon, Apr 23, 2018 at 7:04 PM, Aidan Kahrs <abkahrs(a)gmail.com> wrote: >> >> Hello. >> I know this thread has been kinda quiet the last few days. I wanted to put >> out an update that the draft documentation is finished. I have gotten input >> from my team. I would now like input from people within the docs effort >> before I say it is ready to publish. >> >> The draft docs can be found at >> https://pagure.io/fedora-docs/ remix-building/blob/master/f/ remix-ci.adoc <https://pagure.io/fedora-docs/remix-building/blob/master/f/remix-ci.adoc> > > > One comment: > > 14: Why is this server required to be a CentOS server? I have no problem > with CentOS but we should explain that choice in the context of a Fedora > Remix. > My experience is that it _should not_ be anything but a Fedora system. It should be at least be the target Fedora version or higher. Ideally, you always run the target version's livemedia-creator+Anaconda, which is why Koji uses mock to set up the environment and then run it inside of there. In addition, it's a very bad idea to recommend using "createrepo" instead of "createrepo_c", due to the former not supporting most of Fedora's newer RPM features and potentially weird things happening there. If you're using livecd-creator, you can get away with a lot more, since you're no longer sensitive to Anaconda's fragilities and the build engine is DNF. I believe we may be talking about different servers. The page seems to indicate the CentOS server is used to serve the bits. regards, bex -- 真実はいつも一つ！/ Always, there's only one truth! ______________________________ _________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists. fedoraproject.org <devel-leave(a)lists.fedoraproject.org> -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org _______________________________________________ docs mailing list -- docs(a)lists.fedoraproject.org To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org _______________________________________________ docs mailing list -- docs(a)lists.fedoraproject.org To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org _______________________________________________ docs mailing list -- docs(a)lists.fedoraproject.org To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org

1 0

Re: Contributing docs for maintaining and creating a Fedora remix Comments
by Aidan Kahrs 24 Apr '18

24 Apr '18

Leslie, Thank you for the tips. As far as the French editing, I would take that up with the larger Fedora Docs group. The plan is for the TigerOS team to make the initial contribution but we cannot commit to long term maintenance as we are all students and have high turnover within the team. Thank you. Sincerely, Aidan Kahrs abkahrs(a)fedoraproject.org On Tue, Apr 24, 2018, 8:55 PM Leslie S Satenstein <lsatenstein(a)yahoo.com> wrote: > I forgot to mention the fine difference between "finished" and "completed" > > Finished means dead, disposable, no further action. > Completed, means, ready for the next stage > > > > Regards > > > * Leslie* > *Leslie Satenstein* > *Montréal Québec, Canada* > > > > ------------------------------ > *From:* Aidan Kahrs <abkahrs(a)gmail.com> > *To:* For participants of the Documentation Project < > docs(a)lists.fedoraproject.org> > *Cc:* Leslie S Satenstein <lsatenstein(a)yahoo.com> > *Sent:* Tuesday, April 24, 2018 1:29 PM > *Subject:* Re: Contributing docs for maintaining and creating a Fedora > remix Comments > > Leslie, > Thank you for the suggestions on phrasing. We will certainly consider them > and are open to pull requests once the final version has been published. > Thank you. > Sincerely, > > Aidan Kahrs > abkahrs(a)fedoraproject.org > > On Tue, Apr 24, 2018, 1:04 PM Brian (bex) Exelbierd <bexelbie(a)redhat.com> > wrote: > > > > On Tue, Apr 24, 2018 at 6:54 PM, Leslie S Satenstein < > lsatenstein(a)yahoo.com> wrote: > > Brian > Is it possible for me to get a "text document or libreoffice word > document?" > > > The link > https://pagure.io/fedora-docs/remix-building/blob/master/f/remix-ci.adoc > leads to an AsciiDoc formatted text document. Asciidoc is described at > asciidoctor.org and is the current preferred documentation format. > > > The author starts by saying using Jenkins. > > What is Jenkins and where can I get it or information about it. Not stated > in the draft. > > > Jenkins is a CI system. It is reasonable that readers of this document > would know this. https://jenkins.io/ > > > > Example of correction: > > The choice of CentOS was to maximize support time and stay within the RHEL > family. > The choice of using CentOS was to maximize support time and to stay within > the RHEL family. > I would have written > > The decision to use CentOS was to maximize support time and to stay within > the RHEL family. > > I did write you earlier about doing some editing and writing. I would be > glad to work with authors to proof their writing. > > > I am sure they would appreciate it. > > > I presume you can accept updates after go-live. > > > I don't see why they wouldn't. I know they would prefer PRs via pagure.io > . > > regards, > > bex > > > > > Regards > > > * Leslie* > *Leslie Satenstein* > *Montréal Québec, Canada* > > > > ------------------------------ > *From:* Brian (bex) Exelbierd <bexelbie(a)redhat.com> > *To:* Development discussions related to Fedora < > devel(a)lists.fedoraproject.org> > *Cc:* For participants of the Documentation Project < > docs(a)lists.fedoraproject.org>; "tigeros(a)ritlug.com" <tigeros(a)ritlug.com> > *Sent:* Tuesday, April 24, 2018 5:56 AM > *Subject:* Re: Contributing docs for maintaining and creating a Fedora > remix > > > > On Tue, Apr 24, 2018 at 11:19 AM, Neal Gompa <ngompa13(a)gmail.com> wrote: > > On Tue, Apr 24, 2018 at 5:03 AM, Brian (bex) Exelbierd > <bexelbie(a)redhat.com> wrote: > > +devel list to attract feedback from other folks in releng or working on > > other remixes and spins > > > > On Mon, Apr 23, 2018 at 7:04 PM, Aidan Kahrs <abkahrs(a)gmail.com> wrote: > >> > >> Hello. > >> I know this thread has been kinda quiet the last few days. I wanted to > put > >> out an update that the draft documentation is finished. I have gotten > input > >> from my team. I would now like input from people within the docs effort > >> before I say it is ready to publish. > >> > >> The draft docs can be found at > >> https://pagure.io/fedora-docs/ remix-building/blob/master/f/ > remix-ci.adoc > <https://pagure.io/fedora-docs/remix-building/blob/master/f/remix-ci.adoc> > > > > > > One comment: > > > > 14: Why is this server required to be a CentOS server? I have no problem > > with CentOS but we should explain that choice in the context of a Fedora > > Remix. > > > > My experience is that it _should not_ be anything but a Fedora system. > It should be at least be the target Fedora version or higher. Ideally, > you always run the target version's livemedia-creator+Anaconda, which > is why Koji uses mock to set up the environment and then run it inside > of there. > > In addition, it's a very bad idea to recommend using "createrepo" > instead of "createrepo_c", due to the former not supporting most of > Fedora's newer RPM features and potentially weird things happening > there. > > If you're using livecd-creator, you can get away with a lot more, > since you're no longer sensitive to Anaconda's fragilities and the > build engine is DNF. > > > I believe we may be talking about different servers. The page seems to > indicate the CentOS server is used to serve the bits. > > regards, > > bex > > > > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ______________________________ _________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave@lists. fedoraproject.org > <devel-leave(a)lists.fedoraproject.org> > > > > > -- > Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org > > > > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org > > > > > -- > Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org > > > >

1 0

First time post - Request to post a new "How To": Spring Boot Authentication with FreeIPA
by Chris Kolodziejczyk 24 Apr '18

24 Apr '18

http://techdevsolutions.com/blogs/spring-freeipa This is a guide I wrote for securing a Spring Boot application using FreeIPA. Not sure if this is the place for that request, but I presume someone can lead me in the right direction at least.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs April 2018