{"action":"created","issue":{"url":"https://api.github.com/repos/aquynh/capstone/issues/1293","repository_url":"https://api.github.com/repos/aquynh/capstone","labels_url":"https://api.github.com/repos/aquynh/capstone/issues/1293/labels{/name}","comments_url":"https://api.github.com/repos/aquynh/capstone/issues/1293/comments","events_url":"https://api.github.com/repos/aquynh/capstone/issues/1293/events","html_url":"https://github.com/aquynh/capstone/issues/1293","id":383942075,"node_id":"MDU6SXNzdWUzODM5NDIwNzU=","number":1293,"title":"Who would be insterested in joing a new fork of this project?","user":{"login":"E3V3A","id":194392,"node_id":"MDQ6VXNlcjE5NDM5Mg==","avatar_url":"https://avatars1.githubusercontent.com/u/194392?v=4","gravatar_id":"","url":"https://api.github.com/users/E3V3A","html_url":"https://github.com/E3V3A","followers_url":"https://api.github.com/users/E3V3A/followers","following_url":"https://api.github.com/users/E3V3A/following{/other_user}","gists_url":"https://api.github.com/users/E3V3A/gists{/gist_id}","starred_url":"https://api.github.com/users/E3V3A/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/E3V3A/subscriptions","organizations_url":"https://api.github.com/users/E3V3A/orgs","repos_url":"https://api.github.com/users/E3V3A/repos","events_url":"https://api.github.com/users/E3V3A/events{/privacy}","received_events_url":"https://api.github.com/users/E3V3A/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-11-23T23:38:51Z","updated_at":"2018-11-27T03:58:08Z","closed_at":null,"author_association":"NONE","body":"After having spent nearly two months watching the painful non-progress of Capstone, I think it is time to consider making a more user-friendly and progressive fork of the project.  It is in my honest experience that unless something is really starting to move, this project will be another potentially fantastic project on which it's tombstone will not read RIP, but DBL, *Death By Loneliness* (or ignorance!)\r\n\r\nHowever, I would like to hear more clearly from the maintainers of this project-trilogy before taking on such an endeavor. I would like to know what their plans are and whether or not they would help support such an obligation. (I have been in brief contact with @aquynh who stated he will look into cases and issues and consider adding people to help with the maintenance. That was > 1 months ago, and essentially nothing has happened since.)\r\n\r\nCurrently there are **789 Capstone forks** out there, and **several dozens of those, contain potentially valuable additions and fixes to Capstone**. There are currently **19 pending PR requests that are not making any progress**, (the oldest one from 2015), for no other reason than lack of participation of the owners of this project. Then we have the **306 open issues**, where the majority is lacking clear or  actionable response from the maintainers or are out of date and can be closed. \r\n\r\nThis is a very sad and an extreme case of counter productivity of an otherwise potentially great project. \r\n\r\nI would love to hear what other developer participants think about this? (There are 267 people watching the project, so I assume there should be at least 26 people concerned. So if you are concerned, please write your opinion here.)\r\n\r\nI would love to see the revival of this place and having an active RE community more involved. \r\nAnyway, at the end of the day, I just want to see shit moving along and making progress, and I am happy to contribute and help doing so.\r\n\r\nFree :beers: and :heart:  to all!\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/aquynh/capstone/issues/comments/441896011","html_url":"https://github.com/aquynh/capstone/issues/1293#issuecomment-441896011","issue_url":"https://api.github.com/repos/aquynh/capstone/issues/1293","id":441896011,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MTg5NjAxMQ==","user":{"login":"XVilka","id":203261,"node_id":"MDQ6VXNlcjIwMzI2MQ==","avatar_url":"https://avatars1.githubusercontent.com/u/203261?v=4","gravatar_id":"","url":"https://api.github.com/users/XVilka","html_url":"https://github.com/XVilka","followers_url":"https://api.github.com/users/XVilka/followers","following_url":"https://api.github.com/users/XVilka/following{/other_user}","gists_url":"https://api.github.com/users/XVilka/gists{/gist_id}","starred_url":"https://api.github.com/users/XVilka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/XVilka/subscriptions","organizations_url":"https://api.github.com/users/XVilka/orgs","repos_url":"https://api.github.com/users/XVilka/repos","events_url":"https://api.github.com/users/XVilka/events{/privacy}","received_events_url":"https://api.github.com/users/XVilka/received_events","type":"User","site_admin":false},"created_at":"2018-11-27T03:58:08Z","updated_at":"2018-11-27T03:58:08Z","author_association":"NONE","body":"Multiple people review PRs, multiple people merge them. It is highly\nsubjective, if someone is unsure - he waits for another person to decide,\nbut those cases are not that common.\n\nOn Tue, Nov 27, 2018, 11:26 AM Nguyen Anh Quynh <notifications@github.com\nwrote:\n\n> You are right that V4 release does not solve the main problems, but i am\n> trying to figure out how to move fwd with v5.\n>\n> How does that work with radare? Multiple pepole help to review PRs, then 1\n> person makes the final decision of merging?\n>\n> —\n> You are receiving this because you commented.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/aquynh/capstone/issues/1293#issuecomment-441888152>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AAMZ_Zl4vyqa7p11m_L0e84hSSkEiQUcks5uzLD3gaJpZM4YxMM1>\n> .\n>\n"}}
{"actor":{"display_login":"XVilka"}}