Tracking of NDA signatures

Hi everyone,

The document is ready now.

Hi @Guilhermems, the KDE e.V. board in collaboration with some community members is working on maintaining and building some of the relationships mentioned here.

If other solutions don't work, another option is to use a shared text file on share.kde.org, and just list there the posts. It might be a bit easier than editing phabricator tasks.

If there were any templates for posters designed, it would be good to have the editable files uploaded somewhere for future use.

The e.V. supporters have been informed and we can now share this publicly.

In T13465#236830, @paulb wrote:

In T13465#236825, @mmustac wrote:

One little gem I found out lately is the option to bind a shortcut to "open klipper at mouse position" option which is really useful in my opinion

Interesting... So what does it do? I tried it but nothing happened.

There are additional ones listed here: https://manifesto.kde.org/benefits.html

Thank you @ognarb!

In T11799#222481, @paulb wrote:

@colomar Are you still more or less in charge of the Advisory Board? If not, who is? Either way, I would need a text for the report.

Kirogi, that @hein demonstrated in Akademy 2019, might be a crowd pleaser. Perhaps hard to do a live demo, but maybe a video of it in action?

Looks good to me, should do the job fine! =)

I've already sent the CfP in the community and devel mailing lists, no response so far. We should probably bump it closer to the deadlines.

Hi Piyush,

For some reason I can't tag him on mobile, but Nicolas Fella can probably offer insights on the number of contributors, repos and commits. I've sent him a message to check this task.

Snail mail sent, please let me know once it arrives to close this task.

Here's an idea off the top of my head:

I just sent it via email.

Neofytos Kolokotronis
neofytosk@kde.org

Closing as this took place a couple of weeks ago, here's a summary: http://neofytosk.com/post/kdes-onboarding-sprint-making-it-easier-to-setup-a-development-environment/

How about devising a promo plan for the new goals? They will have been decided and announced by Monday.

Added Ubucon, as Diogo Constantino from the organizers team reached out to me inviting KDE to attend their annual event.

I see that so far the a discussion has revolved around the technical side of things. How about thinking a bit more on how we plan to reach out to these organizations? Can we form a strategy and start building collaborative relationships with them?

Off the top of my head, here's a suggestion on rephrasing this one: "Improve documentation and presentation/communication of KDE's work and structure"

@skadinna I think it's worth mentioning Google Season of Docs and describe how KDE's participation could possibly contribute towards this goal: https://developers.google.com/season-of-docs/

Thanks @skadinna for the reminder email.

@paulb is there any update on this? Did David ever respond to @skadinna's email? If not we should probably bump the discussion.

This seems directly relevant to T9776, can you take a look @jriddell? Perhaps we can merge these two objectives or some overlapping aspects of them regarding Applications?

@jbbgameich just a friendly request for us lurkers that like to keep an eye on Plasma Mobile development: would it be possible to add screenshots to the applications you host on invent so we can take a peak into how they look? =D thanks, and keep up the awesome work!

In T7050#189213, @lavender wrote:

@neofytosk Can you give some explanation?

A new date is set for the Streamlined Onboarding Sprint 2019. It will take place on July 22-23 in Nuremberg, Germany. Please register your interest on https://community.kde.org/Sprints/Onboarding/2019!

New date is set for July 22-23 in Nuremberg, Germany. Please register your interest on https://community.kde.org/Sprints/Onboarding/2019!

As the sprint in May did not gather enough participants, we will have to move it to a later date. I will let you know once more info is available.

Hey everyone,

In T8623#178409, @dkazakov wrote:

Hi, all! I'm sorry, I found out that I will not manage to come to the sprint this time :( If you happen to gather next winter, I might try to join though.

Onboarding

Mozilla is successful in building a community and onboarding new members. For KDE onboarding is now also a goal, so we might be able to learn from Mozilla'a experience here.
Plasma Mobile uses a fork of Mozilla's whatcanidoformozilla.org website for the Find your way page.

In T10580#178135, @skadinna wrote:

My suggestion is to look into whether this can be co-organized with the Onboarding sprint in Athens, which is taking place in May. (https://phabricator.kde.org/T8623)

Pinging everyone subscribed to the task in order to register their date preferences, as we need to inform the venue by early March:
@bshah @vijaykrishnavanshi @nicolasfella @dkardarakos @dkazakov @albertvaka @aacid @ervin @sharvey @gladhorn @dfaure @elvisangelaccio @valorie @lydia

closing this as it is now done. If we end up switching to gitlab, we should remember to reintroduce a similar tag.

Hey everyone, it took a while but I am thrilled to announce that we have finally found a place to host us in Athens. It will be available for the 3 out of 4 weekends of May 2019.

We should definitely list the #kde-welcome channel and if possible highlight it so it stands out. It's a new one created as part of the onboarding goal and it suits the purpose of this page perfectly. =)

Would it make sense to split this list to FOSS related and non-FOSS related events?

Looks great to me, keep it up! =)

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 T9729#167975, @bshah wrote:

No I mean, well, the dates you have on the poll, we have requested, exactly those dates to Endocode (4-9). So I wonder if we need poll at all :)

In T9142#167968, @ognarb wrote:

I'm also thinking about writing a blog post, about how contributing to the wiki is an easy first contribution (was for me) and how people can also help. Opinion?

Do it and let us know when it's out! =) It's a great way to publicize this task, share your experience and hopefully inspire new contributors.

Great to see the interest for this sprint increasing!

Judging from the responses so far, it seems like a good candidate would be Berlin/Germany, the week before or after FOSDEM.

In T8686#164113, @fabianr wrote:

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

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

Ι 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 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!

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?

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

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.

There's a minor typo in the drop down "Kontact" menu on the top bar, Akregator is misspelled as Akreagtor.

In T9468#156700, @skadinna wrote:

Sorry to derail the discussion, but I have another question: would it make sense to include something like "post approval rules" in this policy?

Meaning, define some rules for how a person with social media access should approach the whole Promo team with an idea to post something. For example, specify how many other team members need to approve the post, or how long to wait for feedback before going forward and posting something. Or is this just nitpicking and unnecessarily complicating everything? 😅

I'm only asking because I don't think we have it defined anywhere, but on the other hand, maybe it doesn't need to be so strictly defined. So I'd love to hear your thoughts.

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.

Hi @dkazakov, it's great that you are interested and I'm sure your experience would be valuable.

Unfortunately I can't help this time, but here's the announcement for Applications 18.04 that can be used as a template for the structure:
https://www.kde.org/announcements/announce-applications-18.04.0.php