Re: [Tcllib-devel] Supplemented documentation for markdown package

[Andreas K. <and...@gm...>]

Oops. Lost track of that yesterday (*).

> 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.

Thanks.

> > 
> >> 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.

Yes, exactly
 
> > 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>

Nice. ... Although there is the feeling that the separating line is
needed ... I am wrong. Looking at
[Common Mark](https://spec.commonmark.org/0.30/#example-76),
it agrees with the report.

Note: It is actually example 77, but linking that directly keeps the
preceding explanatory text out of sight.

> 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.

Sure.

> I also want to look at the other open ticket on the Markdown module.

Go ahead and thank you ...

> After this, I would really like to add more of the extended markdown
> syntax to the module.

You are going definitely for maintainer here, I believe ;)
Good that you have read all the documents around that already.

> 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.

Looping Sean in here. ... That said IIRC he is not the original author
either. I believe the original code was pulled and forked from the
... Caius Project (also MIT license) (Just looked at the code and found the 
ref)

We (Tcllib) have already changes in our code upstream has not
taken. Having more is fine with me. Especially if ours becomes more
capable in the bargain. I cannot speak to Sean's opinion (which is why
I looped him in)

> 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.

That sounds really good. Tklib has not had that much love over the
years than it should. It is mainly Csaba updating Tklib's opies of
some of his packages (tablelist, mentry)

(*) The distraction delaying this response was actually me using the
Tklib example `examples/canvas/osm.tcl` as foundation for a small map
widget and then an app enabling me to (relatively) quickly assign (**)
geo coordinates to the pictures I have taken over time. And then using
that to start through my collection, beginning in 2001.

Current image on the left, list in the middle, map display on the
right, various buttons and fields for coordinate display, naming
important coordinates for quick re-selection, etc.

(**) I should note that the assignments are __not__ stored in the
pictures themselves. I save them into a TSV file with the pictures
identified by hash. Plan is to feed that into a larger system for
document storage and indexing, where things can be tagged any which
way. For the longer term future, when I have enough geo tagged data I
will look into reverse geocoding as means of translating them into
addresses.

> > 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!

Welcome to Tcllib.

> Regards, und beste Grüße aus dem Norden (Lübeck),
> Torsten

-- 
Happy Tcling,
	Andreas Kupries <and...@gm...>
			<https://core.tcl-lang.org/akupries/>
			<https://akupries.tclers.tk/>
	Developer @	SUSE Software Solutions Germany GmbH
-------------------------------------------------------------------------------