Documentation, such as README and CONTRIBUTING files, can serve as the first point of contact for potential contributors to free/libre and open source software (FLOSS) projects. Prominent open source software organizations such as Mozilla, GitHub, and the Linux Foundation advocate that projects provide community-focused and process-oriented documentation early on in order to foster recruitment and activity. In this paper we investigate the introduction of documentation into FLOSS projects, as well as whether early documentation conforms to these recommendations or explains subsequent activity in communities. We use a novel dataset of FLOSS projects packaged by the Debian GNU/Linux distribution and conduct a quantitative analysis of examine README (n=2280) and CONTRIBUTING (n=452) files when they are first published into projects repositories. We find that projects create minimal READMEs proactively, but often publish CONTRIBUTING files following an influx of contributions. The initial versions of these files rarely focus on community development, and instead describe processes and offer technical summaries. The findings suggest that FLOSS projects do not create documentation with community building in mind, but rather brevity, usage, technical features and processes.