Re: Hoisting other libraries from M2BSK?

[Alice Osako]

Benjamin Kowarsch:
> I didn't mean to make the repo completely writable for everyone. If 
> somebody wants write access, they will have to ask and they are 
> unknown to me or other contributors, they will need to introduce 
> themselves and state their purpose, perhaps a quick video chat. If it 
> is somebody who actively contributes on this list, then I'd just grant 
> them write access.
>
> Anyway, I will try to make some time to set up a new repo and move the 
> code over. Perhaps some time this week, or on the coming weekend. We 
> can take things from there then.

Sounds great!

Would this all be in one repo, or would you be breaking it down into 
multiple repos based on the specific subject matter (as I had been 
planning to do)? Both have their advantages and disadvantages. Overall, 
a single repo probably makes the most sense, though it would mean that 
client programmers would by adding the whole as a sub-module even if 
they only need, say, the Integer library. Alternately, breaking it up 
would mean that many client programmers would end up with several 
sub-modules, which could become unwieldy. It is a common question with 
libraries, and not one with a hard and fast answer.

Feel free to re-import the modified code from here:
https://github.com/Schol-R-LEA/Modula-2-Portable-Bit-Manipulation/tree/main

If you do, I will probably close the repo I created for it and switch to 
using the one you set up for my own projects.

There may be some subtle matters regarding the license (GPL3 vs. LGPL3), 
but I won't open that can of worms if you don't. Since my code is based 
on yours, I will follow your lead on this point.

Similarly, if you are planning to have a single large repo, you might 
want to roll my work on UNICODE character support into the library, 
though that may present a more significant licensing conflict given that 
it was based in part on Chris Lilley's code (which is under GPL3 - the 
whole reason I was using GPL3 was to avoid conflicts with that).

Speaking of which, if Chris Lilley is on this mailing list now, I would 
be interesting in getting his input about the project.