Meeting location change
by Justin W. Flory
Hey all,
This is a friendly notification that our weekly meeting location is
changing. The default #fedora-meeting channel is available in our time
slots on Tuesday, so we will switch FROM using #fedora-meeting-2 TO
#fedora-meeting.
This change is reflecting in Fedocal too and should show the correct
location in the reminder email on Monday.
See you all on Tuesday!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
8 years, 1 month
New to CommOps
by Ryan Mason
Hi all,
My name is Ryan and I'm new to the mailing list, although some of you may have seen me loitering around reddit or IRC.
I've never contributed to something like this before, but I want to contribute as I have a strong passion for linux and open source, and want to one day work at Red Hat - I thought what better place to start than within the Fedora community.
I am a so-so coder and designer, but thought CommOps might be somewhere where I can add some value to the project. Life is pretty hectic at the moment with full-time work, part-time study and baby number one on the way, but I hope to be able to contribute regularly!
My 9-5 is that of a project estimator, however I am studying computer science and taking certifications when I can. Hopefully I can leverage some of my skills I've picked up in the 33 years I've been stomping around the planet to assist the project!
Regards,
Ryan
8 years, 1 month
NewMember - Hello World
by Sachin S. Kamath
Hello CommOps Community :)
My name is Sachin Kamath, currently pursuing my B.Tech in Computer Science
in India. I am an open source enthusiast, a free thinker and love writing
automation scripts. I have contributed to the GlitterGallery project and
had also delivered a talk for Fedora Contribution Camp which happened in my
region. My area of interest include Web-Dev, penetration testing and System
Administration. You can find my blog here : https://blog.sachinwrites.xyz .
I am also active on Github and use it whenever I can :)
Looking forward to contributing to the community.
Regards,
Sachin.
8 years, 1 month
F24 Talking Points: Fedora Server Edition
by Remy DeCausemaker
Server Folks,
It's that time of year again where Fedora Marketing is collecting all
of the talking points for our upcoming F24 release!
For those of you who don't know about talking points, you can read the
ticket in the marketing trac (which includes the SOP instructions)
here: https://fedorahosted.org/marketing-team/ticket/220
tl;dr -- talking points are basically highlights about the release
that are worth mentioning when talking to Fedora Users and other
interested press. This can include things like:
- Performance Enhancements/Increases
- New Features
- Fixed Bugs
- Newly Implemented Ideas
- Collaborations and Partnerships
- Things that often go into Release Notes
- Other novel stuff that only WG contributors would know about, but
the rest of the world should know too!
You can reply-all here, or on the ticket itself, and the CommOps folks
cc'd here will help to integrate your input :)
Thanks for your time, and Happy Hacking.
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
8 years, 1 month
F24 Talking Points: Fedora Server Edition
by Remy DeCausemaker
Server Folks,
It's that time of year again where Fedora Marketing is collecting all
of the talking points for our upcoming F24 release!
For those of you who don't know about talking points, you can read the
ticket in the marketing trac (which includes the SOP instructions)
here: https://fedorahosted.org/marketing-team/ticket/220
tl;dr -- talking points are basically highlights about the release
that are worth mentioning when talking to Fedora Users and other
interested press. This can include things like:
- Performance Enhancements/Increases
- New Features
- Fixed Bugs
- Newly Implemented Ideas
- Collaborations and Partnerships
- Things that often go into Release Notes
- Other novel stuff that only WG contributors would know about, but
the rest of the world should know too!
You can reply-all here, or on the ticket itself, and the CommOps folks
cc'd here will help to integrate your input :)
Thanks for your time, and Happy Hacking.
--RemyD.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
8 years, 1 month
Join page updated
by Justin W. Flory
Hey CommOpsers,
The universal "Join" page now features a new addition to multiple
sections of the page.
https://fedoraproject.org/wiki/Join
Please take a look over the CommOps additions and make sure everything
sounds right, and more importantly, if anything cool and/or
attention-grabby can be added. :)
I'm going to also close out Ticket #37 now as this should finish it up.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
8 years, 1 month
Re: Marketing materials for Python events
by Justin W. Flory
On 03/01/2016 09:01 AM, Jiri Eischmann wrote:
> Hi,
> as Matthew announced at DevConf.cz our primary marketing focus for this
> year are Python developers.
> In EMEA, we've reacted and increased the number of Python events in the
> list of planned events (several PyCons, planning to be at EuroPython
> again...), but I realized we're not ready for that at all, or at least
> I'm not aware of anything.
As a note of reference, fale put together a list of all Python-related
events across the world on the wiki. This can help serve as an excellent
resource for planning for events and putting dates on the calendar.
I encourage all Ambassadors of all regions to take a glance at this page
and see what's coming up soon if you are not aware already.
https://fedoraproject.org/wiki/Python_Events_2016
fale++
> We have no marketing materials. Miro created a "Fedora loves Python"
> sticker for Python CZ, but that's all we have in EMEA. Today, we were
> offered an opportunity to add our swag in conference bags at PyCon SK,
> but we don't have anything usable. Something like a flyer that explains
> why Fedora is the right system for a Python developer would be great.
I think this is something that the Marketing team can and definite
Ambassadors are also encouraged to help with this as well if they are
interested. Like Ruth mentioned, we do have a flyer, but it needs
updating. I think a good immediate objective is:
1) Compiling a list of Python "hot topics" (e.g. "What makes Python
great on Fedora?" "How can working on Python in Fedora be easier than
other distros?" And so on.)
2) Submitting a ticket on the Design Team Trac with this info and a
request to update the flyer for distribution in 2016.
The CommOps team is also heavily invested in helping with this area too
as a supporting team. It's also on our backburner but I'm beginning to
think this is something we should begin moving to the forefront of
planning. After all, these events are happening *now* and in the very
near future, so getting the gears turning ASAP is best.
I'm going to make sure that this email thread is converted to a
Marketing Trac ticket and added to the meeting agenda for Marketing
tomorrow.
> And it's not only about marketing materials, ambassadors should get
> instructions what to show Python developers, so that it won't end up
> like showcasing a la "hey, Fedora is cool, it has Firefox,
> LibreOffice,... and look it has windows just like Windows or Mac". So
> we would definitely need at least some talking points.
I agree with this point as well. Haïkel listed great starting points in
his reply (I think also mentioning that Fedora is actively helping
migrate to Python3 is an excellent point too). Using this as a base
might be a good idea.
I'm also very very very +1 to what Ardian said. A lot of our
infrastructure is based off of Python and showing some of the cool
things that our own developers have made for Fedora with Python is a
great and real-world example of things people can hack onto. I've been
sharing some Python projects in Fedora with some students in my
community, and there's been a lot of interest in Tahrir, the platform
that powers our Open Badges project. Additionally, the fedmsg system, or
in other words, the open firehose of data in Fedora, is also built in
Python, along with many of the cool tools that let us take this data and
show cool things and trends.
Putting together a list of "hot Python projects in Fedora" and some of
the things they enable would also be a good next step to take for
providing talking points and resources to our Ambassadors in the field.
I'm going to work on creating a ticket in the Marketing Trac – I'll make
it a point to share it in this email loop once it's created and provide
a place for people to begin placing down some ideas in a more static
environment.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
8 years, 1 month
The Fedora Budget Website--Now in staging!
by Remy DeCausemaker
It's Alive!
=======
After working for the past couple of weeks with the websites and
infrastructure teams, I'm pleased to share with you all
https://budget.stg.fedoraproject.org/
Thank you nb, robyduck, nirik, puiterwijk, and threebean for your patience
and mentorship :)
So now, budget stakeholders and leaders (Ambassadors, Council, and FAmSCo)
you can visit the site and provide feedback and input.
The actual budget numbers for this year ARE NOT ACTUALLY ZERO, so don't
panic or anything, they just haven't been reported yet ;) When they are, I
will update the website accordingly.
Contributing to Budget.fp.o
=====================
If you would like to help work on the budget site itself (PR's are
certainly welcome) please join #fedora-websites on Freenode and talk to the
team there first. The team is transitioning where our repositories are
hosted, and are making some changes to the fedora-web workflow (while
branching for F24-alpha.) In the future, you should be able to clone the
source for the budget site (and the other Fedora Websites) at
https://pagure.io/fedora-websites. ***WARNING*** Since our production
environment is built from the master branch, be sure to be working in an
alternate branch (git branch budget, for example) Starting now, you can
file tickets for the budget site on the Fedora-websites repo on pagure:
https://pagure.io/fedora-websites
Budget Tracking -- Still a Regional Responsibility
======================================
I will be relying on ambassadors to be tracking your expenditures (like you
always have) so I can be updating the budget numbers section on a quarterly
basis, with reimbursements depending on event reports from regional
delegates. I will help report your budgets on
http://budget.fedoraproject.org (coming soon), but it is still up to the
REGIONS to keep as budget is spent. The good news though, is that now you
have The Community Operations (CommOps) team here to help support
publishing event reports and gathering and reporting metrics.
Budget Data and Files
=================
When there are working budget documents, data, and information fit for
public consumption, I have created a new repo for sharing such files at:
https://pagure.io/budget (it is mostly empty for now, but feel free to
start putting your proposed budgets there if you have them Ambassadors.)
There is in the plans (but not yet implemented) the idea that we can use
webhooks or other git-magic to have the budget numbers and contacts on
budget.fp.o update automatically based on the data in this repo, but that
will likely be a feature for v2.0. For now, I'm OK with starting manually
until we hammer out the details and settle on a process.
Regional Delegates
===============
I would like to start adding all the Regional Delegate selections to our
staging instance in preparation for the site hitting production in the next
week or two, starting now. So, if your region has chosen delegates already,
you can respond here with their names and email addresses, and I will add
them to the site. Alternatively, you could also file tickets on the budget
repo in pagure, (or file pull requests updating your regional delegation's
.yaml file) and I will merge/close them as I update the site.
***The budget process is going to move quickly from here, so Ambassadors
please have your delegation choices sent to me, filed into tickets, or
included in a pull-request by Friday March 4th.***
Budget.next and The Future
======================
I'm excited to help Ambassadors and Project Leadership bring more
transparency to the budget process--one of my core charters as the first
ever Fedora Community Lead. I am hopeful we can develop a process that will
improve reimbursement turn-around, while creating metrics on action and
impact we can use to strategically adjust and improve our financial
situation in the future.
Looking Forward,
--RemyD.
P.S. - I've cc'd a number of public lists in this email, so take special
care when replying to this post.
--
Remy DeCausemaker
Fedora Community Lead & Council
<decause(a)redhat.com>
https://whatcanidoforfedora.org
8 years, 1 month
