First, I would like to state that I am writing this posts (and all of my feedback in these threads) as myself. Don't associate my posts with my role as a moderator. It hasn't happened yet, but just in case ;x
I Fight For The Users wrote:BasharOfTheAges wrote:Just gotta say, the sentiment behind "don't like the way I'm doing it? fork your own branch and change things." doesn't really mesh with having a feedback thread - especially if you want feedback from non-developers (i.e. the overwhelming majority of the user-base).
Sanya-nya has suggested changes based on a fundamentally incompatible design philosophy that I have rejected many times. The only solution forward in that case is forking. (Unless there exists a good explanation for why the present philosophy is wrong which nobody has yet advanced.)
Point 1:
Yeah. I wonder what I can do with said fork. Present it to my future employees, maybe, telling them: "Oh, and by the way, would you be interested in running an AMV database?"
I don't want to sound ill here, but as it stands now you're the basically only person willing and wanting to program this stuff here on the Org. Yes, there are probably some people, maybe even tens of people who could do it. But they don't have time or will to do it. And of those who could learn it, it's even worse, because they would have to learn it and only THEN write it. (As for me, I have no profficiency in RoR, Couch, Lucene, Perl, nor Mojolicious. I could probably get the grasp and start
helping, supposed I'd dedicate two or three months to it, as I've got the very basics of the "usual" stuff - php, Python, C#. Will I? No, most probably not.)
How do I know? Well, there's not anyone helping you write it, is there? No, discussions with people on #Grommet about what to use and tech stuff don't count. You're the only one who commits to this project.
And at this state, telling anyone to fork is just saying: "Hey, you can fork this, and play with it, but you won't be able to do anything with it until you have few months to learn to play with it. And by then my work will be done anyway (and will be ways better, because I know how to write in this) and you'll have a useless fork at your hands which you can show your friends."
I Fight For The Users wrote:Additionally, I am not interested in everyone's feedback. If I seriously considered everyone's opinion, the end product would be shit. I am instead working with a small group of people who I have come to trust. (So far: Ileia, AisuzuZwei, and Brad has chimed in about typefaces.) Membership is not closed, but I do give more serious consideration to feedback that demonstrates more than superficial knowledge of my goals and design principles.
Point 2:
You've just undermined the very three threads you've made here, congratulations. The fact that you don't even
consider feedback from some people (you wrote that yourself) is highly disheartening. And at this point the question arises, why don't you just pick those few people you trust and develop showing the website to only them?
And as for the last sentence - I know that you have the most power (if not all of it), writing the code. But from that sentence it seems that you know the best what is good for the community. Aaaand... I think that's not a good thing. If I wanted to, I could make a really ugly comparison here. And you could reply with a really nice comparison in reply. Well... after all, I just want to say that
I don't think it's a good thing to decide about the whole community for itself. Again.
I Fight For The Users wrote:The end product here might still fail, but it won't fail from lack of focus. (You know, because the past few years of this design thing have seen so much progress.)
Point 3:¨
My biggest fear at this moment? That even after all that mentioned above the final result will be fine. This way or that way. But no-one will be able to work with it except you and we'll get to dokidoki doing all the things again. Except it will be you and not doki. A perfectly documented and perfectly written website is kind of... useless if you want to add a new feature, or change an old one, and find out that you can't find anyone who works in RoR/Lucene
and is able and willing to dedicate some considerable amount of time to it.
Hah... lots of useless words FTW. I can already see how I am losing anyway orz