Hi Jack, Thanks for the response. I would be happy to help with the user facing documentation. I'm not sure exactly which KDE docs you are talking about so a link would be appreciated. For reference I am running KDE Neon with KMM 5.0.1 (my package manager says 5.0.1, KMM itself says 5.0.0 but I think I saw there was a bug about that), so I should be all up to date for making new user documentation. Do you have a checklist of work to be done, or some task you would like to delegate to me?
Thanks, Joshua On Sun, May 27, 2018 at 1:48 PM, Jack <ostrof...@users.sourceforge.net> wrote: > On 2018.05.27 13:21, Joshua Christopher wrote: >> >> Hi developers, >> >> I've been using KMM for a couple years now and want to start giving >> back. I am a C++ developer at my job but only have a hobbyist >> understanding of Qt and QML. I'm not sure if I would be capable of >> fixing bugs just yet due to my unfamiliarity with the KMM code base >> and Qt. >> >> Would you be interested in me helping to triage bugs? It seems there >> are a quite a few unconfirmed or stalled bugs on the tracker right >> now. >> It also looks like there may be a need to update documentation, e.g.: >> https://bugs.kde.org/show_bug.cgi?id=340244 >> I'm assuming this is user facing documentation, would you like help >> with that and if so how can I get started? >> Is there anyway I could get helping out with developer docs? That is >> usually a good way to get familiar with a new code base! >> >> Thanks, >> Joshua > > Hello Joshua, > > Thanks for the offer. I'll let one of the developers comment on how you > might help with the code, but I do most of the documentation (user facing) > support. Bug 340244 is really only left open as a place-holder and > reminder, mainly for myself. When we released 5.0, I only got about half > way through the manual in terms of assuring it matched how the current > version works, and I updated screen-shots as I went. I do hope to get to > the rest of the manual soon, and will do the screen-shots as I go. However, > if you really are interested in producing a complete set of new screen > shots, I wouldn't mind - the main issue is doing so with a consistent style. > I can point you to the KDE docs on documentation if you wish, but we can do > that through direct email, no need for all of that on the list. I'll leave > the issue of triaging bugs to the developers, other than to say that the > distinctions of unconfirmed v. confirmed is pretty arbitrary - there are > many bugs that go directly from new to resolved without ever being > confirmed. I suppose it might introduce some consistency - just to confirm > if more than one person sees the problem, or can reproduce the crash. Also > - at some point, we really should find all the bugs against versions older > than 4.8 - some have probably been fixed in newer versions, but without the > bug having been resolved; others could be marked either unmaintained or > needsinfo unless someone else can confirm the problem still exists in 5.x. > > While 4.8 will continue to be maintained for a while, I doubt much effort > will be spent fixing bugs or crashes. It is only necessary for those few > distributions (including KDE-Windows) where 5.0 is not yet reasonably > available - but those cases are slowly decreasing. > > Jack
