Federated calendar and event organiser
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.rst 1.6 KiB

  1. Calendar.social
  2. ===============
  3. Keep your calendar ond organise events in the Fediverse.
  4. How to contribute
  5. -----------------
  6. First, see our Code of Conduct. That’s probably the most important part.
  7. We are more than interested in
  8. - Feature ideas. The project is in its early phase, so every idea is welcome (even if it doesn’t
  9. get into the first release.)
  10. - Bug reports. Even though the project is in the early phase, we don’t want bugs to sneak in to
  11. stay there forever. Report everything you find.
  12. - Documentation. Because well, obviously.
  13. - Fixes, features, actually implemented.
  14. - Find your favourite issue/feature request
  15. - Fork and clone the repository
  16. - Create a branch for your work
  17. - Code!
  18. - Push to your branch
  19. - Open a Pull Request
  20. - Go through the review process with us
  21. - Enjoy your work getting into the main tree
  22. FAQ
  23. ---
  24. Why doing a federated calendar when you can send around vCard files via email?
  25. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  26. Because this project is about much more than a plain calendar. It’s also an event organiser,
  27. where you will be able to collaborate with others making events happen.
  28. Why is it not on GitHub/GitLab/any other popular hosting service?
  29. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  30. Because running my stuff is one of my hobby. I run my own Matrix homeserver, my own Mastodon
  31. instance, why would my Git repositories be different? It might change in the future, though; I’m
  32. not an enemy of said services and if this project turns out to be successful I might move it away
  33. from here.