We need more hands on deck capable of dealing with the transformation of packages from Debian to Devuan

As of today, if I were to say, "I have a few hours to spare, let's see if I can help transform a package from Debian to Devuan" I couldn't name a single one in need of attention because there isn't written wishlist anywhere. Hopefully that problem will solve itself now that I'm the DNG mailing list and the IRC and checking for new threads here more often, but what I'm saying is feel free to talk about your wishlists in front of me. I'm not looking to be given an assignment by a "Devuan manager", but I'm actively keeping my ears open for things that need doing.

To involve yourself in the Devuan project is different. It will require that you put yourself forward and take part and interest in the daily discourse (primarily on IRC discussions), and there step up to take on sorting out particular matters as needs and opportuinty arises.

You know and trust yourself I hope, but the key will be to become known and trusted among the Devuan group members, to then eventually be given opportunity for direct contribution to and responsibility for matters then at hand.

Thus: personal engagement to build trust and then eventually contribute towards the commons in the "cloak" of Devuan.

We do see people doing their own thing and publish their works on this forum. That's also good. Those are personal efforts fully driven by themselves, on the side of, rather than by, the Devuan project.

Devuan contributors are 99% self-motivated. Since only you know you skills and interests, wouldn't it be more logical for you to hang around and if you see something that needs attention and piques your interest, just do what needs to be done and submit the fix? There are very few times I have ever asked someone to do something and then only after knowing them for some time. IOW . . . this is not a top down organization where we assign projects. If you see something that needs attention perhaps discuss it on our channels then just do it or not.

IMO a wiki is a low priority project for Devuan. We need more hands on deck capable of dealing with the transformation of packages from Debian to Devuan

I am a man prone to flit between many hobbies, but right now I'm building something based on Devuan and so interested in contributing back to the community a little, so feel free to shove problems in front of my nose in case I bite down and fix something.

Sounds like a job for a PHP programmer who's into web development! wink

Several decades ago, I was lured into using PHP for parts of my websites and got badly burned by upgrades that would break the sites and require extensive reconstruction. On one complicated site, I went through the hassle of moving all that php data to a very long list of text archives that would never need to be touched again. They haven't needed any maintenance/reconstruction since then. 

IMO a wiki is a low priority project for Devuan. We need more hands on deck capable of dealing with the transformation of packages from Debian to Devuan and avoiding the onslaught of challenges being thrown at us by Debian and their corporate masters nearly daily. Focusing on a wiki is a bit like fiddling while Rome burns . . .

I would like to ask a question concerning the future of documentation in Devuan. Will all documentation for Devuan remain on this forum, or will there be some kind of wiki or another site to help out with documentation? Just asking!

Sounds like a job for a PHP programmer who's into web development!

If anyone has actually created a centralized guidebook to "Administering Systems Without SystemD", I'm too green to know about it myself, and would like to see it. Devuan supports multiple init systems, so some things aren't going to be the same even across all Devuan systems.