Code Monkey home page Code Monkey logo

rfcs's Introduction

Qiskit RFCs

The purpose of a Qiskit Request for Comments (RFC) is to communicate and engage with the wider community in the development and direction of Qiskit. RFCs enable engineering and research stakeholders to communicate design changes to any component of the larger Qiskit project.

Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow.

Some changes though are "substantial", and we ask that these be put through a bit of a design process and produce a consensus among the Qiskit community and the sub-teams.

This repository is for any project in the Qiskit project to make these design proposals and review and discuss the changes. An RFC can be contained to a single project or it can span multiple projects, if a design decision requires some planning and discussion before implementation an RFC can be used to facilitate that and collect feedback prior to implementation.

RFC Status References/Discussion
0021 Sparse observables with extended alphabets Implementation in progress RFC PR | Implementation
0020 Qiskit release cycle and versioning Implemented RFC PR | Implementation
0019 Classical storage and load instructions Implemented RFC PR | Implementation
0018 Primitive options type change Implementation in progress RFC PR | Implementation
0017 Base Primitive and Units of Primitive Work Implemented RFC PR | Implementation
0016 SamplerV2 Implemented RFC PR | Implementation
0015 Extended Estimator Interface Implemented RFC PR | Implementation
0014 Overhaul Qiskit Experiments Not planned RFC PR | Implementation
0013 Plan to move Qiskit/qiskit-terra/algorithms module to qiskit-community/qiskit-algorithms independent repo Implemented RFC PR | Implementation
0012 Pulse Compiler & IR Not planned RFC PR | Implementation
0011 Plan to rename Qiskit/qiskit-terra repo to Qiskit/qiskit Implemented RFC PR | Implementation
0010 Preliminary representation of rvalue classical expression in Qiskit Implemented RFC PR | Implementation
0009 Operation: the interface for valid QuantumCircuit operations Implemented RFC PR | Implementation
0008 Unify Pulse Commands and Instructions Implemented RFC PR | Implementation
0007 Dataframe for Qiskit Experiments Implemented RFC PR | Implementation
0006 Generalized Unroller and Equivalence Library Implemented RFC PR | Implementation
0005 Aqua Circuit Interoperability Update Deprecated RFC PR
0004 Richardson error mitigation Implemented RFC PR | Original PR | Implementation
0003 Aqua 0.7 Operator Redesign Deprecated RFC PR | Original PR
0002 Aqua 0.7 Release Priorities and Plan Deprecated RFC PR | Original PR
0001 Aqua 0.7: Ansatz Design Doc Deprecated RFC PR | Original PR

How to RFC?

Use the Qiskit RFC template to prepare your RFC. Make sure you read CONTRIBUTING.md first.

License

This repository is licensed under

Apache License, Version 2.0, (LICENSE or http://www.apache.org/licenses/LICENSE-2.0)

rfcs's People

Contributors

1ucian0 avatar ajavadia avatar arushsamadhia avatar cryoris avatar dongreenberg avatar eggerdj avatar elept avatar ihincks avatar jakelishman avatar jyu00 avatar kdk avatar mtreinish avatar nkanazawa1989 avatar paniash avatar taalexander avatar tsafrira avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rfcs's Issues

Epic - Implementation of RFC `0011`: Plan to rename `Qiskit/qiskit-terra` repo to `Qiskit/qiskit`

Tasks:

gantt
    dateFormat  YYYY-MM-DD
    tickInterval 1month
    axisFormat %b

    section planned releases
    %% From freeze to release
    0.24         : crit, release024, 2023-04-06, 28d   
    release 0.24 : milestone, 2023-05-04   
    %% From freeze to release
    0.25         : crit, release025, 2023-07-05, 22d
    release 0.25 : milestone, 2023-07-27    
    section preparation
    metapackage-repo :metapackage-repo, 2023-03-31, 1d
    rfc-discussion   :done, rfc-discussion, 2023-03-30, 10d
    rfc-merged   :milestone, rfc-merged, after rfc-discussion, 0d 
    section empty-metapackage
    %% These tasks are not interdepedendent and they need to be done before release025   
    ibmq-docs-out-of-metapackage    :ibmq-docs, after rfc-merged, 2w
    docs-out-of-metapackage         :docs, after ibmq-docs, 4w
    benchmarks-out-of-metapackage   :benchmarks, after docs, 4w
    tutorials-out-of-metapackage    :tutorials, after benchmarks, 4w
    section archive-metapackage
    ibmq-out-of-metapackage        :ibmq-archived, after release025, 1d
    move-setup-out-of-metapackage  :setup, after release025, 1w
    pre-archive-doc                :archive-doc, 2023-08-18, 1d
    archive-metapackage            :archive-meta, after archive-doc, 1d  
    section final
    final-rename    : finalrename, 2023-08-21, 1d
    fix-time:       : fix-time, after finalrename, 2w
    final-announcement : milestone, finalannoun
Loading

Estimator's error bars

A derived discussion of #51 about Estimator's representation of error bars:

  1. We propose that the error portion of the data should represent error bars on the expectation values, somehow. That is, standard error instead of standard deviation or variance, or possibly, a two-sided confidence interval.

For reference, see:

With the aim to extracting that conversation from the RFC on the details on the how (having agreed on the spirit of the need for some for of error represetation in TaskResult), please continue the discussion in this issue.

This discussion might result in one of the following out comes:

  • Amending or extending #51
  • An agreement on this issue
  • It's own RFC

Publish RFCs to github pages

Now that we have an RFCs repo once we start merging RFCs we need to have a place to host them. We should add hosting via github pages so we can see the rendered output of the RFCs.

Organize the repo numbering and formatting

  • Create an index #40
    • include what are RFC that are still valid (deprecate those related to Aqua, for example)
  • Change formats:
    • 0001 to md #33
    • 0003 to md #37
    • 0004 formatting issues #35
    • Aqua Circuit Interoperability Proposal.ipynb to md, as 0005 #36
  • Fill the gaps: #38
    • 0008-0011 missing
    • 00013-0024 missing
    • 0026-0029 missing
  • Numbering ####-repo-rename.md #39

Implicitly appending extra dimensions for broadcasting

A derived discussion of #51 about implicitly appending extra dimensions for broadcasting.

For reference, see #51 (comment)

With the aim to extracting that conversation from the RFC but keep it alive, please continue the discussion in this issue

This discussion might result in one of the following out comes:

  • Amending or extending #51
  • An agreement on this issue
  • It's own RFC

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.