My name is Mark and I currently reside in the UK, there are many
reasons why I decided to join the Fedora Project and be involved in the
I consider myself a intermediate user as I have used Fedora for many
years but would love to learn the skills that would make me a a skilful
and knowledgeable administrator, but I am not just about learning
skills I also wanted to be able to give something back and be part of a
community of people like myself who love computing and especially
As I am new to the Fedora community I am still trying to figure out
what exactly I can contribute, and at the moment I can manage time and
enthusiasm to learn new skills and help out where ever I can, so I
thought a good starting point would be to join the apprentices group
and start from there until I gain some skills that would prove useful
to the community.
To elaborate more on my skills I did study computing a few years ago
and that's where I ha my first introduction to Unix, AIX on a RS6000
where I learnt the basics of the shell as well as some Pascal, Cobol
and C programming. To be honest I have not studied programming for
many many years as I do not want to give a false impression on my skill
set but I have the potential to learn these skills again and I am
hoping I can find a mentor who can really help me achieve my goal.
I will end there as I don't want to ramble on to much but if anyone
would like to send me an email or chat on IRC my email address is mmorr
is4055(a)gmail.com and my IRC handle is mmorris4055, feel free to message
The infrastructure team will be having it's weekly meeting today,
2017-02-09 at 19:00 UTC in #fedora-meeting 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.
This shared document is for the next fedora infrastructure meeting.
= 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 (2017-02-09)
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 bodhi-2.4.0 beta deployed to stg, please test! bowlofeggs
#info first mirrorlist container is in production now on proxy02 - kevin/patrick
#info mass rebuild hasn't yet started, but should be soon - releng folks
= 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 fedorahosted migration status
#topic Moving SOPs to the proposed infra-docs sphinx project (https://docs.pagure.org/infra-docs/)
#topic idea to make a packages git repo with all pkgs as submodules - kevin
= Apprentice office hours =
#topic Apprentice Open office hours
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 gsetup 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 info 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.)
#topic Learn about: mirrorlist containers - kevin
= Meeting end stuff =
#topic Open Floor
As some of you may know, every year Google hosts the Google Summer of
Code (GSoC), last year we participated with some decent results for a
few projects. I was just sending this heads up to those whom may be
interested in partaking as a mentor or student (even if you are already
a fedora contributor) for a project within Fedora.
Basic requirements for students and ideas are below and find the full
lowdown at .
What are the eligibility requirements for participation?
* You must be at least 18 years of age
* You must currently be a full or part-time student (or have been
accepted for the fall term) at an accredited university as of the
student acceptance date
* You must be eligible to work in the country you will reside in during
* You have not already been accepted as a Student in GSoC more than once
* You must reside in a country that is not currently embargoed by the
United States. See Program Rules for more information.
Prospective students: read the Student Manual 
Prospective Mentors: read the Mentors Manual 
Hopefully I will see some of you among the applications.
Corey W Sheldon
A goal is not always meant to be reached, it often serves simply as
something to aim at. --Bruce Lee
Absorb what is useful, discard what is not, add what is uniquely your
own. --Bruce Lee
Any man willing to sacrifice security for convenience, is deserving of
neither. -- Benjamin Franklin
Disclaimer: All correspondence shall be deemed of a sensitive nature,
and not re-distributed without good cause or per-approval.
All Emails shall be GPG signed or carry a attached vcf/asc blob, any
email lacking this shall be treated with healthy skepticism.
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
3. Have you looked at or been able to work on any of the fi-apprentice
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. What's the best software documentation you have read?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Note that we recently revamped the getting started and other pages.
Please do take a minute to re-read them and let me know if they are
more clear or need further adjustments.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!
Dear Fedora team.
My subject is about this subject: add Unity 3D software to Fedora like
I want to improve Fedora distro 26 and the subject is Unity 3D.
I think this will increase the number of real users most into area of
Also this can result one great distro for game with low hardware.
Now the Unity 3D come into debian package and sh files.
Can we do that ? How ?
How want to deal with this issue ?
Thnak you. Regards.
I've been mulling on this idea for a while, but Kushal's
opensource.com article last week has inspired me to make this
proposal. I think it would be very nice if we had a documentation
project that covered Fedora Infrastructure Applications as a whole.
I envision it serving the following purposes:
* Provide an excellent "Getting started" guide for new developers.
* Cover the tools we use and the frameworks/libraries our projects
frequently depend on (and why we chose them over alternatives).
This is especially helpful for newer developers who might encounter
a problem and not be aware there's a library or tool we regularly
use that solves it.
* Gives us a place to decide on and document contribution guidelines
that apply to all the projects we maintain.
* Provide a place to document common problems (and hopefully solutions)
projects we work on face.
Some examples of things I would like to document:
* How to start a Sphinx docs project and use various extensions to
generate Python API and REST API documentation automatically. It
would also serve as a guide for new developers on docblock style(s)
* A sample Flask project layout. This would serve to contain a lot of
boilerplate (setup.py, test layout, etc) with various tips and tricks
we all learn as we go.
Release Engineering has a project similar to what I have in mind. I
notice they have their SOPs built in this project and I think it would
be great if we had all the Fedora Apps SOPs built into this project I'm
I'm relatively new here, and two of the challenges I've faced while
getting up to speed is the lack of in-depth documentation for projects
and the huge variance between projects in terms of style. We're a wide-
spread team and everyone is working on several projects at once. I think
if we make an effort to standardize a little bit (and document what will
vary between the projects) it will make it much easier to get involved
in our projects.
Overall, I think it would be a great place to learn from one another and
would make getting involved much easier.
What do you all think?
I had heard word during DevConf that we were supposed to ensure that
contributions to infrastructure applications (such as Bodhi) needed to
come from users who had signed the FPCA. I had not been aware of this,
so I haven't been checking that the users who contribute to Bodhi have
signed the FPCA.
Is this requirement documented anywhere? How should I proceed with
commits that have already been merged in Bodhi?