Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CONTENT] FAQ: Add answers to common questions by IF companies and portfolio managers #35

Open
jwflory opened this issue May 20, 2021 · 1 comment
Assignees
Labels
C: content Improvements or additions to published articles, content, and/or documentation T: new change Adds new capabilities or functionality

Comments

@jwflory
Copy link
Member

jwflory commented May 20, 2021

Content classification

Is this about an existing page or a request for a new one?

Existing page.
The URL for the existing page is: https://unicef.github.io/inventory/faq/

Content description

In a recent workshop, several Office of Innovation portfolio managers and colleagues shared common questions and doubts they see about Open Source. In an effort to better answer common questions that come up across cohorts, the FAQ makes a better catch-all category for answers that might not belong to a larger content of section yet.

The questions from the workshop are listed below:

  1. What are governance models for Open Source tech projects?
  2. What license do we use?
  3. How do you make money if you are Open Source?
  4. How can you be financially sustainable with an Open Source business model?
  5. Does this mean we will no longer be profitable?
  6. How do you handle privacy if everything is Open Source? Is it less secure?
  7. What is the benefit for them?
  8. Miscellaneous questions about patents and patent law
  9. How do you collaborate with other developers?
  10. What are DevOps / infrastructure deployment best practices for Open Source software?
  11. How do we decide what components should be Open Source?
  12. "So we'll become a non-profit? Who will own our company?"
  13. How do you safely and ethically create open data from an existing dataset?
@jwflory jwflory added C: content Improvements or additions to published articles, content, and/or documentation T: new change Adds new capabilities or functionality labels May 20, 2021
@jwflory jwflory self-assigned this May 20, 2021
@jwflory
Copy link
Member Author

jwflory commented Sep 17, 2022

Related to unicef/inventory-hugo-theme#162.

@jwflory jwflory moved this from Backlog to In progress in Open Source @ OoI Ventures Oct 6, 2022
jwflory added a commit that referenced this issue Oct 7, 2022
This commit reworks the Frequently Asked Questions (F.A.Q.) page on the
site to include more useful information about the UNICEF Open Source
Inventory, how it is maintained, who is responsible for it, how to
contribute, and more.

This also changes the file from an AsciiDoc to Markdown file because the
content inside of the FAQ shortcodes must be Markdown in order to
render. Therefore, it does not make sense to keep the file as AsciiDoc
when all the contents of the file are written in Markdown.

Closes #35.
Closes unicef/inventory-hugo-theme#162.

Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <[email protected]>
@jwflory jwflory moved this from In progress to Pending review in Open Source @ OoI Ventures Oct 7, 2022
jwflory added a commit that referenced this issue Oct 7, 2022
This commit reworks the Frequently Asked Questions (F.A.Q.) page on the
site to include more useful information about the UNICEF Open Source
Inventory, how it is maintained, who is responsible for it, how to
contribute, and more.

This also changes the file from an AsciiDoc to Markdown file because the
content inside of the FAQ shortcodes must be Markdown in order to
render. Therefore, it does not make sense to keep the file as AsciiDoc
when all the contents of the file are written in Markdown.

Closes #35.
Closes unicef/inventory-hugo-theme#162.

Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: content Improvements or additions to published articles, content, and/or documentation T: new change Adds new capabilities or functionality
Projects
Status: Pending review
Development

Successfully merging a pull request may close this issue.

1 participant