Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub
On Jun 4, 2013, at 3:18 PM, Răzvan Crainea raz...@opensips.org wrote: Hello all! After migrating all the OpenSIPS repositories from SourceForge to GitHub[1], the next step is to proceed with the tracker migration. We wrote down two options here: 1. Move all tickets (patches, feature requests, bugs) to the GitHub tracker. There are several problems with this approach: first is that we won't be able to preserve the submitter information, therefore it will no longer be updated about further updates (comments, fixes, etc). Moreover this has to be done manually, so it requires a lot of time and effort. 2. Keep all the tickets already opened on SourceForge, but open new tickets on GitHub. In this case you will no longer be able to open tickets (this will be blocked from SourceForge), but only to update the new ones (comment, close, etc). All new tickets will have to be opened on the GitHub tracker. We prefer the second option because it overcomes all the issues of the first one. The downside is that for a certain period of time we will have to follow two different tracks (both SourceForge and GitHub). However, we believe that this is an acceptable compromise. I think it's a good thing to do, this will probably also help in removing old tickets that have been lingering around for too long ;-) Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub
I would vote for the second option. It would take a bit to clean up but it would be cleaner and much less work. Usually when you move things, there are errors, mistakes, etc. It would be cleaner and less work with option 2. Regards, Ali On Tue, Jun 4, 2013 at 9:18 AM, Răzvan Crainea raz...@opensips.org wrote: Hello all! After migrating all the OpenSIPS repositories from SourceForge to GitHub[1], the next step is to proceed with the tracker migration. We wrote down two options here: 1. Move all tickets (patches, feature requests, bugs) to the GitHub tracker. There are several problems with this approach: first is that we won't be able to preserve the submitter information, therefore it will no longer be updated about further updates (comments, fixes, etc). Moreover this has to be done manually, so it requires a lot of time and effort. 2. Keep all the tickets already opened on SourceForge, but open new tickets on GitHub. In this case you will no longer be able to open tickets (this will be blocked from SourceForge), but only to update the new ones (comment, close, etc). All new tickets will have to be opened on the GitHub tracker. We prefer the second option because it overcomes all the issues of the first one. The downside is that for a certain period of time we will have to follow two different tracks (both SourceForge and GitHub). However, we believe that this is an acceptable compromise. Let us know what you think about this plan. Our intention is to do the migration process as smoothly as possible. So if you have a different idea, don't hesitate to share it with us! [1] http://www.opensips.org/About/**GitHub-Migrationhttp://www.opensips.org/About/GitHub-Migration Best regards, -- Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.**com http://www.opensips-solutions.com __**_ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-**bin/mailman/listinfo/develhttp://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] OpenSIPS Documentation re-Factory
Hello, The new documentation lay out is much much better and it is much easier to find the info you need faster. Thanks for the great work. I found a broken link though: Database schema Overall, well done!! Regards, Ali Pey On Mon, Jun 3, 2013 at 5:01 AM, Bogdan-Andrei Iancu bog...@opensips.orgwrote: ** Hi Pete, We avoided to purge the old URLs (actually we reconfigured all of them as redirects to the new corresponding pages) to avoid external broken links (there are external pages linking parts of the docs by the old pages). The Indexing of the functions is not yet addressed - we try to find a way to automatize the way the Index is generating. The 1.4 one is manually done, but this simply does not work on regular bases :(. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developerhttp://www.opensips-solutions.com On 06/02/2013 10:42 AM, Pete Kelly wrote: The main menus at least are much better than before. One of the problems with the old docs was that some of the links still pointed to v1.4 versions etc and you really had to click a lot of links to get through to the modules documentation. Now it's in a tree structure and contains the version at the end it's much cleaner. Is there a way to purge the old URLs so that any search results won't bring them up? The function index is very useful but it seems to be stuck on 1.4 still: http://www.opensips.org/Documentation/Script-FunctionsIdx-1-4 On 31 May 2013 13:43, Bogdan-Andrei Iancu bog...@opensips.org wrote: Hello, In the past weeks, we undertook a complex process of re-factoring the OpenSIPS documentation on the OpenSIPS web site. The main targets of this re-factoring were: - enhancing docs by covering new areas like installing, configuring, db managing - creating an OpenSIPS Manual with a logic flow to help you with understanding OpenSIPS from downloading to scripting. - re-structuring in a per-version approach (you can jump across versions for the same topic) and with a next and prev linking (to go through documentation in a more fluid way). The root of everything is http://opensips.org/Documentation/Manuals , please give it ride and let us know your opinion on this: - is it better than before ? - missing topics in manual ? - broken links ? Feeback is welcome and it we will make it matter ;) Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] OpenSIPS Documentation re-Factory
Hi Ali, Thanks for pointing that out - it supposed to work :(, but I will investigate the problem. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 06/04/2013 08:15 PM, Ali Pey wrote: Hello, The new documentation lay out is much much better and it is much easier to find the info you need faster. Thanks for the great work. I found a broken link though: Database schema Overall, well done!! Regards, Ali Pey On Mon, Jun 3, 2013 at 5:01 AM, Bogdan-Andrei Iancu bog...@opensips.org mailto:bog...@opensips.org wrote: Hi Pete, We avoided to purge the old URLs (actually we reconfigured all of them as redirects to the new corresponding pages) to avoid external broken links (there are external pages linking parts of the docs by the old pages). The Indexing of the functions is not yet addressed - we try to find a way to automatize the way the Index is generating. The 1.4 one is manually done, but this simply does not work on regular bases :(. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 06/02/2013 10:42 AM, Pete Kelly wrote: The main menus at least are much better than before. One of the problems with the old docs was that some of the links still pointed to v1.4 versions etc and you really had to click a lot of links to get through to the modules documentation. Now it's in a tree structure and contains the version at the end it's much cleaner. Is there a way to purge the old URLs so that any search results won't bring them up? The function index is very useful but it seems to be stuck on 1.4 still: http://www.opensips.org/Documentation/Script-FunctionsIdx-1-4 On 31 May 2013 13:43, Bogdan-Andrei Iancu bog...@opensips.org mailto:bog...@opensips.org wrote: Hello, In the past weeks, we undertook a complex process of re-factoring the OpenSIPS documentation on the OpenSIPS web site. The main targets of this re-factoring were: - enhancing docs by covering new areas like installing, configuring, db managing - creating an OpenSIPS Manual with a logic flow to help you with understanding OpenSIPS from downloading to scripting. - re-structuring in a per-version approach (you can jump across versions for the same topic) and with a next and prev linking (to go through documentation in a more fluid way). The root of everything is http://opensips.org/Documentation/Manuals , please give it ride and let us know your opinion on this: - is it better than before ? - missing topics in manual ? - broken links ? Feeback is welcome and it we will make it matter ;) Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org mailto:us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org mailto:us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org mailto:us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
