There is a generic category for events on the Phabricator calendar (Event: Meeting). It can be used for sprints or a new category can be created if needed.

created a workboard for the Privacy Sprint: KDE Privacy Sprint

In T8622#172243, @knauss wrote:

Is there any KDE wide calender where this can be added?

Is there any KDE wide calender where this can be added?

Okay finally we have a date and venue:

• What made you step and decide to contribute to KDE?

mail to find a date is sent now.

Find a date at: https://bitpoll.mafiasi.de/poll/8BYKJA5B/

FYI, I've asked @bcooksley and he was kind enough to create the workboard immediately, so everyone can now easily view all the pending junior jobs.

In T8712#167290, @ngraham wrote:

In T8712#167153, @bdhruve wrote:

Hello Everyone,

We have created a Matrix group: https://matrix.to/#/#kde-welcome:matrix.org
Anyone interested to be part of the team, please feel free to join :)

Awesome!

Is this Matrix-only, or is it bridged to IRC?

In T8712#167153, @bdhruve wrote:

Hello Everyone,

We have created a Matrix group: https://matrix.to/#/#kde-welcome:matrix.org
Anyone interested to be part of the team, please feel free to join :)

Here my first email draft for the doodle. Please proofread and change like you think:

Hello Everyone,

I'll be serving as the goal keeper for the next period.

In T8686#164113, @fabianr wrote:

We now have a Junior Job board !
https://phabricator.kde.org/project/view/294/

In T8686#164113, @fabianr wrote:

We now have a Junior Job board !

We now have a Junior Job board !

In T8712#163193, @neofytosk wrote:

Hi @bdhruve , before responding to your suggestions, I would like to be sure if you are referring to this guide: https://community.kde.org/Plasma/DeveloperGuide

Or is it about something else?

In T6831#124886, @ngraham wrote:

In T6831#124835, @IlyaBizyaev wrote:

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

That would be tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=278343

Its age doesn't give me a lot of hope for a fix from Mozilla. I suspect this is one of those cases where if we want it, it'll be up to us to produce and champion the patch.

Hi @bdhruve , before responding to your suggestions, I would like to be sure if you are referring to this guide: https://community.kde.org/Plasma/DeveloperGuide

I'll got ACK from Les Magnas that they are fully free before April.

Well from my end i was going through the Kde-dev-guide, and i offered a few suggestions to Valorie would love to share here as well,
ln the Dev guide it states KDE from developers viewpoint, we could add some thing like KDE from a new contributor point of view or some other nice term, and in this we could give information about:

In T8712#159843, @ngraham wrote:

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?

Ι sent a reminder around a week ago to the people I've been in talks with here in Athens to see if they can provide the place after all but I haven't received any answer yet, other than the acknowledgement that they are indeed late to respond.

In T8623#162141, @ervin wrote:

Do we have any news about that sprint and when/where it'll happen?

Do we have any news about that sprint and when/where it'll happen?

hm... Not sure if this is part of this task, but the new template says

@aacid: right, for a lot a big shared room is fine and for most a two persons room is fine. But I think we also need the possibility for people to have a single room one or two.

Something else that might be very useful in this regard, would be a way to flag, tag, sort, ... tickets by programming language or other skills one would need to accomplish a task.

In T7116#161579, @acrouthamel wrote:

Hey @neofytosk, you can cross off all of the Bugzilla stuff. We've completed those items in the T6832 subtask.

Done, thanks for your work @acrouthamel!

Hey @neofytosk, you can cross off all of the Bugzilla stuff. We've completed those items in the T6832 subtask.

Woohoo! Awesome work, Andrew. Keep an eye on http://pointieststick.wordpress.com/ tomorrow. :-)

I'm going to pull the automated NEEDSINFO handling from here, since this task is specific to new bug reporter experience. I'll work with Harald or whoever else would like to help. For now, I have a manual set of searches that seem to work well enough. I have some other automation ideas as well, so I'll just track that all in a separate task.

+1
We had a similar discussion in Akademy! Since string tags can't be added, we have to create either a group or a project.
Then, we may use the phabricator API to serve the junior jobs wherever needed. And, why not, create sth similar to the findyourway of plasmobile for KDE junior jobs in general.

Maybe we could add a "Junior Job" tag to phabricator? At the moment junior jobs are spread all over phabricator and hard to find. With a global "Junior Job" tag we could collect all these jobs in one place and new contributors could search threw them to find something that fits them.

@sitter - I just wanted to loop you in here since you had offered to script the NEEDSINFO closure bot.

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.

Hello! :)
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/

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++.

In T8712#159843, @ngraham wrote:

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?

Yes. :)

@ngraham are you suggesting to form a group for mentors on Phabricator? If yes, I have some suggestions on that, but we should probably continue this discussion on T8713. Let me know and I'll post my comments there.

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?

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).

Hi Nate,

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.

In T8711#159319, @acrouthamel wrote:

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:
  1. Create a Bugzilla account, do this.
  2. Create a KDE Identity account, do this.
  3. Create a Phabricator account, do this.
  4. Get your dev environment setup, follow these steps.
  5. Pull down this Git repo (say, a tutorial repo), create a branch
  6. Edit this file, commit it, and create a diff via Arcanist.
  7. Once approved, land your commit like this.
  8. You have now followed the basic process and can contribute!

In T8713#159197, @acrouthamel wrote:

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.

This is indeed a good idea, I added it as a subtask of T8712.

Much better now. Thanks!

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)

In T8712#142246, @simgunz wrote:

The link to the Mentoring page is literally the last word of the Getting involved page.

In T8713#159197, @acrouthamel wrote:

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.

Migrating a comment from @schampailler that was posted at T8484#154505:

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?

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.

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:
  1. Create a Bugzilla account, do this.
  2. Create a KDE Identity account, do this.
  3. Create a Phabricator account, do this.
  4. Get your dev environment setup, follow these steps.
  5. Pull down this Git repo (say, a tutorial repo), create a branch
  6. Edit this file, commit it, and create a diff via Arcanist.
  7. Once approved, land your commit like this.
  8. You have now followed the basic process and can contribute!

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. 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.

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.