Repository organisation guidelines

[xzilja]

Introduction

Hey Everyone! Today I planned to re-implement several of deprecated modules via new ones created within react-native-comunity. I soon came to realisation that currently each repo within community is different from one another in various aspects and hence wanted to discuss possibility of unifying them in order to provide consistent experience.

The Core of It

• Some packages lost their typescript definitions once they were extracted from main rn project, since @types/react-native covered pretty much whole codebase.

• .podspec files for iOS are sometimes located either in root of the repository or inside ios folder.

• Some packages have ci process set up in place, others don't

• Packages have different eslint configs, some try to use react-native-community preset, but add extra rules or overwrites

• README files are very different in terms of headline order / having or not having demos, their language style etc...

• Folder organisation is different, some use lib for main code, some use src. Some repos have examples, others don't.

Discussion points

Would it be a good idea to come up with structure / examples of repo organisation for react-native-community in order to make each package more familiar to the user and ensure all of them deliver consistent quality? Or will something like this harm creativity / velocity of maintainers?

[xzilja]

Will break this down into smaller issues