ojoaldato / google-rlint Goto Github PK

What steps will reproduce the problem?

1. go to code.google.com/p/google-rlint
2. read the verbiage (below) and check out the source from SVN

"...RLint is automatically used within Google as part of the peer review 
process for R code. We encourage CRAN package authors and other R programmers 
to use this tool. A user can run the open-source Python-based program in a 
Linux, Unix, Mac or Windows machine via a command line."

3. attempt to proceed with Google's (or "We"'s) "encouraged" steps above
(nb.  This is a perfect use-case for an iPython notebook, as it happens)


What is the expected output?
A source tree with actual code to run, as described above


What do you see instead?
A bunch of edits to a wiki and some remarks about "a few weeks"


What version of the product are you using?
r6


On what operating system?
Ubuntu 14.04 LTS


Please provide any additional information below.

I wanted to chastise the authors of a manuscript for their poor coding style 
and suggest that they use Google's code-review-ready tool, but alas, rlint 
seems to be trapped forever in red tape.  Whatever happened to the concept of 
tossing a project out as "beta" and letting adventurous users find the bugs 
that affect the common case?  (Caribou/Gmail, anyone?) 

If you'd put the code up I and others could at least do something to help (i.e. 
test and break it, recommend authors do the same, spread the word). 

This could be a widely used tool for many people (users of R, as an ecosystem, 
are relatively less likely to be professional developers than those of C++, 
Java, Python... anything that isn't JavaScript or PHP).  But that can't happen 
if you don't push out an alpha release (sans warranty!).  

"If it breaks, you get to keep the pieces."  You know the drill!  You got a 
talk out of vaporware... At least give yourselves a reasonable deadline for 
release, then leave address real "issues" when they merit addressing.

It's a style checker.  For heaven's sake, quit being such scaredy cats.  It's 
not THAT hard to maintain a widely-used package (even I can do it!).

Here's hoping you haven't forgotten why people were excited about this.

For integrating formatters with text editors as in 
https://github.com/google/vim-codefmt/issues/33, it's extremely useful to be 
able to format a subset of lines from a file individually. google-rlint doesn't 
seem to support specifying line numbers: The command-line signature for 
rlint.py listed here doesn't show any kind of --lines argument.

It's possible to hack limited range formatting support into the editor 
integration by splicing lines from the formatted version into the original, but 
it will cause errors or insane formatting for line ranges that don't align 
perfectly with blocks of code. Could google-rlint support formatting ranges of 
lines natively?

What steps will reproduce the problem?
1. svn checkout http://google-rlint.googlecode.com/svn/trunk/ 
google-rlint-read-only
2. Open local folder
3. No code

What is the expected output? What do you see instead?
Some actual code.

What version of the product are you using? On what operating system?
Current revision is r6

Please provide any additional information below.
Browsing the trunk (or any other svn folder) online shows that it is truly 
empty. 

Hopefully the intention of the authors was to actually share the projet. It 
would be welcome to have more lint-style tools for R.

What steps will reproduce the problem?
1. Go to https://code.google.com/p/google-rlint/wiki/Documentation
2. Click on the link 
3. Server not found

What is the expected output?
A PDF 

What do you see instead?
A dead link

What version of the product are you using? On what operating system?
Commit v3


Please provide any additional information below.
It is impossible to have > 100% bugs, so committing *anything at all* will 
reduce (or at worst hold stable) this proportion.
Seriously, it's not like you're releasing nuclear launch codes here. :-)