Would you be interested in contributing (docs, code, testing)?

vimanuelt

Would you be interested in contributing (docs, code, testing)? If not, what are the barriers?

brianthehughes

Absolutely, and I do.

Across all of these topics - Prioritization is a factor. Importance to the Project, Urgency to resolve. Prioritization information is largely undefined/null - as far as I can tell.

Testing barriers/challenges include;

test scope definition
test procedures
open issues / closed issues correlation with updates

Code barriers/challenge;

my git skills/comfort is very novice
the variety of language preferences is equal to the project participants (LOL)
sh and python being core to GhostBSD is great, but again, my skills/comfort is very novice

Docs

guide-style documentation requires start-end to a given topic and many topics are open ended and/or dependent on the user goals or system/service implementation
gracefully leveraging the variety of upstream resources vs. the project layer resources is challenging without an accepted standard to integrate GhostBSD's scope in the larger context of the upstream resource.

vimanuelt

I have contributed to GhostBSD in the past by submitting code and performing testing. The progress bar in Software Station is one example of my work.

Many of my ideas tend to be too ambitious or wide-ranging to include directly in GhostBSD, so I have pursued them through my own independent projects. When there is meaningful overlap, I do try to bring certain ideas back into GhostBSD. That said, most of my contributions to the project now take the form of helping others resolve issues and offering alternative perspectives to support discussion and improvement.