From Fedora Project Wiki

Line 3: Line 3:
* Note talking points schedule at end of Feature List page, and make sure it's clear to developers how talking points fit into the feature cycle/process. (from kashyapc)
* Note talking points schedule at end of Feature List page, and make sure it's clear to developers how talking points fit into the feature cycle/process. (from kashyapc)
* have Community Talking Points - what we're doing with each release that isn't necessarily directly tied to the distro, but Features / Enhancements we're making to the community. SOPs, rawhide, FI, etc, etc. We're giving people a compelling list as to why they should be trying out Fedora 13; why should we not have a compelling list as to why they should try out our community? (rbergero)
* have Community Talking Points - what we're doing with each release that isn't necessarily directly tied to the distro, but Features / Enhancements we're making to the community. SOPs, rawhide, FI, etc, etc. We're giving people a compelling list as to why they should be trying out Fedora 13; why should we not have a compelling list as to why they should try out our community? (rbergero)
[http://www.signarama.com.au/catalog/truck-graphics.html vehicle graphics]

Revision as of 22:04, 7 December 2011

Ideas for next round

  • Note talking points schedule at end of Feature List page, and make sure it's clear to developers how talking points fit into the feature cycle/process. (from kashyapc)
  • have Community Talking Points - what we're doing with each release that isn't necessarily directly tied to the distro, but Features / Enhancements we're making to the community. SOPs, rawhide, FI, etc, etc. We're giving people a compelling list as to why they should be trying out Fedora 13; why should we not have a compelling list as to why they should try out our community? (rbergero)

vehicle graphics