- User Since
- Feb 17 2018, 6:07 AM (31 w, 1 d)
@sitter - I just wanted to loop you in here since you had offered to script the NEEDSINFO closure bot.
Fri, Sep 21
- Change text formatting
Good catch, apparently LibreOffice made a mistake! ;)
- Change default text placement
Yeah I think that is a mistake. D42047 which precedes the current diff, makes much more sense.
- Remove gitconfig
- One more spacing fix to allow people to use next empty line
- Spacing update to help keep content separate
I thought you'd like this. You can thank the LibreOffice team for pointing me to the repo for their create-guided.html.tmpl file. (I had noticed their "1. 2. 3." they placed into the one field).
Thu, Sep 20
How cool is this, how have I not seen this yet?
Wed, Sep 19
Tue, Sep 18
Mon, Sep 17
Sun, Sep 16
Thank you @andersonbruce for all of your work on this, and quickly working on feedback changes! This will be a great addition.
Sat, Sep 15
Are you able to edit the Tags on this? For some reason Event: Bugsquad is listed and is showing on that calendar.
Thu, Sep 13
How about changing the volume icon for the non-playing application to audio-volume-muted.svg? Then, when it is playing audio, it reverts to low/high icons as usual, based on slider location.
Wed, Sep 12
Tue, Sep 11
I've tested this patch on my system. Although it does not resolve the scaling issue I experience, it does not cause any regressions I see. Ship it! :)
I like it. I agree though to maybe make them a bit lighter.
Mon, Sep 10
Yeah exactly, something like that. Where they can git clone (making sure their gitconfig is correct, like how mine wasn't recently), make a branch (and track master), mess it up (lol I've never done that!), submit it via arc diff, tell them how their Git commit is too wordy and needs to break at 80 chars (*ehm* again, never done that before), have someone (newcomer group?) review it and accept it, and then have them arc land it.
I just realized the output was HTML. Ok, I can see what is going on now. If you could let me know if I am missing the "code-editor" though, that would be great!
I highly recommend AsciiDoc (specifically Asciidoctor)! It has a ton of great features, has standardized syntax (unlike Markdown), can easily include sections of source code from other files (super cool and useful for KDE code documentation), can include other AsciiDoc files to make document management easy, requires no special XML formatting application, and if you follow their recommendations (keeping all sentences on one line each, using ATX sections, etc.) it makes source control via Git a breeze. And you can export to any format, including DocBook.
Hey everyone, @xyquadrat, @ngraham, @cfeck, myself, and others have continued this over at the Bugsquad project page here on Phabricator, with the idea of keeping a schedule going. Check out the calendar for the next event!
I'm closing this out. The calendar is created, and the first event is up there, with more to come.
Sun, Sep 9
I've spoken with @xyquadrat regarding kicking off the Bugsquad schedule with Krita, to align with a goal/fundraiser to eliminate bugs. Awaiting details from him, but tentatively we are scheduling for the 16th of September to start. A second date would be either the 23rd, or during the week.
Any movement on this? It would be great to use the dictionary in krunner. Still broken in 5.13.4.
Sat, Sep 8
Thanks, I'll make sure to add to that file if I add more themes.
Fri, Sep 7
Thanks, I can. I'm getting an error in Arcanist, so let me diagnose that and I'll land it.
- Added three missing definitions
You were right again. For some reason that Others= disappeared from my ~/.config/katesyntaxhighlightingrc so I didn't notice it. Even though it was defined and displaying fine in the GUI. Weird.
- Fixed Others definition
- Some Marker color tweaks to ensure Solarized interaction rule adherence
- Fixed Light scheme Error color
- Solarized Light Region Marker fix and small Dark tweak.
I've fixed the section. I'm actually working on the KSyntaxHighlighting themes now, you'll see those in another patch.
- Fixed section code
Thu, Sep 6
What made you step and and decide to contribute to KDE?
- Besides enjoying the DE, it appeared to be a community that was making smart decisions (2017 Goals for example) and was growing.
What was your point of entry to KDE?
- Nate's blog posts basically, and Nate himself.
In what area are you contributing to (development, translation, documentation etc.)?
- Right now a mix of development and bug triaging, with maybe documentation later.
How did you decide where to contribute?
- I decided to work in areas that will help in the 2017 Goals. I like the productivity goal to polish the DE, and I like the onboarding goal to make the project easier to join. Helping a long-time FLOSS project grow is something I'd like to do. Right now my development efforts are small patches, since I'm not much of a programmer right now. Just things I know I can handle. So I'm now focusing on bug triaging, to hopefully assist those who do know how to program well.
What steps did you follow to get involved?
- I started out talking with Nate, he helped me through the 1-2-3 of getting signed up with my various accounts and a dev evironment. He and Henrik recommended some Phabricator Tasks and bugs/feature requests to tackle. Mostly icon fixes, menu edits, stuff like that. From there, I just spent time browsing randomly through Phabricator, finding Tasks and Projects that were interesting. Watching the Activity feed on the right is also helpful to see what cool things are happening and might be worth looking at to offer comments or assistance.
What did you enjoy most in the process of joining KDE?
- The friendliness of everyone, and the ease of joining. There were no trials or tests to go through.
What where the difficulties you came across?
- The introductory process of reading Wiki pages. Even with the improvements to Get Involved, there is no easy 1-2-3, here is how you get started. For example, to get started as a developer, you are pointed to an article, which has lots of information, sure, but is not a set procedure really. I was looking for something like:
- Create a Bugzilla account, do this.
- Create a KDE Identity account, do this.
- Create a Phabricator account, do this.
- Get your dev environment setup, follow these steps.
- Pull down this Git repo (say, a tutorial repo), create a branch
- Edit this file, commit it, and create a diff via Arcanist.
- Once approved, land your commit like this.
- You have now followed the basic process and can contribute!
I love all of these HIDPI fixes lately.