This project is used to collect and work on the KDE community's goals in 2017.
@sitter - I just wanted to loop you in here since you had offered to script the NEEDSINFO closure bot.
Fri, Sep 21
Wed, Sep 19
AFAIK two people in two beds in a room is the default that KDE eV sponsored solution since basically halves the price for hotels in rooms, sharing more then 2 people in a room gets annoying and usually is avoided and only one person per room is too expensive and only granted in some cases, but please confirm with the board what i'm saying is true.
Tue, Sep 18
Thu, Sep 13
Indeed it was. You might like what the Plasma Mobile project came up with: https://www.plasma-mobile.org/findyourway/
Sorry if this was posted before, but looks interesting: https://whatcanidoformozilla.org/
Wed, Sep 12
What made you step and and decide to contribute to KDE?
I've always wanted to contribute to something. I was very happy with what is going on in KDE lately (Plasma in particular but also the more common apps) and Nate's blog made it seem very approachable, even for someone new to KDE/Qt/C++.
Oh, maybe I'm stating the obvious, but the whole patch submission process is absolutely bearable. Nothing fancy. The problem lies more in the way it is explained. Once you have Neon and arc running, it's a breeze.
Thank you so much for taking the time to respond here @acrouthamel . Hopefully as we gather more responses we will be able distinguish some common themes among newcomers' feedback.
A good next step might be creating a formal Phabricator group for this, to which people could add themselves. Then for example we could document that new contributors should add the group as a reviewer for their first patches, which could help make sure that those critical first patches don't get lost and always have someone available who can help. Thoughts?
Tue, Sep 11
the only suggestion where people aren't sharing rooms is the french one then :)
The Linux Hotel in Essen-Host (https://www.linuxhotel.de, German only) is are really nice location. I was there once some years ago and forgotten about it :D I ask them today by phone, but they can only host at maximum 25 persons. And this only if several share a two bed room. They proposed to asl "Unperfekt Haus" in Essen Cetrum (https://www.unperfekthaus.de, German only).
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.
This is indeed a good idea, I added it as a subtask of T8712.
Much better now. Thanks!
Sun, Sep 9
here's an (in danish only, sorry) overview of scouts houses in dk http://hyttefortegnelsen.dk/
but, most require you to be rather scouty, as it is 3 layered bunk beds with 5-6 beds in a room - there's usually a big kitchen (though we would have to cook for ourselves) and only 1 common room, so the work room and eating area would be the same room (unless you want to use the outdoors, which is always dicey with the weather)
I was seeing the Kontact prototype website and maybe it could be an interesting first step for this task - an website listing our software related to academia/science/research field.
Together with @stolborg , we are evaluatiing currently two options:
- Les Magnas (France, Provence, Pierrerue): http://auxsaisons.free.fr/
- 2h by train/bus reachable from Marseilles (nearest airport)
- how people get from the bus station to the venue ( shuttle service needed)
- local scout huts in Denmark (likely far out and lessluxurious)
- do we need to cook by ourselfs (I know people, who like to cook for us)
- how people reach the venue?
- can people sleep in small rooms?
Sat, Sep 8
I was thinking that a way to facilitate a newcomer getting into a project could be to find him a code buddy, another newcomer working on the same project.
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!
Wed, Sep 5
I like this, but I feel this should be merged into T8712. The welcome team would make this one of their steps for on-boarding a newcomer.
I'd be glad to help out. This is something that would be a huge help in my opinion. I'm pretty new (I'll answer those newcomer questions shortly), and I know having an easier to find on-boarding group would have been great. Luckily, I found Nate and started bothering him, so it all worked out. But I'm sure a lot of people could use a helping hand to get settled into a KDE project.
I hope not, I'd rather keep it in-house.
I'm sure that there is no need to use Google Calendar after all the effort to move part of release schedule and promo stuff out of it...
Hi everyone just thought I'd drop a note here as well. I've had @sysadmin recreate the Bugsquad, but in Phabricator for easy collaboration. I'd like to resurrect it, with a set schedule of triaging days as you started here. I've asked @sysadmin about adding a calendar to the project, or allowing other Calendar edit access. If not, I'll create a Google Calendar people can subscribe to I suppose.
Tue, Sep 4
I agree with keeping UNCONFIRMED/CONFIRMED. I was going to make an argument for keeping that as I think it makes sense. Bugs come in, someone looks at it, and reproduces it (or takes other action). So for the triagers I think it makes sense to be able to easily find bugs that have not been reproduced yet.