Helping us to run endless list of tasks will let developpers more time to focus on the code. so please
- read this document
- ask any question about it on sympa-users or sympa-fr mailing lists
- pick a task and let us know
- if you're stuck, let us know how we can help you back
ASAP * sympa meetup at JP'17? * CfP JP'17? * CfP RMLL * CfP JRES * CfP perl conference * CfP Fosdem
- curration of the sympa contrib page: create updated repos of every relevent pluggins we should/can support
- sympa spore spec
- as we should remove the "content part" of sympa, farming/driving CMS, wikis or Blogs is much more relevant (explore pft, ikiwiki, drapper, statocles, webgui twiki, ...)
- translate the current documentation to a git-book/pandoc thing
- setup a pootle? no idea what to do there ...
- start writing guides or other tutorial support for
- administrator
- listmaster
- group owner
- group member
- themer
- translator
- developper/contributors
-
blog about sympa (in any language, for anything worth to share)
not only to make all the world know that sympa is alive and cool but it's a good way to give some perspectives on how sympa is used (good readling for the developpers)
-
provide support on the sympa-users mailing list
-
help us to run hackathons and meetings
- find venues
- organize, invite
- spread the world using blogs, mailing lists and social networks
-
run betas and give us feebacks any kind of feedback (UX, install and run, perfs, ...)
-
translate
having an up to date translation both for UX and documentation is very important for a successfull project.
-
fund rising
cash should help to organize events (trainings, hackathons, ...) as well as running servers for the project.