Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »



 Table of Contents



Topic suggestions for work during the November 2020 Developer Congress.  Please follow checklist below for submitting your proposed topic.  An accompanying issue, where additional details can be provided, can be added to the 2020 Developer Congress Project Issue Board.

Topic Proposal Checklist

Example

Title: Update ActiveFedora to work on Fedora 5.
Description: We have a branch sitting around that almost gets ActiveFedora working with Fedora 5, we could work together to get this passing.
Links: https://github.com/samvera/active_fedora/tree/fedora_5
Proposed By:   Trey Pendragon (Slack: @tpendragon)
Facilitator: Seeking a facilitator.

NOTE: Put this information in the Proposed Topics table below.

Proposed Topics

You can...

  • add a topic to the table of proposed topics below (See Topic Proposal Checklist and example above for guidance on proposing a topic.)
  • identify yourself as a facilitator for a topic you propose or a topic proposed by others (See Facilitator Guide below.)
  • indicate your interest in one or more topics


TitleDescriptionLinksProposed ByFacilitatorSignup

















































Facilitator Guide

If you're facilitating a topic we recommend you provide these resources to attendees:

Goal of this template is to enable leaders of specific issues to be able to collect resources for those interested in contributing; aiming to provide a shared knowledge base before beginning the work together.

  • Propose your issue or topic in the Proposed Topics table above
  • Time estimate how long the session will last (For example: 3hrs, (2) 8hr days, etc.)
  • Provide zoom link or slack room link that will be used for contributors to gather
  • Include list of GitHub issues that are related to the specific issue
  • Include list of languages a contributor should be familiar with
  • Include list of repositories that the group will be using as resources
  • Prep your 60 second summary for the kick off introduction on first day


  • No labels