[Cuis] Package structure et al

[Juan Vuletich]

Hi Folks,

Just experiment, and document your finding. If you come up with a 
"recommended practice", that would be great. It doesn't need to be 
perfect. But if we do it the same way, and keep improving the docs, it 
will be consistent and efficient.

Thanks,
Juan Vuletich

H. Hirzel wrote:
> Yes, Ken
>
> I have now deleted my former repository https://github.com/hhzl/Cuis
> and forked it again from https://github.com/jvuletich/Cuis.
>
> I had copies of other packages in a subdirectory in the deleted
> repository. Before I copied oujt the things I had done there. I
> consider it now as an exercise of learning how to use branches with
> github.
>
> Now I am applying the new system you propose, i.e. write load scripts
> which follow it.
>
> Thank you for your idea of labeling the base directory with the version number.
>
> Thus I have
>
> Cuis4.1
>     Cuis
>     Cuis-PetitParser
>     Cuis-Ia-En
>
> I got this by doing
>
> mkdir Cuis4.1
> cd Cuis4.1
> git clone git clone https://github.com/hhzl/Cuis.git
> git clone  git clone https://github.com/hhzl/Cuis-PetitParser.git
> git clone  git clone https://github.com/hhzl/Cuis-Ia-En.git
>
> Regards
>
> --Hannes
>
> On 1/9/13, Ken Dickey <Ken.Dickey at whidbey.com> wrote:
>   
>>> May I ask you to rework (not much) what you have written in the
>>>       
>> previous mail, describe how we think development should be done in
>> terms of directory structure, put it into an *.md file, add it to your
>> Cuis fork and issue a pull request to Juan?  This will keep the
>> results of this thread readily accessible to other people who will
>> join the Cuis effort  :-)
>>
>> Hannes,
>>
>> I will be happy to do that, but let's allow some other folks time for
>> discussion and critique.
>>
>> -KenD
>>
>>
>>     
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
>
>