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

clarify how to contribute / collaborate #10

Closed
aspiers opened this Issue Oct 2, 2016 · 10 comments

Comments

Projects
None yet
4 participants
@aspiers
Copy link

commented Oct 2, 2016

Hi there,

Really awesome that this is on github! Please can you update the README (or create a CONTRIBUTING.md) in order to clarify where bugs / feature requests etc. should be submitted, and whether pull requests are welcome here or should gerrit be used instead.

Thanks!

@jimmytipit

This comment has been minimized.

Copy link
Member

commented Oct 25, 2016

Thanks for filing the issue and again, apologies for the long time for the response. For now, all bugs should be submitted to summitapps@openstack.org. We'll update the documentation with this info after the current summit.

The apps will be moving to Gerrit shortly after the Barcelona Summit, but in the meantime, pull requests can be made via github. I'll also clarify this in the documentation.

@colemancda colemancda added the question label Oct 25, 2016

@aspiers

This comment has been minimized.

Copy link
Author

commented Oct 25, 2016

Thanks a lot for the response, but I beg you to reconsider and standardize an open issue tracker for this. This Zendesk support system is a black box which goes directly against the ethos of OpenStack's four Opens. It is also an extremely inefficient way of developing software, for reasons which I would hope are obvious enough to anyone who works within OpenStack and understands the benefit of its openness that I wouldn't need to enumerate them. For example, the ability to search, browse, and contribute to all existing issues previously submitted is absolutely paramount.

What I am asking for could be implemented literally within a matter of minutes. For example, you could declare this GitHub issue tracker as the official place to track issues. Or you could set up a launchpad project and use that bug tracker. Either would be perfectly adequate and far better than a system where 100 people could be reporting the same bug as each other all at the same time, without any having knowledge of the reports of the others.

Thanks for listening!

@aspiers

This comment has been minimized.

Copy link
Author

commented May 30, 2018

Any update on this? Thanks ...

@smarcet

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

Hello Adam, apologies for the long time for the response. As you suggested we will be start using this
https://github.com/OpenStack-mobile/summit-app-android/issues as official issue tracker to collect all bugs and feedback, thank you for your patience

Regards

@smarcet smarcet closed this Nov 12, 2018

@aspiers

This comment has been minimized.

Copy link
Author

commented Nov 12, 2018

Thanks @smarcet that's great - but has that been communicated anywhere? Currently in the app if I go to About and Report a Problem it does not redirect me to this issue tracker but rather suggests sending a mail to summitapp@openstack.org. Until that is changed I would recommend re-opening this issue.

@smarcet smarcet reopened this Nov 12, 2018

@smarcet

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

sure good point will do
regards

@aspiers

This comment has been minimized.

Copy link
Author

commented Nov 12, 2018

@smarcet commented on 12 Nov 2018, 12:22 GMT:

sure good point will do

regards

Thanks! BTW has this plan been abandoned or just postponed?

@jimmytipit commented on 25 Oct 2016, 10:43 BST:

The apps will be moving to Gerrit shortly after the Barcelona Summit, but in the meantime, pull requests can be made via github. I'll also clarify this in the documentation.

@jimmytipit

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

@aspiers The move to gerrit has just been postponed. We've been working on moving our sites to a new data center, which has required a whole bunch of unanticipated additional work. At some point... we will move to Gerrit ;)

@aspiers

This comment has been minimized.

Copy link
Author

commented Nov 12, 2018

Got it, thanks for the info!

@aspiers

This comment has been minimized.

Copy link
Author

commented Nov 15, 2018

I'll submit a new issue for clarity. The general question here has been answered.

@aspiers aspiers closed this Nov 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.