On Thu, Sep 28, 2017 at 3:01 PM, Robin Chan <[email protected]> wrote:
> Because I just don't know, and because it might help with this > proposal consideration...could we list out the types of updates that > belong in the demo? > In theory, the demo is an opportunity to highlight anything at all that might be of interest to the Pulp community. Mostly the event serves as a chance to demo work that was completed in the prior three weeks, and receive questions or feedback about it. But even with that as the main focus, it's also a good time to keep people informed about what is happening that could affect them sooner. Work that gets demo'd often does not get released for a substantial period of time, so interesting as it may be, users have to wait to take advantage of it. Thus we take a couple of minutes to highlight releases, important upcoming changes, deprecations they should start planning for, current known problems, things that need to be tested, key problems that need to be solved, etc. Likewise it is a chance to set expectations about what is likely to come in the future: big new features or changes being planned, what is the release cadence, what direction is the project going in general, what is being prioritized or not and why, etc. On the community-specific front, it's a good chance to invite and encourage people to participate by highlighting other participants, events such as conferences or meetups, new or improved documentation, channels of communication, "case studies" of how people use Pulp successfully, etc. At a high level, we want to take a few minutes to help people feel connected to Pulp as a living project they can engage with. Ok, so putting that in list form, and remembering that not all of this should be a part of every demo: releases important upcoming changes deprecations to start planning for current known problems things that need to be tested key problems that need to be solved big new features or changes being planned what is the release cadence what direction is the project going in general what is being prioritized or not and why highlight community participation events such as conferences or meetups new or improved documentation for contributors highlight channels of communication (email list, twitter, blog posts, etc) how are other people using Pulp I'm sure there are more items that could be added to that list.
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
