Re: Outdated application pages at kde.org/applications
2011/3/14 Jaroslaw Staniek : > Hi, > (cc'd to kde-www) > > Just noticed [1] is outdated regarding app names and information. I > plan to handle changes at least the outdated information for Kexi. > > But what I am not sure about is possible duplication: do we need > kde.org/applications when we have userbase? > It is hard to maintain two places. > > That's not all. There's also a clash with community.kde.org. For > example Dolphin has outdated development page [2]. > How it would be fixed? Maybe by adding just links to appropriate > userbase/community sites? > > [1] http://www.kde.org/applications/office/ > [2] http://www.kde.org/applications/system/dolphin/development > > -- > regards / pozdrawiam, Jaroslaw Staniek > http://www.linkedin.com/in/jstaniek > Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) > KDE Software Development Platform on MS Windows (windows.kde.org) > ___ The initial idea of the app pages was to have a quick overview of all relevant facts for a given application and make it easily maintainable, as those pages are generated from plain json files, see e.g. http://websvn.kde.org/trunk/www/sites/www/applications/apps/dolphin.json?view=markup for the dolphin file. Even more, it was intended to automate the task of updating those information. Sadly, it never got this far (yet?). Of course, open for suggestions to improve this situation. Cheerio, Ingo ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Outdated application pages at kde.org/applications
2011/3/15 Jaroslaw Staniek : > On 15 March 2011 08:40, Ingo Malchow wrote: >> 2011/3/14 Jaroslaw Staniek : >>> Hi, >>> (cc'd to kde-www) >>> >>> Just noticed [1] is outdated regarding app names and information. I >>> plan to handle changes at least the outdated information for Kexi. >>> >>> But what I am not sure about is possible duplication: do we need >>> kde.org/applications when we have userbase? >>> It is hard to maintain two places. >>> >>> That's not all. There's also a clash with community.kde.org. For >>> example Dolphin has outdated development page [2]. >>> How it would be fixed? Maybe by adding just links to appropriate >>> userbase/community sites? >>> >>> [1] http://www.kde.org/applications/office/ >>> [2] http://www.kde.org/applications/system/dolphin/development >>> >>> -- >>> regards / pozdrawiam, Jaroslaw Staniek >>> http://www.linkedin.com/in/jstaniek >>> Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) >>> KDE Software Development Platform on MS Windows (windows.kde.org) >>> ___ >> >> The initial idea of the app pages was to have a quick overview of all >> relevant facts for a given application and make it easily >> maintainable, as those pages are generated from plain json files, see >> e.g. >> http://websvn.kde.org/trunk/www/sites/www/applications/apps/dolphin.json?view=markup >> for the dolphin file. >> >> Even more, it was intended to automate the task of updating those >> information. Sadly, it never got this far (yet?). Of course, open for >> suggestions to improve this situation. > > So maybe what we need is either > 1. idea how to enable sharing between userbase and kde.org, or > 2. make the kde.org description very light/generic in terms of content > so we rarely have to update them, i.e. no versions, no links depending > on versions, etc. > > I do not see 1. as very valuable or something easy. > > -- > regards / pozdrawiam, Jaroslaw Staniek > http://www.linkedin.com/in/jstaniek > Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) > KDE Software Development Platform on MS Windows (windows.kde.org) > Indeed, and 2. is already (mostly) the current way it works. Some adjustments are of course needed, like support for git locations. We can't reduce maintenance to zero, i guess :) And right now i remembered some plans we had when we wrote the new app system. We wanted to make it possible to have the corresponding json file in the app's own repo. So app devs don't need to bother with locations. That way the work what needs to be done is 1. app dev updates the json file with current information 2. web team takes care of setting up the location of that json file in our website system 3. a possible cronjob reads from that repo location only that file and makes it show on the app pages That way the devs and webteam can take care of what is relevant to them. How does that sound? Would need some rewrite first, sure. ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Outdated application pages at kde.org/applications
2011/3/15 Emil Sedgh : >> And right now i remembered some plans we had when we wrote the new app >> system. We wanted to make it possible to have the corresponding json >> file in the app's own repo. So app devs don't need to bother with >> locations. That way the work what needs to be done is >> >> 1. app dev updates the json file with current information >> 2. web team takes care of setting up the location of that json file in >> our website system >> 3. a possible cronjob reads from that repo location only that file and >> makes it show on the app pages > > Isnt most of that already possible by projects.k.o projects list? Projects > have name's, description, categorization and even icon there. > It is, even though a collection of all the links about an app or screenshots are missing. Something like the entry point for plain users. ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Outdated application pages at kde.org/applications
2011/3/15 Albert Astals Cid : > A Dimarts, 15 de març de 2011, Ingo Malchow va escriure: >> 2011/3/15 Jaroslaw Staniek : >> > On 15 March 2011 08:40, Ingo Malchow wrote: >> >> 2011/3/14 Jaroslaw Staniek : >> >>> Hi, >> >>> (cc'd to kde-www) >> >>> >> >>> Just noticed [1] is outdated regarding app names and information. I >> >>> plan to handle changes at least the outdated information for Kexi. >> >>> >> >>> But what I am not sure about is possible duplication: do we need >> >>> kde.org/applications when we have userbase? >> >>> It is hard to maintain two places. >> >>> >> >>> That's not all. There's also a clash with community.kde.org. For >> >>> example Dolphin has outdated development page [2]. >> >>> How it would be fixed? Maybe by adding just links to appropriate >> >>> userbase/community sites? >> >>> >> >>> [1] http://www.kde.org/applications/office/ >> >>> [2] http://www.kde.org/applications/system/dolphin/development >> >>> >> >>> -- >> >>> regards / pozdrawiam, Jaroslaw Staniek >> >>> http://www.linkedin.com/in/jstaniek >> >>> Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) >> >>> KDE Software Development Platform on MS Windows (windows.kde.org) >> >>> ___ >> >> >> >> The initial idea of the app pages was to have a quick overview of all >> >> relevant facts for a given application and make it easily >> >> maintainable, as those pages are generated from plain json files, see >> >> e.g. >> >> http://websvn.kde.org/trunk/www/sites/www/applications/apps/dolphin.jso >> >> n?view=markup for the dolphin file. >> >> >> >> Even more, it was intended to automate the task of updating those >> >> information. Sadly, it never got this far (yet?). Of course, open for >> >> suggestions to improve this situation. >> > >> > So maybe what we need is either >> > 1. idea how to enable sharing between userbase and kde.org, or >> > 2. make the kde.org description very light/generic in terms of content >> > so we rarely have to update them, i.e. no versions, no links depending >> > on versions, etc. >> > >> > I do not see 1. as very valuable or something easy. >> > >> > -- >> > regards / pozdrawiam, Jaroslaw Staniek >> > http://www.linkedin.com/in/jstaniek >> > Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) >> > KDE Software Development Platform on MS Windows (windows.kde.org) >> >> Indeed, and 2. is already (mostly) the current way it works. Some >> adjustments are of course needed, like support for git locations. > > AFAIR I added a hack for git locations some time ago. > > Albert Indeed, wasn't that sure about it anymore, thanks for the reminder. ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Please update http://kde.org/applications/office/
2012/5/7 Jaroslaw Staniek : > On 7 May 2012 17:23, Cyrille Berger Skott wrote: >> On Monday 07 May 2012, Jaroslaw Staniek wrote: >>> I feel there's simple reason why these pages are out of date and even >>> if fixed soon, will be get outdated quickly again. Redundant vs >>> userbase. Let's fix this problem somehow first, e.g. by only having >>> minimal information at kde.org. E.g. I wouldn't like to maintain >>> feature list of Kexi on userbase and >>> http://kde.org/applications/office/kexi/. >> You should discuss that issue with the webteam. > > OK CC'd kde-www - guys please explain what's the idea behind copying > userbase now. Cyrille does get it quite good below. > >> Right now, we just want to be >> put in the best light on kde.org (or any light). But my guess is that the >> kde.org page is supposed to be minimal and changes barely, meaning the list >> of >> features should be minimal and very broad, while the userbase page would have >> a more detailed version. Exactly. The benefit of having a detailed version on userbase is rather simple: there is a great ... userbase which updates content regularly. At least more than on some json file or in closed down websites. ;) > > For me, Userbase is the minimal page,while krita.org/kexi-project.org > are default pages. Same for KDevelop, and any larger project that has > its own page. Other projects can treat userbase as the start page but > this is case-by-case. That is of course up to the project to decide what is a valuable information resource. The idea was once (some years back) raised to have a central place for information about any KDE app. And be it only a list of further links, which is possible, as you can see in the sidebar of the app pages. Afterall, we are talking about ~80 different subdomains for KDE, most of them app or project specific ones. Not easy for a plain user to find what s/he wants. > > So kde.org adds nothing more than a visit card -like info for apps, so > in order to fight the chaos I am considering to indeed leave only > visit card -like info there for my maintained app. I assume you are talking about the kde.org page. Like you said, it is up to you. A simple feature list or even just a description with updated links for further information is fine. Afterall, we are only talking about a json file ;) It should at least fullfill what a new user expects or wishes to see there, preferably without clicking through 3 sites. > > -- > regards / pozdrawiam, Jaroslaw Staniek > http://www.linkedin.com/in/jstaniek > Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) > KDE Software Development Platform on MS Windows (windows.kde.org) Cheerio, Ingo ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Please update http://kde.org/applications/office/
2012/5/7 Jaroslaw Staniek : > On 7 May 2012 20:06, Ingo Malchow wrote: > >> Exactly. The benefit of having a detailed version on userbase is >> rather simple: there is a great ... userbase which updates content >> regularly. At least more than on some json file or in closed down >> websites. ;) > > So I minimized amount of the information: anyone with sufficient karma > please see the attached patch and apply it. > > Also please upload the missing kexi.png by copying > http://userbase.kde.org/images.userbase/1/11/Kexi_form.png > > Thanks. > > -- > regards / pozdrawiam, Jaroslaw Staniek > http://www.linkedin.com/in/jstaniek > Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) > KDE Software Development Platform on MS Windows (windows.kde.org) > Updated, thanks. Cheerio, Ingo ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
