terranexum / flowgrow Goto Github PK

Prepare documentation on how GitHub is to be used to keep track of issues, establish when development milestones are met, and how to report progress in terms of issues, hours, milestones, and contributors over time. Being able to generate such a report to share with collaborators and backers would be great.

Determine the pros/cons of various social media schedulers, select one, and start loading content according to the calendar

Develop documentation for GitHub Issues on how to log hours - if there is a custom field in GitHub or a GitHub integration to a user-friendly time tracking program (a browser extension?), use this to log hours.

Set up a GitHub integration with Discord so that contributors in our Discord can be notified about new issues, comments, and task updates.

Implement a GitHub integration from OpenCollective to the TN website to showcase our backers and contributors

Our Discord integration with GitHub (developed in an earlier issue) allows notifications in a channel of when new issues, comments, and task updates arrive. These should then be integrated into relative materials/insights for social media updates with generative AI assistance if possible.

Incoming content (comments/messages/feedback) being replied/responded to with how TN's work can help solve the identified problems would be easier to write if a notification comes in to Discord that matches a suitable content label (pull request notifications do not need replying to), and this triggers the production of a reply that then gets written and approved by a contributor before they add it to the content calendar.

Content may get handled by generative AI but the format and layout of such content can always use creative layout skills. This could be done in Canva, then exported to Google Slides or Google Docs as needed.

Open hardware projects (OpenQuantum, OpenCarbon/CarbonWall, any IoT or electronic circuitry projects, etc.) should reside on our community page on Hackster.io. Documentation should be provided on Hackster.io and linked to GitHub Issues whenever updates are desired. Set up the page and individual projects and provide their links in documentation here for how to contribute to hardware projects.

When milestones are reached or issues are resolved, APIs or third-party integrations should be used to gather this information and share it with the community.

Two types of posts that will be useful:

1. Project Updates: Milestones, new features, major project developments
2. Resolved Issues: Success stories and/or improvements made (not automatic notifications from GitHub when issues close, but could reuse some content from those issues)

Develop a template of nice content to thank those who are helping us both financially and through providing their time that draws from the reported results from GitHub Issues, milestones, and other notable news. This should be automated in some way with code provided here on FlowGrow so others who reuse our code can do the same. Keeping the community up to date is essential.

Two types of content that should be developed:

1. Contributor Spotlights: Financial and time contributors
2. OpenCollective Updates: New backers, financial/time contributions, use of time and funds

On OpenCollective, set up the ability for new contributors to choose whether they wish to contribute in terms of money, time, or both.

Implement a GitHub integration from OpenCollective to the GitHub README here to showcase our backers and contributors

Investigate how to get GitHub issues over to our timebanking site on hOurworld.org: https://hourworld.org/bank/index.htm?hw=2094. 35,000 members there all over the world. Provide notes below in this issue's comments on how this might be accomplished and if it is possible, please prepare documentation on how this might be done.

Prepare documentation on how to use labels in GitHub Issues to categorize tasks as to which teams they should go to, to be used perhaps in auto-routing these to the appropriate contributors. Such categories can include marketing, development, design, testing, hardware, software, etc.

Determine how to get LinkedIn company page and comment notifications to GitHub as new issues - an issue template just for these would be great. These would then be visible in Discord when they come in, and replies can be discussed before closing out the issue by doing the following:

1. writing appropriate content for the reply after discussion, as needed
2. replying to the comment/message with good material that may inspire more discussion and thus more written content later
3. suggesting updates to our content strategy and product development depending on audience feedback received

This will help provide us with content CI/CD (continuous improvement/continuous delivery) from every post to enable us to always be aware of our community, its changing needs, and to respond quickly in the most agile manner.

Describe a strategy for automating how the following types of content can be customized for improved readability and interactivity before being added to a social media scheduler like Buffer or Hootsuite:

Content Calendar from Contributors
Contributor Spotlights - Financial and time contributors
OpenCollective Updates - New backers, financial/time contributions, use of funds
Project Updates - Milestones, new features, major project developments
Resolved Issues - Success stories and/or improvements made
Important Announcements - Project or organization

Develop documentation on how task management and collaboration is to be done on GitHub Issues for new contributors - any task (issue) that hasn't been assigned is available for self-assignment and these can be discussed and collaborated on by anyone. Documentation will ideally reside in our public Google Docs space (link to be provided), with permissions set to anyone with the link can edit. The links can then be referred to on GitHub for a good balance of version control and easy collaboration among technical and non-technical collaborators.