<commit_before>###Summary

The PyCon Organizers Manual, an effort started by the 2016 - 2017 Python Software Foundation Board of Directors, is meant to be an evolving document containing information about how to get started organizing a PyCon or other Python conference.

####Notes on Why a PyCon Organizers Manual and How to Read 

This manual is meant to be collection point, unifying the work of previous projects and integrating voices of different segments of the Python community, and hopefully will become a common ground for Python organizers. That being said, this manual is also a work in progress. Anyone is welcome to contribute and offer feedback. If you would like to participate, please read the [how you can contribute](docs/how_to_contribute.md) chapter to get started. 

####Table of Contents

See something missing? Make a [pull request](https://github.com/lorenanicole/pycon_organizers_manual/pulls) or [add an issue](https://github.com/lorenanicole/pycon_organizers_manual/issues)!

[How You Can Contribute to this Manual](docs/how_to_contribute.md)
[Fundraising](docs/fundraising.md)
[Financial Aid](docs/financial_aid.md)
[Developing a CFP](docs/developing_a_cfp.md)
[Speaker Selection](docs/speaker_selection.md)
[Code of Conduct](docs/code_of_conduct.md)
[Selecting a Venue](docs/selecting_a_venue.md)
[Marketing](docs/marketing.md)
[Regional Specific Information for Events](docs/regional_specific_information.md)
[Committees](docs/committees.md)
[Volunteers](docs/volunteers.md)
[Accommodation](docs/accommodation.md)
[Recording Talks and General AV Support](docs/recording_talks.md)
[Etc](docs/etc.md)<commit_msg>Add spaces for table of contents<commit_after>###Summary

The PyCon Organizers Manual, an effort started by the 2016 - 2017 Python Software Foundation Board of Directors, is meant to be an evolving document containing information about how to get started organizing a PyCon or other Python conference.

####Notes on Why a PyCon Organizers Manual and How to Read 

This manual is meant to be collection point, unifying the work of previous projects and integrating voices of different segments of the Python community, and hopefully will become a common ground for Python organizers. That being said, this manual is also a work in progress. Anyone is welcome to contribute and offer feedback. If you would like to participate, please read the [how you can contribute](docs/how_to_contribute.md) chapter to get started. 

####Table of Contents

See something missing? Make a [pull request](https://github.com/lorenanicole/pycon_organizers_manual/pulls) or [add an issue](https://github.com/lorenanicole/pycon_organizers_manual/issues)!

[How You Can Contribute to this Manual](docs/how_to_contribute.md)

[Fundraising](docs/fundraising.md)

[Financial Aid](docs/financial_aid.md)

[Developing a CFP](docs/developing_a_cfp.md)

[Speaker Selection](docs/speaker_selection.md)

[Code of Conduct](docs/code_of_conduct.md)

[Selecting a Venue](docs/selecting_a_venue.md)

[Marketing](docs/marketing.md)

[Regional Specific Information for Events](docs/regional_specific_information.md)

[Committees](docs/committees.md)

[Volunteers](docs/volunteers.md)

[Accommodation](docs/accommodation.md)

[Recording Talks and General AV Support](docs/recording_talks.md)

[Etc](docs/etc.md)
{'fraction_non_alphanumeric': 0.08449004224502112, 'fraction_numerical': 0.004828002414001207, 'mean_word_length': 6.00845665961945, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1291604', 'n_tokens_mistral': 1001, 'n_tokens_neox': 941, 'n_words': 346}