GSOC2018 - Revision history

Mike: add 'student projects' hyper-link

2018-02-02T14:28:47Z

add 'student projects' hyper-link

← Older revision		Revision as of 14:28, 2 February 2018
Line 27:		Line 27:
	* talk to your professor about ASCEND, and whether there might be ways to incorporate project work with ASCEND into your degree.		* talk to your professor about ASCEND, and whether there might be ways to incorporate project work with ASCEND into your degree.
	* you might like to try tackling some little example problems that we previously used as tests for our GSOC applicants: [[OpenMP Exercise]], [[ANTLR exercise]]. We'll update here if we manage to write any new example problems.		* you might like to try tackling some little example problems that we previously used as tests for our GSOC applicants: [[OpenMP Exercise]], [[ANTLR exercise]]. We'll update here if we manage to write any new example problems.
			* take a look at our [[Student projects]] page for some existing GSOC projects. Surely, you are very welcomed to propose your own project!

	== Application template ==		== Application template ==

Mike: tiny grammar

2018-01-31T10:52:31Z

tiny grammar

← Older revision		Revision as of 10:52, 31 January 2018
Line 1:		Line 1:
	ASCEND is ~~apply~~ to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2018. Please read below if you are interested in participating!		ASCEND is applying to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2018. Please read below if you are interested in participating!

	The following application guidelines are retained for future reference.		The following application guidelines are retained for future reference.

Jpye at 03:47, 21 January 2018

2018-01-21T03:47:45Z

← Older revision		Revision as of 03:47, 21 January 2018
Line 1:		Line 1:
	ASCEND is apply to participate in [https://summerofcode.withgoogle.com/ GSOC] in ~~2017~~. Please read below if you are interested in participating!		ASCEND is apply to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2018. Please read below if you are interested in participating!

	The following application guidelines are retained for future reference.		The following application guidelines are retained for future reference.

Jpye: Jpye moved page GSOC2017 to GSOC2018

2018-01-21T03:47:20Z

Jpye moved page GSOC2017 to GSOC2018

← Older revision		Revision as of 03:47, 21 January 2018
(No difference)

Jpye: /* Application template */

2017-02-14T02:16:50Z

Application template

← Older revision		Revision as of 02:16, 14 February 2017
Line 50:		Line 50:

	'''Milestones'''		'''Milestones'''
	* What are the goals of your project? Are they [https://en.wikipedia.org/wiki/SMART_criteria ''specific'', ''measurable'', ''achievable'', ''~~relevant~~'' and ''time-specific'']?		* What are the goals of your project? Are they [https://en.wikipedia.org/wiki/SMART_criteria ''specific'', ''measurable'', ''achievable'', ''realistic'' and ''time-specific'']?
	* Give a schedule, showing the order in which you will achieve the specified goals. If possible, show that you have discussed the plan with your proposed mentor.		* Give a schedule, showing the order in which you will achieve the specified goals. If possible, show that you have discussed the plan with your proposed mentor.

Line 57:		Line 57:
	* Note that we require an ''absolute minimum'' of a weekly email update from all our students.		* Note that we require an ''absolute minimum'' of a weekly email update from all our students.

	'''~~Coding~~ experience'''		'''Programming language experience/expertise'''
	* Programming languages you have learnt, and how many lines of code, approximately, you have written in each.		* Programming languages you have learnt, and how many lines of code, approximately, you have written in each.

	'''~~Up and running?~~'''		'''Relevant experience'''
	* ~~Please give us as much evidence as you can to~~ show that you have ~~got our code running on your machine -- compiled it from~~ the ~~source code yourself --~~ and ~~that you've figured out~~ how to ~~use it independently. The more independent use that you can show,~~ the ~~better. If~~ you~~'ve identified a bug, report it and link to your bug report~~. ~~If you've written a new model, or some new code to add~~, ~~tell us about it. The more you~~'~~ve done, the easier it is for us to trust in~~ your ~~ability to contribute~~.		* List jobs, projects, courses etc that show that you have the required knowledge and experience for this project. Explain briefly how they relate to the project you are seeking.
			* Only list things that are relevant, we don't want your whole CV.

	'''~~Open source experience~~'''		'''Experience with ASCEND'''
	* Is this your first contact with the ASCEND project?		* Is this your first contact with the ASCEND project?
	* List or link to any code, patches, documentation or bug reports contributed to ASCEND or other projects.		* List or link to any code, patches, documentation or bug reports contributed to ASCEND or other projects.
			* Please give us as much evidence as you can to show that you have got our code running on your machine -- compiled it from the source code yourself -- and that you've figured out how to use it independently. The more independent use that you can show, the better. If you've identified a bug, report it and link to your bug report. If you've written a new model, or some new code to add, tell us about it. The more you've done, the easier it is for us to trust in your ability to contribute.
	~~'''Relevant work experience'''~~
	* ~~Only if~~ it'~~s relevant~~, ~~eg engineering or computer science paid work.~~
	* Give the ~~project details~~.

	''~~'Relevant studies'''~~
	* Courses that you have completed that are relevant to ~~ASCEND: engineering~~, ~~maths~~, ~~computer science. Say why they are relevant~~.

	'''Why ASCEND?'''		'''Why ASCEND?'''
	* ~~What is it that makes~~ you ~~want to work with~~ our project?		* If you can, say something insightful about the ASCEND project ''specifically'' -- something about our project that interests you more than others available in GSOC.

	[[Category:GSOC]]		[[Category:GSOC]]

Jpye: /* Application template */

2017-02-14T02:12:12Z

Application template

← Older revision		Revision as of 02:12, 14 February 2017
Line 46:		Line 46:
	'''Project proposal'''		'''Project proposal'''
	* Project title as provided on the [[Student projects]] page (or something of your own)		* Project title as provided on the [[Student projects]] page (or something of your own)
	* Then, a description of the project ''in your own words''.		* Then, a description of the project ''in your own words''. What do you think you will be able to achieve, and what will your approach be? Why did you choose this idea?
	* Why did you choose this idea?		* What progress have you made already? This might be a more detailed plan, getting up and running, some initial coding, familiarising yourself with related tools, or some general bug-fixing or bug-reporting for ASCEND more broadly.
	* ~~Show us that~~ you~~'ve thought about (~~and/or ~~discussed) what would ''really'' be involved in your chosen project. Give~~ some ~~details of how you will implement the solution, and what progress you have already made~~.

	'''Milestones'''		'''Milestones'''
	* What are the goals of your project? ~~How is your success with these goals~~ measurable?		* What are the goals of your project? Are they [https://en.wikipedia.org/wiki/SMART_criteria ''specific'', ''measurable'', ''achievable'', ''relevant'' and ''time-specific'']?
	* What is your planning schedule/steps for completing these goals? (These will be preliminary, ~~for further discussion)~~		* Give a schedule, showing the order in which you will achieve the specified goals. If possible, show that you have discussed the plan with your proposed mentor.

	'''~~Other projects~~'''
	* Give ~~one or two other projects~~ that you ~~would be interested in, if~~ the ~~first is unavailable~~.

	'''Other commitments'''		'''Other commitments'''

Jpye: /* Application template */

2017-02-14T02:04:23Z

Application template

← Older revision		Revision as of 02:04, 14 February 2017
Line 30:		Line 30:
	== Application template ==		== Application template ==

	'''''The following is the 'application template' that you can use when submitting your formal proposal to ASCEND via the GSOC website. Please check back here before the application deadline to ensure you have included all of the requested information'''''		'''''The following is the 'application template' that you can use when submitting your formal proposal to ASCEND via the GSOC website. Please check back here before the application deadline to ensure you have included all of the requested information. Please take care with formatting, and try to use a concise style.'''''

			'''About you'''
	* Name: full name (preferred 'friendly' name in brackets)		* Name: full name (preferred 'friendly' name in brackets)
	* Email:		* Email:

Jpye: /* Application template */

2017-02-14T02:02:56Z

Application template

← Older revision		Revision as of 02:02, 14 February 2017
Line 30:		Line 30:
	== Application template ==		== Application template ==

	'''''The following is the 'application template' that you can use when submitting your formal proposal to ASCEND via the GSOC website.'''''		'''''The following is the 'application template' that you can use when submitting your formal proposal to ASCEND via the GSOC website. Please check back here before the application deadline to ensure you have included all of the requested information'''''

	* Name: full name (preferred 'friendly' name in brackets)		* Name: full name (preferred 'friendly' name in brackets)

Jpye at 02:01, 14 February 2017

2017-02-14T02:01:43Z

← Older revision		Revision as of 02:01, 14 February 2017
Line 9:		Line 9:
	* [https://developers.google.com/open-source/gsoc/faq GSOC FAQs]		* [https://developers.google.com/open-source/gsoc/faq GSOC FAQs]
	* [https://developers.google.com/open-source/gsoc/timeline timeline]		* [https://developers.google.com/open-source/gsoc/timeline timeline]
	* [http://en.flossmanuals.net/gsocstudentguide/ GSOC Student Guide]: more detailed information about the programme
	* '''[[Student projects]]''': our list of project ideas with ASCEND (or propose your own)		* '''[[Student projects]]''': our list of project ideas with ASCEND (or propose your own)
	* [[:Category:GSOC]]: read about ASCEND projects/students with GSOC in previous years		* [[:Category:GSOC]]: read about ASCEND projects/students with GSOC in previous years

Jpye: Created page with "ASCEND is apply to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2017. Please read below if you are interested in participating! The following application gui..."

2017-02-14T02:00:55Z

Created page with "ASCEND is apply to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2017. Please read below if you are interested in participating! The following application gui..."

New page

ASCEND is apply to participate in [https://summerofcode.withgoogle.com/ GSOC] in 2017. Please read below if you are interested in participating!

The following application guidelines are retained for future reference.

== General information ==

GSOC is a programme that lets students be paid for work that they do to contribute to an open-source software project. It is a competitive programme for which students must make themselves known to the software project directly, and then apply to Google for selection. Students who get involved well in advance of the deadlines usually have a much better chance of being selected. Some links for people wanting to learn about GSOC for possible future participation:
* [https://en.wikipedia.org/wiki/Google_Summer_of_Code general information about the programme (wikipedia)]
* [https://developers.google.com/open-source/gsoc/faq GSOC FAQs]
* [https://developers.google.com/open-source/gsoc/timeline timeline]
* [http://en.flossmanuals.net/gsocstudentguide/ GSOC Student Guide]: more detailed information about the programme
* '''[[Student projects]]''': our list of project ideas with ASCEND (or propose your own)
* [[:Category:GSOC]]: read about ASCEND projects/students with GSOC in previous years
* '''our application template''' is at the bottom of this page.

We'd like to encourage anyone interested in our project to get in contact with us, and make a proposal! In general, the best way to learn about ASCEND is first to actually try to use it: so, ''please, [[SvnInfo|get the code]], [[Building ASCEND|build it]], try writing some models'', ponder our [[student projects]] list, and make your proposal. If you would like to discuss any of this, you can [[Support|get in contact with us]].

Please note that to actually formally apply to participate in the GSOC, you must do so via the GSOC website, you don't apply to us.

== Ways to get involved ==

* read the [[ASCEND overview]] and understand what ASCEND actually does.
* download our 'trunk' code [[SvnInfo|using subversion]] then [[Building ASCEND|build it]], and then [https://lists.sourceforge.net/lists/listinfo/ascend-sim-users let us know] about any issues you come across. Try to help us fix those issues. If you want an overview of the code, see our [[Developer's Manual]].
* ''use'' ASCEND! write some models to solve some problems that you have come across in your coursework or elsewhere. Preferably they should be non-trival: simultaneous nonlinear equations, optimisation problems, dynamic problems, etc. Send us your completed models, and work to make them general and reusable. Make use of existing reusable models from our [[model library]] where possible. If we see someone who's actually worked out what ASCEND is and how to use it, we're much more likely to sit up and pay attention!
* read our [[:Category:Documentation|documentation]] and help us to improve it: this is a wiki, so anyone can edit it. (Note: because of endless spam, you have to first register and we have to manually review your submission, but if you look like you're a real human-being person thing, then we're happy to have you.)
* take a look at our [http://bugs.ascend4.org|bug tracker] and find a bug that you can fix, or a feature request that you can implement
* get onto our [https://lists.sourceforge.net/lists/listinfo/ascend-sim-users mailing list] and open a discussion on features you would like to see in ASCEND
* talk to your professor about ASCEND, and whether there might be ways to incorporate project work with ASCEND into your degree.
* you might like to try tackling some little example problems that we previously used as tests for our GSOC applicants: [[OpenMP Exercise]], [[ANTLR exercise]]. We'll update here if we manage to write any new example problems.

== Application template ==

'''''The following is the 'application template' that you can use when submitting your formal proposal to ASCEND via the GSOC website.'''''

* Name: full name (preferred 'friendly' name in brackets)
* Email:
* Location: country, city during coding period
* University: current university and course, year started, length, expected completion date.
** Please include an email address and website reference for a '''professor at your university''' whom we can contact to confirm your enrolment status if required.
* Skype ID: (if you have one)
* Are you subscribed to our [[Support|ascend-sim-users]] mailing list? YES/NO (we prefer YES!)
* Phone number: (optional)
* URL link to your CV: (optional)
* URL link to your personal blog/homepage: (optional)

'''Project proposal'''
* Project title as provided on the [[Student projects]] page (or something of your own)
* Then, a description of the project ''in your own words''.
* Why did you choose this idea?
* Show us that you've thought about (and/or discussed) what would ''really'' be involved in your chosen project. Give some details of how you will implement the solution, and what progress you have already made.

'''Milestones'''
* What are the goals of your project? How is your success with these goals measurable?
* What is your planning schedule/steps for completing these goals? (These will be preliminary, for further discussion)

'''Other projects'''
* Give one or two other projects that you would be interested in, if the first is unavailable.

'''Other commitments'''
* We expect our GSOC students to be online (we prefer Skype) and immediately contactable for at least 35 hours a week, working directly on their GSOC project. If you expect this to be difficult, or if you expect to work at odd hours, we want to know in advance.
* Note that we require an ''absolute minimum'' of a weekly email update from all our students.

'''Coding experience'''
* Programming languages you have learnt, and how many lines of code, approximately, you have written in each.

'''Up and running?'''
* Please give us as much evidence as you can to show that you have got our code running on your machine -- compiled it from the source code yourself -- and that you've figured out how to use it independently. The more independent use that you can show, the better. If you've identified a bug, report it and link to your bug report. If you've written a new model, or some new code to add, tell us about it. The more you've done, the easier it is for us to trust in your ability to contribute.

'''Open source experience'''
* Is this your first contact with the ASCEND project?
* List or link to any code, patches, documentation or bug reports contributed to ASCEND or other projects.

'''Relevant work experience'''
* Only if it's relevant, eg engineering or computer science paid work.
* Give the project details.

'''Relevant studies'''
* Courses that you have completed that are relevant to ASCEND: engineering, maths, computer science. Say why they are relevant.

'''Why ASCEND?'''
* What is it that makes you want to work with our project?

[[Category:GSOC]]