Developer's Meeting 21 October 2024

[tjlane]

Developer's Meeting

Topic: Docking Criteria Discussion
21 October 2024

Agenda:

• after a request, what needs to happen for a project to be included in the RSS GH org?
• what about the RSS homepage?
• who gets to decide these things and how is that done?

Attendees: Kevin / Doeke / Ali / TJ / Minhuan / Jack / Doris / Dennis

---

introduction

• @kmdalton There is a potential conflict: research code vs. production code. User centric vs. developer centric.

• Quickly converged to two-tier system: dev & production

• Polished code should be visible on rsstation.io

• Research: in the GH org

• All public repos, by necessity...

• Doeke: what is the scope of RSS?

• consensus: anything between detector and model finalization is fair game.

• @dennisbrookner, Doeke, @JBGreisman, Rick, @kmdalton are current GH owners

• For public inclusion: we'll use GH discussions

Criteria for beta / RSS GH inclusion

• Public form: new user a template to make a case
• An owner can sponsor, wait one week, if no objection: pulled in
• objection triggers wider internal discussion

Criteria for production / frontpage card status

• Documentation
• Welcome blog post
• Versioning
• Tests
• will follow same process as beta inclusion: application via form, then sponsorship and approval

Admittedly details are vague, this is partially on purpose. Keep things light. Lots of discretion for current owners.

Idea is to use meteor to pilot this application system.

Keeping things tidy

Idea is lots of freedom for devs, but we need to maintain quality. @JBGreisman: contract with users. We briefly discussed using periodic (annual?) review to keep quality high. Needs more thought.

• automation? stalebot help with this?

last things

Quarterly meetings? No one wants them.

Action:

• @dennisbrookner , update the website, make a cookie cutter repo
• @kmdalton : application for beta
• @tjlane: fill out the form
• @alisiafadini: blog post

[kmdalton]

Can I get feedback on this template? @tjlane @alisiafadini

[tjlane]

@kmdalton worked well! Here's some random feedback:

• maybe say to include user handles (@...) in the list of authors?
• should we add a section that asks why your project conforms to the beta vs production track? perhaps we should write down a few guidelines at some point...
• all important: we need better emojis for the Management and Repositories discussion cards