On Sun, Dec 12, 2010 at 07:19, <no-re...@cfengine.com> wrote: > Forum: Cfengine Help > Subject: Once more unto the code bridge: repository > Author: mark > Link to topic: https://cfengine.com/forum/read.php?3,19721,19721#msg-19721 > > Reviving this discussion of a forum for code snippets once again, I have been > thinking about the various options. I'm afraid I wasn't very impressed with > github (found it quite hard to navigate) and see the wood for the trees. I > also didn't get a lot out of reading about Plone. I think the repository > should be hosted by Cfengine so that it is easy to find and has a sense of > `stamp of approval'. > > I don't feel like I have an answer, but I am wondering about the following: > > * Simply using SVN to keep versioned code. Login/authentication based on a > proper engine room registration account. > * Adding an interface that allows indexing, commentary and knowledge > integration using Cfengine's own knowledge map and some PHP magic. > > What I like about this is the versioning that SVN and ViewVC add. We could > put some resources into this in the new year if people think it would be a > good solution.
If you do got the SVN route, I'd like ot mention websvn as a viewing tool (http://www.websvn.info/). I use it at $dayjob, and find it a lot nicer to use, simpler to setup (in our environment) and faster than viewsvn. While SVN (et al) is nice for code, it seems to be less useful for non-code documentation and explanations. Various notes about how to best organized bundles and files come to mind as an example. Having everything backed by version control is nice, but putting everything one more "level down" inside a file (instead of just displayed as a webpage) makes the information harder to find. -- Jesse Becker _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
