------------------------------ On Fri, Jun 27, 2014 12:58 AM BST ahi wrote:
>> I am still waiting for the documentation update. This is the >> 4th time I am requesting it. You MUST make an effort in the next half-day. >I am updating and adding docstrings as I am working. >As for a more comprehensive documentation I was thinking about wiki >pages, what do you think? This is really a WTF moment - if you don't understand that abbreviation in your locale, it means "what-the-f*ck" (-are-you-thinking). Please just write, put it in a file, anything - just write it down. Discussion about where the material should go can happen later. Move material around is easier than move nothing. Nothing is nothing. I still haven't seen you updating the top level readme. So I am asking a *5th* time. After asking the 2nd time, I have started the discussion with the linux foundation admins about possibly failing you at mid-term evaluation. And there is still 17 hours to decide. The bottom line is, this is supposed to be a library *for others*. You really fail on two scenarios, at least, and possibly more: (1) user has a specific task to do. trying to see whether this work suits his purpose. Top level readme - what exactly is this? what is it supposed to do? is it supposed to do what he has got in mind, or is it something completely unrelated? completely irrelevant? None of these can be answered at a glance. You fail. (2) developer looking to see whether to write his own thing or adapt something already in existence. Checked out git. ok, no middle-level description in any part to speak of - cannot easily find one's way around the code. Try running just "nosetests" to see what it does, whether it does any damages. Piles of warnings; code does not run with a variety of simple syntax errors to cryptic errors. try to give you the benefit of the doubt, assuming that you only make one recent mistake. Try revert the most recent commit (or groups of most recent commits), piles of different errors. Try reverting one more recent commit/commits - another piles of different errors. The commit log is not helpful - it is all one-liners, sometimes the one-liners does not match the actual code change. Most developers would prefer to write their own code after undo'ing the last one or two commits, and neither of those works cleanly "as advertised". That is, if they haven't given up earlier after just looking at the recent commit log and have a look at the coding style and presence/absence of comments, etc. You also fail. Please just write. You are *not* working, if it is of no use to others. Stop coding *immediately* - and you should have stopped 10 days ago - if that's what it takes to convince you that you MUST write. Please just write. _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
