-
-
Notifications
You must be signed in to change notification settings - Fork 57
Add a 'current-work' location to allow people to highlight current areas of focus or interest #250
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a2cd7bd
Add a 'current-work' location to allow people to highlight current ar…
Relequestual d8e0889
Add first thing of focus to the list
Relequestual 817f458
Fix formatting
Relequestual 6de09e5
Fix formatting for focus list template
Relequestual f43212a
Fix show/hide template in readme for listing things
Relequestual 5a359e3
Fix grammar
Relequestual b931c1c
Remove suggestion to use PRs for current-work list updating
Relequestual 588240d
Fix grammar
Relequestual 34bdd48
Updated current work readme
Relequestual File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| # The JSON Schema Organization's areas of focus or interest | ||
|
|
||
| ## About | ||
| ### What is this space? | ||
|
|
||
| During an [Open Community Working Meeting](https://github.com/json-schema-org/community/issues/244), it was suggested that we could have a place for the core team (and maybe active community members?) to indicate which areas of their work most require attention from the core team members, in the form of GitHub Issues, Pull Requests, and Discussions. | ||
|
|
||
| ### Why? | ||
|
|
||
| We concluded there was a LOT of activity taking place, and it was hard to get people to respond to the most immediately important things. It is indeed hard to focus on priority items when there are many new GitHub Issues and Discussions each week, especially for those who are community members or not working on JSON Schema full or even part time. It was suggested that by asking for one to three items of priority, we might find it easier to draw attention where we feel it is needed. | ||
|
|
||
| ### How? | ||
|
|
||
| The process will initially be manual and require people to commit to the adjacent file which contains the list. | ||
| The list will be used as it is found on Friday to help assist populate the following Monday's Open Community Working Meeting agenda. | ||
| We may introduce automations to assist in this at a later point, or a medium that isn't storing data in a text file. | ||
|
|
||
| #### How should the file be updated? | ||
|
|
||
| Initially, it's expected that only those who are actively contributing should look at or add items to the list. | ||
| To add items to the list, make commits directly in this repo. | ||
| If you'd like permission to commit to the repo, please do ask on our [Slack server](https://json-schema.org/slack) in the `#community` channel. | ||
|
|
||
| If you're adding to the list for the first time, please copy the below template, and add your GitHub username in alphabetical order. | ||
|
|
||
| <details> | ||
| <summary>Show/hide template</summary> | ||
|
|
||
| ```md | ||
| **Link:** [Link to Github Issue, Pull Request, or Discussion]<br/> | ||
| **What?:** [The most simplest basic explanation of what the thing is about. Think a single tweets length or less.]<br/> | ||
| **Why does it matter?:** [Pitch why people should care about this too. Why do you care about it?]<br/> | ||
| **What can we do?:** [What would you like us to do in relation to this thing?]<br/> | ||
| ``` | ||
|
|
||
| </details> | ||
|
|
||
| ### Show me the details | ||
|
|
||
| OK! Great! You want [the-list.md](./the-list.md) | ||
|
|
||
| ## More? | ||
|
|
||
| @relequestual had some ideas on how automation could make this easier to use and encourage engagement, but it lead to a rabbit hole of questions and looking at docs and there wasn't any low-hanging fruit to be had. He intends to write up some suggestions on this soon. | ||
|
|
||
| ## I have a suggestion on this process... | ||
|
|
||
| Great, let's hear it! Create a new [Discussion](https://github.com/json-schema-org/community/discussions) and let's talk. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| # The JSON Schema Organization's areas of focus or interest | ||
|
|
||
| ## What is this document? | ||
|
|
||
| Please see the adjacent [README](./README.md). | ||
|
|
||
| ## The lists of things | ||
|
|
||
| ### @relequestual | ||
|
|
||
| **Link:** https://github.com/json-schema-org/community/pull/250<br/> | ||
| **What?:** Creating this file and the guide on how to use it<br/> | ||
| **Why does it matter?:** People feel it would be easier to see areas of focus if we highlight them<br/> | ||
| **What can people do?:** Review and approve this PR! =]<br/> |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a situation where this is anything other than "look at it and respond"? This question feels like unnecessary boilerplate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it could be you want someone to review the PR, or maybe you just want thoughts so far. Maybe you're looking to tackle one last bit relating to a specific comment. If it's a Discussion, it might be a specific thread you want people to reply to. IDK. Assumptions bad.
If we find it not useful, we can remove it later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I want something specific looked at I'll say so in the entry. This line just feels like an annoyance and I don't plan to include it in my entries. This is supposed to be the easiest possible process for us to draw attention however we need it. I really don't like boilerplate - I'm not going to block the PR over it, but I don't like it.