[Cuis] Package structure et al

[Juan Vuletich]

Hi Ken,

KenD wrote:
> FYI: I keep siblings in a directory named by the (major) release:
>  ../CUIS-1.4/Cuis
>  ../CUIS-1.4/Cuis-Ia-En
>
> I would prefer this to .gitIgnore as I suspect there will be fewer name collisions.
>
> We already have the potential for confusion with package names.  
>
> Perhaps someone wants to add code for Interlingua to Spanish/French/Italian/.. in the Interlingua package.
>
> If the code is unshared, siblings can be loaded in any order.  If common code is used, there will be a composition order.
>
> In the ideal world, one should be able to look at package info [assume a package header/manifest & requirements] and do a transitive closure over all package requirements to get a proper load order or find a missing requirement or code clash [e.g. same class name defined with different code].
>   

This would be good, indeed. It is just that as everybody's time is 
limited, it is important to prioritize.

> The question I like to ask is "What is the simplest thing that will work?". (eXtreme Programming question)
>
>
> In the short term, I favor sibling directories as I think that this will confuse me the least.
>
> I would like to move to a package header which gives the compatibility.version = major.minor and lists package dependencies: zero or more of { packageName compatibility }.. ).
>
> I don't think an implementation is needed until the first package with a dependency requirement, but given networking, web servers, and so forth this day may not be far off.
>
> As far as I am concerned, Juan is king of the CUIS universe (think Linus Torvalds and Linux).  We should not overburden him with demands.
>
> One way to go forward is to have people who propose things do a prototype/sample implementation.  This helps avoid too many people proposing too many things, gives concrete examples to aid communication, and gives people something to try out and improve or discard.  Juan can then either ignore, replace, improve, or adapt a suggestion without having to write every line of code himself.
>
> Right now we are doing "baby steps" so this is not (yet) a big thing.  But success must be carefully managed so CUIS can grow without being smothered.
>   

Thank you Ken. This is very thoughtful.

Cheers,
Juan Vuletich

> Wow.  This is getting long.  I better stop typing.
>
> So, what is the simplest thing which works?
>
> -KenD
> --------------------
> When I works, I works hard.
> When I rests, I rests easy.
> When I thinks, I goes to sleep.
>
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
>
>