Basic code in https://invent.kde.org/jjazeix/mentorship-kde-org/-/tree/master (copied from eco.kde.org so it's the same theme for now)

You are missing a

Goals

section in the task description.

Here you write what you want to achieve with the task - or even better, the website. In this case it may be more than one thing and could be something like

1. Increase the number of applicants
2. Make it easier for applicants to apply and more likely to succeed
3. Offer a place to host applicants blogs
4. Keep applicants motivated and informed so they are more likely to complete their assignments

or whatever you think.

Benson proposes:

May wish to use a name such as contribute.kde.org or grow.kde.org as it
might be a little more welcoming to people new (and perhaps not so new)
to KDE.

In T17010#300768, @jjazeix wrote:

Benson proposes:

May wish to use a name such as contribute.kde.org or grow.kde.org as it
might be a little more welcoming to people new (and perhaps not so new)
to KDE.

That would be very confusing. "Contribute" and "grow" can mean anything and everything.

If there is no other proposition regarding the name of the website, I'll ask for the git repository creation on November 25/26th and I'll push the code from my local repository in it (https://invent.kde.org/jjazeix/mentorship-kde-org).

GSOC uses the name contributor rather than mentee. The aim is to get people to become more involved with KDE, so it is more of a guide by the side role than a sage on the stage role. Many people who go through these programs are/should be encouraged to guide others in the following program.

In T17010#300857, @jjazeix wrote:

If there is no other proposition regarding the name of the website, I'll ask for the git repository creation on November 25/26th and I'll push the code from my local repository in it (https://invent.kde.org/jjazeix/mentorship-kde-org).

Some name ideas so we find the best-possible name for the initiative. Note: there is no need to comment on each name, I include them here for the sake of brainstorming:

• advance.kde.org
• begin.kde.org
• build.kde.org
• develop.kde.org
• enter.kde.org
• go.kde.org
• join.kde.org
• make.kde.org
• participate.kde.org
• start.kde.org

Of these, the one I like most is join.kde.org. To me "join" has the sense of "start here and continue after", which is what we want. It is also short and simple. I don't know if it is a benefit or drawback that it follows the same format as many distributed social networks (e.g., joindiaspora, joinmastodon).

Thank you for the ideas!
If I have to filter a few, I would remove build/develop as it looks like too developer oriented (and build.kde was previously a Jenkins instance if I'm not wrong).

join/enter/participate/mentorship/start looks good for me.

There could also be events.kde.org or contribute.kde.org (as proposed by Benson) but it seems too generic.

Would be happy with join/enter/start . Not keen on events, could be Akademy or similar. grow.kde.org, germinate.kde.org or involved.kde.org might be other possibilities.

Another choice maybe welcome.kde.org

join/enter/participate/mentorship/start looks good for me.

I would really encourage to keep the focus on mentorship. We already have a page for getting involved and it's here https://community.kde.org/Get_Involved . It would be best to not make it confusing by creating something named similarly.

It might be a good idea is to reuse the season.kde.org website name as we are discussing killing the current PHP website powering it.

It might be a good idea is to reuse the season.kde.org website name as we are discussing killing the current PHP website powering it.

That would make sense, OR re-direct from there to the new site for returning visitors.I rather like the mentorship.kde.org address as it is still specific for these kind of programs, but not so general as "get involved", "join", etc.. Using "mentorship" will also cover any new program we decide to adopt in the future.

Thank you all for your inputs!

season.kde.org is specific to SoK so I agree that redirection makes more sense than reusing the name.
I can potentially see the issue that newcomer reading mentorship.kde.org will consider it's for people who want to mentor, not to be mentored but my English vocabulary is not good enough to know if there is a word from the mentee.
To add my +1 on this choice, the new website will be specifically for people who wants to get mentored or to mentor (yes, it's a start/join but specific to this use case so better have it in the name).

collaborative learning programs probably captures what is desired, see https://www.researchgate.net/publication/305160722_Cooperative_and_Collaborative_Learning_Definitions_and_Applications_in_Japanese_Universities but it is too long a name.

In T17010#300897, @jjazeix wrote:

Thank you all for your inputs!

season.kde.org is specific to SoK so I agree that redirection makes more sense than reusing the name.
I can potentially see the issue that newcomer reading mentorship.kde.org will consider it's for people who want to mentor, not to be mentored but my English vocabulary is not good enough to know if there is a word from the mentee.
To add my +1 on this choice, the new website will be specifically for people who wants to get mentored or to mentor (yes, it's a start/join but specific to this use case so better have it in the name).

For what it is worth, I interpret mentorship.kde.org as a place to get information about mentorship programs, both for mentees or mentors, although probably more for mentees. It is unfortunate that there is a hierarchical dynamic to the meaning to mentorship -- as opposed to "collaborative learning program", but I really cannot think of a word that captures that.

From me +1 for mentorship.kde.org.

In T17010#300898, @kbkmde wrote:

collaborative learning programs probably captures what is desired, see https://www.researchgate.net/publication/305160722_Cooperative_and_Collaborative_Learning_Definitions_and_Applications_in_Japanese_Universities but it is too long a name.

Thank you for finding the name, unfortunately a bit too long.
Could programs.kde.org work?

If not, I'll suggest we go with mentorship.kde.org to avoid lose more time

learning-programs.kde.org or learn.kde.org would be great, clp is short, but perhaps not descriptive enough. Of course, if there is a better french/german/etc word, that would also be great.

Maybe klp.kde.org Kollaborative Learning Programs

Thank you all for all the proposals. In order to not to wait too much and miss the beginning of the SoK, we went with mentorship.kde.org.
I've uploaded a first version of the website in https://invent.kde.org/websites/mentorship-kde-org and have created some issues to keep a track of the remaining work.
Now is the time to update the texts, design the website, ensure we have everything written and we are ready to start SoK soon!

Ok. Thanks for considering alternative names.

Website is published (https://invent.kde.org/websites/mentorship-kde-org/), let's review the content and make sure the procedure is ready for SoK contributors.

do we really want to translate it?

I don't know what capacities our translation teams have. Although I think blogging is very important for communication within the community, the posts likely have limited impact and are rather time sensitive: in a few years they may not be read by many people at all. I think using the translation teams for other aspects of KDE work may be more worthwhile if we have to choose where to put these resources.

Another idea: Contributors have the option of blogging in their native language and translating it into English with a tool like Deepl, and we publish it in both languages. The mentorship team (maybe with Promo help?) can edit the English texts for clarity. I don't think this will be too much work, although it does add to the overhead of running these programs.

Although English is probably - in most cases - a prerequisite for contributing to international teams such as those in KDE, giving contributors this option when communicating about their own work may be a nice way of showing respect for the diversity of our community. And perhaps it strengthens a sense of belonging in our global communities when they see members of their home community contributing to such a large international project like KDE.

Just some thoughts. Hope it makes sense.

In T17010#301666, @joseph wrote:

do we really want to translate it?

I don't know what capacities our translation teams have. Although I think blogging is very important for communication within the community, the posts likely have limited impact and are rather time sensitive: in a few years they may not be read by many people at all. I think using the translation teams for other aspects of KDE work may be more worthwhile if we have to choose where to put these resources.

For me, the blog post are too technical and I would assume people who read it to be able to read English. Regarding the website itself, the aim of SoK or GSoC is to contribute to KDE and thus people will need to speak English to discuss with mentors and community.

So if we consider the website is for these category of people, for me it's a prerequisite to be able to read English and there is no plus-value to translate. I can raise the point to the translation teams to have their opinion if someone thinks we should translate them (or at least partially).
I would not add the addition to blog in a specific language as I don't know much how the planet.kde.org will handle it. If we have different languages, they should not be posted in the English section but it would mean we need to do one feed per language. Also, contributors are required to blog in English (I'm not sure if it is a written rule but we never have contributors not blogging in English as English is the common language to discuss in the community).

I don't think also we should edit the contributors blogs. We can comment so they rephrase/fix small typos, but it's basically their post so we should not do it for them, it's part of the exercise.