Unox should use a travis ci system test

hnsl / unox

Unison OS X unison-fsmonitor adapter.

101 stars 12 forks source link

Unox should use a travis ci system test #3

Closed hnsl closed 7 years ago

EugenMayer commented 7 years ago

I guess, that one is outdate :)

hnsl commented 7 years ago

Naah, opening it again. I still think unox should have some sort of test. Unless there's tests I don't know about?

EugenMayer commented 7 years ago

Not saying it should not, but either you really think about starting to take action about this, or the issue queue distracts from items want to be actually done to "those nice to have but never somebody will work on"

I thin, since this has been arround since more then 2 years without an action, its rather the second one, arent you honest about that? :)

hnsl commented 7 years ago

Maybe the enhancement label is useful to make that distinction? Normally you'd have a low priority setting for those kinds of "wishlist" bugs so you don't get distracted.

hnsl commented 7 years ago

I also feel not closing is useful if someone comes along and has time and wants to contribute.

EugenMayer commented 7 years ago

If you keep an issue open that open without taking action, you show a sign too, right?

There is no focus
Nobody really looks at issues
there is no activity anyway

I am sure, that is a one-sided POV, but do not forget, you are dealing with a community of developers. They always feel to have very few time and want to invest them "efficiently".

Literally nobody will ever pick up an issue you created 2 years ago with a simple comment.

hnsl commented 7 years ago

You are likely more familiar with Github than I am so that sounds reasonable.

EugenMayer commented 7 years ago

Again, not at all against tests, but if they should happen, we have to take action, not just write about we like "them to be there". Thats obvious :).

Its like "make the code better" and "refactor the code to be readable" tickets :). Thanks for listening!