#145 Fedora 33 planning
Closed: Fixed 3 years ago by chrismurphy. Opened 4 years ago by chrismurphy.

Changes/features, ideas, wishlists, guest speaker suggestions, long term view of agenda:

Schedule
Changeset
Workstation kanban could use a quick review to confirm the Doing+1 items that will become Doing; and look over what's been Done in F32 cycle that will be archived.

While "meat and potatoes" topics are for sure on-topic, this is also a good opportunity to get creative and ask for "cake and pie" that off-hand people are reluctant to suggest as issues in their own right. Why not?


Flock to Fedora is now Nest with Fedora There's still a call for ideas, maybe some of the issues discussed at today's meeting could be further developed here? That link doesn't have a date or details. Use this flock pagure page to file ideas as issues, but feel free to discuss preliminary ideas as it relates to Workstation here in #145.

This week the WG had a discussion today about high-level goals for workstation and some themes came out:

  • Coherence and quality, and improving the workstation's public image
  • Competitiveness with other Linux distros
  • Developer target audience
    • Delivery of developer-focused features
    • Toolbox elaboration: terminal integration, toolbox portability, etc
  • App availability
    • More apps through Flathub
    • Better multimedia codecs story
    • Better Electron story

It would be good if we could try and identify key tasks within each of those high-level goals.

We also stumbled into a couple of discussion topics which it could be useful to return to:

  1. Is Fedora too conservative with regards to new technologies?
  2. What's our app availability strategy? One particular question here is the relationship between the 3rd party repos we manage, and those that users have to manually enable themselves

Metadata Update from @chrismurphy:
- Issue untagged with: meeting

3 years ago

This is a very open-ended issue. Is there anything concrete that we should be tracking in this issue tracker? If so, let's create separate issues. Otherwise, can we close this?

Metadata Update from @chrismurphy:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata