Hi everyone, it has been a long time but my interest in Perkeep has come up again. (I am working on a Google Takeout importer right now). As I am recently working much on an Apache project a question came up in my head while looking at the projects activity again: Would Perkeep work and grow as an Apache project? Is this something anybody ever considered?
This idea/discussion might be out of place, but I am asking anyway because my first thought was that Perkeep works almost exactly like an Apache project. A diverse group of people contribute from time to time, the license fits, most processes and ideas are similar to Apache ones and the major platform for discussion is a mailing list. What are the challenges to move Perkeep forward? From my point of view it's that maintainers don't have the time to work on it and from an end users perspective it may needs to be more approachable. Going through the Apache Incubator would be a lot of work and may not be successful. But I know some people that may have good advice for this and the project might grow the community in that environment. After becoming member of an Apache project I started to understand why it works like that and why this sense of shared ownership matters. If this idea does not make any sense please ignore it and apologize me for thinking out loud. P.S: I love Perkeep. It still runs very stable in my setup even after ignoring it for some time. It's a great project and I wish I could contribute more to make it even better. Kind regards Niklas Merz -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/694ba6e1-fa34-4948-a857-7266862fe090o%40googlegroups.com.
