Ok, I have open an issue, it will be fixed in the next released but why not directly tell me that on github ?
You are viewing a single comment's thread from:
Ok, I have open an issue, it will be fixed in the next released but why not directly tell me that on github ?
I don't think you are ought to do that. That's not the process. Utopian after accepting the issue will add it to github as an issue.
What? But the purpose is not to solve the bugs quickly? Why wait for someone's approval to post an error (during hours, days, months? I don't really how the moderation work here)? If it really is, sorry but it's stupid. As a developer who works on his spare time, I can say that time is precious, if it is still necessary to wait to have access to error returns that can be resolved quickly or with other errors already in visibility of the same type. It's not terrible.
After I do not say it's your fault, I thank you for having seen the error but, I would like to know just as it is anyway me who will code.
That is great but hey thats how it works in utopian i guess. We are supposed to contribute to utopian before having it posted in github. I hope you understand.
I understand that it is the rules of utopian and that you have to follow them.
But I'm not going to wait patiently for a nice Utopian policeman, who comes from a platform I did not know two days ago, to give me permission to create a bug issue on my own repository. :) It's simply a big joke!
Hello @kunzisoft
In Utopian we make sure to check each and every bug report we get. We don't push issues to Github if we don't have a direct consent from the project owner.
Contributors are welcome to push Github issues themselves as long as Utopian is not mentioned in the process, to avoid any breach of the Github Terms of Service.
I suggest @neupanedipen to properly report an important issue on Github for the project owner to know and react immediately, since this is the main reason why Utopian incentivises bug reports and contributions in general.
I am really sorry for that in that case. I was unknown about the procedures. Thank you for letting me know!
I was actually waiting for the moderators approval and confirmation of the bug before actually wasting the PO's time.
I am extremely sorry the mistake.
Hello @elear,
Thank you for the response. I must say that I am a little lost by the platform, after that it is surely a time of adaptation but I still don't understand how all the elements work. I only know what my needs are in terms of development.
@neupanedien
I just think that we do not have the same constraints and the same objectives, the whole thing would be to harmonize the work but it takes a time of adaptation and understanding.
Obviously I am listening to improve things at my level because it is with listening that we advance. So, do not be sorry, you allowed me to quickly fix a bug! ;)
@elear
Can you tell me a little about utopian and how it works, it will help me a lot because for now I'm swimming in a lot of info and I didn't find a clear process. (I only know a small part of steemit). Do you have roadmaps for newcomers?
For utopian, I hope you don't have too much trouble and it will be resolved quickly, tell me if I can help?
Utopian is a platform to try to help fund people contributing and making open source projects by giving an upvote to them. The contribution reports are reviewed by a moderator to determine if they are worth upvoting and how much they are worth upvoting.
Check out https://join.utopian.io/ and https://join.utopian.io/rules/
Whenever you make an update on your project, you could make a development contribution and be rewarded by utopian if they deem it fit.
In this case, @neupanedipen made a bug report contribution. To make sure to not spam project owners, utopian used to wait until it was accepted before sending it to GitHub, but this was because project owners were getting spammed and seeing the utopian name, and it defaced the name.