# Meeting notes

## 09/06/2023

## 09/04/2023

* Thrust 1: (Ecosystem discovery)
AIM: To identify new application domains and stakeholders for the IronHacks Ecosystem!
Measurable outcome: reaching 2000 new types data scientists
* 1.1. Workshop with data providers (E.g. cyber security or image processing)
* Identify XX data providers
* Identify XX data sets
* 1.2. Classical Data Science Hacks for new types of data scientists using new types of data (e.g. security or image processing)
* 1.3. Analysis/Paper competition (Paperthon): Researchers would analyzse the data and come up with

* Thrust 2: Community building and OSS sustainability
* 2.1. Contribfest for developers 1:
* Github issues, ...
* 2.2. Steering community for sustainability
* Design of funding mechanisms
* BUsiness model design

Timeline:

1.1. M1 to M3
2.1. M2 to M6
1.2. M4 to M8
1.3. M6 to M11
2.2. M6 to M12

Here is also a paper about IronHacks architecture that could help: https://www.overleaf.com/project/64516bf102633688773705c7

## 08/24/2023

### Agenda

1. Letters

> Each letter writer should clearly describe how they have contributed and will continue to contribute to the development of OSE including the technical advancements enabled by these contributions and the value proposition associated with the product.

In addition to the above information, each letter of collaboration (not to exceed two pages) must contain the name of the letter writer, current affiliations, and relationship to the members of the proposing team.

We need letters from ~~potential~~current "users" and/or "contributors":

1. Users:
1. Researchers of data science & software engineering: they are trying to understand data science programming or software engineering practices(letter from: Stevens Institute Aron Lindberg, Purdue professor [e-mail])
2. Data Scientists: they want to use the platform (Winners from previous year; associations like informs or AIS or OCIS; )
3. Contributors
1. Data providers: they want their data to be studied (letter from: Safegraph (@sabine); State - Workforce Development (@harsha)
2. Developers: Professional and student developers (Matt @)

2. Diagram:
We could consider also using Guac as a source for data? And running Network analytics challenges with scholars in data science? @sa3hhkZtTWusxpL0vlpitA

Action items
- [ ] Get letters:
- [ ] Sabine (Stevens,CS purdue Prof, and Matt Harris)
- [ ] Manthan (Winners from previous years)
- [ ] Diagram:
- [ ] Santiago first pass before weekend and share in drive
- [ ] Sabine reviews
- [ ] Discuss

## 07/13/2023

### Agenda

- Overview of the POSE program
- [Link to NSF Grant](https://new.nsf.gov/funding/opportunities/pathways-enable-open-source-ecosystems-pose)
- [Call for POSE](https://new.nsf.gov/tip/updates/nsf-announces-solicitation-open-source-ecosystems)
- Deadline - Sept 7, 2023
- Decision is made: Planning grant $300,000
- [Empirica](https://empirica.ly/)
- Reverse engineer activities based on outcomes
- Gap: There is a unique OSS solution for an research platform for people studying programming in the cloud/ ML/data science in the cloud. Howver, it needs to grow into an OSS ecosystem, with an
- 1) a leadership team
- 2) org structure for managing the project
- 3) a distributed development process
- 4) a community of developers

see picture here
)
An example look at this:
https://www.otree.org/
Try to understand their ecosystem and the developer community
Empirica

- Phase 1: Project
-

- Open issue: Clarify users and developers()
- Goal:
(1) Discovery of users
(2) Discovery of hack makers (datasets submitters)
(2) Governance effort
- End users: Researchers (social scientists etc.) and hackers (data scientists)

### Action Items

- Letter of collaborations, identify potential collaborators that are willing to contribute (e.g. RCAC, Linux Foundation, Red Hat)
- Understand the key components of the ecosystem of Ironhacks: Conceptualize the ecosystem based on Figure 1 (use an annex in the proposal)
- check out the POSE proposal from santiago: it is in the folder "prior docs" - read it and use it to adapt the structure of the existing overleaf: sections should be adapted

>1. Letters of Collaboration (required)

>A minimum of three and up to five letters of collaboration from third-party users or contributors of the open-source product must be uploaded as Supplementary Documents. These letters of collaboration must be from current users or contributors (who are not directly related to the proposing team) of the open-source product that is the subject of the proposed OSE. Each letter writer should clearly describe how they have contributed and will continue to contribute to the development of an OSE. These letters do not have to conform to the standard format specified in the PAPPG. In addition to the above information, each letter of collaboration (not to exceed two pages) must include the name of the letter writer, current affiliations (institution or place of employment), and relationship to the members of the proposing team