search

outroll / vesta

VESTA Control Panel
http://vestacp.com
GNU General Public License v3.0
2.97k stars 1.03k forks source link

Close github issues #669

Closed n1trux closed 7 years ago

n1trux commented 8 years ago

I see that the preferred way of tracking bugs is http://bugs.vestacp.com/ – so please close Github issues.

sman591 commented 8 years ago

:+1: I personally love GitHub issues because it ties in fantastically with pull requests and the open source community, but if https://bugs.vestacp.com is the appropriate tracker, github issues shouldn't be enabled

anton-reutov commented 8 years ago

https://bugs.vestacp.com - is official bug tracker of VestaCP project

n1trux commented 8 years ago

Yes, that is what I said.

Satanity commented 8 years ago

registration does not work bugs.vestacp.com

anton-reutov commented 8 years ago

registration working fine. You should activate your account via email

Satanity commented 8 years ago

i dont get the mail to activate

anton-reutov commented 8 years ago

Your account sanity has been activated by administrator

Satanity commented 8 years ago

thank u!

n1trux commented 8 years ago

now, er, can you disable Github Issues?

chipitsine commented 8 years ago

most probably, nobody cares of github, can you please open a ticket at http://bugs.vestacp.com/ ?

anton-reutov commented 8 years ago

GitHub issues will be closed at the end of development version 0.9.8-16 https://bugs.vestacp.com/issues/199

SysVoid commented 8 years ago

Personally I prefer GH Issues. It's generally more secure and reliable than a 3rd party.

n1trux commented 8 years ago

Me too, but if the developers don't want to use github Issues and therefore don't use them at all, I'd much prefer them to link to the official bug tracker instead of just ignoring the github Issues. >200 Issues have piled up… many of them not relevant anymore.

I'd volunteer in cleaning the issues up, triaging bugs and "copying" them to the internal tool, but then I'd need rights for this repository, which probably won't happen.

@anton-reutov: you wanted to close the Issues after 0.9.8-16? ;)

anton-reutov commented 8 years ago

https://bugs.vestacp.com/ is official bug tracking system of VestaCP project All ideas and bugs we take only from the bug tracker Ideas and bugs are not considered on the github

n1trux commented 8 years ago

@anton-reutov we know that, so disable Github Issues already:

https://help.github.com/articles/disabling-issues/

SysVoid commented 8 years ago

@n1trux I am working my way through the old ones, closing them one by one.

If Vesta ends up closing issues completely, then I will no longer participate in the project. I won't be signing up to a 3rd party in order to track issues.

serghey-rodin commented 8 years ago

@n1trux thanks for help! please email me skid at vestacp.com

@SysVoid since we have more devs involved in the project we decided to not close github issues. At least for a while. It is definitely handy tool for developers. However it seems like are underestimating bugs.vestacp.com. The advantage is that we can form desired bug reports. We can ask submitters to specify every single detail we need like distro, architecture and so on. Actually bug.vestacp.com it is much more powerful tool. So let's find out the best way to use both systems.

sman591 commented 8 years ago

@serghey-rodin FWIW, you can create contribution guidelines and GitHub issue and pull request templates, which would help the need for structured bug reports, pull request details, etc. Regardless of which system is used, I'm sure there could be some use out of it

SysVoid commented 8 years ago

@serghey-rodin I think what @sman591 mentioned is really helpful.

We can make PR templates, and close any issues that don't conform to the template. That way all issues from the time we start that are in the same format and contain all information needed to resolve.

Also, I think we should make better use of GitHub Labels, since that will help us categorise the issues.

anton-reutov commented 8 years ago

bugs.vestacp.com is official bug tracking system of our project and we will continue to work with him SysVoid you can continue to work with github issues I think this issue should be closed

serghey-rodin commented 8 years ago

@sman591 I was trying to find something like that but ended up configuring labels. Thanks! It is exactly what I was looking for.

@SysVoid can you please take a look https://help.github.com/articles/creating-an-issue-template-for-your-repository/ and make template for our GH Issuses?

SysVoid commented 8 years ago

@serghey-rodin definitely.

SysVoid commented 8 years ago

All done.

skurudo commented 7 years ago

Do we still need this discussion? Github issues will be live. @SysVoid May be need to close this one?

SysVoid commented 7 years ago

Closing issue. Thanks for your input, everyone! May the octopus issues live!