Page Comparison

Old Business

Developer Onboarding wiki pages for review and enhancement - /wiki/spaces/ADC/pages/894533891

Notes from last meeting:

Should Core Committers be responsible for the Resource for Developers section of the tech-docs, scavenge what is useful from the developer on-boarding resources and sunset the rest?

Some of it (especially what needs to be current with the latest release) should go to tech docs. Background info should stay and be marked as historical or unmaintained. 

This team should mark the pages they want moved to tech docs.  Once they're in tech docs, Core Committers is interested in their accuracy and maintenance but wouldn't want to be primarily responsible for them. 

Once tech docs is onboard, link to tech docs and say that they have moved to to tech docs. Mark is going to bring this up at the next tech-docs meeting.  

Lots of things being updated and making forward movement. 

New Business/Open Discussion

3.0 update

Everyone

Core Committers Mission/Community Engagement

One primary action item from the last meeting was the team's desire/need to move away from the current role of the group as primarily reviewing PRs to play a more active role in fostering a community of developers in ArchivesSpace. We discussed the possibility of hosting quarterly calls similar to the “office hours” the training corps is testing. These calls would include as many of the Core Committers as possible with a theme or topic for the call that would require about 10-15 minutes of “presentation” from a team member and then we’d take questions from a feedback form and on the fly. Hopefully community discussion will spring up naturally. I mocked up a working doc for us to keep the ball rolling on this discussion between meetings. I already put lots of my own thoughts on the doc, please do the same. You can find that at https://docs.google.com/document/d/168Je7iVUb2QspI_EdKpCCiQR-jO2vqcwA8RRwIcXwfw/edit?usp=sharing.

Notes from last month:

Pre-Covid/when Laney was on board the team felt more purposeful.  The group has felt adrift. 

This group may not be the best to address reviewing PR. The group is a lot and another commitment.  Is there value in that?

The conversations are valuable and great connections are being made.  Is there a way to increase those valuable conversations. 

There is a desire to have a better idea about the background and design of the application.

A larger discussion about how decisions are made in lots of different ways and places was had. Core Committers doesn't understand where information comes from or how decisions.  This group feels like it is operating in a vacuum/in the dark. 

This group could be the group to form a developer community.  How do we do that without giving an individual invite to people but make them feel empowered on their own? Could this group offer more mentorship/engagement.

The idea of an office hour or quarterly call for this group like the trainers came up. 

Merging PRs was important for the team to accomplish when there was one paid developer for ArchivesSpace.  Now there is less urgency and need for help with that. Some felt reviewing PR was personally valuable to if it isn't a value to ArchivesSpace, it may not be valuable anymore. Though there may be projects or short term need for someone to take point as reviewer.

Closed Pull Requests since April 12, 2021
(is:pr is:closed base:master merged:>2021-4-12)

44 closed