Packager Experience objective proposal
by Ben Rosser
Hello,
Following a discussion [1] on the devel list, Till encouraged me to
propose a "packager experience" (or possibly "packager quality of
life") Community objective to the Council.
Basically, the goal of this objective would be to organize people to
work on various annoyances (be they minor or major) that currently
exist in the packager workflow. This probably involves creating a new
SIG or WG focused on improving the packager workflow-- identifying
problems and figuring out solutions (likely by contributing to various
tools and other projects in the packaging pipeline like fedpkg, or
Koji/Bodhi/Pagure/etc.).
My understanding of the Objective proposal process here is that I
create a draft page on the wiki and then start a discussion on this
list, so I thought I would do just that. Here is a very early draft I
wrote on the wiki:
https://fedoraproject.org/wiki/Objectives/Packager_Experience
I only recorded three issues on the wiki draft-- all to do with the
retiring of pkgdb2, as that's what started this discussion. But I'm
sure I can come up with more, and I'm equally sure the community would
as well once we started a discussion. (I think, for example, that
improving the package review process might also be something in the
scope of this objective).
These problems might seem a bit small, or minor, to be worthy of a
Community Objective to fix them, but I think that's part of the
problem-- something like having to manually request Pagure API keys to
create new packages (this was what the linked discussion on the devel
list was about) might only be a minor annoyance, but that means it
doesn't get attention, while bigger, more urgent things do. If we
could collect a list of such minor annoyances and set up a plan to fix
them-- and also set up a group or process responsible for fixing
similar issues as they crop up in the future-- I think it would do a
lot to improve the overall experience of packaging software in Fedora.
Thanks for your consideration!
Sincerely,
Ben Rosser
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
4 years, 7 months
Council Elections — December 2018: Results announcement
by Ben Cotton
The elections for Council - December 2018 have concluded, and the results
are shown below.
Council is electing 1 seat this time.
A total of 213 ballots were cast, meaning a candidate
could accumulate up to 852 votes (213 * 4).
The results for the elections are as follows:
# votes | name
- --------+----------------------
610 | Dennis Gilmore (ausil)
- --------+----------------------
295 | Eduard Lucena (x3mboy)
286 | Alejandro Perez (aeperezt)
247 | John M. Harris, Jr. (JohnMH)
Congratulations to the winning candidates, and thank you all
candidates for running this elections!
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
4 years, 9 months
Fedora’s Strategic Direction: An Update from the Council
by Matthew Miller
The Fedora Council met last week in Minneapolis, Minnesota. It’s a lovely
city, but rather cold, so we largely stayed within the interconnected
network of enclosed bridges known as the Skyway — and in our conference room
working. One of our main projects was the draft below. This is a follow-on
from our update to the mission statement last year. It represents the way
the Fedora Council would like the Project to make that mission a reality — a
guiding policy. We’d like wider community feedback on this approach (and the
write-up of it), after which we plan to include the final version in the
project documentation.
Fedora’s Mission
----------------
“Fedora creates an innovative platform for hardware, clouds, and containers
that enables software developers and community members to build tailored
solutions for their users.”
We do this within the context of the four foundations: freedom, friends,
features, and first.
Context
-------
The Fedora Council identifies the short-, medium-, and long-term goals
necessary to keep the Project on the leading edge of technology. The
Fedora.next initiative focused the outputs of the project around use cases.
In 2017, we updated the mission statement to reflect changes in the
computing landscape. Today, it’s too difficult to build new solutions in
Fedora.
Our Approach
------------
We will make it easy for the community to build solutions, address specific
developer problems, and meet their end users’ specific needs. We will do
this by encouraging and helping Objectives which make the necessary changes
required to ease the process. This accelerates the transformation of Fedora
into a community that enables the construction of solutions.
Internally, Fedora focuses on enabling these solutions to be built. The
outputs of Fedora are the Solutions our community members build. Our focus
on enablement allows experimentation without prior judgement or gate-keeping.
What does this mean?
--------------------
Teams such as Design, Documentation, Packagers, Release Engineering, and
Quality Assurance provide building blocks and offer services to other
community members and Teams. Services and building blocks include: CI
infrastructure, community building advice and guidance, event funding, logo
services, RPM or other software packages, swag, testing and validation, user
support, or UX design.
Anyone may use Building Blocks like software packages and artwork to create
a Solution. Solutions include: Fedora Workstation, KDE Plasma, and the
Python Classroom Lab. Teams define criteria for services they provide to
solution-builders. For example, teams providing press and promotional
support may choose to provide additional support to Solutions with larger
user bases.
Teams are free to define elements of their Solutions, such as intent,
deliverables, and release cadence. Teams can build Solutions from any
building block and pick and choose what tools they use. Based on their
choices, they get different levels of ability to use the Fedora trademark
(i.e. “Fedora Remix” vs “Powered by” vs Fedora”). Some solutions are the
premier showcases that we call Editions; these are used in the gating tests
for our releases.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4 years, 9 months
[Fedocal] Reminder meeting : Council (Subproject Report)
by mattdm＠fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Council (Subproject Report) on 2018-12-12 from 10:00:00 to 11:00:00 US/Eastern
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
The Fedora Council will hold our regular Subproject Report meeting this week
at 10:00am US/Eastern. All are welcome!
To convert to your local time, run:
date -d 'TZ="US/Eastern" 10am tomorrow'
This meeting will be conducted via video chat at https://meet.jit.si/FedoraCouncil with notes taken in #fedora-meeting-1 on IRC.
This week's primary meeting chair (usually the FPgM, FPL, or FCAIC) will
reply to this message with specific information.
Source: https://apps.fedoraproject.org/calendar/meeting/5237/
4 years, 9 months
[tickets] branch master updated: Update README.md
by git repository hosting
This is an automated email from the git hooks/post-receive script.
bex pushed a commit to branch master
in repository tickets.
The following commit(s) were added to refs/heads/master by this push:
new 0658bb7 Update README.md
0658bb7 is described below
commit 0658bb754578ba384933cc0500824cab11db5d73
Author: Brian (bex) Exelbierd <bexelbie(a)redhat.com>
AuthorDate: Mon Dec 10 20:51:21 2018 +0000
Update README.md
Fix #240 by updating links
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 1da06bc..4f2ec6a 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ which need a specific resolution. Tickets are discussed during [weekly
meetings](https://meetbot.fedoraproject.org/teams/council/).
**For more information, please see the [Fedora Council
-charter](https://docs.fedoraproject.org/fedora-project/council/charter.html).**
+charter](https://docs.fedoraproject.org/en-US/council/).**
## File a new ticket
@@ -25,4 +25,4 @@ following places:
* **Mailing list**: [council-discuss@lists.fedoraproject.org](https://lists.fedoraproject.org/admin/lists/council-discuss@lists.fedoraproject.org)
* **IRC channel**: `#fedora-council` on freenode
([webchat](https://webchat.freenode.net/?channels=fedora-council))
-* **Documentation/Information**: [https://docs.fedoraproject.org/fedora-project/council/charter.html](https...
+* **Documentation/Information**: [https://docs.fedoraproject.org/en-US/council/](https://docs.fedoraproject...
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
4 years, 9 months
