Hi everyone,
The docs repositories for CoreOS, Silverblue, and container tooling are now set up (links below). I used the template repository that Adam linked in a previous email. Thanks for that! More content will be added this week. This was just an initial commit.
https://pagure.io/fedora-docs/containers https://pagure.io/fedora-docs/coreos https://pagure.io/fedora-docs/silverblue
The local building didn't work because of errors that I'll verify another time (with regards to whether it's because of the code or my current system).
How do we go about integrating them as sections in the current Fedora documentation? The goal is to publish some of the current really good documentation we have (like Chris Negus' Kubernetes on Fedora guide, container guide in general, etc.), and to be able to tell people where to go in order to get informed. With the integration into Fedora docs we now don't have to worry about infrastructure and formatting anymore, which is really nice.
Thanks, Sanja
Hey Sanja,
Great to see this!
I've just tried a local build of all three and it worked fine for me (using "./build.sh && ./preview.sh"). Let me know if I can be of any help.
About the next step, let me know when you're ready and I'll add them to the Fedora Docs. I think the best way to integrate them would be to link them from the "Technical Teams" section [1]. All three repos then get their own space, the same way as Modularity [2] has. Would that work for you?
Cheers! Adam
[1] https://docs.fedoraproject.org/en-US/fesco/teams/ [2] https://docs.fedoraproject.org/en-US/modularity/
On Mon, Aug 20, 2018 at 10:55 PM Sanja Bonic sanja@redhat.com wrote:
Hi everyone,
The docs repositories for CoreOS, Silverblue, and container tooling are now set up (links below). I used the template repository that Adam linked in a previous email. Thanks for that! More content will be added this week. This was just an initial commit.
https://pagure.io/fedora-docs/containers https://pagure.io/fedora-docs/coreos https://pagure.io/fedora-docs/silverblue
The local building didn't work because of errors that I'll verify another time (with regards to whether it's because of the code or my current system).
How do we go about integrating them as sections in the current Fedora documentation? The goal is to publish some of the current really good documentation we have (like Chris Negus' Kubernetes on Fedora guide, container guide in general, etc.), and to be able to tell people where to go in order to get informed. With the integration into Fedora docs we now don't have to worry about infrastructure and formatting anymore, which is really nice.
Thanks, Sanja
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
Hi,
Putting it under Technical Teams would mean it is three clicks away from the original documentation (Engineering -> Technical Teams -> x). That diminishes the value of having it integrated into the Fedora documentation since there is no search bar on top where people would find things if they searched for it, it'd be a "have to know it to find it" thing.
Silverblue, CoreOS, Containers are important parts of how Fedora can position itself as not just the distribution it is known for, but also for the value its container-based development options bring to developers. These three sections should be incorporated onto the main site of the Fedora documentation. There are two options I can think of to achieve that:
1. Either as boxes under "Fedora Project & Community" or 2. the whole "Engineering" part under "Fedora Project & Community" could be taken out, made its own point and Modularity is then its own section box just like Silverblue, CoreOS, and Containers.
Otherwise the content is hidden away. Let me know whether you think one of the options is feasible or whether you have other ideas. Thanks for your help!
Cheers, Sanja
On Tue, Aug 21, 2018 at 9:13 AM, Adam Samalik asamalik@redhat.com wrote:
Hey Sanja,
Great to see this!
I've just tried a local build of all three and it worked fine for me (using "./build.sh && ./preview.sh"). Let me know if I can be of any help.
About the next step, let me know when you're ready and I'll add them to the Fedora Docs. I think the best way to integrate them would be to link them from the "Technical Teams" section [1]. All three repos then get their own space, the same way as Modularity [2] has. Would that work for you?
Cheers! Adam
[1] https://docs.fedoraproject.org/en-US/fesco/teams/ [2] https://docs.fedoraproject.org/en-US/modularity/
On Mon, Aug 20, 2018 at 10:55 PM Sanja Bonic sanja@redhat.com wrote:
Hi everyone,
The docs repositories for CoreOS, Silverblue, and container tooling are now set up (links below). I used the template repository that Adam linked in a previous email. Thanks for that! More content will be added this week. This was just an initial commit.
https://pagure.io/fedora-docs/containers https://pagure.io/fedora-docs/coreos https://pagure.io/fedora-docs/silverblue
The local building didn't work because of errors that I'll verify another time (with regards to whether it's because of the code or my current system).
How do we go about integrating them as sections in the current Fedora documentation? The goal is to publish some of the current really good documentation we have (like Chris Negus' Kubernetes on Fedora guide, container guide in general, etc.), and to be able to tell people where to go in order to get informed. With the integration into Fedora docs we now don't have to worry about infrastructure and formatting anymore, which is really nice.
Thanks, Sanja
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/YDXL6T2QELEFHMPHVOARC6KCXD5JQETL/
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/VNJWJIZMVCHAVIYYV6OSQNRRMTQBW7GR/
On Tue, Aug 21, 2018 at 01:52:06PM +0100, Sanja Bonic wrote:
Putting it under Technical Teams would mean it is three clicks away from the original documentation (Engineering -> Technical Teams -> x). That diminishes the value of having it integrated into the Fedora documentation since there is no search bar on top where people would find things if they searched for it, it'd be a "have to know it to find it" thing.
Adam, can the left nav have multiple levels, so we can list the various teams immediately without a need for a click on that index page?
I think it'd also be good to have direct links on the front page, although that's already kind of a scary mess.
On Tue, Aug 21, 2018 at 3:46 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Aug 21, 2018 at 01:52:06PM +0100, Sanja Bonic wrote:
Putting it under Technical Teams would mean it is three clicks away from the original documentation (Engineering -> Technical Teams -> x). That diminishes the value of having it integrated into the Fedora
documentation
since there is no search bar on top where people would find things if
they
searched for it, it'd be a "have to know it to find it" thing.
Adam, can the left nav have multiple levels, so we can list the various teams immediately without a need for a click on that index page?
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on the left. So that was the reason I haven't listed the groups there, because if I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
Perhaps I could mark those links somehow? Or swap the pages under Engineering, so the "Teams" page would show up by default, and for more info about FESCo, people could click in the menu. Would that work?
I think it'd also be good to have direct links on the front page, although that's already kind of a scary mess.
Agree.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on the left. So that was the reason I haven't listed the groups there, because if I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up by default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
I'd like them as bubbles on the front page and think they belong there, naturally - especially with no search or index available. It is, after all, user documentation. One could argue to put them under the Fedora Project & Community part as well, but I do prefer it to be under User Documentation. If that's possible within how you envision things, then that's the best solution.
On Tue, Aug 21, 2018 at 6:52 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on
the
left. So that was the reason I haven't listed the groups there, because
if
I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up by default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/SQBGZ7HS4QTY67AHKFZRBRTWIKAKBCD7/
Let's do bubbles under User Documentation, then.
My initial reasoning was that if we put everyone on the homepage, it becomes messy. Bur since we don't have so many thing there, yet, let's go with it and fix it when it's needed. Good thing about the architecture is that all the URLs stay the same, no matter where we place the pointer.
And I definitely agree that search needs to be a priority.
On Tue, 21 Aug 2018 at 20:05, Sanja Bonic sanja@redhat.com wrote:
I'd like them as bubbles on the front page and think they belong there, naturally - especially with no search or index available. It is, after all, user documentation. One could argue to put them under the Fedora Project & Community part as well, but I do prefer it to be under User Documentation. If that's possible within how you envision things, then that's the best solution.
On Tue, Aug 21, 2018 at 6:52 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on
the
left. So that was the reason I haven't listed the groups there, because
if
I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up
by
default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
Is it possible to get a "accusé de réception" when we send an email. And if we send an email to you, is zip the proper file extension?
Regards Leslie
On Tuesday, August 21, 2018, 2:44:38 p.m. EDT, Adam Samalik asamalik@redhat.com wrote:
Let's do bubbles under User Documentation, then. My initial reasoning was that if we put everyone on the homepage, it becomes messy. Bur since we don't have so many thing there, yet, let's go with it and fix it when it's needed. Good thing about the architecture is that all the URLs stay the same, no matter where we place the pointer. And I definitely agree that search needs to be a priority. On Tue, 21 Aug 2018 at 20:05, Sanja Bonic sanja@redhat.com wrote:
I'd like them as bubbles on the front page and think they belong there, naturally - especially with no search or index available. It is, after all, user documentation. One could argue to put them under the Fedora Project & Community part as well, but I do prefer it to be under User Documentation. If that's possible within how you envision things, then that's the best solution. On Tue, Aug 21, 2018 at 6:52 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on the left. So that was the reason I haven't listed the groups there, because if I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up by default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
Leslie, I'm not sure if you mean Adam or myself now - I can confirm when I get an email. Do you mean for adding content for one of the three repositories?
On Tue, 21 Aug 2018, 19:58 Leslie S Satenstein, lsatenstein@yahoo.com wrote:
Is it possible to get a "accusé de réception" when we send an email. And if we send an email to you, is zip the proper file extension?
Regards
- Leslie*
On Tuesday, August 21, 2018, 2:44:38 p.m. EDT, Adam Samalik < asamalik@redhat.com> wrote:
Let's do bubbles under User Documentation, then.
My initial reasoning was that if we put everyone on the homepage, it becomes messy. Bur since we don't have so many thing there, yet, let's go with it and fix it when it's needed. Good thing about the architecture is that all the URLs stay the same, no matter where we place the pointer.
And I definitely agree that search needs to be a priority.
On Tue, 21 Aug 2018 at 20:05, Sanja Bonic sanja@redhat.com wrote:
I'd like them as bubbles on the front page and think they belong there, naturally - especially with no search or index available. It is, after all, user documentation. One could argue to put them under the Fedora Project & Community part as well, but I do prefer it to be under User Documentation. If that's possible within how you envision things, then that's the best solution.
On Tue, Aug 21, 2018 at 6:52 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on
the
left. So that was the reason I haven't listed the groups there, because
if
I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up by default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
Perfect, thanks - I'll let you know when it's ready to be published in its first form. Working towards getting that ready from my side by Friday morning European time (as usual, I hope it works out that way). Cheers!
On Tue, Aug 21, 2018 at 7:44 PM, Adam Samalik asamalik@redhat.com wrote:
Let's do bubbles under User Documentation, then.
My initial reasoning was that if we put everyone on the homepage, it becomes messy. Bur since we don't have so many thing there, yet, let's go with it and fix it when it's needed. Good thing about the architecture is that all the URLs stay the same, no matter where we place the pointer.
And I definitely agree that search needs to be a priority.
On Tue, 21 Aug 2018 at 20:05, Sanja Bonic sanja@redhat.com wrote:
I'd like them as bubbles on the front page and think they belong there, naturally - especially with no search or index available. It is, after all, user documentation. One could argue to put them under the Fedora Project & Community part as well, but I do prefer it to be under User Documentation. If that's possible within how you envision things, then that's the best solution.
On Tue, Aug 21, 2018 at 6:52 PM, Matthew Miller <mattdm@fedoraproject.org
wrote:
On Tue, Aug 21, 2018 at 03:53:50PM +0200, Adam Samalik wrote:
I don't wanna break the philosophy of the left menu only changing pages within the same component. Component == a section with its own menu on
the
left. So that was the reason I haven't listed the groups there,
because if
I click on something in that menu, I expect the menu stays there. It wouldn't in this case. Does that make sense?
It makes sense, but without search (or really any index, even) it makes things harder to find....
Or swap the pages under Engineering, so the "Teams" page would show up
by
default, and for more info about FESCo, people could click in the menu. Would that work?
Yeah, I think that'd definitely help. Make "Engineering" the index, basically. But wait! The more I think about it, the less sure I am that these really belong there anyway. These aren't engineering team docs -- they're user docs for these projects. I think maybe they're better as bubbles in the User Documentation on the front page.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/SQBGZ7HS4QTY67AHKFZRBRTWIKAKBCD7/
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/YHQ3TGKCBOGDYI54TOQONHXCYQ63UYGC/
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists. fedoraproject.org/message/IYYKHKQAUCO6VRTGNE6N4F3GHIHHN6XW/
That's a good point, I think I agree. Let me think about that for a while. Other people's ideas/opinions welcome!
On Tue, Aug 21, 2018 at 2:52 PM Sanja Bonic sanja@redhat.com wrote:
Hi,
Putting it under Technical Teams would mean it is three clicks away from the original documentation (Engineering -> Technical Teams -> x). That diminishes the value of having it integrated into the Fedora documentation since there is no search bar on top where people would find things if they searched for it, it'd be a "have to know it to find it" thing.
Silverblue, CoreOS, Containers are important parts of how Fedora can position itself as not just the distribution it is known for, but also for the value its container-based development options bring to developers. These three sections should be incorporated onto the main site of the Fedora documentation. There are two options I can think of to achieve that:
- Either as boxes under "Fedora Project & Community" or
- the whole "Engineering" part under "Fedora Project & Community" could
be taken out, made its own point and Modularity is then its own section box just like Silverblue, CoreOS, and Containers.
Otherwise the content is hidden away. Let me know whether you think one of the options is feasible or whether you have other ideas. Thanks for your help!
Cheers, Sanja
On Tue, Aug 21, 2018 at 9:13 AM, Adam Samalik asamalik@redhat.com wrote:
Hey Sanja,
Great to see this!
I've just tried a local build of all three and it worked fine for me (using "./build.sh && ./preview.sh"). Let me know if I can be of any help.
About the next step, let me know when you're ready and I'll add them to the Fedora Docs. I think the best way to integrate them would be to link them from the "Technical Teams" section [1]. All three repos then get their own space, the same way as Modularity [2] has. Would that work for you?
Cheers! Adam
[1] https://docs.fedoraproject.org/en-US/fesco/teams/ [2] https://docs.fedoraproject.org/en-US/modularity/
On Mon, Aug 20, 2018 at 10:55 PM Sanja Bonic sanja@redhat.com wrote:
Hi everyone,
The docs repositories for CoreOS, Silverblue, and container tooling are now set up (links below). I used the template repository that Adam linked in a previous email. Thanks for that! More content will be added this week. This was just an initial commit.
https://pagure.io/fedora-docs/containers https://pagure.io/fedora-docs/coreos https://pagure.io/fedora-docs/silverblue
The local building didn't work because of errors that I'll verify another time (with regards to whether it's because of the code or my current system).
How do we go about integrating them as sections in the current Fedora documentation? The goal is to publish some of the current really good documentation we have (like Chris Negus' Kubernetes on Fedora guide, container guide in general, etc.), and to be able to tell people where to go in order to get informed. With the integration into Fedora docs we now don't have to worry about infrastructure and formatting anymore, which is really nice.
Thanks, Sanja
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org/m...
-
Adam Samalik -
Leslie S Satenstein -
Matthew Miller -
Sanja Bonic