todogroup / working-hours

This repo is for tracking activities that we work on during TODO Group Work Days
15 stars 5 forks source link

Guide: Good first issue #26

Open Sealjay opened 2 years ago

Sealjay commented 2 years ago

Goal

Create a TODO Guide to improve content, submitted by @byjrack - topic: Good first issue

"Good First Issue" and more focused project engagement for the enterprise/end user communities With the significant increase in "end user" communities by organizations there is a base recognition that FLOSS is important and they need to be involved Many first issues are focused on the individual developer, but organizational motivations and barriers are likely different

  • Entering into contacts (DCO, CLA, etc) can be a challenge
  • Organizational contribution policy may not exist and the project can help direct key org decision makers to communities like TODO to establish one
  • Organizations may not use a FLOSS project directly, but through the lens of a commercial service or distribution so value of contribution may be blocked
  • Contribution opportunity may be unclear and undervalued within the organization leading to a lack of incentive structure (and potentially significant risk)

I think we can learn a bunch from the DNI efforts in the ecosystem and while the causes are significantly different I see much of the same results (apathy, frustration, etc) Goal would be to provide handles for "what's next" after that corporate investment to support broader engagement by that organization

Description

This was ideated in https://github.com/todogroup/work-day-activities/issues/19 and https://github.com/todogroup/todogroup.org/issues/143

Action Items