# Building Community ###### tags: `PulpCon 2020` # Agenda ## Prompt: What is the best way for Pulp to grow its community? Proposal from bmbouter: Adjust from the strategy of "attract contributors" to an exclusive focus on "attract users". Questions for discussion: * Retrospective question: Was accepting co-maintenance responsibility for pulp_cookbook the right decision? * Retrospective on the "conference workshops", how does the contributor vs user strategy worked out in those session? * What is more important to attract more users: more plugins, better plugins, or more usable things around plugins (UI, CLI, operator, etc)? ## Discussion notes * What does being in pulp org (on GH) mean for repositories? - co-maintainance - how are community contributions handled? - How are neccessary changes for breaking changes handled? * Do we focus to attract contributors or users? * users tend to not know about pulp * if you can get it up and running in an hour it is interesting * users will lead to contributors in a natural way * The original reason we had an "attract contributors" strategy * Pulp3 was not GA, you can't build a large userbase on software that isn't built and GA * It was likely the correct strategy at that time * Ideas on attracting users: * Rest api is a good toolbox, CLI and UI, ... can focus around workflows * Common workflows should be easy * See examples of users work flows - marketing important for prospective new users