On 10/21/2011 09:07 AM, panyasan wrote: > We could have a qooxdoo-contrib account at github and make each contrib a > sub-repository, couldn't we? So they wouldn't be all lumped together. So for > each new contrib, the devs would create a repository and make the author a > committer. Plus, if one wants to have a contrib outside under their own > account, that would also be possible. I like the centralized approach > better, however, because it allows finding the stuff better and better > supports the contrib demobrowser. But we could have it both ways. Of course, > T would have to update the generator to support git - which, I assume, is > possible.
As I wrote in a comment to the weekly, and also referring to Greg's remarks, checking contribs out is probably too clumsy. It might be enough, for both projects using a particular contrib as well as building the contrib demo browser, if each project would be downloadable in its source form from an URL. (That's what already is happening with "contrib://" URLs in projects' configs). That would rid the generator and the contrib-browser building script of any need to fiddle with different VCS's. The changed semantics for the "contrib://" scheme would be that the generator, rather than constructing a download URL in a fixed manner, would query the contrib catalog to find out which download URL this particular contrib is using. The catalog will play a bigger role for finding contribs, as you might not be able to look into a single repo anymore to see them all. But this doesn't seem to be unusual, just look at similar efforts like the Python Package Index (pypi.python.org). I haven't heard enough about sub-repositories yet. How are they created? Can you clone them individually? T. ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
