kopete website

Wed Oct 22 22:22:03 UTC 2014

On Thursday 23 October 2014 00:17:11 Jeremy Whiting wrote:
> Pali,
> 
> On Wed, Oct 22, 2014 at 4:07 PM, Pali Rohár 
<pali.rohar at gmail.com> wrote:
> > On Wednesday 22 October 2014 23:44:41 Jeremy Whiting wrote:
> >> Pali,
> >> 
> >> Here's my plan,
> >> 
> >> 1. I'll coordinate with ben about placing the sound files,
> >> and these two kopetemessage.xsd and oscarversions.xml on
> >> either files.kde.org or download.kde.org.
> >> 2. Then I'll ask sysadmin to make apache rewrites from the
> >> old urls to the new ones.
> >> 3. Then I'll add the faqs from the website to the .docbook
> >> faq section in kopete's sources.
> >> 4. Then ask sysadmin to make kopete.kde.org an apache
> >> rewrite to the userbase page.
> >> 5. Then finally remove kopete content from svn.
> >> 
> >> Sound like a good plan? Did I miss any steps?
> > 
> > Sounds good. Then please document somewhere how to update
> > oscarversions.xml file in future.
> > 
> > Anyway in svn is another stuff and I have no idea if is
> > somewhere else...
> > 
> > * chatwindowstyleguide
> 
> I think this is here
> https://docs.kde.org/stable/en/kdenetwork/kopete/chatwindowsty
> leguide.html no ?
> 
> > * emoticons docbook
> 
> I don't see that on the website, where are you seeing that?
> 
> > * jabber extensions in protocols
> 
> Is this
> https://docs.kde.org/stable/en/kdenetwork/kopete/jabber-plugi
> ns.html what you mean?
> 

All folders are in svn: 
http://websvn.kde.org/trunk/www/sites/kopete/

> >> BR,
> >> Jeremy
> >> 
> >> On Wed, Oct 15, 2014 at 4:20 PM, Ben Cooksley
> > 
> > <bcooksley at kde.org> wrote:
> >> > On Thu, Oct 16, 2014 at 3:28 AM, Pali Rohár
> > 
> > <pali.rohar at gmail.com> wrote:
> >> >> Hello,
> >> > 
> >> > Hi Pali,
> > 
> > Hello, why I did not received this email??
> 
> I guess Ben forgot to cc you on that one.
> 

Ah, ok. I'm not in kde-www list, so CC me.

> >> >> first one important thing:
> >> >> 
> >> >> kopete icq/aim protocol is downloading this file at
> >> >> kopete startup: http://kopete.kde.org/oscarversions.xml
> >> >> 
> >> >> That file contains version information needed for icq
> >> >> client to successfully authenticate with icq server. All
> >> >> these data are also in icq source code. But in past
> >> >> those data was changed and downloading data from
> >> >> kopete.kde.org cause that older kopete versions was
> >> >> able to connect again. Data from website override
> >> >> hardcoded data in kopete source code.
> >> >> 
> >> >> And I updated data from website to icq source code only
> >> >> for v4.14 release. So if you cut down that url all
> >> >> kopete versions before v4.14 stop working.
> >> >> 
> >> >> So after updating kopete.kde.org website, please make
> >> >> sure that above url will still work and please write me
> >> >> how to change that file in future (so when something
> >> >> will be broken I can update it).
> >> >> 
> >> >> File is downloaded with KIO::get(url) so if you are
> >> >> going to do some magic (redirect/etc) please make sure
> >> >> that it will not be broken.
> >> > 
> >> > KIO is intelligent enough to handle redirects - we
> >> > enabled mandatory SSL for kopete.kde.org a while back,
> >> > and based on your commentary here the file is still
> >> > being retrieved without problems.
> > 
> > Ok. Test case for Kopete is:
> > 
> > 1) install older version of Kopete (e.g. 4.13)
> > 2) clean user ~/.kde directory (so kopete config file with
> > cached info from oscarversions.xml will not be available)
> > 3) try to login into ICQ and AIM account
> 
> Ok, once the redirects are in place I'll e-mail you and you
> can test. I don't have any icq or aim accounts myself.
> 

Ok. I can test ICQ account.

> >> >> In kopete source code I see reference to another file:
> >> >> http://kopete.kde.org/files/kopetemessage.xsd
> >> >> 
> >> >> But I do not have idea how that file is used.
> >> > 
> >> > Likely used to validate the format of the XML data which
> >> > Kopete uses at some point. Perhaps this is how it stores
> >> > conversations on disk?
> > 
> > "This is the XSD schema of a Kopete message in XML form.
> > This is both the format that the XSL stylesheets will
> > expect, as well as the format that results from saving the
> > chatwindow contents."
> > 
> > "This is *not* the same as the format of the history
> > plugin."
> > 
> >> >> Next, I did nothing with docbook. Basically I do not
> >> >> have time for updating all those user guide books, etc
> >> >> and also I'm not very interesting in writing such text.
> >> > 
> >> > Thanks,
> >> > Ben
> >> > 
> >> >> On Wednesday 15 October 2014 00:09:13 Jeremy Whiting 
wrote:
> >> >>> Pali,
> >> >>> 
> >> >>> Have you ever done anything with the kopete docbook ?
> >> >>> If so would you mind adding the faqs from
> >> >>> https://kopete.kde.org/faq.php to it? I've added links
> >> >>> to the userbase page pointing to the docbook copy of
> >> >>> the pipes and chat style guides on
> >> >>> https://docs.kde.org/development/en/kdenetwork/kopete/c
> >> >>> hat wind owstyleguide.html so those should be taken
> >> >>> care of. I also added a link to KDETalk below those on
> >> >>> userbase. I'll ask about where to put the sound files
> >> >>> for the pronunciation of kopete in english and spanish
> >> >>> from the kopete.kde.org site.
> >> >>> 
> >> >>> thanks,
> >> >>> Jeremy
> >> >>> 
> >> >>> On Tue, Oct 14, 2014 at 3:44 PM, Jeremy Whiting
> >> >> 
> >> >> <jpwhiting at kde.org> wrote:
> >> >>> > Exactly.
> >> >>> > 
> >> >>> > On Tue, Oct 14, 2014 at 3:42 PM, Pali Rohár
> >> >> 
> >> >> <pali.rohar at gmail.com> wrote:
> >> >>> >> Sounds good. Also editing userbase wiki page should
> >> >>> >> be simpler then editing something in svn...
> >> >>> >> 
> >> >>> >> On Tuesday 14 October 2014 23:31:56 Jeremy Whiting
> > 
> > wrote:
> >> >>> >>> Pali,
> >> >>> >>> 
> >> >>> >>> Thanks for the information on what's useful in the
> >> >>> >>> existing site. I can do like we did for
> >> >>> >>> dolphin.kde.org. I'll first move the important
> >> >>> >>> content from those three pages you pointed out into
> >> >>> >>> userbase, then ask kopete.kde.org to be a rewrite
> >> >>> >>> to userbase kopete page. then remove this old
> >> >>> >>> content from svn completely. Does that sound like
> >> >>> >>> a good idea? I especially like the idea of
> >> >>> >>> userbase because the content can be easily
> >> >>> >>> translated by end-user's into their own language.
> >> >>> >>> 
> >> >>> >>> BR,
> >> >>> >>> Jeremy
> >> >>> >>> 
> >> >>> >>> On Tue, Oct 14, 2014 at 3:20 PM, Pali Rohár
> >> >>> >> 
> >> >>> >> <pali.rohar at gmail.com> wrote:
> >> >>> >>> > On Tuesday 14 October 2014 23:07:04 you wrote:
> >> >>> >>> >> Pali,
> >> >>> >>> >> 
> >> >>> >>> >> Long time no see. How's it going? I see you've
> >> >>> >>> >> been fixing bugs and such in kopete lately and
> >> >>> >>> >> thought I'd shoot you an e-mail. I've been
> >> >>> >>> >> cleaning up svn websites folder migrating sites
> >> >>> >>> >> to git repos and such and kopete is one of the
> >> >>> >>> >> remaining few sites there.
> >> >>> >>> >> http://websvn.kde.org/trunk/www/sites/ and it's
> >> >>> >>> >> also terribly out of date. I wondered which of
> >> >>> >>> >> these options you'd prefer:
> >> >>> >>> >> 
> >> >>> >>> >> 1. Close kopete.kde.org completely (user's can
> >> >>> >>> >> still find information about it from the
> >> >>> >>> >> userbase and www.kde.org application pages) 2.
> >> >>> >>> >> Keep kopete.kde.org and redirect it to the
> >> >>> >>> >> kopete userbase page or www.kde.org kopete
> >> >>> >>> >> application page.
> >> >>> >>> >> 3. Migrate kopete web content to git and update
> >> >>> >>> >> it to reflect kopete current status etc.
> >> >>> >>> >> 
> >> >>> >>> >> I can help with any of these but wanted to ask
> >> >>> >>> >> which you prefer. I wont be updating the site
> >> >>> >>> >> content itself in anyway, you can do that or
> >> >>> >>> >> find someone else to do it, but I can do the
> >> >>> >>> >> migration. Let me know what you think.
> >> >>> >>> >> 
> >> >>> >>> >> BR,
> >> >>> >>> >> Jeremy
> >> >>> >>> > 
> >> >>> >>> > Hello,
> >> >>> >>> > 
> >> >>> >>> > I have never touched kopete website because I did
> >> >>> >>> > not know how and also I did not have time for it.
> >> >>> >>> > Even I did not know what website is in svn...
> >> >>> >>> > 
> >> >>> >>> > In last years I fixed lot of bugs in kopete and
> >> >>> >>> > implemented some new options. You can see in
> >> >>> >>> > kopete git that I regularly pushing changes. But
> >> >>> >>> > I really do not have time for maintaining web
> >> >>> >>> > site or something similar.
> >> >>> >>> > 
> >> >>> >>> > So I think the best would be to keep
> >> >>> >>> > kopete.kde.org DNS record and redirect webpage
> >> >>> >>> > to userbase.
> >> >>> >>> > 
> >> >>> >>> > I think there are 3 important things on
> >> >>> >>> > kopete.kde.org webpage:
> >> >>> >>> > 
> >> >>> >>> > 1) Pipes Plugin guide:
> >> >>> >>> > https://kopete.kde.org/pipesimplementationguide/i
> >> >>> >>> > nde x.ht ml
> >> >>> >>> > 
> >> >>> >>> > 2) Chat window style guide:
> >> >>> >>> > https://kopete.kde.org/chatwindowstyleguide/index
> >> >>> >>> > .ht ml
> >> >>> >>> > 
> >> >>> >>> > 3) Info about existence of KDE XMPP server:
> >> >>> >>> > https://kdetalk.net/
> >> >>> >>> > 
> >> >>> >>> > I do not know if these two guides are somewhere
> >> >>> >>> > else so this could be backup (or link from
> >> >>> >>> > userbase?).
> >> >>> >>> > 
> >> >>> >>> > --
> >> >>> >>> > Pali Rohár
> >> >>> >>> > pali.rohar at gmail.com
> >> >>> >> 
> >> >>> >> --
> >> >>> >> Pali Rohár
> >> >>> >> pali.rohar at gmail.com
> >> >> 
> >> >> --
> >> >> Pali Rohár
> >> >> pali.rohar at gmail.com
> >> >> 
> >> >> _______________________________________________
> >> >> kde-www mailing list
> >> >> kde-www at kde.org
> >> >> https://mail.kde.org/mailman/listinfo/kde-www
> > 
> > --
> > Pali Rohár
> > pali.rohar at gmail.com
> 
> BR,
> Jeremy

-- 
Pali Rohár
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-www/attachments/20141023/4c462edd/attachment-0001.sig>