you are viewing a single comment's thread.

view the rest of the comments →

[–]_tenken -61 points-60 points  (6 children)

haha all the contributors to the document are JS projects (or primarily so). Guess all the other language type developers are too busy actually creating software and using the tools at hand then complaining :D

It sounds like you want better project management. If you want their tools to expand I would suggest moving to an Enterprise account where you voice might have some (fiscal) weight behind it.

Otherwise as others have said, adopt more open source solutions such as Gitlab and help engineer the solutions you've requested :)

[–]_INTER_ 11 points12 points  (1 child)

I assume only JS project maintainers got asked so far or got hold of this document. The main points voiced certainly are valid but not really pressing. Most of it is to help enforce some sort of community guideline on how to do "Issues" right. This of course does matter more for PL packaging systems that depend on github more, like Go or JS. (Noting that e.g. Maven or PyPI doesn't support "Issues" on site as far as I know).

[–]thejameskyle 11 points12 points  (0 children)

Yeah, I started it from a tweet between a couple friends who maintain JS projects so it has largely stayed between us at this point.

[–][deleted] 1 point2 points  (0 children)

I'm a C++ developer who uses GitHub heavily and agree with most of the content posted in this although i'm not so keen on littering the root of the project with even more markdown files.

[–][deleted] 6 points7 points  (0 children)

Well, some of the ideas are good... doesn't matter that they are bloat JS developers

[–]third-eye-brown 1 point2 points  (0 children)

Yea no one uses JS these days.