Re: [Qgis-community-team] Documentation Split
On 13/03/2019 08.01, matteo wrote: > Hi guys, > > I also agree to split the main repo in 2 one (static and dynamic). > > Don't know the drawbacks (transifex, redirecting, and all the other > stuff... ping Richard). > > But yes it should help to maintain the structure cleaner. Agreed. But let's wait till we have some clearer sight on some experiments different people currently doing: - Matteo: direct connection between github <-> transifex - Me: vanilla sphinx + readthedocs theme - Will: screenshot machinery ? - All: finalize 3.4 branch (make translatable) Regards, Richard Duivenvoorde ___ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. Qgis-community-team@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-community-team
Re: [Qgis-community-team] Documentation Split
Hi guys, I also agree to split the main repo in 2 one (static and dynamic). Don't know the drawbacks (transifex, redirecting, and all the other stuff... ping Richard). But yes it should help to maintain the structure cleaner. Best Matteo ___ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. Qgis-community-team@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-community-team
Re: [Qgis-community-team] Documentation Split
Hi Harrissou, DelazJ escreveu no dia terça, 12/03/2019 às 14:35: > > My position would be like yours: separate version-based docs from the > "static" ones, we can move them to the static repo (aka website) but it > wonder if it's technically possible and wouldn't make sense to keep them > next to the documentation (from the end user point of view). > > Definitly. I mean, it makes sense to keep them in the same docs.qgis.org page, but they shouldn't be under any specific version of QGIS, so maybe we need to come up with a new structure for it. Cheers, Alex Regards, > Harrissou > > If I recall, the kick-off for this discussion started because the >> QGIS-Documentation repository includes docs that are tied to a particular >> version of QGIS (user manual, pycookbook, training manual) and need to be >> released in every LTR, and "static" or independent pages like the Developer >> guide or Documentation Guidelines, that can/should be updated whenever we >> want. >> >> I would like to discuss this splitting: How many repositories, and which? >> Any opinions? >> >> Personally, I don't think we need to split every document in one repo, >> has that will only lead to more work managing it. Could we just move the >> "static" content to the website? That is: >> >> QGIS-Documentation >> --- >> >> pyqgis_developer_cookbook >> training_manual >> user_manual >> >> Website >> -- >> developers_guide >> documentation_guidelines >> gentle_gis_introduction >> >> >> Best regards, >> >> Alexandre Neto >> -- >> Alexandre Neto >> - >> @AlexNetoGeo >> http://sigsemgrilhetas.wordpress.com >> http://gisunchained.wordpress.com >> > ___ >> Qgis-community-team mailing list for organizing community resources such >> as documentation, translation etc.. >> Qgis-community-team@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-community-team > > -- Alexandre Neto - @AlexNetoGeo http://sigsemgrilhetas.wordpress.com http://gisunchained.wordpress.com ___ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. Qgis-community-team@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-community-team
Re: [Qgis-community-team] Documentation Split
Hi Alex, Le mar. 12 mars 2019 à 13:39, Alexandre Neto a écrit : > Hi all, > > At the hackfest, and even before that, we have been talking about > splitting the documentation in more that one repository. > > Thanks for raising this. Indeed, a long standing question: http://osgeo-org.1560.x6.nabble.com/Qgis-community-team-Management-of-release-independent-documents-td5318107.html My position would be like yours: separate version-based docs from the "static" ones, we can move them to the static repo (aka website) but it wonder if it's technically possible and wouldn't make sense to keep them next to the documentation (from the end user point of view). Regards, Harrissou If I recall, the kick-off for this discussion started because the > QGIS-Documentation repository includes docs that are tied to a particular > version of QGIS (user manual, pycookbook, training manual) and need to be > released in every LTR, and "static" or independent pages like the Developer > guide or Documentation Guidelines, that can/should be updated whenever we > want. > > I would like to discuss this splitting: How many repositories, and which? > Any opinions? > > Personally, I don't think we need to split every document in one repo, has > that will only lead to more work managing it. Could we just move the > "static" content to the website? That is: > > QGIS-Documentation > --- > > pyqgis_developer_cookbook > training_manual > user_manual > > Website > -- > developers_guide > documentation_guidelines > gentle_gis_introduction > > > Best regards, > > Alexandre Neto > -- > Alexandre Neto > - > @AlexNetoGeo > http://sigsemgrilhetas.wordpress.com > http://gisunchained.wordpress.com > ___ > Qgis-community-team mailing list for organizing community resources such > as documentation, translation etc.. > Qgis-community-team@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-community-team ___ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. Qgis-community-team@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-community-team
[Qgis-community-team] Documentation Split
Hi all, At the hackfest, and even before that, we have been talking about splitting the documentation in more that one repository. If I recall, the kick-off for this discussion started because the QGIS-Documentation repository includes docs that are tied to a particular version of QGIS (user manual, pycookbook, training manual) and need to be released in every LTR, and "static" or independent pages like the Developer guide or Documentation Guidelines, that can/should be updated whenever we want. I would like to discuss this splitting: How many repositories, and which? Any opinions? Personally, I don't think we need to split every document in one repo, has that will only lead to more work managing it. Could we just move the "static" content to the website? That is: QGIS-Documentation --- pyqgis_developer_cookbook training_manual user_manual Website -- developers_guide documentation_guidelines gentle_gis_introduction Best regards, Alexandre Neto -- Alexandre Neto - @AlexNetoGeo http://sigsemgrilhetas.wordpress.com http://gisunchained.wordpress.com ___ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. Qgis-community-team@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-community-team
