Hi Gerrit,
Gerrit Voß wrote:
>
> I'll have a look. But quickly just something else. I'm tempted
> to move my trees to git-hub (staring with OpenSG.svn.git) so you (or
> anybody) can write to them to. So we don't have to send patches around
> so much, especially the ones that add or move around many files tend to
> be painful.
Is there an easy way to mirror the svn to github? Or would it make more sense
to
do it the other way around, i.e. we use git at the core and only sync master
changes to svn? I would like to avoid having to manually sync the two repos, as
it can be error-prone. I guess we could write a little script that watches the
trunk on github and mirrors it into svn, assuming github has some sort of
notification system.
Related notes: I've been looking more into Google Code. It is somewhat limited,
i.e. the wiki has no hierarchy, only one level, no macros, no attachments and
no
image display. The fact that it lives in the repository makes up for some of
those, as we should be able to extend things with scripting (you can trigger
HTTP request on commits) or Gadgets (not sure how those will work exactly, but
I
think we can figure it out). I have a rough script to transfer the Trac Wiki to
Google Wiki, and I think I can finish that fairly quickly once I have a project
to play with. I found a project that can create GWiki code from doxygen XML, so
getting docs in the wiki should be fairly easy.
I set up a dashboard at http://reiners.cacs.louisiana.edu/OpenSG_Dashboard. I
haven't set up an actual dailybuild (installing new machine right now), but
that
should go up soon.
Open issues:
- I have not started on Issue migration, that one might be harder as I think
there is no API for creating issues.
- I'm not sure how to do a dailybuild release, I haven't seen a way to do that
in CDash. Did I miss it or do they really not have downloads of nightly build
releases? Putting them on GC is a problem, as they don't let you delete files
and the dailybuilds would use up too much space over time.
- Size limits. GC has a default limit of 1G for the repo and 100MB for
downloadable files. I don't think we have > 100MB packages any more since SGI
is
gone, so that should be fine. However, our doxygen HTML version is more than a
gig already, so hosting that would kill the repo, especially if we try to
update
it. I'll have to see how big it is in GWiki, but given that the bulk is images
it probably won't make a big difference. Given that it can be only HTML I don't
have a problem hosting it somewhere else though. There is also a script that
converts GWiki to HTML, so we can take stuff from the /wiki into the doxygen
with a little scripting.
So overall I think we're good to go with moving.
Comments?
Dirk
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
