![]() Any suggestions are very welcome on that topic. Publishing the roadmap is must-do as well. Looking at other open source projects, what I am thinking of is writing some “help wanted” tickets with very defined user stories and even prototypes to have people step in on a small feature without having to understand the whole platform. But I totally agree that we do have to put more effort in talking to the community and being more transparent on the roadmap. ![]() There’s already a lot of material for starting digging and contributing. It may just not fit the needs at a given point.Īlso, all the codes (server and desktop client) are on Github, and we’ve put great effort in updating the admin and developer docs for Cells on the website. I’ve been doing open source for years now, and I am used to the standard “this is not a working project” messages, whereas tons of people all around the world use it everyday in production. It’s waaay smoother and much more reliable than Pydio 8. Using Cells as a collaboration tool for sharing documents in an organisation is a perfect match, and in fact many of our open source users as well as paying customers are super happy with that. Considering Pydio Cells “not finished” seems a bit unfair to me. First of all, thank you for your messages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |