Hi,
Documentation is the authorative source. It is maintained and checked for each
Qt release. We should make sure the platform notes are correct and complete.
Misleading information in wiki should be deleted or marked as deprecated.
Similar activity has been done to other pages, sometimes we may even want to
move items from the wiki to docs. It is fine to have wiki to support, but there
is high risk of wiki content to become outdated.
Yours,
Tuukka
On 20/09/2019, 12.03, "Development on behalf of Giuseppe D'Angelo via
Development" <development-boun...@qt-project.org on behalf of
development@qt-project.org> wrote:
Il 20/09/19 07:53, Tuukka Turunen ha scritto:
> Or remove the wiki entry and make sure platform notes in documentation
are in shape?
>
> No need for duplicated info on these basic items.
It's a bigger problem -- the *same* wiki is used for official
information (e.g. releasing info; coding guidelines; security policies)
as well as for unofficial, community-driven content. Nobody knows the
official status of any individual page just by looking at it.
So now there's information on the wiki AND in the docs about Qt on
INTEGRITY, they both appear on Google search results, and of course
they're in contradiction with each other (wiki says that Qt on INTEGRITY
is community-driven, docs say it's officially supported; wiki does a
shared build, docs say only static builds work).
My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
