RE: Call for Steem Developers - Building Curie's frontend
I know xeroc has some major skills. I'm not doubting the abilities, nor the intentions. I have been a great advocate for curie, having upvoted every post I have ever seen and made posts requesting that others do the same.
I have seen in the past others speak of their distaste for curie, and it is that which I referred to in my previous comment.
If we go this route - the code will be closed, but its operations can still be made transparent..
By the operations being transparent, do you mean that someone will explain what's going on in the code, but without it being publicly viewable?
If so, I feel that any transparency in that case would be subjective, for one would need to place there trust in a human, rather than in a visible, irrefutable code.
I fear this would not help to sate the reservations of those that already harbour doubts about Curie, and I would hate to see anymore animosity within the community in regards to this issue.
I feel Curie offered me a ton of help, and I know they have helped a lot of others too. It seems that, based on this post, it was already part of the plan to make it open source, perhaps for similar reasons. I don't think that you should so easily abandon your initial vision for this new advancement of the project.
I understand why open source aligns well with Curie's spirit and that has always been the intention. However, personally, I feel Curie's primary goal is to curate posts; reward and retain new authors. So far, we haven't really heard back from any developer who would make this an open source project and finish in a timely manner. So it's a simple dilemma - consider closed source by committed developers or the new authors you seek to reward suffer due to lower operational capacity.
Of course it's important that even if it's closed source, other curation guilds have access to this functionality.