-
Notifications
You must be signed in to change notification settings - Fork 234
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
Enable Projects? #1810
Comments
Cc @erictraut as main driver behind the typing spec. |
I haven't previously used GitHub projects in any of my repos, so I'm not familiar with the functionality they provide. I'm open to the idea if others think it would be useful. @JelleZijlstra, any thoughts? |
I don't see a strong need at the moment, but also haven't used projects much. |
It's been a while since I've used projects. One of the nice things is that you can sort issues (but also simple text items) into custom lists. I was reminded of that when I saw Eric's final slide, which could be represented in a project. This could also be useful if we started to seriously work on the documentation, with multiple issues. On the other hand, the overhead to manage these lists is larger and - as Jelle - pointed out, it's not clear whether we really need this extra flexibility/overhead. I'm on the train right now, but will just temporarily enable projects just so we can play around with them - without the guarantee that we will keep them. |
It seems that nowadays projects are created at the org level. This is inappropriate for us to use, so I'm closing this. |
Would it make sense to enable Projects in this repository? This could be used to track larger scale projects like the typing spec "completion" or the documentation structure.
The text was updated successfully, but these errors were encountered: