On Thu, Jul 30, 2015 at 11:30:36AM +0200, Karel Gardas wrote: > Spent already some time in netbsd/bitrig wapbl code to see what's > relevant for Open and how to structure it to small sensible patches to > push for review. This will take some energy and time indeed, the > problem is that anytime the word "bitrig" comes to Open mailing list, > it's either ignored or start kind of non-engineering discussion. > So it's indeed a beg to get an answer to question: is anytime spent in > netbsd/bitrig wapbl/snapshoting code to review, understand, analyse, > prepare for review to Open wasted or not? If, even socially, it's > wasted, then indeed, it's more productive and beneficial to project to > spent it on different things...
If you were serious about approaching a project like this, you would determine the answers to the above questions yourself. Requirement analysis is part of the project. As for "social" concerns, you don't have to worry about any of that. Just make sure the technical work you produce is sound and any 3rd party code you use make use of as part of your work is suitably licensed. I hope your next mail comes in a few weeks and has a small and correct vfs/softdep bug fix attached to it. That would indicate progress. But if you just keep asking about what to do, then your time (and the time anyone else is spending on this discussion) will probably be wasted. Before expecting help and direction you'll have to demonstrate a fair amount of self-reliance to avoid the impression that you'll drain the resources of anyone willing to help you.
