-
Notifications
You must be signed in to change notification settings - Fork 15
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
Project setting to allow public read access #278
Comments
We have plans for a couple of things in this area:
Would any of the above give you what you want? If not can you explain in a bit more detail what you're after. |
Thanks & yes! #1, a reader type user, would work for our purposes. We would just post credentials for such a user publicly so that anyone interested could take a look at what's going on and what's planned. It would be even better if we could set the project to be publicly readable - i.e. you do not have to be a user at all - just to make it simpler for someone who's casually curious. But that is a very minor difference on the scale of things. |
Ok, understood re: publicly readable. Thanks for the clarification. |
For internal reference only; external users will not be able to open the following links: |
We'd like to be able to refer interested parties to our Codetree project so that they can easily see what the plan for development is. Just sending people to look at Github issues across several repos is confusing, especially for non-developers (e.g., potential funders) who just want to know how much total planned work there is, what we could do with say another developer-year, what we're up to now, etc.
This might also benefit Codetree in that non-users would see "oh, this group is organizing their project on Codetree, what a nice and intuitive interface..." and you could directly link potential users to some example projects.
The text was updated successfully, but these errors were encountered: