-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Further discussion about project organisation #437
Comments
I have to think about it as it is an important decision for the project. In the short term (ie. coming months), we will continue working in 2016-06-19 11:50 GMT+02:00 Jerry Jacobs notifications@github.com:
|
I understand it is not an easy decision, and in a few months we can reconsider how we want to continue. Because And as you have seen by PR #434 it took me more time than expected to make it work again on windows. I'm not fixing windows for myself, as I only use *nix, and OS X machines. And I would be very sad if in the meantime the windows build is broken again when there are pull-request contributions. As you are aware of my rate of development and contributions, and funding by Dual Inventive. I would like not to get stuck when the tooling is not sufficient. |
I understand well what you say. I am not against changing the project organization. In fact, I have thought 2016-06-19 13:27 GMT+02:00 Jerry Jacobs notifications@github.com:
|
I currently see no reason to move anything out of GitHub in the near future. Since February we have a separate |
This project has been transferred to a git-organisation today, as agreed between @texane, @xor-gate and @Nightwalker-87. This will ease collaboration and possible transitions between maintainers in the future, as this project is now hosted within a shared account. Also it will offer new possibilities and features for further evolution of this project. I'll leave it at that for now and may go into details at a later point in time... |
Thanks @Nightwalker-87 for the public update. If you need some ideas please drop them here so we can discus. I will make time for it to move the project further and give my advice. |
Also a big thanks to @texane and the other contributors who took care of the project while I was busy with life of course ;=) |
The reorganisation of the project and the related transfer to a public git-organisation seem to have resolved this issue. All further general notes related to this project will be published in #874. |
I would like to followup on your comments of the pull request (PR #434) when it took me long time to make the windows MSYS build work again, as people have silently broken it in the past time.
I agree 100% it is bad to put constrains on personal accounts for integration with other services (continues integration, continues deployment). Hopefully you understand I want to take the project to a higher level for first-time users, and enhance the flow and documentation for older users. And give better support for contributions and issue tracking.
I completely understand you can not do this alone, and I highly appreciate you made me als collaborator and maintainer. Github organisations are made for this purpose and I already own a few which enhances collaboration.
To take the project to the next level with correct continues integration and binary releases I have the following suggestions:
Or
The problem with approach two is that all the issues and pull-request will be resolved and merged into
texane/master
and I have to manually do everything instlink/stlink
.With the first approach all the history, pull-requests and issues are transfered to
stlink/stlink
and you are also granted admin rights on the organisationstlink
. And then you can revoke all your private access to 3th party integrations on your personal account.@texane let me know what you think, and how you would like to continue.
The text was updated successfully, but these errors were encountered: