Topics brainstorm

[jamalv]

Let’s think about some topics that would be good to add to the knowledge base.

Please just shoot in the comments and we’ll figure out some structure later :)

I’ll start with some rough ideas:

Contributing

• Contributing to the knowledge base
• how to contribute - guidelines
  • creating a pull request
• opening issues
• following styleguides

Project management

• way of working / project management
• sprint demo’s
• standups / zoom

Developer documentation

Product vision / roadmap

• goals / vision
• architecture
• brand design

[maxvisser]

lets start with the content of the website, imo this really outdated and shouldnt be on there anymore. Do we want to keep the current structure of home, platform, collaboration, media, contact?

also for the product docs: documention for compiling me-ios and me-android.

if we keep the backend open source we could add the forus api

[martijndoornik]

Something along the lines of "I am a developer. Where the hell do I start looking for this and this?" maybe? People 'validating' the code of the platform, me app, etc.

[martijndoornik]

I unassigned people? How? I didn't even press anything?

[jamalv]

👻 ?

[TomForus]

Considering the project management

I think we should focus on:

• The deliverables of the differrent teams
• How every team is built up

• If there are any third parties involved?

  In my opinion it has no use to open-source the financial part of these teams.

[MaartenForus]

Martijn made a good point regarding the intro for developers. I suggest we add some info for non developers as well. A guide which starts with what is a knowledge base in the first place, who is it for, what is the structure and which parts are understandable for non tech types that stumble upon the docs. Legal issues and licensing policies are interesting. And a explanation of the pros and cons of deployment locally vs getting it as Saas?

[jamalv]

closing due to inactivity