I am a guy with too much free time. But that's okay, because I can use this free time to contribute to KDE! My main job is bug triaging (currently in the top 5 as visible here), and sometimes I also write patches.
Reddit account: u/onlyasegfault
I am a guy with too much free time. But that's okay, because I can use this free time to contribute to KDE! My main job is bug triaging (currently in the top 5 as visible here), and sometimes I also write patches.
Reddit account: u/onlyasegfault
In T10318#285926, @ognarb wrote:@xyquadrat do you still have your website on a git repo somewhere?
Another belated ping. I've just mentioned Kile to friends and whilst they downloaded it because of my recommedation, multiple people mentioned they disliked the design of the website.
It seems to me as if we'd want to place the deadline agressively early compared to last year. Publishing something about 2019 in September 2020 does seem a bit disconnected, "late to the party". Now I know that there are often more pressing tasks at hand than the e.V. report, but still, I'd say we should try to get this done by the end of April if possible. Earlier is always better, of course :)
And for (sub)releases that happen inbetween - those are 99% of the time bugfix releases either way, no? Looking at the changelogs for 20.08.1/2/3, they do not seem to contain something that'd warrant a separate article - so then we just can keep doing it the way we do right now, have a changelog and site for them but not a fully-fledged release announcement.
To chime in as well:
Since we will migrate off Phabricator entirely earlier or later, I think it would be more sensible to use the Nextcloud calendar.
Quick stat overview:
The conditions around releases have changed quite a lot since this task was opened. We now are editing announcement texts on GitLab, allowing all Promo members (and others) to easily contribute. Reaching out to developers is also usually necessary any more, since we have now implemented the "Noteworthy" label, which should ideally replace this. The Plasma 5.20 announcement process has been much smoother as well. I'd therefore close this task tomorrow if no further objections are raised.
Generally, I think that the concept of "let's plan our upcoming posts" is a great idea. Although I do wonder if it wouldn't be better to use the Calendar feature from Phabricator for that? (and in the future, maybe a matrix calendar integration, that'd be even cooler)
From what I have heard, this was some sort of config issue and the Nextcloud Markdown editor should work fine now without any conflict problems. Is that correct? If yes, do we still want to keep this task open or can it be closed?
We have added one task here:
https://community.kde.org/SoK/Ideas/2021
Ping :)
I'd suggest changing the icon at https://invent.kde.org/plasma/plasma-nano to the chosen one and also add it to the repo.
Old task without much progress - let's close this and revisit this later on if it fits.
Old task without much progress - let's close this and revisit this later on if it fits.
For a different type of celebrity: Given that our software is used at NASA, potentially somebody that has worked on a programme where KDE software was used could send us friendly message.
Mail sent to kde-community and kde-devel. If we receive feedback that should be incorporated, we can do that directly in the Commit Policy (or wherever we put it).
The additional features I have mentioned in T13595#239528 are probably more advanced, but I would still consider including them since your casual user will not see the Appstream description at all. Mostly users who are looking for a better file manager will encounter the text we are working on, and this user group is probably more knowledgeable than the average.
Features:
Navigation (or breadcrumb) bar for URLs, allowing you to quickly navigate through the hierarchy of files and folders.
Most people probably don't think of URLs when browsing through files. Also, is that a special feature? As far as I know basically every file manager has a similar navigation bar.
Supports several different kinds of view styles and properties and allows you to configure the view exactly how you want it.
Maybe add examples (icons, detailed list) for "view styles"
Split view, allowing you to easily copy or move files between locations.
Additional information and shortcuts are available as dock-able panels, allowing you to move them around freely and display exactly what you want.
Multiple tab support
"Tabs support" instead, since there have to be multiple tabs by definition for this to be useful.
Informational dialogues are displayed in an unobtrusive way.
Is that a feature that differentiates Dolphin from other file managers? In my opinion this could be dropped.
Undo/redo support
Rather minor.
Transparent network access through the KIO system.
Reword as "Easily access remote file shares as if they were local through the powerful KIO system" or similar ("network access" is quite abstract)
This is a very old task that does no longer reflect the current state of things (e.g. the Applications section has changed quite a bit). Do we want to revive this effort or close the task instead?
The three wiki pages are merged into one, and kde.org/download links there. Possibly kde.org/download could be made a bit more visually attractive, but then again from kde.org we by now mostly link to kde.org/applications, which has download links on the respective application pages. So, any objections to close this task as done?
Stale for over 3 years now, closing. We might look at this again in the future, but that should be a new task with an updated situation view.
Do we need more work here or can we close this task? I see that plasma-mobile.org has this nice "What do you want to do?" questionnaire based on asknot, which should provide a decent onboarding experience.
Is this still relevant, and if yes, relevant to Promo? Seems like more of an internal thing.
At this point in time, I think it is more sensible to concentrate our efforts on other things. Let's explore this again in the future, once we have grown further and do need deeper insights on the market.
Seems like the consensus in #kde-promo is that https://kde.org/stuff/metastore.php should be enough for now.
I assume with Akademy the e.V. report is done and this task can be closed, right?
Given that conf.kde.in has happened in January, this task should now be resolved.
Seems like this has not been changed in the end. Would be a simple task, so I think we should pick this up again and quickly finish it.
I don't know what the exact feature requirements would be, but https://demo.codimd.org/features might be another option.
Sorry, I meant "whenever a KCM is rewritten, that's a cool new user-facing feature" (e.g. the Bluetooth one that is currently being worked on). That isn't very clear from the description though, I see that now.