I'd like to also point out that the SSL certificate is not valid for the host name wiki.xmpp.org, thus leading to browser certificate errors.
Regards On Mon, Sep 1, 2014 at 4:06 PM, edhelas <[email protected]> wrote: > Hi, > > I'm currently looking at our official Wiki (https://wiki.xmpp.org/) and > there's a couple of things that need to be cleaned. > > On the main page, the XMPP technologies panel : > - The Client/Server list in https://wiki.xmpp.org/web/Tech_pages/BOSH need > to be updated (last change 2010) > - Same for the Jingle page https://wiki.xmpp.org/web/Tech_pages/Jingle (last > change 2010) > - Same for the Pubsub page https://wiki.xmpp.org/web/Tech_pages/PubSub (last > change 2010) > > - We can delete the https://wiki.xmpp.org/web/Tech_pages/Reliability page > (empty, never changed) > - Same for https://wiki.xmpp.org/web/Tech_pages/Privacy > - Same for https://wiki.xmpp.org/web/Tech_pages/Admin > - Same for https://wiki.xmpp.org/web/Tech_pages/Disco > > - The page https://wiki.xmpp.org/web/XMPP_URIs need to be seriously updated > or deleted (last change 2010) > > Furthermore I really think that we need to create several pages like > https://wiki.xmpp.org/web/PubSubIssues to list all the issues and we find in > the related XEP. On the mailing list we easily loose the emails that talked > about theses issues in our history. > > By listing all all of them with a clear explanation and where exactly it > appear in the XEP we will be able to really track them and fix them during > the meetings :) > > Or maybe we can use a bugtracker for that ? > > Also, it would be nice to have a system that give us a clear overview of > which client and server implement each XEP. I know that the work is huge but > maybe with tools that use the Disco/Caps system we will be able to fill > theses informations easily. > And because an implementation status is not a boolean we have to list all > the stuffs that are not well implemented in the clients/server with (if > possible) a link to their bugtracker. > > All theses stuffs will help us to have a clearer idea of where we are and > what we have to do for the the future. > > Regards, > > Jaussoin Timothée aka edhelas -- Daniele
