Skip to content

Commit 1b5d213

Browse files
Merge pull request #41 from oss-slu/project-meltshiny
Project meltshiny
2 parents 7fefb6f + f5a6772 commit 1b5d213

File tree

10 files changed

+186
-42
lines changed

10 files changed

+186
-42
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: New Contributor
3+
about: Template to add someone as a new contributor.
4+
title: "[DATE]: [FEATURE NAME]"
5+
labels: contributor, needs triage
6+
assignees: octocat
7+
---
8+
9+
We are excited you want to [become an Open Source with SLU contributor](#21). The success of our projects depends on active involvement. If you want to be recognized as a contributor:
10+
11+
- [ ] Add your name to the list in `docs/about/contributors.md`;
12+
- Each entry must include a name;
13+
- Each entry may optionally include a link to a GitHub user profile;
14+
- Add your entry to the end of the list.
15+
- [ ] Add a link to merged Pull Request or a closed Issue in an OSS [project](https://oss-slu.github.io/docs/portfolio) to this Pull Request. You can use the autolinked references formats for [issues and pull requests](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#issues-and-pull-requests).

docs/about/about.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,17 @@ title: About Us
44
custom_edit_url: null
55
---
66

7-
Open Source with SLU was established to help SLU researchers with their custom software needs and to give students practical software development experience. The program is funded by a grant from Alfred P. Sloan foundation and employs Computer Science graduate students to prototype, design, and deliver open-source software to help SLU researchers and their collaborators worldwide. Undergraduate students enrolled in project-based courses work with Open Source with SLU under the mentorship of our graduate students to contribute to ongoing open source projects.
7+
Open Source with SLU was established to help SLU researchers with their custom software needs, and to give students practical software development experience. The program is funded by a grant from the Alfred P. Sloan Foundation, and employs Computer Science graduate students to prototype, design, and deliver open-source software to help SLU researchers and their collaborators worldwide. Undergraduate students enrolled in project-based courses work with Open Source with SLU under the mentorship of our graduate students to contribute to ongoing open source projects.
88

99
## Leadership Team
1010

1111
### Daniel Shown
1212

13-
Daniel Shown is the Program Director of the Open Source with SLU program. He handles the program's daily operations, builds connections with industry partners, works with internal and external clients of the program, guides and supports our graduate students. Daniel's focus is to ensure that the program follows its mission of research support, commitment to open-source, and providing students with relevant software development experience.
13+
Daniel Shown is the Program Director of the Open Source with SLU program. He handles the program's daily operations, builds connections with industry partners, works with internal and external clients of the program, and guides and supports our graduate students. Daniel's focus is to ensure that the program follows its mission of research support, commitment to open-source, and providing students with relevant software development experience.
1414

1515
### Kate Holdener, Ph.D.
1616

17-
Kate Holdener is an Assistant Professor of Computer Science at Saint Louis University. Her main focus in the department is on software engineering courses. She founded the open-source software program in an effort to engage more student in open-source development, as a way to give them practical experience during school.
17+
Kate Holdener is an Assistant Professor of Computer Science at Saint Louis University. Her main focus in the department is on software engineering courses. She founded the open-source software program in an effort to engage more students in open-source development, as a way to give them practical experience during school.
1818

1919
## Graduate Students
2020

@@ -23,6 +23,7 @@ Graduate students are at the heart of our open-sour​ce program. They work with
2323
### Current Graduate Assistant Team Leads
2424

2525
- Abhilash Kotha
26+
- Logan Wyas
2627
- Ruthvik Mannem
2728
- Sailikhita Pulijala
2829
- Yash Kamal Bhatia
@@ -37,12 +38,12 @@ Graduate students are at the heart of our open-sour​ce program. They work with
3738

3839
## SLU Research Team Leads
3940

40-
Staff from Saint Louis University's Research Computing Group have been key partners, and have even taken on the responsibility of leading teams of undergraduate students. Their work includes active open source projects being used in academia and research. Projects involve SLU researchers across campus, regional organizations such as the Taylor Geospatial Institute, Washington University in Saint Louis, Newberry Library, the Jesuit Archives, Missouri Botanical Garden, and the St. Louis Federal Reserve. They are also involved in international open standards groups such as the International Image Interoperability Framework (IIIF) and Open Geospatial Consortium (OGC). This team supports the popular public tools TPEN ([t-pen.org](https://t-pen.org)) and the Rerum ecosystem ([rerum.io](https://rerum.io)).
41+
Staff from Saint Louis University's Research Computing Group have been key partners, and have even taken on the responsibility of leading teams of undergraduate students. Their work includes active open-source projects being used in academia and research. Projects involve SLU researchers across campus, regional organizations such as the Taylor Geospatial Institute, Washington University in Saint Louis, Newberry Library, the Jesuit Archives, Missouri Botanical Garden, and the St. Louis Federal Reserve. They are also involved in international open standards groups such as the International Image Interoperability Framework (IIIF) and Open Geospatial Consortium (OGC). This team supports the popular public tools TPEN ([t-pen.org](https://t-pen.org)) and the Rerum ecosystem ([rerum.io](https://rerum.io)).
4142

4243
### Patrick Cuba
4344

44-
Patrick Cuba is the IT Architect for RCG at SLU. His service is focused on consulting and project development, translating research questions into features and helping to accellerate human-driven research. Specifically, he designs, develops, and implements technological solutions for use cases that escape typical vendor solutions, usually because of requirements for sustainability, openness, or customizable encoding. He has a passion for the record of human knowledge, especially supporting controversy, ambiuguity, and attribution.
45+
Patrick Cuba is the IT Architect for RCG at SLU. His service is focused on consulting and project development, translating research questions into features, and helping to accelerate human-driven research. Specifically, he designs, develops, and implements technological solutions for use cases that escape typical vendor solutions, usually because of requirements for sustainability, openness, or customizable encoding. He has a passion for the record of human knowledge, especially supporting controversy, ambiguity, and attribution.
4546

4647
### Bryan Haberberger
4748

48-
Bryan Haberberger is the Full Stack Developer for RCG at SLU. He works in the technology stacks behind various projects, and his focus shifts sprint by sprint. Simply put, he is a professional developer on campus and a resource for faculty, staff, students and outside collaborators looking for software development expertise, especially in the realm of Web Applications. In recent years, he has accrued specialized skills with geospatial data on the web and is a member of the Open Geospatial Consortium as well as a IIIF Maps TSG co-chair as part of his commitment to open source technologies.
49+
Bryan Haberberger is the Full Stack Developer for RCG at SLU. He works in the technology stacks behind various projects, and his focus shifts sprint by sprint. Simply put, he is a professional developer on campus and a resource for faculty, staff, students, and outside collaborators looking for software development expertise, especially in the realm of Web Applications. In recent years, he has accrued specialized skills with geospatial data on the web and is a member of the Open Geospatial Consortium, as well as an IIIF Maps TSG co-chair, as part of his commitment to open-source technologies.

docs/about/community.md

Lines changed: 35 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,52 @@
11
---
22
id: community
3-
title: Community Engagement
43
custom_edit_url: null
54
---
5+
66
# Community Partners
77

88
## About
9+
910
We welcome the participation of anyone interested in contributing to the projects in our portfolio. You can work on open issues on projects in our portfolio, create a new issue, or e-mail us if you want to be more involved.
1011

12+
Join the conversation in the Open Source with SLU [Slack workspace](https://join.slack.com/t/oswslu/shared_invite/zt-24f0qhjbo-NkSfQ4LOg5wXxBdxP4vzfA).
13+
14+
## Overview
15+
16+
* Join our Slack workspace.
17+
* Contribute changes to an Open Source with SLU project.
18+
* Add your name to the Contributors list.
19+
* After making five contributions, you can be added to the `oss-slu` team in GitHub by contacting one of the program staff.
20+
21+
## Getting Startted
22+
23+
The success of our projects depends on active involvement. Anyone interested in getting involved with Open Source with SLU projects can sign up by opening a [Pull Request (PR)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) on the [contributors](contributors.md) page in this website. The PR will be merged when the Pull Request includes a link to a merged ticket from a project in the [portfolio](../portfolio.md) that they made contribution to, and the PR has been approved by the current tech lead on that project.
24+
25+
If you want to be recognized as a contributor, your pull request should include your name and a link to the work you have completed on an Open Source with SLU project.
26+
27+
* [ ] Add your name to the list in `docs/about/contributors.md`;
28+
* Each entry must include a name;
29+
* Each entry may optionally include a link to a GitHub user profile;
30+
* Add your entry to the end of the list.
31+
* [ ] Add a link to an already merged Pull Request or a closed Issue in an OSS [project](https://oss-slu.github.io/docs/portfolio) to your Pull Request. You can use the autolinked references formats for [issues and pull requests](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#issues-and-pull-requests).
32+
33+
## Join the `oss-slu` Team
34+
35+
After making five contributions, you can be added to the `oss-slu` team in GitHub by contacting one of the program staff. Send an e-mail to <[email protected]> or a slack message to the current Tech Lead on the project(s) you made contributions to. Include a list of at least five closed Issues and/or merged Pull Requests that you worked on.
36+
1137
## Git
12-
All our projects are stored in public GitHub repositories. To make code contributions to our repositories, you will need to know the basics about Git and GitHub. We recommend this <a href="https://youtu.be/RGOj5yH7evk">video tutorial</a>, if you are not familiar with these tools.
38+
39+
All our projects are stored in public GitHub repositories. To make code contributions to our repositories, you will need to know the basics about Git and GitHub. We recommend this [video tutorial](https://youtu.be/RGOj5yH7evk), if you are not familiar with these tools.
40+
1341
## Guidance
42+
1443
When you are ready to contribute code to one of our open-source project, here is the process you should follow:
44+
1545
1. Identify the issue you want to work on and post a comment in this issue, asking the repo maintainer to assign the issue to you.
16-
2. Crate a fork of our repository. Here is GitHub documentation for how to <a href="https://docs.github.com/en/enterprise-cloud@latest/get-started/quickstart/fork-a-repo">create a fork</a>
17-
3. Clone your fork of the repository. Here is GitHub documentation for how to <a href="https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository">clone a repository</a>.
46+
2. Crate a fork of our repository. Here is GitHub documentation for how to [create a fork](https://docs.github.com/en/enterprise-cloud@latest/get-started/quickstart/fork-a-repo)
47+
3. Clone your fork of the repository. Here is GitHub documentation for how to clone [a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository).
1848
4. Follow the developer guide to install project dependencies and run the code.
1949
5. Make the necessary code changes to resolve the issue. Commit and push your changes frequently. Use meaningful commit messages when committing your code.
2050
6. Test your changes, verifying that the issue is resolved.
21-
7. Create a pull request - a request to merge changes from your fork of the repository to the original repository. Here is GitHub documentation for how to <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork">create a pull request</a>. Make sure to note the issue number that your pull request resolves, and include details of your solution.
51+
7. Create a pull request - a request to merge changes from your fork of the repository to the original repository. Here is GitHub documentation for how to [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). Make sure to note the issue number that your pull request resolves, and include details of your solution.
2252
8. One of our repository maintaners will review your pull request and will either merge it with the original repo, or request some changes. If changes are requested, go back to step 5 and proceed from there.

docs/about/contributors.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
id: contributors
3+
custom_edit_url: null
4+
---
5+
# Contributors
6+
7+
These people have contributed to Open Source with SLU projects. They have been added in (approximately) the order in which they became contributors.
8+
9+
- [Kate Holdener, Ph.D](https://github.com/kate-holdener)
10+
- [Daniel Shown](https://github.com/kungfuchicken)

docs/about/partners.md

Lines changed: 24 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -10,37 +10,33 @@ Open Source with SLU welcomes opportunities to partner with community outreach p
1010

1111
## Capabilities
1212

13-
+ Developing a new generation of workforce: hands-on experiences in software engineering and open source software ecosystems
14-
+ Software development & maintenance
15-
+ AI and ML tools
16-
+ Web, mobile, and desktop apps
17-
+ IoT and cyber-physical systems
18-
+ Research support.
19-
+ Idea generation through short-term events.
20-
+ Innovations by sustained development efforts.
21-
+ Maintenance of existing software repositories.
22-
+ Open Scholarship and Open Work strategies.
23-
+ Open source community and ecosystem building
24-
+ Research software translation for community and industry impact
13+
- Developing a new generation of workforce: hands-on experiences in software engineering and open-source software ecosystems
14+
- Software development & maintenance
15+
- AI and ML tools
16+
- Web, mobile, and desktop apps
17+
- IoT and cyber-physical systems
18+
- Research support
19+
- Idea generation through short-term events
20+
- Innovations by sustained development efforts
21+
- Maintenance of existing software repositories
22+
- Open Scholarship and Open Work strategies
23+
- Open-source community and ecosystem building
24+
- Research software translation for community and industry impact
2525

2626
## Opportunities
2727

28-
+ Exploratory development
29-
+ Proof of concept
30-
+ Feasibility studies
31-
+ Skilled talent
28+
- Exploratory development
29+
- Proof of concept
30+
- Feasibility studies
31+
- Skilled talent
3232

3333
## Get Involved
3434

35-
+ Internships
36-
+ Mentorships
37-
+ Sponsored events
38-
+ Partners on projects
39-
+ Sponsor student teams
40-
+ FLOSS thought leadership
41-
+ Community advisory board
42-
+ Industry consortium membership
43-
44-
45-
46-
35+
- Internships
36+
- Mentorships
37+
- Sponsored events
38+
- Partners on projects
39+
- Sponsor student teams
40+
- FLOSS thought leadership
41+
- Community advisory board
42+
- Industry consortium membership

docs/about/students.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ custom_edit_url: null
88

99
## About
1010

11-
Teams of students form the core of our efforts developing open source software. Our initial program is structured around teams of 2-4 undergraduate Computer Science students enrolled in the capstone course. Each team of undergraduate students has an assigned Tech Lead, usually a Graduate Student and sometimes a faculty or staff member. Regular project deliverables are expected from each team. Many teams work on sustainment of existing software codebases, and sometimes teams work on new projects.
11+
Teams of students form the core of our efforts developing open-source software. Our initial program is structured around teams of 2-4 undergraduate Computer Science students enrolled in the capstone course. Each team of undergraduate students has an assigned Tech Lead, usually a Graduate Student and sometimes a faculty or staff member. Regular project deliverables are expected from each team. Many teams work on sustainment of existing software codebases, and sometimes teams work on new projects.
1212

1313
## Guidance
1414

15-
Specific guidance for students working on Open Source with SLU projects goes here...
15+
Specific guidance for students working on Open Source with SLU projects is forthcoming...

docs/portfolio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ We are currently accepting project requests. You can submit your request via thi
2222
- ![DEER](project_deer/deer_100.jpg) **[Data Entry & Exhibition for Rerum](project_deer/about)** A designer's framework for non-destructive annotation and template rendering for distributed digital resources and collections.
2323
- **[Drone World](project_droneworld/about)** - DroneWorld is a platform for testing small unmanned aerial systems (sUAS) applications by simulating realistic test scenarios based on specified requirements.
2424
- [Gallery of Glosses](./project_gallery_of_glosses/about) - Interfaces to view and manage Glosses.
25-
- MeltShiny
25+
- **[MeltShiny](project_meltshiny/about)** - automates the analysis and visualization of DNA melting curves for researchers in chemistry, biology, and genetics..
2626
- ![Mouser](project_mouser/100x100.png) [**Mouser**](project_mouser/about) - This software is used for tracking the data of animal experiments.
2727
- **[Pi4Micronaut](project_pi4micronaut/about)** - A Java library crafted for developers who aim to build IoT applications leveraging the Raspberry Pi platform.
2828
- **[Rerum Geolocator](project_rerum_geolocator/about)** - The application enables users to enhance discovery and access to digital resources through geographic visualization and annotation.

0 commit comments

Comments
 (0)