November 2018 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

Koji / epel-7 - What's going on?
by Frantisek Zatloukal 02 Jan '19

02 Jan '19

Hi, I am currently trying to build new resultsdb[0] into epel7-candidate. However, I am facing some (weird?) behavior around python-flask, I am able to do a successful build of resultsdb (depending on python-flask) in mock epel-7 and koji scratch epel-7 [1]. However, it is failing on not-available python-flask in koji to epel-7-candidate [2]. Am I overlooking something? Thanks very much! [0] https://src.fedoraproject.org/rpms/resultsdb/blob/epel7/f/resultsdb.spec [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=31025152 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=31025187

5 9

ostree: silverblue manifest is now fedora-silverblue.yaml
by Dusty Mabe 30 Nov '18

30 Nov '18

Corresponding configs change is in: https://pagure.io/workstation-ostree-config/pull-request/115# This will require the bodhi machines to have the hotfixed pungi rpm with this fix: https://pagure.io/pungi/pull-request/1088 This was already hotfixed on the composer machines. Dusty

2 3

Meeting Agenda for 2018-11-29
by Stephen John Smoogen 28 Nov '18

28 Nov '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-11-08 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2018-11-29) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info tflink is on extended PTO #info bodhi updated #info fpdc with release info available in staging (https://fpdc.stg.fedoraproject.org/api/v1/release) - cverna = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info nirik is on call from 2018-11-22->2018-11-29 #info smooge is on call from 2018-11-29->2018-12-06 #info ??? is on call from 2018-12-06->2018-12-13 #info Summary of last week: (from nirik ) #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Bodhi 3.11.1
by Randy Barlow 28 Nov '18

28 Nov '18

Bodhi 3.11.1 was released and deployed to production today: https://bodhi.fedoraproject.org/docs/user/release_notes.html

1 0

ansible: fedmsg-hub-3 support
by Adam Williamson 27 Nov '18

27 Nov '18

hey folks! just wanted to pass along a note about this change I made to the infra scripts today: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=6c390c… What I did was extend a bit of scaffolding that already exists to handle fedmsg deployment differently if the host is in a group with 'python34-fedmsg' in its name (the 'python34' there is a EL-ism, but I didn't want to change it) so it now also covers fedmsg-hub as well as fedmsg-base. Now, if a system is in a group with 'python34-fedmsg' in its name and the 'fedmsg/hub' role is run on that system, instead of enabling the 'fedmsg-hub' service, it'll enable the 'fedmsg-hub-3' service. The 'restart fedmsg-hub' handler is also tweaked so it conditionally restarts *both* 'fedmsg-hub.service' *and* 'fedmsg-hub-3.service' (this seemed like the easiest solution to the service restart problem; as we're using conditional-restart.sh, whichever isn't present will just be ignored). This should help with moving things from Python 2 fedmsg to Python 3 fedmsg. It should be relatively easy to extend to the other fedmsg roles too, if desired - I didn't do that as I didn't want to change too much, and fedmsg-hub is all I needed for the box I'm migrating. Please let me know if you have any comments, concerns or suggestions about this, thanks! I did ask around on IRC and it didn't seem like anyone had a better idea or plan for doing this, so I just went ahead... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 26 Nov '18

26 Nov '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-11-27 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

NO INFRASTRUCTURE MEETING ON 2018-11-22
by Stephen John Smoogen 22 Nov '18

22 Nov '18

There will be no Infrastructure meeting on 2018-11-22. Please have a good and safe week and see you next week on 2018-11-29 -- Stephen J Smoogen.

3 2

How does an apprentice graduate ?
by Clement Verna 19 Nov '18

19 Nov '18

Hi all, Is there an official way for an apprentice to move ot the next level ? ( joining the sysadmin group ?). I was looking at [0] but could find anything about how an apprentice stops being an apprentice. [0] - https://fedoraproject.org/wiki/Infrastructure_Apprentice

2 2

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 19 Nov '18

19 Nov '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-11-20 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

attention brno folks: testing wanted
by Kevin Fenzi 19 Nov '18

19 Nov '18

Hey everyone. A while back we had reports from folks particularly in Brno that operations to pagure.io were very slow. We put in place a workaround while we worked on the issue with network providers and tried various things. I'd like to know if any of those things have fixed (or at least made better) the issue. So, if you had slow pagure connections in the past, can you: * do some initial tests: time git clone https://pagure.io/pagure.git time curl https://pagure.io/pagure/issue/3714 time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi * then add: 140.211.169.204 pagure.io or (if you use ipv6): 2605:bc80:3010:600:dead:beef:cafe:fed8 pagure.io to your /etc/hosts file * Then run the tests again: time git clone https://pagure.io/pagure.git time curl https://pagure.io/pagure/issue/3714 time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi * Then remember to REMOVE the hosts entry so it's not there later causing you confusion. Thanks in advance for any testing. kevin

5 5

Packages Full text search API : fedora-search
by Clement Verna 19 Nov '18

19 Nov '18

Dear all, In a effort to run fedora-packages [0] on our infrastructure Openshift instance, I have been working on replacing the current full text search engine powered by xapian by a new service that uses postgresql full text search capabilities and Django DRF. The proof of concept of this service [2] is running on a dedicated Openshift instance [3]. There is currently only one API available that allow to search for a package. For example http://fedora-search-fedora-search.e8ca.engint.openshiftapps.com/?q=firefox will return the search results related to the firefox packages. I will be working on adding fedora-search support in fedora-packages, I am also looking for feedbacks and possible applications that could use this new service. [0] - https://github.com/fedora-infra/fedora-packages [1] - https://xapian.org/ [2] - https://github.com/fedora-infra/fedora-search [3] - http://fedora-search-fedora-search.e8ca.engint.openshiftapps.com/

1 0

[release] fedora-messaging-1.1.0
by Jeremy Cline 16 Nov '18

16 Nov '18

Hey folks, I've tagged fedora-messaging v1.1.0[0]. It's available in PyPI, Rawhide, and will be coming to Fedora 29's updates-testing repository soon, along with the infra repositories for Fedora 28 and EPEL 7. It's a small feature release that adds a testing module to make writing unit tests easier along with some initial work to make recording and republishing messages (for integration tests and such) easy. [0] https://github.com/fedora-infra/fedora-messaging/releases/tag/v1.1.0 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

2 2

infrastructure.fedoraproject.org
by Anatoli Babenia 16 Nov '18

16 Nov '18

Good Sunday. ) I found this https://infrastructure.fedoraproject.org/ while searching for this list. Maybe make it a single page entrypoint for all related things? Static site generator with quick links to sources, SOP, wiki (?) and this list.

4 6

Bodhi 3.11.0 beta deployed to staging
by Randy Barlow 16 Nov '18

16 Nov '18

Greetings! bodhi-3.11.0 beta has been deployed to staging: https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html#v3-11-0 This deployment uses Python 3 only!

1 1

Introducing Luiz Carvalho
by Ralph Bean 15 Nov '18

15 Nov '18

Hi all, Just an FYI - I've moved off of the Factory 2 team inside Red Hat to take a different role in the internal devops organization there. Luiz Carvalho (lucarval in both FAS and irc) takes my place leading the Factory 2 team! He's a good point of contact for greenwave, MBS, ODCS and freshmaker along with giulia, jkaluza, and mprahl. Say hi in channel sometime. -Ralph p.s., I'll still be around to help out as I can. :)

5 4

Fedora Infrastructure Meeting 2018-11-15 15:00
by Stephen John Smoogen 15 Nov '18

15 Nov '18

This is where I normally give a paste of the agenda and stuff but our gobby server took a dirt nap today. We are restoring it but in the meantime I would like to invite everyone to a meeting in #fedora-meeting-1 at 15:00. There will be cake. -- Stephen J Smoogen.

1 0

[PATCH] Pull OSTree repo from compose/atomic/repo during AH ISO creation
by Sinny Kumari 13 Nov '18

13 Nov '18

We recently noticed inconstancy in OSTree version for ppc64le ISO in compose https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-201811… . OSTree version for ppc64le ISO was 29.20181111.0 while expected was 29.20181112.0. This patch (available in email attachment) is to fix inconsistency in OSTree version which may occur during AH artifacts creation. pull ostree content from repo https://kojipkgs.fedoraproject.org/compose/atomic/repo/ instead of https://kojipkgs.fedoraproject.org/atomic/repo/.

3 4

Re: wiki _Getting Started_ workflow
by Blaise Pabon 13 Nov '18

13 Nov '18

Michal, Kevin, Thanks for updating the Getting Started section. It's now more consistent with the videos. I know it might not seem like a big deal, but first impressions are important in order to give newcomers the confidence to continue. By the way, kudos to the Silver Blue team, (I know it's a different list...) I ran the fc29 Installer yesterday and the experience was so polished it was almost... sensual. Best, Blaise -- LinkedIn <https://www.linkedin.com/in/blaisepabon/> | Quora <https://www.quora.com/profile/Blaise-Pabon> | Github <https://github.com/blaisep> “If you want to go fast, go alone. If you want to go far, go together.” --African proverb

1 0

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 12 Nov '18

12 Nov '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-11-13 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

Statistics. Stats for installled or downloaded packages
by Anatoli Babenia 12 Nov '18

12 Nov '18

Good Monday. ) I am trying to find package installation/download statistics for Fedora. https://fedoraproject.org/wiki/Statistics is the page that pops up first in search results, and it is kind of 6 years outdated. It would be really great to update it with current situation. I can not do this, because acquiring CLA+1 for wiki edits is too hard and didn't happen even though I sent several requests to different groups. The second reason - I don't know what to write as there seems to be no contact point except this groups. There is also unlinked https://fedoraproject.org/wiki/Statistics_2.0 page with many good stories including mine - `Parse mirror logs: what packages are being the most downloaded?`, but no links or tracker items to see the status and jump in. I found a request to open stats@ list https://pagure.io/fedora-infrastructure/issue/2223 which speaks about https://github.com/fedora-infra/datanommer/ as a new location. There are still no examples of getting package popularity data. I need stats to see how many people are using qdigidoc package to make it more official.

7 13

wiki _Getting Started_ workflow
by Blaise Pabon 12 Nov '18

12 Nov '18

Hi, (I tried to correct this myself, but the wiki requires "at least one non cla* group to be able to login and edit") So, I followed the steps in getting started, watched both videos, and browsed the easyfix page. - The second video refers to a best practices page <https://fedoraproject.org/wiki/Infrastructure/AppBestPractices>, which is not listed in the Getting Started: First Steps <https://fedoraproject.org/wiki/Infrastructure/GettingStarted#First_steps> . - I suggest moving the Infrastructure Issues <http://pagure.io/fedora-infrastructure/issues> link *from* First Steps <https://fedoraproject.org/wiki/Infrastructure/GettingStarted#First_steps> *to* the What's Next section <https://fedoraproject.org/wiki/Infrastructure/GettingStarted#What_is_next.3F> ; - and moving the Easyfix Page <https://fedoraproject.org/easyfix/> link *from* the What's Next Section *to* the First Steps section. This will align with the sequence described in the videos (and progress in order of complexity). Cheers, Blaise -- LinkedIn <https://www.linkedin.com/in/blaisepabon/> | Quora <https://www.quora.com/profile/Blaise-Pabon> | Github <https://github.com/blaisep> “If you want to go fast, go alone. If you want to go far, go together.” --African proverb

3 2

pagure.io is missing terms of use
by Pavel Holica 11 Nov '18

11 Nov '18

Hello, first of all I don't know if fedora-infrastructure is managing pagure.io instance, but I'd expect so, if not, I'm sorry for noise. The problem I hit today was that I wasn't able to find terms of use for projects on pagure.io and I couldn't even find clear information about contact for that particular instance of pagure. I tried to google those information as well but wasn't successful. The only information I could find was about the pagure project (in terms of code, not service). I believe it would be beneficial to have some information on the pagure.io about the terms of use of pagure.io and contact to the subject responsible for the pagure.io service. Why I was looking for this? I just wanted to know what is ok to host on pagure.io Thank you

2 1

Infrastructure Meeting at 15:00 UTC tomorrow.
by Stephen John Smoogen 08 Nov '18

08 Nov '18

Due to making it that Kevin would have to get up at 05:00 UTC to make the meeting we have moved it to 15:00 UTC This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-11-08 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2018-11-08) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info tflink is on extended PTO #info updates/reboots of infrastructure #info There will be NO infrastructure meeting 2018-11-22 #info Red Hat Employees have a usual break 2018-12-22 -> 2019-01-02 = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info nirik is on call from 2018-11-01 -> 2018-11-08 #info bowlofeggs is on call from 2018-11-08->2018-11-15 #info puiterwijk is on call from 2018-11-15->2018-11-22 #info nirik is on call from 2018-11-22->2018-11-29 #info smooge is on call from 2018-11-29->2018-12-06 #info ??? is on call from 2018-12-06->2018-12-13 #info Summary of last week: (from smooge ) #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

2 2

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 05 Nov '18

05 Nov '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-11-06 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

Introduction: Mike Travis
by Mike Travis 05 Nov '18

05 Nov '18

Hello, My name is Mike Travis. I've been a user of Fedora since Fedora 7. I'm going through all the infrastructure documentation and videos on the Fedora Project Youtube channel. I'm also interested in Fedora package management. I'm the Director of IT at a software company in Madison, Wisconsin. I work with a lot of different technologies and always want to learn new things. I manage 400+ CentOS 7 servers at AWS with Ansible. I work with a variety of software/tools everyday: MySQL, Elasticsearch, Redis, Ansible, Jenkins, Sentry, Nagios, Graphite, Grafana, Prometheus, Docker, PHP, Bash, Python, Ceph, ELK Stack. I learn best through videos / reverse engineering / building systems I'm unfamiliar with. My IRC handle is travmi. I've been attending the Infrastructure meeting for a couple weeks now. --- Mike

1 0

Meeting Agenda Item: Introduction Blaise Pabon
by Blaise Pabon 03 Nov '18

03 Nov '18

Hello, my name is Blaise Pabon I've been watching from the sidelines for a long time (25 years?) and I have decided that I want to do more to help out. I'm eager to help the fedora project be more accessible to newcomers. In the short term, I would like to get the opennms <https://opennms.org/en/install-centos> builds into koji and the fedora container registry. IRC handle: bpabon on the #fedora-admin channel Skills: I'm literate in Spanish, French and English I'm very comfortable with git, networking (WiFi, IP,TLS), SMTP email services, python Sphinx and rST. I'm comfortable with Git, Python, Jira, Jenkins, Maven. I have worked for several large software development companies, using commercial tools. This my first open source project with an infrastructure team like we have at work. Thank you, Blaise

2 1

Meeting Agenda 2018-11-01
by Stephen John Smoogen 01 Nov '18

01 Nov '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-11-01 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2018-11-01) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info tflink is on extended PTO #info Final Freeze is over. F29 is out #info RHEL-7.6 is out. Reboots incoming #info F29 is out, time to start rebuilding <=F27 boxes #info staging Koji synced with production - mizdebsk = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info smooge is on call from 2018-10-25 -> 2018-11-01 #info nirik is on call from 2018-11-01 -> 2018-11-08 #info ??? is on call from 2018-11-08->2018-11-15 #info ??? is on call from 2018-11-15->2018-11-22 #info Summary of last week: (from smooge ) #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2018