Hello,

I would like to make an online conference/meeting system. The project would be open source. So I was wondering, if anyone would be willing to help me in the making of this application?

If you're interested and you want to help me, please visit:

I'm a beginner programmer, so I need all the advice/help I can get.

Thank you very much for reading/helping...

Aleksej Lazanski

Dani AI

Generated

A short, practical roadmap to turn the idea into a working open‑source conference system. The exchange from shows good intent; ’s questions correctly push for a clear scope; and ’ point about using a lightweight framework is useful for early velocity. The single most important early decision is the product scope: text/scheduling only, one‑to‑one audio/video, multi‑party conferencing, or broadcast/recording — each choice changes the architecture and hosting needs.

A sensible MVP and near‑term milestones:

  • Define one meeting mode (e.g., scheduled meetings + text chat) and user stories.
  • Basic auth, meeting creation, and calendar/scheduling backend.
  • Lightweight real‑time layer for presence/chat (WebSocket or polling).
  • Add browser media (getUserMedia + signaling) for two‑party WebRTC next.
  • If multi‑party is required, integrate an SFU/recording component later.
  • Document contribution process, license, and minimal deployment instructions.

Architecture and tech notes:

  • WebRTC is the browser standard for audio/video; it needs signaling, STUN/TURN for NAT traversal, and HTTPS/WSS in production.
  • Signaling can be implemented in PHP (persistent sockets like Ratchet) or a small Node service; separating signaling from PHP app logic keeps things modular.
  • For more than a few participants, use an SFU/media server (open‑source options exist) rather than full mesh.
  • Recordings and moderation require server‑side media handling and storage planning.

Common pitfalls and project hygiene:

  • Browser media requires HTTPS (localhost excepted) and proper certificates.
  • TURN servers are essential for reliable connections behind NATs/firewalls.
  • Start with an easily runnable demo (one button to join) so contributors can test quickly.
  • Add CONTRIBUTING.md, issue templates, and CI early to attract collaborators.

This set of choices produces a clear, incremental plan that keeps early work achievable while leaving room to add audio/video, recording, and scaling later.

Recommended Answers

All 3 Replies

i suggest using something like the codeigniter framework as its lightweight and easy to learn/adapt to and has loads of useful features at its disposal (i.e. a calendar class)

Member Avatar for Member #120589

How serious are you? How many people have you got on board? This sounds like a beginner's pet project. What type of meeting are you talking about? Video streaming? Party VOIP? Chat? Something like USTREAM? Timetable scheduling? Live minutes?

Are you looking to host the streaming or will this be down to the user website's own host?

You need to provide a lot more information. Don't worry about other people stealing your ideas - you're not the first person to do it.

How serious are you? How many people have you got on board? This sounds like a beginner's pet project. What type of meeting are you talking about? Video streaming? Party VOIP? Chat? Something like USTREAM? Timetable scheduling? Live minutes?

Are you looking to host the streaming or will this be down to the user website's own host?

You need to provide a lot more information. Don't worry about other people stealing your ideas - you're not the first person to do it.

Thank you very much for showing interest in this project. I will supply all the information about the project on very soon...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.