Category:Project History and Roadmaps - Revision history

Jwgranville: /* Instructions */

2025-07-11T23:26:33Z

Instructions

← Older revision		Revision as of 23:26, 11 July 2025
Line 18:		Line 18:
	* First create a page with a title appropriate for your item. There's no hard convention yet, but strive for readability/searchability.		* First create a page with a title appropriate for your item. There's no hard convention yet, but strive for readability/searchability.
	* In the source of that page, add the following on the first line: <code><nowiki>[[Category:Project History and Roadmap]]</nowiki></code>		* In the source of that page, add the following on the first line: <code><nowiki>[[Category:Project History and Roadmap]]</nowiki></code>
	* Your page will be automatically indexed into ~~the~~ category. You can also add an entry in the timeline below.		* Your page will be automatically indexed into this category. You can also add an entry in the timeline below.

	=== Page contents ===		=== Page contents ===

Jwgranville at 23:25, 11 July 2025

2025-07-11T23:25:02Z

← Older revision		Revision as of 23:25, 11 July 2025
Line 9:		Line 9:
	Perhaps we could also include short biographical pages for contributors that care to share their information, but I'll wait to see what the group thinks of that before jumping in myself. ~Joe G		Perhaps we could also include short biographical pages for contributors that care to share their information, but I'll wait to see what the group thinks of that before jumping in myself. ~Joe G

			== Project Timeline ==
			This list may not stay accurate as it grows. Verify any inferences with human sources.

			* [[The Conception of EDURange]] [2011]: Conceptually, EDURange started around 2011 when Jens, Michael Locasto, and Richard started talking about creating exercises for cybersecurity courses. The idea was generated at a dinner with Michael, Sergey Bratus, Brian Fite, and Richard. Brian was packet master for a competition called PacketWars, and he was looking for a way to be a player and not the one running the competition. ... - Richard
	== Instructions ==		== Instructions ==
	Do not write individual items here; this page is just for indexing and coordinating the entries under this category.		Do not write individual items here; this page is just for indexing and coordinating the entries under this category.
Line 27:		Line 31:

	Do not add future items to this main timeline. Future goals that don't come to pass may need to be edited after the fact to avoid confusing readers - let's put such content in a dedicated place where it doesn't clutter up more reliable information.		Do not add future items to this main timeline. Future goals that don't come to pass may need to be edited after the fact to avoid confusing readers - let's put such content in a dedicated place where it doesn't clutter up more reliable information.

	~~== Project Timeline ==~~
	~~This list may not stay accurate as it grows. Verify any inferences with human sources.~~

	* [[The Conception of EDURange]] [2011]: Conceptually, EDURange started around 2011 when Jens, Michael Locasto, and Richard started talking about creating exercises for cybersecurity courses. The idea was generated at a dinner with Michael, Sergey Bratus, Brian Fite, and Richard. Brian was packet master for a competition called PacketWars, and he was looking for a way to be a player and not the one running the competition. ... - Richard

Jwgranville: /* Project Timeline */

2025-06-30T17:15:09Z

Project Timeline

← Older revision		Revision as of 17:15, 30 June 2025
Line 31:		Line 31:
	This list may not stay accurate as it grows. Verify any inferences with human sources.		This list may not stay accurate as it grows. Verify any inferences with human sources.

	* [[The Conception of EDURange]] [~~time?~~]: Conceptually, EDURange started around 2011 when Jens, Michael Locasto, and Richard started talking about creating exercises for cybersecurity courses. The idea was generated at a dinner with Michael, Sergey Bratus, Brian Fite, and Richard. Brian was packet master for a competition called PacketWars, and he was looking for a way to be a player and not the one running the competition. ... - Richard		* [[The Conception of EDURange]] [2011]: Conceptually, EDURange started around 2011 when Jens, Michael Locasto, and Richard started talking about creating exercises for cybersecurity courses. The idea was generated at a dinner with Michael, Sergey Bratus, Brian Fite, and Richard. Brian was packet master for a competition called PacketWars, and he was looking for a way to be a player and not the one running the competition. ... - Richard

Jwgranville: /* Timeline entries */

2025-06-30T17:14:41Z

Timeline entries

← Older revision		Revision as of 17:14, 30 June 2025
Line 24:		Line 24:

	=== Timeline entries ===		=== Timeline entries ===
			Please try to keep timeline entries to a brief paragraph. Include the name of the page, the time in question, and your name as author.

	Do not add future items to this main timeline. Future goals that don't come to pass may need to be edited after the fact to avoid confusing readers - let's put such content in a dedicated place where it doesn't clutter up more reliable information.		Do not add future items to this main timeline. Future goals that don't come to pass may need to be edited after the fact to avoid confusing readers - let's put such content in a dedicated place where it doesn't clutter up more reliable information.

	~~Please try to keep timeline entries to a brief paragraph. Include the name of the page, the time in question, and your name as author.~~

	== Project Timeline ==		== Project Timeline ==

Jwgranville: Added instructions

2025-06-30T17:12:17Z

Added instructions

← Older revision		Revision as of 17:12, 30 June 2025
Line 8:		Line 8:

	Perhaps we could also include short biographical pages for contributors that care to share their information, but I'll wait to see what the group thinks of that before jumping in myself. ~Joe G		Perhaps we could also include short biographical pages for contributors that care to share their information, but I'll wait to see what the group thinks of that before jumping in myself. ~Joe G

			== Instructions ==
			Do not write individual items here; this page is just for indexing and coordinating the entries under this category.

			* First create a page with a title appropriate for your item. There's no hard convention yet, but strive for readability/searchability.
			* In the source of that page, add the following on the first line: <code><nowiki>[[Category:Project History and Roadmap]]</nowiki></code>
			* Your page will be automatically indexed into the category. You can also add an entry in the timeline below.

			=== Page contents ===
			Please include context for your items, as future contributors may use these accounts for research. Readers should not need to rely on edit history to determine the date and author. At a minimum, the page should include:

			* Your identity as the writer.
			* The date of the original post.
			* The timespan, if the post refers to something that has already happened or has a concrete goal date.

			=== Timeline entries ===
			Do not add future items to this main timeline. Future goals that don't come to pass may need to be edited after the fact to avoid confusing readers - let's put such content in a dedicated place where it doesn't clutter up more reliable information.

			Please try to keep timeline entries to a brief paragraph. Include the name of the page, the time in question, and your name as author.

			== Project Timeline ==
			This list may not stay accurate as it grows. Verify any inferences with human sources.

			* [[The Conception of EDURange]] [time?]: Conceptually, EDURange started around 2011 when Jens, Michael Locasto, and Richard started talking about creating exercises for cybersecurity courses. The idea was generated at a dinner with Michael, Sergey Bratus, Brian Fite, and Richard. Brian was packet master for a competition called PacketWars, and he was looking for a way to be a player and not the one running the competition. ... - Richard

Jwgranville: Created page with "This is a page to collect our history, accomplishments, needs, goals and wishlist items. The idea is to document all of the high-level material we've produced, such as publications, major code releases and trial results. This collection can then be used as a timeline of our work and trajectory. As this content is developed we may want to adopt standards for how things are organized - particularly to distinguish between proposed goals, agreed-upon plans and retired item..."

2025-06-30T16:34:17Z

Created page with "This is a page to collect our history, accomplishments, needs, goals and wishlist items. The idea is to document all of the high-level material we've produced, such as publications, major code releases and trial results. This collection can then be used as a timeline of our work and trajectory. As this content is developed we may want to adopt standards for how things are organized - particularly to distinguish between proposed goals, agreed-upon plans and retired item..."

New page

This is a page to collect our history, accomplishments, needs, goals and wishlist items.

The idea is to document all of the high-level material we've produced, such as publications, major code releases and trial results. This collection can then be used as a timeline of our work and trajectory.

As this content is developed we may want to adopt standards for how things are organized - particularly to distinguish between proposed goals, agreed-upon plans and retired items that are reference only.

When making pages for a code release or academic paper it would be great to include working permalinks to the resource in question, especially full text for literature. A brief statement including additional details would also be helpful - such as who contributed to it and when, and a description of the state of the project at the time.

Perhaps we could also include short biographical pages for contributors that care to share their information, but I'll wait to see what the group thinks of that before jumping in myself. ~Joe G