This afternoon at PuppetConf, we spent a nice chunk of time discussing Armatures, largely in incomplete sentences. Here are some of them.
## Good things about the project/process - People DO care (yay) - Implementation done in parallel with documentation works well (see arm-2,9) ## Less good things ### Commenting/feedback needs work - It's unclear how to engage - We need a reasonable way to collect and correlate various sources of discussion. Perhaps we add additional files in the repo w/ chat transcripts and the like. - Include a section in the ARM itself to record supporters/commentors - Low-friction thumbs up/like/+1 ### Visibility/awareness - Moar and better office hours - Real web site (there's an open PR with a first crack at this) - User interviews - discover use cases, survey the viability of an implementation, and so on - Automation and help for writing, perhaps using Github's magic 'Forking with the Edit Button' thing, along with clear prompts. ### Steep participation curve - Is this a perception, or a reality? - Where does one start? ### Stalling out - Process needs timers like community pull requests - 1 week without activity = ping - 2 weeks = closed - What happens when the idea is good but has no dev resources? - Perhaps a neutral and encouraging status like "patches accepted" -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
