GSoC Students Recommendations - Revision history

Prajwal S N at 18:45, 10 March 2025

2025-03-10T18:45:57Z

Radostin at 05:11, 13 April 2023

2023-04-13T05:11:44Z

Radostin at 05:09, 13 April 2023

2023-04-13T05:09:41Z

Ptikhomirov: /* Takeoff */

2022-05-23T21:28:02Z

Takeoff

Radostin: /* Contributing */

2020-02-29T15:33:46Z

Contributing

Amikhalitsyn: /* Contacts */

2020-02-25T12:58:54Z

Contacts

Xemul: Created page with "Category:GSoC == Contacts == The main entry point for the community is the `criu@openvz.org` mailing list. Also, the ideas pag..."

2019-01-29T07:13:08Z

Created page with "Category:GSoC == Contacts == The main entry point for the community is the <code>criu@openvz.org</code> mailing list. Also, the ideas pag..."

New page

[[Category:GSoC]]

== Contacts ==

The main entry point for the community is the <code>criu@openvz.org</code> mailing list. Also, the [[Google Summer of Code Ideas|ideas]] page contains mentors' personal e-mails for each sub-project.

== Takeoff ==

Starting playing with CRIU is as simple as one, two, three:

# Get the sources from [https://github.com/checkpoint-restore/criu]
# Build them with <code>make</code>
# Do your first C/R by running a simple test with <code>zdtm.py run -t static/env00</code>

Here are links for further reading

* [[Installation]]
* [[CLI]]
* [[Simple loop]]
* [[ZDTM test suite]]

== Contributing ==

When a new patch is ready, it can be submitted for merging either [[How_to_submit_patches|via the CRIU mailing list]] (recommended) or via github PR.

@@ Line 10: / Line 10: @@
 Starting playing with CRIU is as simple as:
-# Get the sources from [https://github.com/checkpoint-restore/criu]
+# Get the sources from [https://github.com/checkpoint-restore/criu the GitHub repository]
 # Build them with <code>make</code>
 # Do your first C/R by running a simple test with <code>zdtm.py run -t zdtm/static/env00</code>

← Older revision		Revision as of 05:11, 13 April 2023
Line 1:		Line 1:
	[[Category:GSoC]]		[[Category:GSoC]]
−
	This page provides some insights for potential Google Summer of Code (GSoC) contributors. By following these recommendations, students can increase their chances of success in the programme and gain valuable skills and experience in open-source development.		This page provides some insights for potential Google Summer of Code (GSoC) contributors. By following these recommendations, students can increase their chances of success in the programme and gain valuable skills and experience in open-source development.

@@ Line 1: / Line 1: @@
 [[Category:GSoC]]
 == Contacts ==
@@ Line 5: / Line 7: @@
 The entry points for the community is the [https://github.com/checkpoint-restore GitHub checkpoint-restore project], [https://gitter.im/save-restore/CRIU Gitter] and <code>criu@openvz.org</code> mailing list. Also, the [[Google Summer of Code Ideas|ideas]] page contains mentors' personal e-mails for each sub-project.
-== Takeoff ==
+== Getting Started ==
-Starting playing with CRIU is as simple as one, two, three:
+Starting playing with CRIU is as simple as:
 # Get the sources from [https://github.com/checkpoint-restore/criu]
@@ Line 13: / Line 15: @@
 # Do your first C/R by running a simple test with <code>zdtm.py run -t zdtm/static/env00</code>
-Here are links for further reading
+The links below include some additional resources that you may find helpful to explore further.
 * [[Installation]]
@@ Line 22: / Line 24: @@
 == Contributing ==
-When a new patch is ready, it can be submitted for merging either [[How_to_submit_patches|via the CRIU mailing list]] or via GitHub PR.
+Once a new patch is prepared, it can be submitted for merging by creating a [https://github.com/checkpoint-restore/criu/blob/criu-dev/CONTRIBUTING.md GitHub pull request].

← Older revision		Revision as of 15:33, 29 February 2020
Line 22:		Line 22:
	== Contributing ==		== Contributing ==

−	When a new patch is ready, it can be submitted for merging either [[How_to_submit_patches\|via the CRIU mailing list]] ~~(recommended)~~ or via ~~github~~ PR.	+	When a new patch is ready, it can be submitted for merging either [[How_to_submit_patches\|via the CRIU mailing list]] or via GitHub PR.