Hi Peter, I see you are very eager to help (thanks for that), but I also need to adjust my way of working and scripts I build around that, so please be patient. I think it is good if I do the migration myself and can check and validate that everything is working (and put in my latest set of changes).
I check out your tip of turning doxygen on github into an organisation. Regards, Dimitri On Apr 27, 2013, at 2:32 , Peter Morgan <[email protected]> wrote: > Am looking more into this, but again dont want to waste time.. > > But.. if the move to github.. (or any git hosting).. in gitlab... > then > we need to migrate.. > I can help with that as done this before.. once on a project with 5 devs.. > ie svn to git migration.. > > http://git-scm.com/book/en/Git-and-Other-Systems-Migrating-to-Git > > ########### > Problems > ##########'# > Authors who have identities.. > but there are ways around this.. but its complex.. and easier with new > identities and matching later.. > > Maintaining backward svn and sf.net > We can push that another way, by making every commit to master, > thereby "commit" to trunk as sf.net if needed... > I am still an advocate for svn as its don't download the "whole history, > instead just changes" and this is good downstream.. > So we can make it mix both ways..later... > > Do make it automated.. though.. > > We need to use a build farm.. eg Jenkins > > RedHat are still testing their openshift platform > and got a version running here > https://doxygen-pedromorgan.rhcloud.com > login=doxygen > pass=h2o > > and thats a couple of job that poll the repos, > pull source > check for changes > and recompile the source on a remote machine.. which is mine atmo > but any app can be one.. > > We also build rpm,s etc same way > and update website.. > > So that is the way to go imho, and the way a few other projects go.. > > Also..for dimirti.. > with github.com.. > u can trun doxygen from an user into an "organisation". .which is a good > idea... > This means u can then add admins etc and allow others to manage parts etc.. > > anyway.. > Will start a svn to git migration id u give the "nod" to go ahead.. > as I got the stuff on machine and been there done that so it should be ok.. > > Pete > > > On 26 April 2013 23:58, Peter Morgan <[email protected]> wrote: > Hi all, > > This is following on from a previous discussion about git... > > I see that > https://github.com/doxygen > is there and its dimitri etc.. > > But also a search for doxygen shows so many mirrors.. etc etc all outta date.. > > So is there a possibility to at least create the github.com version as > official.. > so we can all fork.. > > There are tools to import and if help is required then am around 2 assist ... > But generally speakin i would expect a > "master" - branch which is stable > "next" - which is the next dev flavour (like trunk/) > > and all the tags etc should import with > git svn checkout.. > > There are so many clones though... we'd save github/aws a lot of disk > space..... maybe > https://github.com/search?q=doxygen&ref=cmdform > > regards > Pete > > > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Doxygen-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/doxygen-develop
