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

Contacting the addon maintainer #2

Open
marmistrz opened this issue Jan 22, 2014 · 4 comments
Open

Contacting the addon maintainer #2

marmistrz opened this issue Jan 22, 2014 · 4 comments

Comments

@marmistrz
Copy link

When an addon is buggy it'd be great to be report the bug directly to the author. Contacting the author via e-mail would be a great option

@gl3nn
Copy link
Member

gl3nn commented Jan 22, 2014

If nobody will find the time to implement this, I might add it to the
server-side GSoC project. ( A bit more sophisticated than just being able
to send a mail to the addon owner though.)

On Wed, Jan 22, 2014 at 8:17 PM, Marcin Mielniczuk <notifications@github.com

wrote:

When an addon is buggy it'd be great to be report the bug directly to the
author. Contacting the author via e-mail would be a great option


Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

@marmistrz
Copy link
Author

Or maybe a bugtracker for each track? ;) This way the spam could be reduced

@gl3nn
Copy link
Member

gl3nn commented Jan 22, 2014

I do think a bugtracker per addon is a bit of overkill.. but we could just
list a simple page of reported bugs for everyone to see. That will give us
insight on whether the addon is still maintained or not, and it could
eventually clean up our repositories.

On Wed, Jan 22, 2014 at 8:22 PM, Marcin Mielniczuk <notifications@github.com

wrote:

Or maybe a bugtracker for each track? ;) This way the spam could be reduced


Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-33057423
.

@marmistrz
Copy link
Author

Might be ;)

But no bugtracker at all is not enought! Underkill? :)

Still, before removing the addon permanently the author should be contacted, and if no reply e.g. within a month, then permanent removal.

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