Concerning Cosmos - I have no affiliation with them. I am a contributor to LotionJS which is built on Tendermint (a proof of stake blockchain).
I am happy to contribute code to a blockchain. I’d like to do that for NEM right now, but NEM isn’t set up for that. We have many problems to conquer before I or the community can make contributions.
Also it is important to note that NEM is not the solution to every blockchain need. This is an important thing for people who are a part of NEM to understand – especially when it comes to making promises to potential NEM adopters. If a company is looking specifically for customized on-chain smart contracts, they should know that NEM isn’t the right choice for them.
Right now it is not about competing blockchains, it is about spreading blockchain throughout the world. We should be friends with other chains.
It was an example, you know what I mean, no need to try and “word” me around.
It’s a great philosophy, I’m the same - blockchain for all as far as I’m concerned
You would be privy to highly sensitive information that could be an advantage. Are you willing to sign a non-compete? Just a yes or no will be fine, thanks
Sorry, wasn’t trying to belittle you. If I am able to operate Devslopes and the projects I am committed to I will sign a non-compete. If a non-compete was presented that prevented me from working on Cacheout or Devslopes I would have to decline the council appointment.
I can’t speak to how these particular individuals became involved or claim to have any knowledge on what they have contributed. I can explain how NEM open source development compares to other platforms and open-source projects. And this is all through my own perspective - I could be completely misguided.
There are no issues/features listed on any of the Github projects for developers to grab and work on
The catapult-server README does not include enough information to compile the source code. There are critical pieces of information missing which I had to figure out on my own to build the code (such as which version of C++ is used as well as which version of Cmake is used by the team - among other things). My point here is not to complain, but it is something that will prevent people from contributing.
Thankfully, due to you (gimer) and Jag I was able to obtain needed information through forums as well as Slack (Catapult Critical Development Information)
But it was not easy information to find.
I’ve raised multiple issues hoping to contribute or at least receive discussion, but never received responses or was left without ongoing dialog:
I’ve advocated the notion of making a list of features for devs to work on but was left without response:
I’m not angry or anything, but I wanted to give you my personal experiences in wanting to contribute to NEM’s code.
Here is my take (it could be wrong, but it is my take):
Core devs are very busy and can’t promote open source
There is no person who is driving community developer involvement
It is very difficult to have technical discussions with core devs
I think there are probably reasons why contributing is not as easy as Bitcoin, or the Lotion framework I have been contributing to. NEM roadmap not released and can’t be shown to the public. Devs are busy developing and not getting support from the foundation. In the NEM developer Slack channel, all public conversations are typically around issues with developers trying to use the SDKs. I’m not privy to any channel where discussions of features or bugs or issues takes place where I can participate ie “Oh Yeah I’m going to work on this bug”.
I think Aleix provides the most interaction with contributors on the NEM2 TypeScript SDK. I have been personally interested in contributing to Catapult and I think developers that are brought in the community will want the chance to contribute to the core blockchain.
My comments above in this thread are about creating a better open-source community. I’m not saying people have not contributed to NEM open source.
At the end of the day I do not personally believe that if I contribute, it will be valued or even considered/taken seriously. I feel confident that if today, I grabbed a Bitcoin issue and submitted a PR, someone would at least look at it and give feedback. This is the problem I am referring to at its whole (that I would like to fix).
We don’t have any active issues in our catapult-server repo because none have been opened, and we don’t have any known issues in the publicly released code. Our other repos do have issues, which you can feel free to work on, e.g.: https://github.com/nemtech/catapult-rest/issues. Additionally, you can always open issues for bugs, enhancements or feature requests.
The best contribution guide I can find for NEM tech is a boilerplate template:
The catapult-server README does not include enough information to compile the source code. There are critical pieces of information missing which I had to figure out on my own to build the code (such as which version of C++ is used as well as which version of Cmake is used by the team - among other things).
Other people (e.g. proximax) have successfully forked catapult-server and have made significant changes to it. They do not seem to have encountered the problems you mention.
So basically do everything that’s important from the tech and adption side of things, previous council members have (pathetically) failed to do, got it.
Personally, I recommend Mark Price for NEM Council member. I don’t know him personally but I got a free training via Devslopes!
Technical skills? Yeah he has it. We need a council member that can walk the talk, that can read codes so that where ever he is, we can sit down and help a NEM would-be adaption project. We don’t need talker, its time to upgrade the council membership to:
Skill sets:
Can talk the technology;
Can code the NEM coding language;
Professional and good customer relations;
Can determine a client or customer;
Can listen to the community;
A leader and not a bossy-playing person;
A person who can look into dissatisfaction of clients and not telling “If you don’t want NEM, don’t”
A person who is not a “pointing-finger” to get away from problem;
A well informed leader and not a “I have no clue” leader.
Mark Price, I hope you are more than what I enumerated!
I have some basic questions I’m asking all candidates:
What is your position on the current election process and using PoI for elections like this?
What is your position on making processes, decisions and information more transparent for the community? (Council decisions, who voted on what, Foundation Charter, roadmaps, etc.)
What is your position on the foundation’s outside communication?
There needs to be much more than this, I feel the same as Mark on this, but it isn’t anyone’s fault, it just needs to change if things plan to move forward. Code should be under a single “Organisation” on Github, it is time to culture NEM’s official “products”, the fact that NanoWallet is under a completely separate account doesn’t help as its the main wallet that NEM push, it should be under whatever NEM’s main Github is.
That might mean giving up some control on the code via PR’s but if it is managed properly with a proper code quality definition, automated tests, lint, coverage and CS ops built in then it shouldn’t really affect anyone. A release manager would help here.
I’m not really sure to be honest. At the end of the day I’m excited the elections are taking place. They almost didn’t happen at all. I’ll take what I can get.
This one is easy. Everything should be transparent. Voting history, budget reports, roadmap, charter, bylaws, etc. The entire community should be able to read the laws and clearly know what NEM council can and can not do, then also that lets those who break the laws be put in the spotlight.
I"m not completely sure what you mean. If we are talking about NEM Foundation communication - it is currently fairly non-existent. Every branch of NEM should work within bounds and rules and have scheduled meetings and reports.
If you are talking about NEM Council members taking part in outside projects I think it should work like any company. If you are an employee such as President, VP, Treasurer, etc you should do your job and not actively run a business.
If you are a council member (which is not employment) it is like you are on a board of directors. You take your experience in your own companies, work, history/etc and use that to benefit the foundation.
I think what we DON’T need is people on the council who don’t have a very specific skill. People should vote for council members who can add value to a specific area.
Yeah. I wasn’t trying to attack any of the team or developers. Running Devslopes the last few years and training beginner to intermediate developers we learn interesting things from our analytics. If a developer can’t solve a problem within a couple of hours, and can’t find a place to get help, they will abandon the technology.
We heard it all the time, “Oh I don’t use AWS because their tutorials are awful”.
My point is, this is the world we live in now - people learning through videos and documentation (instead of universities) - we just have to do some proper handholding in the beginning.
It is also important that developers in a community feel welcomed and valued. I don’t think this is the job of the developers as much as a technical community manager or someone who can foster good conversation, competitions, challenges, etc.
+1
There is a conflict of interest. Whose interests would be looked after?
Would decisions be taken in the best interests of NEM, and someone whose company is developing a competing fork of NEM would have insider knowledge for their competing products.
