-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
CfAMeeting2011Agenda
Wednesday
This day will be devoted to general discussions about coordinating efforts to develop AstroPy.
10:30am |
Coffee / snacks / video setup |
11:00am |
Introduction Each participant introduces themselves (name, institution, experience, interests). We need to keep this short, less than a minute for each participant. |
11:20am |
Agenda Go briefly over the agenda, and add any missing items. |
11:30am |
Progress made so far Summary of progress made so far via the mailing list |
11:40am |
Development workflow Discussion session on the development process for affiliated packages and for the core package. The discussion will center around the existing workflow for development. Detailed agenda
|
1.00pm |
License Short discussion to decide what license AstroPy should be developed/released under. Detailed agenda
|
1:15pm |
Lightning talks
|
1:30pm |
Lunch |
2:15pm |
Initial areas of development The coordination committee will propose a set of initial areas of development, and the purpose of this discussion will be to discuss these, identify missing initial areas, and agree on a final list. The aim will then be to identify participants who would be willing to -- at least temporarily -- coordinate the efforts for a specific area of development. This does not imply a definite choice, but more that after the meeting these coordinators can then try and get all people interested in that area to start coordinating efforts, including potentially decide on a longer term coordinator. But leaving the meeting, we should have at least a volunteer for each area of development to ensure that things get started. We can then discuss how we expect the design of affiliated packages to work. Should affiliated package teams inform the rest of the developers of their design plans for the package, and wait for it to be approved before going ahead with coding? Finally, we can discuss how to best communicate during the development process. Are we worried about driving people away from the astropy mailing list? Should we create astropy-dev? Should each affiliated package team have their own method of communication and only communicate via astropy-dev when reporting back to the overall group, or should all discussions be done via astropy-dev for the record? Detailed agenda
|
3:45pm |
Lightning talks
|
4:00pm |
Afternoon break |
4:30pm |
Long-term transition Discussion session on how we envisage the transition to AstroPy over the next few years. Detailed agenda
|
5:30pm |
Timeline and milestones Discussion session on timeline and milestones for the project. The aim will be to decide whether we want to set any milestones for inclusion of the initial affiliated packages and for an initial public release. Detailed agenda
|
6:45pm |
Lightning talks (Online data access and sharing)
|
7:00pm |
Finish |
8:00pm |
Dinner at a local restaurant |
Thursday
This day will be devoted to more specific coding topics, and will include some hands-on work. The morning sessions will in all likelihood lead to work on the guidelines, core package, or template package being necessary. A session after lunch is planned for people to split into groups and implement these changes.
9:30am |
Coffee / snacks / video setup |
10:00am |
Testing framework Finalize the discussion that was carried out on the list regarding unittest vs nose vs py.test and designate a small group to update the testing guidelines. Detailed agenda
|
10:45am |
Core package layout Determine whether everyone is happy with the current layout of the core package, especially regarding interfacing to external C and python libraries. The current layout is available here One of the points to discuss will be whether we definitely want to go ahead with the idea that we provide any required external C library in Detailed agenda
|
11:30am |
Template package layout Discuss what steps need to be taken to finalize the template package so that coding can already start on Friday. The current template package is available here. Detailed agenda
|
12:10pm |
Lightning talks (Packaging and Releasing)
|
12:30pm |
Lunch |
1:15pm |
Splinter coding/writing session Break into groups to implement decisions from the morning. |
3:00pm |
Afternoon break |
3:30pm |
Each group designates someone to present the updated documents and packages. Subsequent discussion and modifications if needed. |
5:30pm |
Brief discussion on possibility of a logo/website design competition |
6:00pm | Finish |
If time permits, we can also discuss the following topics:
- Funding possibilities
- Packaging/distribution issues