hi, the most natural way to start working on something like RKTeaching would probably be to fork it as the RKWard community group. hopefully, we will see more development like this in the future. however, this does not work so well with the rather monolithic external-plugins repo. it also makes it a bit hard to tag releases of individual plugins, and if you'd like to contribute to just one of those you'd still have to get them all, which might become a problem over time (when it grows). is there a real advantage of having all plugins in one repo?
if not, i would like to try to split the external plugins repository on github into one for each plugin[1]. this might also be a good idea for the XiMpLe and rkwarddev packages, which are currently part of the RKWard sources and cannot be tagged/cloned individually. viele grüße :: m.eik [1] https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/ -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ rkward-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/rkward-devel
