Create an issue tracker for the Foundation

[ripper234]

(offtopic)

@pmlaw stated that this github repo is only meant for issues on the bylaws.

I think it's vital to have a public issue tracker for general issues. The level of discourse and engagement I got over the last few weeks has been amazing, from various Foundation staff and board members ... and it's important we have some place where we can get that level of engagement and track general issues.

I argue that the forums aren't enough, well, because they're not an issue tracking system. For that reason they attract all kinds of discussions ... but an issue tracker would attract very specific discussion and is just more suited for tracking issues.

I propose a github repo or public Zendesk be opened and used to tracking issues.

May this be the last (offtopic) issue I open on this legal repo.

[pmlaw]

@ripper234 Zendesk would be a good pick for that, or Get Satisfaction.

[ripper234]

+1

[danielmcclure]

This sounds like a great idea. Just wanted to voice up as someone that has
been observing the recent discussions rather than actively participating.
This format has generated some interesting discussion and would happily
have responded where I felt I could add value.

On 9 June 2014 05:55, Ron Gross notifications@github.com wrote:

+1

—
Reply to this email directly or view it on GitHub
#14 (comment)
.

[bg002h]

@ripper234 What about the foundation forum? It's visible by the public, but only members can participate in the discussions. Is that "public" in the sense you mean above? How "public" should it be?

[ripper234]

@ripper234 What about the foundation forum? It's visible by the public, but only members can participate in the discussions. Is that "public" in the sense you mean above? How "public" should it be?

Well @bg002h , a forum isn't exactly an issue tracker.
An issue tracker is for constructive targeted issues that need resolving (e.g. "forum login not working" which is an issue I had myself several times during the recent elections).

Regarding 'how public' - the general approach should be start with 'public' and opt-in to privacy when there's a need. I don't see a need for privacy here, or for restricting participation - I think that all of forums, github and issue trackers are great mediums to engage with the community (but each should be used for a specific purpose).

[bg002h]

@ripper234
Ahhh...I get it now (my apologies for the rather silly suggestion, I'm on the steep part of the learning curve).

I agree. We need to use the right tool for each job.