> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/mentorship/mentorship-program-timelines.md).

# Program Schedule & Timelines

The Linux Foundation Mentorship Program follows the following term names; however, the program administrators can use any *Term* name during program creation. For details, see **program terms** of [Program Setup](/lfx/mentorship/administrators/enroll-your-program/mentorship-project-enrollment-form.md#MentorshipProjectApplication-ProgramSetup).

### **Full-Time Terms:**

### **Spring Term: March 1st - May 31st**

* **Mentorships available on LFX Mentorship:** mid-January
* **Mentee applications open on LFX:** approximately 4 weeks
* **Mentee application review and acceptance:** approximately 2 weeks before the term begins.

{% hint style="info" %}
**Note:** Dates may vary based on project guidelines.
{% endhint %}

### **Summer Term: June 1st - August 31st**

* **Mentorships available on LFX Mentorship:** mid-April
* **Mentee applications open on LFX:** approximately 4 weeks
* **Mentee application review and acceptance:** approximately 2 weeks before the term begins.

{% hint style="info" %}
**Note:** Dates may vary based on project guidelines.
{% endhint %}

### **Fall Term: September 1st - Nov 30th**

* **Mentorships available on LFX Mentorship:** mid-July
* **Mentee applications open on LFX:** approximately 4 weeks
* **Mentee application review and acceptance:** approximately 2 weeks before the term begins.

{% hint style="info" %}
**Note:**

1. Dates may vary based on project guidelines.
2. Part-time terms will continue for three to six months based on project guidelines.
   {% endhint %}

### **Activity Timelines**

The mentorship program is designed to provide a structured and supportive learning experience for mentees. Below is an overview of the program timeline for the full-time and part-time schedules.

### Full-Time Mentorship Program (12 weeks)

The full-time mentorship program is a 12-week intensive experience that includes regular evaluations and stipend payments.

* **Week 1-3**: The mentorship program begins with initial work assignments.
* **End of Week 3**: First mentee evaluations are due (optional for mentors and program administrators).
* **End of Week 6**: Midterm mentee evaluations are due, and the first stipend payment (50% of the total amount) is approved.
* **End of Week 9**: Third mentee evaluations are due (optional for mentors and program administrators).
* **End of Week 12**: Final mentee evaluations and mentee feedback/blog submission are due, and the second stipend payment (50% of the total amount) is approved.

### Part-Time Mentorship Program (24 weeks)

The part-time mentorship program is a 24-week experience that includes regular evaluations and stipend payments.

* **Week 1-6**: Mentorship program begins with initial work assignments.
* **End of Week 6**: First mentee evaluations are due (optional for mentors and program administrators).
* **End of Week 12**: Midterm mentee evaluations are due, and the first stipend payment (50% of the total amount) is approved.
* **End of Week 18**: Third mentee evaluations are due (optional for mentors and program administrators).
* **End of Week 24**: Final mentee evaluations and mentee feedback/blog submission are due, and the second stipend payment (50% of the total amount) is approved.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxfoundation.org/lfx/mentorship/mentorship-program-timelines.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.