Re: [kde-community] KDE Wiki Organisation
On 2016-03-09 13:07, Cornelius Schumacher wrote: On Mittwoch, 9. März 2016 11:20:50 CET Alex Merry wrote: We have outlines of how the wikis will be laid out internally, which will be documented in Help:Structure pages on the wikis. Community won't change much, other than gaining some new top-level sections from TechBase. TechBase will change substantially, becoming more product-based, so you can easily search for information on Frameworks, or Plasma, or Marble, or what have you, and kdelibs4-based information can be kept with a clear separation from Frameworks, for example. Thanks for sorting this out. I think this is a valuable and important step. Will you update http://wiki.kde.org as well to reflect what you decided about the structure? Yes, we're planning to do that. Just as soon as I find out how :-). No doubt there's a repository somewhere. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] KDE Wiki Organisation
I'm sure many of you have noticed that the TechBase and Community wikis have become a bit of a wilderness of outdated and hard-to-navigate information. On top of that, the line between TechBase and Community is rather blurred. At the CERN-based sprint, some of us have been working on this. Firstly, where is the line between the wikis? The new world (I mean, wiki) order is: - TechBase contains information for downstream developers of a product. Think of it as UserBase for developers. That means that if you're writing documentation, tutorials etc aimed at people using a library, writing plugins or using other APIs, it should go on TechBase. For example: how to use the Marble library to include a map in your app, or how to write a Plasmoid, or how to use a DBus interface to control KMail. - Community is anything aimed at ourselves (the KDE community). So this includes the sort of team scratchpad stuff we've all be using it for, as well as documentation about integrating a project into the KDE infrastructure, community and infrastructure rules and conventions, introductions for new community members and so on. - UserBase is, as it always was, end-user documentation. The biggest impact of this is that things like the Policies and Schedules[0] are being moved to Community (of course, the old pages will remain, but will be replaced with links to the new ones). We have outlines of how the wikis will be laid out internally, which will be documented in Help:Structure pages on the wikis. Community won't change much, other than gaining some new top-level sections from TechBase. TechBase will change substantially, becoming more product-based, so you can easily search for information on Frameworks, or Plasma, or Marble, or what have you, and kdelibs4-based information can be kept with a clear separation from Frameworks, for example. Do join us on #kde-www if you want to help out. We certainly won't have finished by the end of the week; there is a lot of work to do. Alex [0]: You may be thinking about Schedules that it's also important to packagers, but it's primarily a community organisation thing. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Berlin meet-up this weekend?
I'm in Berlin from Thursday evening to Monday afternoon because of a C++ conference (which I recognise a few KDE names at in the speakers list, let alone the attendees). Anyone fancy meeting up one evening? Or even during the day on Sunday or Monday. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Leaving KDE community
On 2015-11-03 02:21, Gustav González wrote: Hello everybody, This year I had a really hard time, so I couldn't work on Tupi as much as I would like it. For personal reasons I have decided to move back the source code of my project to Github (where I had it initially). The latest months I wasn't in the mood even to answer some mails mentioning Tupi in this list, so I chose to wait for the right moment to send this message, and I think it is today. The KDE community is great and I really appreciate the work you are doing, but I feel I don't fit here. No big deal at all and no hard feelings, I just don't want to discuss my decision. My excuses if I disappoint you. I'm sorry to hear that, but wish you well in the future. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Community Identity Guidelines
While sorting through the Development section of Techbase, I came across the Community Identity Guidelines (CIG) page at [1]. This appears to be rather out of date, referring to the K Desktop Environment as our preferred formal name, for example. It is also incomplete, with links to pages that don't exist. This is the sort of thing that would have fallen under the domain of the Marketing Working Group in the past, but I believe that's kind of dead now, so I'm asking here. Do we still want something like this (essentially a Brand Bible for KDE)? Do we in fact already have it in another location? Where is the best location for it (maybe the Community wiki or a static web page)? Any input on what should be done with this is appreciated. Alex PS: there are other out-of-date pages linked from [2]. I'm trying to press for information in more domain-specific locations for those, but the questions are largely the same. [0]: https://techbase.kde.org/Development [1]: https://techbase.kde.org/Development/Guidelines/CIG [2]: https://techbase.kde.org/Development/Guidelines ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 2015-08-17 19:19, John Layt wrote: On 17 August 2015 at 17:57, Alex Merry alex.me...@kde.org wrote: The general equivalent of this page is https://community.kde.org/Get_Involved - it gives an overview of the areas you can get involved in, and links to pages with more detail about how to get involved in that way. I think it makes a nice jumping-off point, and is good for emphasising that writing code is far from the be-all-and-end-all of KDE. It's very much a community involvement page, though, and techbase needs an equivalent whose selection is more along the lines of I want to write code / I want to use the Frameworks in my own project / I want to deploy KDE software to 20 000 computers. The how to build our software is just one part of that. Co-ordinating the development track on the community wiki and the build / send in patches track on the techbase wiki is going to take some thought, though. You mean like https://techbase.kde.org/Contribute? :-) It may help to have standard names for these sorts of matching pages. Not quite. I think techbase's Contribute page I think actually tries to do the job of community's Get Involved page, but does it significantly less well. My understanding is that Techbase is aimed at a wider audience than just KDE developers (including ISVs and sysadmins), and it could do with a starting point the entire audience - this is neither a contribute nor a get involved page. Actually, it could reasonably be called Getting Started, but then we'd need to pick a different name for the current Getting Started page (which is really aimed at developers). Or it could just be the landing page for Techbase. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 2015-08-17 16:47, Sebastian Kügler wrote: The following doc takes the point of view of a new developer or designer who would like to contribute, it has high-level starting points: https://community.kde.org/Plasma/Mobile/Contributing The general equivalent of this page is https://community.kde.org/Get_Involved - it gives an overview of the areas you can get involved in, and links to pages with more detail about how to get involved in that way. I think it makes a nice jumping-off point, and is good for emphasising that writing code is far from the be-all-and-end-all of KDE. It's very much a community involvement page, though, and techbase needs an equivalent whose selection is more along the lines of I want to write code / I want to use the Frameworks in my own project / I want to deploy KDE software to 20 000 computers. The how to build our software is just one part of that. Co-ordinating the development track on the community wiki and the build / send in patches track on the techbase wiki is going to take some thought, though. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Berlin Meet-up (tonight or tomorrow)
Hey, I happen to be in Berlin this weekend for a conference (where I ran into some KDAB folks), and was wondering if anyone in the area would be up for maybe going out for dinner tonight or tomorrow evening. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
