Little utility to use as basis for some more HS experiments
http://ogt.github.io/boxchareditor/
(it is obvious to me by know that the model of HS that I follow is for programmers.
It requires that you right a first version of what you want
It requires that the first version has an architecture that makes it easy for people to contribute, pull requests to not cause conflicts. This means that the basic file structure, modularization of your code has to be there - from you. This means that not only is it for programmers, but its actually primarily for strong programmers that can architect their code for change. Thats a rather different paradigm than the one that is made feasible by OD.
Anyway back to github.
Things I learned:
Creating a gh-pages branch and make it the default
Deleting your master branch
> hub clone repo
> cd !$
> git branch -D master
> git push origin :master
(assumes that you have already made another branch the default in the github -> settings->default branch place )
Adding a fork me image
Changing the home page/ description of the repository so as they both point to each other
(the service points to its underlying code page, the code base points to the service)
This last bit seems important. In some sense, just like in old open source, the license would actually require that every binary distribution of the code would provide a reference to a place where someone can easily get the source code for the binary.
Similarly, in the "open startup" world, every web app/web service, should be pointing to a place where someone, can fork a repository which ideally can be autodeployed (assuming that you provide config vars/urls/credentials to any external services it may use/need).
boxchareditor satisfies that small requirement
http://ogt.github.io/boxchareditor/
(it is obvious to me by know that the model of HS that I follow is for programmers.
It requires that you right a first version of what you want
It requires that the first version has an architecture that makes it easy for people to contribute, pull requests to not cause conflicts. This means that the basic file structure, modularization of your code has to be there - from you. This means that not only is it for programmers, but its actually primarily for strong programmers that can architect their code for change. Thats a rather different paradigm than the one that is made feasible by OD.
Anyway back to github.
Things I learned:
Creating a gh-pages branch and make it the default
Deleting your master branch
> hub clone repo
> cd !$
> git branch -D master
> git push origin :master
(assumes that you have already made another branch the default in the github -> settings->default branch place )
Adding a fork me image
Changing the home page/ description of the repository so as they both point to each other
(the service points to its underlying code page, the code base points to the service)
This last bit seems important. In some sense, just like in old open source, the license would actually require that every binary distribution of the code would provide a reference to a place where someone can easily get the source code for the binary.
Similarly, in the "open startup" world, every web app/web service, should be pointing to a place where someone, can fork a repository which ideally can be autodeployed (assuming that you provide config vars/urls/credentials to any external services it may use/need).
boxchareditor satisfies that small requirement
No comments:
Post a Comment