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

Project setting to allow public read access #278

Open
kimberscott opened this issue Oct 3, 2018 · 4 comments
Open

Project setting to allow public read access #278

kimberscott opened this issue Oct 3, 2018 · 4 comments

Comments

@kimberscott
Copy link

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.

@rstocker99
Copy link

We have plans for a couple of things in this area:

  1. A reader type user that can see issues but not change issues.

  2. Users that can CRUD issues but that are NOT backed by Github issues.

  3. A light weight planning mode. Something higher level than issues.

Would any of the above give you what you want? If not can you explain in a bit more detail what you're after.

@kimberscott
Copy link
Author

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.

@rstocker99
Copy link

Ok, understood re: publicly readable. Thanks for the clarification.

@ac21 ac21 added this to the 2019-Q2 milestone Apr 24, 2019
@ac21 ac21 modified the milestones: 2019-Q2, 2019-June-1, 2019-May-2 May 18, 2019
@ac21 ac21 modified the milestones: 2019-May-2, 2019-June-1 May 23, 2019
@ac21 ac21 removed the Prioritized label May 23, 2019
@ac21 ac21 modified the milestones: 2019-June-1, 2019-June-2 Jun 10, 2019
@ac21 ac21 modified the milestones: 2019-June-2, 2019-July-1 Jun 27, 2019
@ac21 ac21 modified the milestones: 2019-July-1, 2019-Sep-2, 2019-Oct-1 Sep 12, 2019
@ac21 ac21 modified the milestones: 2019-Oct-1, 2019-Oct-2, 2019-Nov-1 Oct 21, 2019
@ac21 ac21 modified the milestones: 2019-Nov-1, 2019-Nov-2 Nov 15, 2019
@ac21 ac21 modified the milestones: 2019-Nov-2, 2019-Dec-1 Nov 18, 2019
@ac21 ac21 modified the milestones: 2019-Dec-1, 2020-Q1 Dec 18, 2019
@ac21 ac21 modified the milestones: 2020-Q2, 2020-Q3 Jul 6, 2020
@ac21 ac21 modified the milestones: 2020-Q3, 2020-Nov-1 Oct 7, 2020
@ac21 ac21 modified the milestones: 2020-Nov-1, 2020-Q4, 2020-Dec-2 Nov 17, 2020
@ac21 ac21 modified the milestones: 2020-Q4, 2021-Q1 Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants