From: Torsten B. <be...@ty...> - 2021-09-13 21:00:38
|
Der Andreas, thanks for taking the time to answer. > >> What is the recommended way of submitting such a change? > >> Should I send it as a ticket on the fossil repository of tcllib? > > Yes. OK, I'll do that. > >> What are actually the requirements to become a contributor who is >> able to commit to the repository directly? > > How much can you agree with > > https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/ > tcl_community_communication.md > > ? I had read those documents unter https://core.tcl-lang.org/tcllib/dir?ci=tip&name=devdoc <https://core.tcl-lang.org/tcllib/dir?ci=tip&name=devdoc> already because I was looking for some guidance on how to contribute. This is totally fine with me and I appreciate you have spelled out clearly in the document how the Community is working. From your answer I see it works just the same as for the core. The more is contributed with good quality, the higher the chance will get to be trusted. Fine with me. > > Do you plan to submit only documention changes ? No. I have also looked at the tickets which are open for the Markdown module and I think I have fixed this one: https://core.tcl-lang.org/tcllib/tktview/5b8e3a9e9bb8a12fe4d0 <https://core.tcl-lang.org/tcllib/tktview/5b8e3a9e9bb8a12fe4d0> I have added a few more test in markdown.test that expose the problem and can see that it works now in my version. But I want to add some more tests still to be sure I haven't broken something else. I also want to look at the other open ticket on the Markdown module. After this, I would really like to add more of the extended markdown syntax to the module. But, before I do this, I would like to have some feedback whether such additions are actually appreciated. I am not the original author of that package and can understand when the intention is to not go beyond the basic markdown implemented. I'll write my own version then. However, if this is welcome, I just do the work in tcllib and give it back to the Community. I also have some private packages here that I am using for years now, and at some point I think I am ready to make them public. Mostly, they are rather additions to tklib, however. > > At the beginning I would prefer to get patches via tickets, with > possibility to upgrade to commit access after a while. Sure, no problem! I am glad to help in whatever way yo find suitable! Regards, und beste Grüße aus dem Norden (Lübeck), Torsten |