-
-
Notifications
You must be signed in to change notification settings - Fork 48
Promoting community involvement #34
Comments
I'm not sure how to promote exactly, but I definitely intend to spend more time helping out and making PRs. Very interested in seeing this project work out. |
You can start by creating a community guideline as well as fix #33. I'm interested in contributing but don't know where to start. |
I've just updated the contributing document with a long list of sources, and where to contact me. I would LOVE to guide you through the process, or even some things that this project absolutely needs. I'll work on adding documentation-- what do you think would work best? I can detail how the kext flow works, if needed too. |
That would be awesome. I have to admit though, contributing to this repository requires a lot study at first. I once tried to combine Black80211 with USB wifi dongle driver, but eventually abandoned it as it is extremely difficult to control the user space of a kext from the kernel space of another kext (it was only possible in theory), but it's been sometime and I completely forgot everything what I did and how Black80211 works. However, I'll try to recap things (I'm in quarantine anyway) and start contributing here (if I can). |
That is the problem, quite honestly. The sheer amount of code (we're WAY past 10k sloc) and complexity requires that you spend a good week/two weeks pouring over any/all resources that you have. Also, yeah. Controlling kext to kext is incredibly difficult, however Black80211 is relatively easy to understand and tinkering with it helps. I have a full VM test bed for quick restarts too, rather then testing on bare metal. |
I will promote on my twitter and suggest that others do too. This sort of project has interest from those in the jailbreak community and some very knowledgeable individuals might be interested in contributing. Best of luck! |
How do we promote community involvement? I would REALLY enjoy more eyes reviewing over the code in this repo. The device-logs is a hub of activity, but I wish there were more pull requests and help with code.
The text was updated successfully, but these errors were encountered: