#247 Change to Changes (idea)
Closed: Completed 5 years ago Opened 7 years ago by bex.

I was doing some thinking about Fedora Marketing and wound up reading through some of the F26 Changes. I realized that out template doesn't seem to specifically call out some data would be helpful to the outreach teams (Marketing, Ambassadors, Magazine, etc.) in promoting our releases.

I'd like to consider expanding the "Benefits to Fedora" and "User Experience" sections of the Changes template. I am thinking of: (note all examples are hypothetical and possibly wrong)

1.5 Benefits to Fedora (complete all that apply)

1.5.1 Benefits to Fedora (technical)

Describe the technical benefits of this change. This is how the change makes the distribution technically better. For example:

  • This change modifies a package to use a different language stack that reduces install size by removing dependencies
  • This upgrade results in faster resolution of user requests from /etc/passwd
  • This change causes 100% of proprietary programs to be Open Source

1.5.2 Benefits to Fedora (distribution)

Address the benefits of this change to the Fedora Distribution as a whole or the specific Editions/Spins/etc. it applies too. This section is for the benefits to the project. For example:

  • This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server. Building for a more related package set will allow for greater reuse of OpenQA tests.
  • This change ensures that a minimal set of tools required for contribution to Fedora are installed easing the onboarding of new contributors.

1.9 User Experience (complete all that apply)

1.9.1 User Experience (technical)

Describe the specific interactions that will change for the user. For example:

  • Kerberos tickets that can be renewed will be automatically renewed and survive reboots.
  • The user's home directory will automatically clean and file downloaded files, placing them in date specific folders after 30 days.
  • The default installation of Firefox will be enabled for kerberos based SSO resulting in fewer login screens.

1.9.2 User Experience (beneficial)

Why is this change good for users? How does it help them be more productive? What is the benefit of this change? For example:

  • Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
  • Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running."
  • Python developers will find the package separation between Python 3 and Python 2 makes it easier for them to know what is installed and being used by which version. Dependency auto-completion will cause executed code to automatically pull packaged pypi packages as needed by the Python interpreter. This will result in more successful executions of code during the development process.
  • Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.

I believe these sections will help drive our changes into a story for our users and show that we are making decisions for the distribution to benefit our users. We do that today but we aren't necessarily telling our users about it. I hope this data will help the outreach groups do even more in the way of sharing this story.

I'd appreciate your feedback on this. Will this actually help the outreach teams?


Metadata Update from @jflory7:
- Issue priority set to: no deadline
- Issue set to the milestone: Future releases
- Issue tagged with: needs feedback, release preparation

6 years ago

Metadata Update from @x3mboy:
- Issue tagged with: meeting

6 years ago

As a current member of FESCo, I'm in favor of this. The "Changes" template as it is currently tries to get the change owner to help the marketing effort by describing why the change is important, but doesn't seem to elicit enough detail to really help the marketing of the change. As such, I think a more descriptive template (like the examples above) would be helpful to guide the change owners to provide more detail.

What would you suggest as the next step @jsmith? I don't want to see the change process become so burdensome that people avoid it, but I also want to make sure we are prepared to take changes beyond the bits shipping.

I think the next logical step is to build a "patch" or two for change templates (Self-contained changes and System-wide changes), and then open a FESCo ticket with the proposed changes.

Metadata Update from @bt0dotninja:
- Issue assigned to bt0dotninja

6 years ago

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

6 years ago

FESCo discuss the ticket and decided update the changes template taking in account some ideas from the marketing proposal[1].

the agreed changes are here:

https://fedoraproject.org/w/index.php?title=Changes%2FEmptyTemplate&type=revision&diff=516458&oldid=516457

The user experience section becomes mandatory :grin:

this looks fine for me, what says the mktg team??

[1] https://meetbot.fedoraproject.org/teams/fesco/fesco.2018-04-20-15.06.html

Closing as fixed, FESCo did changes for a better changes page.

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

5 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 6 years ago View Comment