-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add a 'current-work' location to allow people to highlight current areas of focus or interest #250
Changes from 5 commits
a2cd7bd
d8e0889
817f458
6de09e5
f43212a
5a359e3
b931c1c
588240d
34bdd48
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# 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 log their current areas of focus or interest 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 focus on the "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. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd change 'focus on the "important things"' to 'respond to the most immediately important things' or something of that sort. This is about responding to each other, rather than priorities in general. |
||
|
||
### 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, only those who are actively contributing should look at add items to the list. | ||
Relequestual marked this conversation as resolved.
Show resolved
Hide resolved
|
||
To add items to the list, either make commits directly, or make a PR and then nudge someone to approve it. | ||
If you'd like permission to commit to the repo, please do ask. | ||
|
||
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/> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 commentThe 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. There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
``` | ||
|
||
</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. |
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/> |
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.
Can we change "log their current areas of focus or interest" to "indicate which areas of their work most require attention from the core team members"?