Public roadmap and a process to onboard contributors

Dev Talk
1

Continuing the discussion from LibreTime Development Priorities:

1 Like
2

Does anyone else think folks would benefit from a public roadmap and a more defined process for contributing? What about seeing if we can find someone able/interested in a few hours/wk of project management?

3

When you take a look at the github repo you will see that the lastest commit is from april 2017,so there is no “active development” or whatsoever, from my perspective the people who are involved in this project are mostly arguing about religious reasons to use slack or not, so i would suggest get a motivated developer from https://www.fiverr.com and point out the most important features and enhancements that are nessesary to update the curent codebase.

Regards

4

@macbroadcast if you’ve abandoned this project please stop posting here.

5

Bumping this up as there’s been an uptick in contributions from maintainers, interest from new contributors, and some early stage financial support via https://opencollective.com/libretime

Is there still a need?

6

How about https://github.com/LibreTime/libretime/projects/2 as some sorts of overview?

7

That’s a great overview! Not sure how many newcomers to the project (or even folks that already want to contribute) would even know to go there. Is there a section on ‘how to get invovled’ on http://libretime.org or the new site in the works? https://github.com/LibreTime/libretime/pull/590

8

Is there a section on ‘how to get invovled’ on http://libretime.org or the new site in the works?

Apart from the waaay to technical stuff in the main README.md not that I know of. This is certainly an area to improve.

9

We probably should create a documentation task in gihub? Could actually be a good task for non coders who would like to get invovled!

10

Possibly we could incorporate some of these ideas on the new site?