Hi, Ok, good news that the devel.opensaf.org is under easy control. We should probably disable the ticket system of trac ASAP, at least block for opening new tickets (if it's possible), some kind of read only mode, did you guys actually triage the bugs and moved just the relevant ones, or there's need to save the tickets as well? For the wiki there's probably a way to get a dump of trac database and import somewhere in the sourceforge wiki, just guessing here, tho. The mailing list archives I never touched, but pipermail already serves the archives as html, so it's probably easy enough as well. Of course this would need direct access to the system, I'll take a look over the weekend at the alternatives for doing all that, and then hopefully someone with full access can do it, or I can then request access for you.
Regards, Guilherme Moro On 29 April 2014 18:11, Jonas Arndt <[email protected]> wrote: > > On 04/29/2014 06:55 AM, Guilherme Moro wrote: >> >> Hi, >> >> The project was completely migrated to Sourceforge, is this a valid >> assumption? >> >> if you go to http://www.opensaf.org/page/14944~220835/Projects >> They are still referencing http://devel.opensaf.org/hg/opensaf as the >> main check-in point >> >> http://devel.opensaf.org/ have some other information that seems >> outdated as well >> >> So, for now we seem to have duplicated info scattered around the old >> trac system and the new home of the project (sourceforge). And most of >> the google search you do will point to outdated information. >> >> I know the tickets were migrated already, but we should start >> deactivate the old systems gradually, and put everything in just one >> place. >> >> I'm willing to help with that, so who can guide me through whatever >> got decided regarding this migration, and more importantly, who >> decides this stuff anyway? ;) >> >> Regards, >> >> Guilherme Moro >> >> > The migration is going slowly and we should indeed clear up some links and > language. The fact is that we still don't necessarily want to fully retire > the old server as the wiki has a lot of good information. It should be made > clear that you can't use it to create new tickets though. We should probably > mark the old wiki with big red letters "Dated Information" or something > similar. We have a session in a meeting tomorrow to talk about it. > > Thanks for your offer to help out. We do fully control the devel.opensaf.org > website/wiki and we might very well pick you up on the offer to help out > there. The www.opensaf.org we will need to request changes to (on the todo > list after tomorrow's meeting). Who decides? Well we have a small group of > people that are part of the technical leadership council (TLC) and we meet > biweekly to discuss stuff like this (and other stuff). It doesn't mean we > take all the decision. Feedback from the users/devel list is very important. > > Cheers, > > // Jonas > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. Get > unparalleled scalability from the best Selenium testing platform available. > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
