Yes, I was thinking in a simple list, as I've said before.<br><br>Yesterday night I was near of start a gist, but was to late and I went to sleep :)<br><br>I've several packages to add to the gist, I should fork it, update, and then request you a pull?<br>
<br>Or you prefer to update yourself being that are only a bit of text....<br><br>Cheers.<br><br><br><div class="gmail_quote">2012/12/27 H. Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/27/12, Angel Java Lopez <<a href="mailto:ajlopez2000@gmail.com">ajlopez2000@gmail.com</a>> wrote:<br>
</div><div class="im">> My second suggestion was a list.<br>
<br>
</div>+1<br>
<br>
You may fork <a href="https://github.com/jvuletich/Cuis" target="_blank">https://github.com/jvuletich/Cuis</a><br>
add a 'doc' subdirectory<br>
<br>
and start your list as an text file there.<br>
<br>
At the moment there are 4 forks and I think you are not among them.<br>
<br>
Or alternatively I could do it myself. :-)<br>
<br>
Here is my fork<br>
<a href="https://github.com/hhzl/Cuis" target="_blank">https://github.com/hhzl/Cuis</a><br>
<br>
Now I have to figure out how to do the 'doc' subdirectory and create the file.<br>
<br>
<br>
For the meantime a gist with a text file might be easier<br>
<br>
something like this<br>
<br>
<a href="https://gist.github.com/4387559" target="_blank">https://gist.github.com/4387559</a><br>
<br>
(markdown, a title is underlined with -------- and shows up bold)<br>
<br>
More on Markdown<br>
here<br>
<a href="http://www.johnmacfarlane.net/pandoc/README.html" target="_blank">http://www.johnmacfarlane.net/pandoc/README.html</a><br>
<br>
Markdown, the main documentation format of github may be converted to<br>
many formats.<br>
<br>
see for example here<br>
<a href="http://www.johnmacfarlane.net/pandoc/try" target="_blank">http://www.johnmacfarlane.net/pandoc/try</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
> If the package "is outside" the central repo, the instructions to<br>
> read/install from Cuis should be at the other author repo. Then, he/she has<br>
> the responsability to update the info, not the central repo author.<br>
><br>
> The central repo author could resolve issues like "I have a new package for<br>
> Cuis at ..., please at to your list", the n he can add to the Package.md<br>
> link page.<br>
><br>
> But having the central repo with the package (not a link), has an<br>
> advantage: central repo could have tags. So, the packages at tag "v0.1.0"<br>
> are all compatible with that tag, and every improvement at tag "v0.2.0"<br>
> should be committed to that tag. The "master" tag is the development tag.<br>
><br>
> So, I could download the v0.2.0 with all the optional packages of that<br>
> version, without struggling going to each package author repo, and trying<br>
> to guess what package/tag is compatible with Cuis v0.2.0<br>
><br>
> Cons: it put more responsability to central repo author(s).<br>
><br>
> On Thu, Dec 27, 2012 at 8:01 AM, Germán Arduino <<a href="mailto:garduino@gmail.com">garduino@gmail.com</a>> wrote:<br>
><br>
>> Yes, it's an option.<br>
>><br>
>> But I was thinking in something more simple, only a list with the link of<br>
>> the repo :) and may be some code to read/install from Cuis (something as<br>
>> we<br>
>> did in the old times of SmallLand ... using a swiki (the only tool that<br>
>> we<br>
>> had in such times)).<br>
>><br>
>> Cheers.<br>
>><br>
>><br>
>> 2012/12/27 Angel Java Lopez <<a href="mailto:ajlopez2000@gmail.com">ajlopez2000@gmail.com</a>><br>
>><br>
>>> Until you have a package manager, first idea:<br>
>>><br>
>>> Use the cuis repo at GitHub.<br>
>>><br>
>>> Every contributor make a fork.<br>
>>> He/she add the code to his/her fork.<br>
>>> Make a pull request to central repo<br>
>>><br>
>>> Maybe, a guide to have folders per package/topic.<br>
>>><br>
>>> Alternatively (or complementary), a PACKAGE.md page at Cuis central<br>
>>> GitHub repo<br>
>>><br>
>>> Angel "MyLifeIsGitHub" Lopez ;-)<br>
>>> github:ajlopez<br>
>>><br>
>>><br>
>>> On Thu, Dec 27, 2012 at 7:49 AM, Germán Arduino<br>
>>> <<a href="mailto:garduino@gmail.com">garduino@gmail.com</a>>wrote:<br>
>>><br>
>>>> Nice!<br>
>>>><br>
>>>> We should have a central place where list all the available packages<br>
>>>> ready to use for Cuis?<br>
>>>><br>
>>>> Cheers.<br>
>>>><br>
>>>><br>
>>>> 2012/12/27 H. Hirzel <<a href="mailto:hannes.hirzel@gmail.com">hannes.hirzel@gmail.com</a>><br>
>>>><br>
>>>>> Hello<br>
>>>>><br>
>>>>> I installed<br>
>>>>> PetitParser.pck<br>
>>>>> PetitTests.pck<br>
>>>>><br>
>>>>> from<br>
>>>>> <a href="https://github.com/pmon/Cuis-PetitParser" target="_blank">https://github.com/pmon/Cuis-PetitParser</a><br>
>>>>><br>
>>>>> RESULT<br>
>>>>> The tests run fine in 4.1.<br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Cuis mailing list<br>
>>>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
>>>>> <a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> ============================================<br>
>>>> Germán S. Arduino <gsa @ <a href="http://arsol.net" target="_blank">arsol.net</a>> Twitter: garduino<br>
>>>> Arduino Software <a href="http://www.arduinosoftware.com" target="_blank">http://www.arduinosoftware.com</a><br>
>>>> PasswordsPro <a href="http://www.passwordspro.com" target="_blank">http://www.passwordspro.com</a><br>
>>>> <a href="http://greensecure.blogspot.com" target="_blank">greensecure.blogspot.com</a> <a href="http://germanarduino.blogspot.com" target="_blank">germanarduino.blogspot.com</a><br>
>>>> ============================================<br>
>>>> _______________________________________________<br>
>>>> Cuis mailing list<br>
>>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
>>>> <a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
>>>><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Cuis mailing list<br>
>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
>>> <a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
>>><br>
>>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Cuis mailing list<br>
>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
>> <a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
>><br>
>><br>
><br>
<br>
_______________________________________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>============================================<br>Germán S. Arduino <gsa @ <a href="http://arsol.net" target="_blank">arsol.net</a>> Twitter: garduino<br>
Arduino Software <a href="http://www.arduinosoftware.com" target="_blank">http://www.arduinosoftware.com</a><br>PasswordsPro <a href="http://www.passwordspro.com" target="_blank">http://www.passwordspro.com</a><br><a href="http://greensecure.blogspot.com" target="_blank">greensecure.blogspot.com</a> <a href="http://germanarduino.blogspot.com" target="_blank">germanarduino.blogspot.com</a><br>
============================================