Community transition roadmap and first steps as a community driven library

[sneerin]

I'm still learning the source code, so please correct me if my assumptions are wrong.

I believe, so far we have 2 initial goals to start from:

1. Make it commercially supporting by any team inside their project( this could be my team, I'm reviewing this possibility)
2. Seamless setup and integration for new brownfield RN projects

Apart from obvious things like stability I can see next steps has to be done first
to achieve goals:

• complete lacking documentation. Especially for the possible integration options. Integration = new devs, new commercial support involved.
• provide simple use cases with tab bars, drawers etc... As a temporary solution could be an integration with existing libs. Not sure about that.
• review existing issues, maybe someone can pick and fix few issues
• prioritize the most lacking functionality, comments are welcome
• verify if it works with RN 0.48+ e.g. upcoming 0.49 has some changes in initial params, fix everything.
• coordination. avoid doing same things because of miscommunication.

I started with documenting initial setup and integration guide. There are lots of chapters that are totally empty. Anyone else? )
We have to think, what suits better for our distributed team. Not sure if trello will be good. We need something to track our progress.
Anyone who wants to contribute, please share your ideas, your vision, your ideas. PR/MR's are welcome.

[nitaliano]

• Documentation is critical and a great first step after it get's stabilized. All feature code from here on out should come with documentation. Even add architecture wikis, so it can be easier for new comers to get a grip on how the codebase is setup.
• Some examples that come to mind could be
  • Integration with existing native applications(Could be as simple as a Todo App, and the "new" todo could be an RN screen).
  • Integration with Redux, and Mobx.
  • Tab bar
  • Drawer
  • Push, Pop, Replace, ...etc
  • Shared Element Transitions
• For tracking progress we should use Github Projects to make it simple and straightforward. We'll be able to keep the board in priority order, setup multiple columns (To Do, In Progress, In Review, Done). It will also help us decide what features will make it into a release.
• We should have a chat channel for this repo, so anyone can asks questions and we can all communicate with each other.

Once we stabilize native-navigation I plan on using it for all RN Mapbox applications moving forward.

[carlosconnected]

Can we also include in the documentation the differences between this project and https://github.com/wix/react-native-navigation so people can make a choice of what project they want to support? There was no clear explanation in #80

[alexwasner]

There has been zero activity on this in 19 days. Is communication about this happening offline in gitter or is there just no roadmap actually being implemented?

[JuanCAlpizar]

@alexwasner did you get any additional information about it? I was wondering the same because I'm considering native navigation for a project it's going to begin next year and I was wondering between this and wix React Native Navigation

[carlosconnected]

@sneerin is there a slack channel where we can talk about this?

[lpalmes]

There is this channel, https://gitter.im/native-navigation-community, you could ask there maybe, i've been thinking about doing same maintenance myself aswell, but i'm not with time right now, the next logical step would be to bring the lib to be compatible with latest versions of react-native, and make sure is stable in my opinion