or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Annual Developer Sprint Week
Hi Andy,
Thanks for considering our request. I've responded to your questions (inline) below. We are fairly flexible, so we are happy to work within your constraints.
Since we are planning to ask a lot from attendees leading up to, during, and after the meeting, we won't know who can attend until we finalize the dates. And we won't know what we can work on until we know who is attending. I understand this makes planning difficult and we will need to be flexible.
On Thu, Oct 20, 2022 at 10:46 AM Andrew J Connolly ajc@astro.washington.edu wrote:
We could, but hadn't planned on it. We will do a lot of pre-meeting work organization and planning, so folks will have a clear idea of what they will be working on and with who. If there is a space we can all be in, it could be useful. But it is not a requirement by any means.
We expect the work group sizes to be between 2 and 10 people. The workgroups will likely not stay the same for the entire week. Ideally, we would have access to:
We can also use a bigger room and just separate ourselves into smaller groups.
We'd be happy to give one or two talks on Scientific Python, NetworkX, scikit-image, etc., as long as the other summit participants can keep working during that time.
Best regards,
Jarrod
Moved to the SP archive
Goals of the meeting
The developer sprint week (i.e., 5 days and 6 nights) aims to provide an opportunity for ~30-50 developers from across the core scientific python libraries to produce significant progress in the following 3 areas:
Joint infrastructure sprint
Better coordination of core projects
Shared development vision
Strategic plan for the next decade
Our community has never before engaged in a deliberative pro-
cess to try and anticipate future challenges.
The strategic plan will identify core needs and future challenges of
the scientific Python community. Rather than focusing on the technical details of one particular core project, the strategic plan would discuss the challenges shared by more projects. The plan will also be used by the community
for support when applying for federal grants.
Participants
Q: ~30-40 seems to trivially fit into eScience space. What is the real maximum number, if we don't need to fit everyone in the same room at once? (if no talks are planned?)
scienfic python ecosystem steering committee
1 Anderson Banihirwe (core: xarray)
2 Brigitta Sipőcz (ecosystem, domain: astropy)
3 Elliott Sales de Andrade (core: mpl)
4 Georgiana Dolocan (core: jupyter)
5 Jarrod Millman (core: networkx)
6 Joris Van den Bossche (core: pandas/scikit-learn)
7 Juan Nunez-Iglesias (core: scikit-image)
8 Juanita Gomez (ecosystem community)
9 Kira Evans (domain: napari)
10 Kristen Thyng (?? JOSS)
11 Lucy Liu (?? scikit-learn contributor experience)
12 Madicken Munk (domain: yt)
13 Matthias Bussonnier (core: ipython)
14 Melissa Weber Mendonça (core: numpy/scipy)
15 Paul Ivanov (core: jupyter)
16 Ralf Gommers (core: numpy/scipy)
17 Ross Barnowski (core: numpy/networkx)
18 Stéfan van der Walt (core: scikit-image/numpy)
community managers
https://scientific-python.org/about/#community-managers
TBD core scientific python projects, people not already in the list above
TBD domain projects (still, we need developers from those projects and not the PIs/scientists/etc)