Welcome aboard, Jeremy!

The easiest way to help out is to use Devuan regularly, and keep track of
the things about it that bother you. Then, try to figure out how to fix
them, and share your fixes--be they new program configurations, shell
scripts, Python scripts or C programs. If you ever get stuck, feel free to
email the list and we can help you :)

-Jude

On Wed, Apr 8, 2015 at 8:40 AM, KatolaZ <katolaz@???> wrote:

> On Tue, Apr 07, 2015 at 10:07:13PM -0400, JeremyBekka C wrote:
>
> [cut]
>
> >
> > I know that I have a lot to learn, especially after reading the
> technical
> > posts here about the development of Devuan, but I am motivated and want
> to
> > learn. There is so much out there to read that I am overwhelmed sometimes
> > and don't really know where to start. There are so many man pages that I
> > really don't know which ones are the most important ones to read first.
> So,
> > I am wondering if I could get some tips on what I need to learn and how I
> > can go about getting the proper training to be of service here in the
> > Devuan community. I would like to be able to help detect and fix bugs,
> and
> > maybe become a package manager someday.
> >
> >
>
> Welcome Jeremy,
>
> as other have already said, there is probably no standard recipe to
> get there :) IMHO, the manpages that you must to read first are those
> of the programs that you need right now, the programming language to
> learn first is the one that you need right now, the tools to use first
> are those that you need right now, and so on. That's because studying
> something that you need or would very much like to know is much easier
> than just reading anything at random.
>
> Having said that, if you don't feel a compulsive need to know anything
> in particular, then you should probably start from the core utils:
>
> $ info coreutils
>
> and when you have gone through them you can start wandering at random,
> e.g.:
>
> $ man `ls /bin /sbin | shuf | head -1`
>
> and when you are done with those, try:
>
> $ man `ls /usr/bin /usr/sbin | shuf | head -1`
>
> But remember: manpages are there to be read when you need them, not to
> be memorised :)
>
> Concerning programming languages, I agree that C should be the first
> choice, together with shell scripting and then one of either Perl or
> Python. But again, if you can't find a way of using them, or you don't
> feel the need to use them for something in particular, then you will
> just learn and forget almost everything.
>
> My2Cents
>
> KatolaZ
>
> --
> [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
> [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
> [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
> [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>