Create a social media/ blogging presence to share updates publicly?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content
Research direction
No files, tests, or entry points are identified. Start by comparing the proposed channels: the CfP website, GitHub Projects, Instagram, Facebook, LinkedIn, a project website, and Substack. Done requires a decided public-update approach, but the issue does not define which channel or implementation is wanted.
Written by the indexing model from the issue text.
Description
Came up in the context of talking about potential friends/partners of the project and how to keep them up to date (hopefully in a not-too-technical manner).
- project updates on the CfP website?
- GH projects updates?
- social media (IG, FB, LinkedIn)?
- blog on our own (yet to built) website?
- blog on a platform (Substack...?)?
- Dominant language
- Java
- Stars
- 16
- Forks
- 5
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 23
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeForPhilly/benefit-decision-toolkit
-
documentation Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#519 ·
Maintainers usually reply within 1 day
-
documentation quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#445 ·
Maintainers usually reply within 1 day
-
Make issue templatesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/benefit-decision-toolkit#425 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
CodeForPhilly/benefit-decision-toolkit#525 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CodeForPhilly/benefit-decision-toolkit#524 ·
Maintainers usually reply within 1 day
All issues in CodeForPhilly/benefit-decision-toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/intellij-quarkus#1626 ·
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/product-integrator-mi#5061 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
quarkiverse/quarkus-roq#1277 ·
Maintainers usually reply within 1 day
-
Typos in page footerOpen
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/logging-site#48 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/maven-surefire#3496 · 3 comments ·
Maintainers usually reply within 1 day