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

Roadmap for 0.1.0 #2

Closed
13 tasks done
nugmanoff opened this issue Jan 26, 2023 · 4 comments
Closed
13 tasks done

Roadmap for 0.1.0 #2

nugmanoff opened this issue Jan 26, 2023 · 4 comments
Milestone

Comments

@nugmanoff
Copy link
Contributor

nugmanoff commented Jan 26, 2023

Following up on conversation with @heckj

Here is the rough roadmap for 0.1.0:

  • Document
  • Transaction
  • Text
    • Embeds
    • Attributes
  • Array
  • Map
  • Observations
  • Swift wrapper
    • Thread-safety
    • Idiomatic API (Conformance to native protocols, "Swifty" feel & etc)
  • Examples
  • Basic docs for library consumers

As of now we will probably be leaving XML types, Undo/Redo Manager, Awareness protocol & other stuff to 0.2.0 due to their complementary nature.

@nugmanoff nugmanoff added this to the 0.1.0 milestone Jan 26, 2023
@nugmanoff nugmanoff pinned this issue Jan 26, 2023
@heckj
Copy link
Collaborator

heckj commented Jan 26, 2023

Question on the flow here - any preference for having me work in my local fork and send pull requests vs. working in the repository directly? Right now I don't think I have permissions on the repo to do anything, but I'm happy to drop in pull requests and add you as a reviewer for work I do. That work OK for you? (If you want me to self-merge at any point, we'll just need to give/get me permissions into the repo)

@nugmanoff
Copy link
Contributor Author

Both ways work for me. But I think we need to get you maintainer permissions, need to ask @dmonad for that. I think we can voluntarily ask for review on big changes from each other, but not block each other on small changes. Common sense applies – when we will like we need review, we ask for it :) Either way – I believe PRs are the way to go now once there are 2 of us.

@dmonad
Copy link

dmonad commented Jan 27, 2023

Now both of you have maintainer access ;)

You can organize the work however you want. Make sure to optimize it over time. I also believe that it makes sense to open a PR for all changes - just for visibility (for each other, and for outsiders).

You seem to already agree on using "common sense" on whether to ask for a review :) Just make sure that you give each other a chance to see more significant changes.

@nugmanoff
Copy link
Contributor Author

0.1.0 release is out 🥳

@nugmanoff nugmanoff unpinned this issue May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants