kopete website

Pali Rohár pali.rohar at gmail.com
Tue Oct 14 21:42:23 UTC 2014


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/index.html
> > 
> > 2) Chat window style guide:
> > https://kopete.kde.org/chatwindowstyleguide/index.html
> > 
> > 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
-------------- 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/20141014/44c203b7/attachment.sig>


More information about the kde-www mailing list