From Fedora Project Wiki
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
{{User:Willo/Infobox2
{{User:Cassmodiah/Infobox2
|REAL-NAME= Graham Williamson
|REAL-NAME   = Graham Williamson
|image=willo.png
|image       = Willo.png
|birthday=
|HOME    = Wollongong, NSW, Australia
|birthplace=
|birthday    = Private
|LOCATION= Canberra, Australia
|homepage    = https://willo.fedoraproject.org/
|FAS-NAME= willo
|pmail       = willo@fedoraproject.org
|pmail=
|gpg         = 4570527F
|gpg=4570527F
|jabber      =  
|homepage=http://blog.packetsgoin.net
|irc-nick     = willo
|irc-nick= willo
|irc-channels = #fedora-admin, #fedora-apps, #fedora, #fedora-devel
|irc-channels=#fedora
|callsign    =
|Twitter=
|twitter      = 00willo
|Identi.ca=
|facebook    =  
|jabber=
|googleplus  =
|linkedin    =
|github      = 00willo
|gitlab      = 00willo
|FAS-NAME    = willo
 
}}
}}


=== To DO ===
=== To DO ===
Line 30: Line 40:
=== Skill Areas ===
=== Skill Areas ===


HIGH:  Sys Admin (RHEL 5/6), networking, security
HIGH:  Sys Admin (RHEL 6/7/8), networking, security, Python, CI (gitlab)


MEDIUM:  Python
MEDIUM:  SELinux, podman, buildah


LOW/MEDIUM:  C/C++
LOW/MEDIUM:  C/C++
Line 47: Line 57:




== Contributions ==
== Contribution within Fedora Project ==
 
* Member, [https://fedoraproject.org/wiki/SIGs/ML Machine Learning SIG]
* Member, [https://fedoraproject.org/wiki/SIGs/Python Python SIG]
* Member, [[Infrastructure_Apprentice | infrastructure apprentice]]
* [https://fedorahosted.org/scap-security-guide/  SCAP Security Guide]


=== Groups I'm contributing too ===
=== Groups I'm contributing too ===
* [https://fedorahosted.org/scap-security-guide/  SCAP Security Guide]
 
* Join the infrastructure team as an [[Infrastructure_Apprentice | infrastrucutre apprentice]]


=== General Wiki Contributions ===
=== General Wiki Contributions ===
Line 62: Line 76:
* [[Koji/ServerHowTo]]
* [[Koji/ServerHowTo]]


== Ideas, I'm Mulling Over ==
== Questions or Tasks that I could do ==
 
=== Q or T ===
* Is there an FAQ somewhere?
** How to create an FAQ easily out of IRC?  - the problem to solve, at least reduce the same question over and over
* Follow on to FAQ - How can I search IRC channels for questions that have likely already been asked?
** See idea, I'm mulling over
* Why is ansible on fedora-project.org and not pagure.io like the rest include infra-docs?
* TASK IDEA - Make a walkthrough - How to submit your first ansible patch?
* Is there a reason for not having an elastic stack or some other setup for searching logs? - ie, easier searching and drill down of /var/log/merged from log01.phx2.  Possibly other logs could go in.  Ansible would make light work of deploying logstash to configure and ingest logs.  Could get really big storage wise.  Maybe POC on stg or something else small and bite-size to see it's usefulness.  Massive insight into the unknown is potentially missing and opportunity to extract useful metrics that are otherwise difficult to see.  Can export to graphana for awesome vis.
* Grafana to display collectd, statsd, anything else that's in graphite.
** evidence of it in ansible and http://grafana.cloud.fedoraproject.org althought doesn't appear to be populated with data
* log01.phx2 system_ident needs updating
* When is best time to use IRC vs email?  Maybe list when coverage of majority of people work times.  So someone can know, if it's a good time to ask on IRC around now.
* hostinfo or sysinfo zodbot command like fasinfo.
** could be useful, pulll from system_indent somehow and apps.fp.o maybe
* add misc help to Zodbot wiki and also note in fi_apprentice page.
* What actions on should be done on discovering a possible problem?  report #fedora-noc, #fedora-admin, both, ticket in infrastructure?
* Suggest edit to status.fp.o on action for user to take on finding a problem and all is green.
* How useful are the other tags in the easy_fix list?
* TASK: create process overview on how changes are implemented.  IE describe change management system.  Maybe already done in SOP, possibly??
* Is there a newbie playground to set things up?  Possibly containing test system data.
 
=== Ideas, I'm Mulling Over ===
 
* Enable a way to search IRC logs without doing it yourself.
** mailing list is easy - can be done via hyperkitty
** Possible IRC archive solutions
*** https://botbot.me - channel op to subscribe
*** roll our own - using some existing stuff like zodbot etc
* Orientation SOP - is it targeted for sysadmin-main or fi-apprentice.
 
 
==== Old - Review shortly ====
* Two ideas referenced from [[Fedora_Engineering/FY14_Plan]]
* Two ideas referenced from [[Fedora_Engineering/FY14_Plan]]
** Improve Fedora Hosted - Something more like gitorious, gitlabhq, allura
** Improve Fedora Hosted - Something more like gitorious, gitlabhq, allura

Latest revision as of 09:10, 27 August 2020

Graham Williamson
Graham Williamson
Graham Williamson
Graham Williamson
Personal Information
Born: Private in
Home: Wollongong, NSW, Australia
Fedora-specific Information
FAS-Name: willo
Fedora-Mail: willo@fedoraproject.org
Miscellaneous Information
Private Mail: willo@fedoraproject.org
GPG-Key: 4570527F
IRC: willo on Libera.Chat, in:
#fedora-admin, #fedora-apps, #fedora, #fedora-devel
Badges (37)
Junior Editor Baby Badger Paranoid Panda Involvement White Rabbit Crypto Panda Bloggin' it! (Planet I) Associate Editor Junior Badger (Badger I) Let Me Introduce Myself Curious Penguin (Ask Fedora I) Mugshot Speak Up! Bona Fide No Longer a Ronin Junior Package Tagger (Package Tagger I) Senior Package Tagger (Package Tagger III) Package Tagger (Package Tagger II) Senior Tagger (Tagger III) Curious Penguin (Ask Fedora II) Senior Editor Egg Mirror, Mirror on the Wall In Search of the Bull (Tester I) Macaron (Cookie I) Embryo Tadpole Froglet Common Bugs Contributor Junior Tagger (Tagger I) Tagger (Tagger II) Building the Outer Ring (Copr Build I) Origin Associate Badger (Badger 1.5) Master Editor Tadpole with Legs Adult Frog
 




To DO

Goals

As a Contributor

  • Create a badge
  • Package some "stuff" for both Fedora and EPEL

Skill Areas

HIGH: Sys Admin (RHEL 6/7/8), networking, security, Python, CI (gitlab)

MEDIUM: SELinux, podman, buildah

LOW/MEDIUM: C/C++

LOW: ASM

VERY LOW: MACHINE CODE

Just random links for me to followup on


Contribution within Fedora Project

Groups I'm contributing too

General Wiki Contributions

Pages I'm actively maintaining

  • None yet...

Pages I'm interested in

Questions or Tasks that I could do

Q or T

  • Is there an FAQ somewhere?
    • How to create an FAQ easily out of IRC? - the problem to solve, at least reduce the same question over and over
  • Follow on to FAQ - How can I search IRC channels for questions that have likely already been asked?
    • See idea, I'm mulling over
  • Why is ansible on fedora-project.org and not pagure.io like the rest include infra-docs?
  • TASK IDEA - Make a walkthrough - How to submit your first ansible patch?
  • Is there a reason for not having an elastic stack or some other setup for searching logs? - ie, easier searching and drill down of /var/log/merged from log01.phx2. Possibly other logs could go in. Ansible would make light work of deploying logstash to configure and ingest logs. Could get really big storage wise. Maybe POC on stg or something else small and bite-size to see it's usefulness. Massive insight into the unknown is potentially missing and opportunity to extract useful metrics that are otherwise difficult to see. Can export to graphana for awesome vis.
  • Grafana to display collectd, statsd, anything else that's in graphite.
  • log01.phx2 system_ident needs updating
  • When is best time to use IRC vs email? Maybe list when coverage of majority of people work times. So someone can know, if it's a good time to ask on IRC around now.
  • hostinfo or sysinfo zodbot command like fasinfo.
    • could be useful, pulll from system_indent somehow and apps.fp.o maybe
  • add misc help to Zodbot wiki and also note in fi_apprentice page.
  • What actions on should be done on discovering a possible problem? report #fedora-noc, #fedora-admin, both, ticket in infrastructure?
  • Suggest edit to status.fp.o on action for user to take on finding a problem and all is green.
  • How useful are the other tags in the easy_fix list?
  • TASK: create process overview on how changes are implemented. IE describe change management system. Maybe already done in SOP, possibly??
  • Is there a newbie playground to set things up? Possibly containing test system data.

Ideas, I'm Mulling Over

  • Enable a way to search IRC logs without doing it yourself.
    • mailing list is easy - can be done via hyperkitty
    • Possible IRC archive solutions
      • https://botbot.me - channel op to subscribe
      • roll our own - using some existing stuff like zodbot etc
  • Orientation SOP - is it targeted for sysadmin-main or fi-apprentice.


Old - Review shortly

  • Two ideas referenced from Fedora_Engineering/FY14_Plan
    • Improve Fedora Hosted - Something more like gitorious, gitlabhq, allura
      • | Allura seems to be way to go, keeping in line with current infra trends (python etc).
    • A Meeting App - next meetings, hot topics, who's saying what, etc. using meeting bot logs
      • fedmsg consumer (if meetingbot is a producer)
  • Idea site (possible name: idea-forge) - like brainstorm.ubuntu.com
    • There were issues with ubuntu'd idea site, that may not (or may) be applicable here.
    • python version of something like that (ideatorrent - inactive) or https://github.com/BBYOpen/BBYIDX
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Willo&oldid=586478"