Nice.<br><br><div class="gmail_quote">2012/12/30 Juan Vuletich <span dir="ltr"><<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok. Added the list to <a href="https://github.com/jvuletich/Cuis" target="_blank">https://github.com/jvuletich/<u></u>Cuis</a> .<br>
<br>
Please send pull requests, or email, to update it.<br>
<br>
Cheers,<br>
Juan Vuletich<div class="HOEnZb"><div class="h5"><br>
<br>
H. Hirzel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12/30/12, Angel Java Lopez <<a href="mailto:ajlopez2000@gmail.com" target="_blank">ajlopez2000@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi people!<br>
<br>
Yes, you usually work on master (it could be called the "developer<br>
branch"), and when you are ready, tag it. Ummm.. you tag your local repo,<br>
and then push the tags to Github. AFAIK, you could move the tag to other<br>
commit, for example, if there are a minor fix in documentation or something<br>
alike.<br>
<br>
Having packages out of the central repo, is more agile.<br>
<br>
</blockquote>
<br>
+1<br>
<br>
<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe a "solution at the middle": some "blessed" (easy to test, to load<br>
from core in central repo, many used, important for community, etc...)<br>
packages are at central repo, and the other packages are listed in a page<br>
<br>
</blockquote>
<br>
I think a 'scripts' and a doc subdirectory in the main repo are fine<br>
at the moments.<br>
I.e.<br>
<a href="https://gist.github.com/4387924" target="_blank">https://gist.github.com/<u></u>4387924</a><br>
should be moved to a directory there and maintained by the community<br>
through pull requests.<br>
<br>
People need to<br>
<br>
a) find the loadable packages<br>
b) know about their status<br>
c) have a means to load them automatically (not through a GUI)<br>
<br>
for example<br>
<br>
<br>
<br>
"To install Cypress, assuming the package files are in 'cuis-cypress-master'<br>
in a subdirectory of the working directory"<br>
<br>
#(<br>
'cuis-cypress-master\Cypress-<u></u>Definitions.pck'<br>
'cuis-cypress-master\Cypress-<u></u>Structure.pck'<br>
'cuis-cypress-master\Cypress-<u></u>Mocks.pck'<br>
'cuis-cypress-master\Cypress-<u></u>Tests.pck'<br>
)<br>
do:<br>
[ :fileName | CodeFileBrowser installPackage:<br>
(FileStream concreteStream readOnlyFileNamed: fileName)<br>
]<br>
<br>
<br>
However preferably directly through web access to github without<br>
having to download the pck files first.<br>
<br>
--Hannes<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Angel "Java" Lopez<br>
@ajlopez<br>
<br>
On Sun, Dec 30, 2012 at 9:01 AM, Juan Vuletich <<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>> wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Angel,<br>
<br>
I really like the idea of having a single and consistent git commit of a<br>
Cuis version and all the packages that work on it. It would make much<br>
easier to go back to some date, and grab stuff that works well together.<br>
One downside is a bit more work for repo admin. A bigger one is that it<br>
makes things a slower for package maintainers. But the consistency might<br>
outweigh them.<br>
<br>
Below, I extracted Angel's comments on this. Folks, please comment. Add<br>
steps or ideas to complete or enhance Angel's suggestion. Or if you don't<br>
like it, please say why. This is a rather important decision, and I'd<br>
like<br>
we to make a good choice.<br>
<br>
One quick question for Angel (I'm a beginner with github): Can we tag a<br>
commit after it was done? That way, we could work together on Cuis and<br>
Packages for several days (involving many commits) and only when we are<br>
all<br>
happy, we can tag the last one as "v4.1 with packages" or something like<br>
that.<br>
<br>
Cheers,<br>
Juan Vuletich<br>
<br>
Angel Java Lopez wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
...<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<br>
"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<br>
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<br>
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>
<br>
<br>
2012/12/27 Angel Java Lopez <<a href="mailto:ajlopez2000@gmail.com" target="_blank">ajlopez2000@gmail.com</a><br>
<mailto:<a href="mailto:ajlopez2000@gmail.com" target="_blank">ajlopez2000@gmail.com</a>><u></u>**><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>
<br>
Angel "MyLifeIsGitHub" Lopez ;-)<br>
github:ajlopez<br>
<br>
<br>
<br>
</blockquote>
______________________________<u></u>**_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/*<u></u>*listinfo/cuis_jvuletich.org</a><<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">h<u></u>ttp://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a>><br>
<br>
<br>
</blockquote></blockquote>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div><br>