Difference between revisions of "User:AndrewJohnson/EPICS Code-athon"
m |
|||
| Line 27: | Line 27: | ||
===Words for Ned's document=== | ===Words for Ned's document=== | ||
Coding Marathons, also called Hackathons (http://en.wikipedia.org/wiki/Hackathon) or Code Sprints, are popular in a number of open source projects. APS would like to host a week-long EPICS Code-athon early in 2008 to work on some of the items on the EPICS To Do list. We will provide a comfortable environment with wireless networking, refreshments and space for up to 20 people to come and work on EPICS core development projects. | Coding Marathons, also called Hackathons (http://en.wikipedia.org/wiki/Hackathon ) or Code Sprints, are popular in a number of open source projects. APS would like to host a week-long EPICS Code-athon early in 2008 to work on some of the items on the EPICS To Do list. We will provide a comfortable environment with wireless networking, refreshments and space for up to 20 people to come and work on EPICS core development projects. | ||
We hope that most of the EPICS core developers will be able to attend, and sites who wish to donate or develop expertise are invited to apply to send a staff member (who must have experience developing EPICS applications) to take one of the remaining places. All travel and expenses must be paid by the participant’s home institution, but that cost compares to that of attending an EPICS meeting. All participants must bring a laptop to develop on. | We hope that most of the EPICS core developers will be able to attend, and sites who wish to donate or develop expertise are invited to apply to send a staff member (who must have experience developing EPICS applications) to take one of the remaining places. All travel and expenses must be paid by the participant’s home institution, but that cost compares to that of attending an EPICS meeting. All participants must bring a laptop to develop on. | ||
The projects to be worked on will be of general use to multiple sites; we will maintain a list, but attendees are invited to bring their own ideas. I also want to arrange a few talks on topics appropriate to the audience (offers or suggestions welcome), and will look for other appropriate diversions too. | The projects to be worked on will be of general use to multiple sites; we will maintain a list, but attendees are invited to bring their own ideas. I also want to arrange a few talks on topics appropriate to the audience (offers or suggestions welcome), and will look for other appropriate diversions too. | ||
Latest revision as of 16:25, 11 September 2007
Ideas for the EPICS Code-athon.
Who, What, Where, When, How, ...:
- 1 week long, probably in early 2008
- Try to arrange a mutually agreeable date?
- Invite all core developers, as many others as possible (20?)
- Work on Base, Tests, Support modules and Extensions only (no applications).
- Move everything to an SVN repository first, so everyone has direct access?
- Plan some whole-group activities during the day:
- Discuss a new record support API — asynchronous, state machine, ...
- Anything from ILC? (Ask Claude to talk about OpenClovis?)
- Use 5th floor - nice environment, wireless network.
- Refreshments:
- Provide Pastries, Coffee/Soda, Snacks in room
- Lunch at cafeteria/401 Grill
- Social activities for evenings, or continue coding?
- Beer ...
- Dinner on Thursday night
Words for Ned's document
Coding Marathons, also called Hackathons (http://en.wikipedia.org/wiki/Hackathon ) or Code Sprints, are popular in a number of open source projects. APS would like to host a week-long EPICS Code-athon early in 2008 to work on some of the items on the EPICS To Do list. We will provide a comfortable environment with wireless networking, refreshments and space for up to 20 people to come and work on EPICS core development projects.
We hope that most of the EPICS core developers will be able to attend, and sites who wish to donate or develop expertise are invited to apply to send a staff member (who must have experience developing EPICS applications) to take one of the remaining places. All travel and expenses must be paid by the participant’s home institution, but that cost compares to that of attending an EPICS meeting. All participants must bring a laptop to develop on.
The projects to be worked on will be of general use to multiple sites; we will maintain a list, but attendees are invited to bring their own ideas. I also want to arrange a few talks on topics appropriate to the audience (offers or suggestions welcome), and will look for other appropriate diversions too.
