Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

latest 1.7.2 source #6

Closed
tehface opened this issue Aug 15, 2014 · 27 comments
Closed

latest 1.7.2 source #6

tehface opened this issue Aug 15, 2014 · 27 comments

Comments

@tehface
Copy link

tehface commented Aug 15, 2014

hey there, wondering if this is the latest 1.7.2.x source as am wanting to port to iOS

cheers :)

@prurigro
Copy link

I'm not the author, but I built and ran the latest commit in this repo and can tell you that the source here is currently for v1.7.1c; which makes sense as the most recent update on the Play Store is a good week or two after the most recent commit here.

Cheers!

@tehface
Copy link
Author

tehface commented Aug 15, 2014

he has released 1.7.2a on the play store so you need to update 💃

@ghost
Copy link

ghost commented Aug 15, 2014

If the maintainer can take the time to make new Play Store releases, be active on twitter, and make blog posts, but can't even occasionally respond to this project's issues/pull requests, then I don't know why they open sourced it in the first place. I'm not sure if @watabou doesn't have email notifications enabled for this repo, or is just being inconsiderate. This was willingly open sourced (presumably), so at least give the minimal amount of responsiveness necessary to not make [potential] contributors feel completely ignored.

@dustinfreeman
Copy link

@pyrohh dude - this is a single person, with finite time, who may have multiple projects, of which Pixel Dungeon may just be a hobby.

From my experience, when you're adding new features, there are a couple steps:
0. Think of feature

  1. Code it up, make sure it works
  2. Put out for testing (in this case, publish on the Google Play Store).
  3. Observe how people interact with new features
  4. (Optional) Document and cleanup in preparation for adding more features.

From @watabou 's point of view, it doesn't make sense doing #4 until the features are stabilized, and it would lead to fragmentation for anyone who's forking the repo.

You can probably be patient.

@ghost
Copy link

ghost commented Aug 16, 2014

I think you misunderstand me. I'm not asking @watabou to do any significant work, I'm not asking the maintainer to implement any of the pull requests, I'm not even asking him to fix any of the bug reports. I'm just asking @watabou to acknowledge the contributions that people are doing on their own time, for free.

The least @watabou could do is respond to some of the damn issues saying what he/she thinks about them.

From @watabou 's point of view, it doesn't make sense doing #4 until the features are stabilized, and it would lead to fragmentation for anyone who's forking the repo.

See above.

The worst possible thing @watabou could do to the contributors is ignore them, and that's what has been done. Not a single issue has been responded to by him/her. How would you like it if you helped someone in public out of purely altruistic intentions, only to be completely ignored? I'm not asking hours of time to be invested, just for a simple comment to acknowledge contributors.

You can probably be patient.

I'm annoyed at @watabou's behavior, not because I feel entitled to a constant and rapid feed of high quality game content for free. A good example would be the silver searcher. I submitted a pull request to that project knowing that the maintainer was busy; he had a few comments left on recent pull requests stating that he was busy but would get around to them when he had the time. He eventually did get around to them, and I felt my work appreciated because he had been transparent.

Again, @watabou hasn't responded to any feedback on this project (at least on GH). If he doesn't respond to GH requests, then a note should be left in the repo saying so. Either email notifications aren't enabled, or he's just being apathetic.

@tehface
Copy link
Author

tehface commented Aug 16, 2014

you know i didn't want to start some " great debate " and i would like it if you don't come to a issue request and start a moan fest it was a simple question.. and for that i don't need to read all of this crap.. am closing the issue and thanks to the moaners on here losing interest in an iOS port really fast.. thank you and good bye

@tehface tehface closed this as completed Aug 16, 2014
@ghost
Copy link

ghost commented Aug 16, 2014

I stand by what I said, but I suppose this was the wrong place to bring it up. Sorry.

@tehface
Copy link
Author

tehface commented Aug 16, 2014

i really don't care what you have to say, the author can do whatever he wants, after all its his project, it does not " give you the right " to tell him what and how to do things period!

@ghost
Copy link

ghost commented Aug 16, 2014

i really don't care what you have to say, the author can do whatever he wants, after all its his project, it does not " give you the right " to tell him what and how to do things period!

Did you even read my post? You're defending incompetence and defending the fact that you haven't gotten an official response. This is hopeless, unsubscribed.

@vlaaad
Copy link

vlaaad commented Aug 18, 2014

@pyrohh +1

@schuylernathaniel
Copy link

The author also doesn't respond to the email he gives in the game and everywhere else that I can find. Its been over a week with three emails sent and no response for any of them.

@vennumallesh
Copy link

I agree

@phikal
Copy link

phikal commented Jan 7, 2015

Updating the repository is even easier than being active, and even that is not done.

@vennumallesh
Copy link

same

1 similar comment
@RameshDasguptasinghpatolai

same

@vennumallesh
Copy link

i agree with @yoyoHoneyS1ngh and @schuylernathaniel

@vennumallesh
Copy link

@yoyoHoneyS1ngh same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants