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

Release History and Planning #1

Open
23 of 24 tasks
danbri opened this issue Apr 1, 2014 · 2 comments
Open
23 of 24 tasks

Release History and Planning #1

danbri opened this issue Apr 1, 2014 · 2 comments
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area.

Comments

@danbri
Copy link
Contributor

danbri commented Apr 1, 2014

Issue #1 tracks high-level plans for schema.org. It gives entry points for release-level issues as well as broader goals that correspond to rough milestones over the next year. In practice, these goals are pretty hit-and-miss w.r.t. people actually doing the necessary work, but they are reported here as aspirations and for discussion.

See also release history and draft next release.

Release plans

Issues Overview

We label issues by topic, workflow status. The most concrete milestone is the next upcoming release, which since April 2019 are monthly, officially on (and named for) the 1st of the month, but in practice released on the first working day following. Work in progress edits can be found on webschemas.org.

We try to avoid unlabelled issues. The most important labels and entry points are:

Historical Meeting agenda and notes

Steering Group background

Elaborating on http://schema.org/docs/about.html -

The day to day operations of Schema.org, including decisions regarding the schema, are handled by a steering group, which includes representatives of the sponsor companies and a small number of individuals who have contributed substantially to Schema.org and related standards. The steering group typically makes decisions by consensus. All members of the steering group have the same standing. The steering group is currently chaired by R.V.Guha, who does not represent his employer in this capacity. Discussions of the steering group are public, see https://groups.google.com/forum/#!forum/schema-org-sg (very rarely used; more often CC:'d threads with the W3C Community Group public list).

@danbri danbri self-assigned this Apr 1, 2014
@danbri danbri closed this as completed Apr 17, 2014
danbri pushed a commit that referenced this issue Sep 19, 2014
Syncing from Dan's repository
danbri added a commit that referenced this issue Dec 11, 2014
Modified property names as discussed in partners meeting, cleaned up com...
danbri pushed a commit that referenced this issue Dec 11, 2014
Tilid video game - updates from recent non-game changes
danbri pushed a commit that referenced this issue Mar 25, 2015
Sync with next iteration of sdo-gozer
vholland pushed a commit that referenced this issue May 14, 2015
Fixed json on "Top 5 covers of Bob Dylan Songs"
@danbri danbri reopened this May 27, 2015
@danbri danbri changed the title Re-implement acknowledgements Meta: schema.org planning May 27, 2015
@danbri danbri added status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. Extension Tracking labels May 27, 2015
danbri added a commit that referenced this issue May 27, 2015
chaals pushed a commit that referenced this issue Jun 22, 2015
chaals pushed a commit that referenced this issue Jun 22, 2015
Merge pull request #1 from rvguha/master
danbri pushed a commit that referenced this issue Mar 18, 2016
@RichardWallis
Copy link
Contributor

RichardWallis commented Aug 12, 2016

Move of fibo extension proposals (PR #1300) in to pending - A candidate for 'in between releases' release.

hhakung added a commit to hhakung/schemaorg that referenced this issue Aug 21, 2018
@danbri danbri changed the title Meta: schema.org planning Release planning Jun 18, 2019
@danbri danbri pinned this issue Jul 17, 2020
@danbri danbri changed the title Release planning Release History and Planning Jul 17, 2020
RichardWallis pushed a commit that referenced this issue Sep 17, 2020
@github-actions
Copy link

github-actions bot commented Oct 11, 2020

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Oct 11, 2020
RichardWallis pushed a commit that referenced this issue Jan 18, 2022
@danbri danbri unpinned this issue Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area.
Projects
None yet
Development

No branches or pull requests

4 participants
@danbri @RichardWallis and others