The Future of the PureScript Book

Feedback
#15

I think having a place to debate and understand the need for ES module support or a compiler-supported packaging solution would be useful.

FWIW, there are long-standing issues for both of these on the compiler issue tracker with stated motivations and debate. I’m not sure that a separate roadmap would be a better place. I could see having more milestones though.

#16

I’m with Phil on this - it’s not so much for the benefit of the organizers, but mostly to promote the language itself. I’d love to see more people using PureScript, as I’m sure all of you would too, so I think Phil’s suggestion is good.

#17

I’m with Phil on this - it’s not so much for the benefit of the organizers, but mostly to promote the language itself

Promote it in what way?

#18

My point is to have a list of the things which are prioritized so I’d know which ones to go look at. There’s no way to know what the “path to 1.0” looks like right now, if it exists at all, there is just the Approved milestone.

#19

I think there is still a sense out there that since Phil isn’t working on it anymore, that not much is done. Having a visible roadmap would give outsiders some perspective that there is active development and a plan, rather than just maintenance.

1 Like
#20

I’ve created this thread to discuss making milestones and important features more visible. New Compiler Milestones

1 Like
#21

I’d like to invite anyone who is interested to help with a code review on updating the original chapter 8 code to work with react-basic-hooks.

I have a working version, but am unsure if this is the best coding style, and would like to get this straightened-out before including code snippets in the chapter text.

Links:

4 Likes
#22

AWESOME! I’ll provide some feedback this weekend

#23

It appears that everyone is in agreement that the book should be moved to purescript-contrib. What are the next steps for that? This may be a good task to combine with the library deprecation effort.

#24

Yea, I’m happy to move the book to -contrib!

As far as I’m aware that simply involves @dtwhitney making any last minute updates, ensuring we credit the work appropriately, and then on GitHub request transferring ownership to the -contrib organization (I can accept the request).

2 Likes
#25

The only remaining PRs are mine, and I’m happy to re-apply those to the new repo if that simplifies the migration effort.

#26

I believe the pull requests and everything else transfers with the repository — the only change is the owner. So hopefully you won’t need to do anything!

#27

I’m taking a look now

#28

It doesn’t look like this is something I can do. It looks like you can just do it, or add me to the org with repo creation privileges:

https://help.github.com/en/github/administering-a-repository/transferring-a-repository

To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.

Once a repository is transferred to an organization, the organization’s default repository permission settings and default membership privileges will apply to the transferred repository.

1 Like
#29

I see that @garyb has invited you @dtwhitney to the purescript-contrib organization so that you can do this.

#30

Yep, sorry, I meant to mention I had done so but then got distracted as I was trying to figure out whether that would give sufficient permissions to create/transfer the repo. I think it will now, after I poked at some other settings.

#31

Ok it looks like it has been moved. I gave access to the “book” team.

#32

Great! I can see the book at its new home: https://github.com/purescript-contrib/purescript-book

Thanks again for all your work, @dtwhitney!

2 Likes
#33

Um… wow! We should have moved the book over a long time ago. I can’t believe the amount of work being done on the book. It’s amazing. Awesome work everyone!

6 Likes
#34

I’ve been working on something that has helped me in getting started with PureScript, a list of definitions for several keywords that I’ve personally found difficult to grapple with. I am sharing them in the hopes that they might be useful to others, maybe something that could be improved/incorporated into a larger document.

1 Like