Membership, post to volunteer #1
Comments
|
Hello, my name is Artem. |
|
Where can I get an overview on what needs to be done? Might be able to contribute.. |
|
Thank you for reaching out, we are very happy to see interest in the project growing. Right now the best overview is currently on the Volunteer page. We are currently just looking for developers who can help maintain the existing clients with the DAO HF code removed. Our aim being to allow easy use of the existing clients without any special flags. We could use more assistance on go-ethereum since I'm currently actively involved in setting up infrastructure, organizing and general support. This is the primary client so it is important. Mist is also an important project, I hope to finish restoration (removing DAO specific code) today but I would be happy for anyone to take on managing upstream patches. We also have need for development on an open source block chain explorer, one exists for Ethereum but it is rudimentary. A way to easily validate contracts on the network is important and this feature does not yet exist in an open source explorer. We could also use a contract to operate as a multisig trust, to transparently hold any funds donated to the development efforts that can be managed in a decentralized way. If you are a developer you are also welcome to just contribute to the discussion and weigh in with your experience. Also if you have ideas for things you think we should be doing I'm interested in hearing them. I think there may be a use for an interactive infographic that analyzes the DAO on our side of the chain so people can easily see the outcome of the situation, that seems to be a question that is raised a lot and having a resource to help people identify the status would be of interest to many. |
|
Is anyone working on a block explorer right now? If not, I'd like to take the lead on that one since we need one. |
|
Hi, I have been a fullstack developer for more than 10 years. Have recently started exploring blockchains and am new to Ethereum. Let me know if I could help in any way. Regards |
|
Hey all! I am very excited to try to help out this project and keep Ethereum Classic alive and well. I am a web developer, full stack capable but shine on the backend. Languages: Ruby/PHP/JS (Node) Please reach out if there is anything I can help with or even custom development/creation @whatisgravity . |
|
@elaineo @aakilfernandes is working on one: There is also http://gastracker.io/ but I'm not sure where its code is. |
|
@arvicco The gastracker.io project is managed by @splix who has volunteered but I'm not sure if he is interested in releasing the code open source. It is his choice and we should respect whatever that is but I hope he considered the idea of making it open source because I think it is well done. It could speed up development and allow for others to build from the great work already done. Not to minimize how much we appreciate you both offering your time, I like to give well thought out individual responses but I think this reply really works well for both of you: if you decide to do this, please don't simply fork the project but pull the code down, create the project in our organization, change the remote and push to the remote. The reason for this is that forks are treated as second class citizens on github, without doing this we can't get access to features like full text search. Doing it in this way also maintains all the commit history so every author is properly credited for their work. The community would appreciate any additional contributions to block explorers as they are a valuable tool which benefits everyone. I went ahead and invited you to the project under the pretext you would work on that but you are welcome to shift to another project, if you do decide to shift just notify us so we can help you get started. |
|
@matthewjamesr Thank you for volunteering your time to the project, your experience seems like you could fit in different projects. If you have experience with web frameworks like rails you may be comfortable diving into Meteor which is the foundation of the Mist client. I have started but have been sidetracked by other tasks, you can either assist in restoration (removing all DAO specific code) and maintaining upstream patches. There is also both JS and and Ruby client, if you are interested in maintaining either of these they are both valuable. I'm not exactly sure how much DAO specific code does exist in these projects, I did not yet investigate but you could also just improve the existing code while maintaining upstream patches. Alternatively the statement above about the block chain explorer may also apply to you. I have invited you to the project. As a reminder to everyone interested, you don't have to just work within the existing projects, you can find other relevant projects to maintain or even start new ones. Just try to document everything as best as you can, and add a description to the volunteer document so others can find it. |
|
@whatisgravity current implementation is really bunch of hacks, it doesn't look good to be release to open source. But now I consider to make another browser, based on my experience, that will be open sourced. The only problem that with all of this happening right now I don't have time to do it right now |
|
@splix Perfectly understandable, each iteration of a project like that gives you new insight on how to improve it. Thank you for putting one together as quickly as you did even if it is just hacks at this point, it has really been helpful for everyone. We look forward to your next iteration. I respect the fact that you built it from essentially scratch because it will make it so there are two foundations to build ETC block explorers from. This kind of diversity is really valuable. @nnadir @elaineo With the information splix provided above, I think if you are interested in contributing to a block explorer it may be best to continue the one found here https://github.com/aakilfernandes/explorer You are also welcome to build your own within the organizational structure too if you feel more comfortable with a specific framework. |
|
@arvicco Do you have any need for assistance on the primary information website? @soundbit is offering assistance. @soundbit Do you have experience primarily with web application development or design, or both? Knowing more details about your background helps identify where you can be most effective. Thank you for volunteering. |
|
Just a friendly reminder, it would be best to use multifactor authentication for your github account dedicated to this project. The security of your account associated with this project is important for the overall security of the community. |
|
@splix I have built custom block explorers before as well ontop of a custom blockchain for proof of concept. I would love to contribute and will create a repo under the org structure. I think it would be a great idea to lock down design cohesiveness as we try to gain more users. That will help others realize, potentially, what services are being worked by this group of developers. Thoughts @whatisgravity? I think the perfect choice for framework would be MaterializeCSS. |
|
@matthewjamesr Any suggestions for a backend? Would it be from scratch or starting from the https://github.com/aakilfernandes/explorer explorer? |
|
@whatisgravity I was thinking custom due to not as many developers being great at nodejs verses php/ruby. I built my first in ruby/rails very basic or could even use php/laravel. Edit 1: I am ok with any option just trying to get a consensus. |
|
I was thinking about something JVM based for backend (groovy/clojure/java). Maybe Golang, but I'm not so familiar with it. Server is needed mostly for additional indexes and custom search. |
|
I completely agree splix about the focus: Geth should be ready, it just needs to have the bootstrap nodes added. I need to check if there are any upstream patches not yet added since my last commit. I'm currently working on Mist. I deleted the project and should have a version ready soon. Do you have a feel for the progress of EthereumJ? I have not yet had time to investigate myself. @matthewjamesr I think a RoR version may be accessible, you could always lay the foundation with that and Materialize CSS. I have experience with both those and can in the future help contribute to at least guarantee it will have the basic feature set others can build from. If you want to do nodeJS it may be better to just work from https://github.com/aakilfernandes/explorer which I believe is a node project. |
|
I agree about focus as well but that will be slightly outside of my knowledgebase. @whatisgravity I will go ahead with a RoR-based explorer for us, will get a repo up tonight and a basic version hopefully by this weekend. |
|
Can we have some place where we can chat? Also, I've noticed that we don't have write access to the repos, are we supposed to fork and make pull requests? |
|
@splix Like a Telegram group? |
|
@matthewjamesr telegram ok, if that works for @whatisgravity |
|
@splix I noticed that too, I started working on creating teams and will address the access immediately. Also upgrading you to owner so I can save you time, there is no need for you to just be a member. I'm okay with telegram |
|
Everyone now has write access, we can add more granularity if we see people abusing it. |
|
@whatisgravity thank you! I've added a ROADMAP.MD, feel free to update. Community is really worried about our plans and when they'll be able to use ETC chain |
|
Hey, I'm pretty strong when it comes to node. I can pick up on @aakilfernandes block explorer where he left off. @matthewjamesr is that okay with you? If there are other urgent tasks I can direct my efforts there instead, but otherwise I'm gonna move ahead on the block explorer. |
|
Would anyone be opposed to using IRC? I'm pretty old school. I'm already on: oftc.net reticulum.oftc.net In the channel #etc-dev I think this would be preferable too because it would be more transparent, anyone can join the channel, and no one has to give out phone numbers. |
|
@elaineo That sounds like a good fit, with your experience in node your help may be useful for future mist client management but I can handle the initial restoration. |
|
@mikeyb I agree with the HTTPS recommendation. Let's encrypt makes it very easy to setup for free and ensures the security. I also recommend setting it up in a way there is perfect forward secrecy. I also agree about the comment regarding the repositories. The github fork is a logical abstraction that doesn't work well for our case. Forks are treated in many ways like second class citizens. Also in the future, if this project is successful we should move to a decentralized git hosting solution and the fork abstraction status in github will be irrelevant. If done properly every commit is saved, the git history is untouched, which is important. That said, for small projects, I think it is really up to the developers working on the project, how they want to handle forking vs. cloning. |
|
@whatisgravity Oh, I see. I'm not familiar enough with open-source licensing to know how appropriate it is to create a new repo vs a fork. The creators of etherwallet complained on reddit about improper attribution when a new repo was created for the chrome extension. |
|
@elaineo do you have a link to that reddit discussion? For etherwallet specifically, just leaving the LICENSE.md file with the current attribution in place should be fine:
You can create a brand new repo with all the current code and use it however you like as long as that license stays in place.
|
|
@mikeyb On Tue, Aug 23, 2016 at 2:07 PM, mikeyb [email protected] wrote:
|
|
Yes, I would also like some clarity on the open-source licensing. It is getting rather annoying hearing from reddit 'lawyers' and random github contributes about how our project should display and place attribution. As such, at what point of changing a project is it no longer "related" to the parent project and they can just be left in a license file. The chrome extension and ether wallet project are approaching the point of being quite different from the myetherwallet project as it was forked some time ago. There is little or no need/desire to import changes from the parent(at least by me); so it seems improper for the original owner to insist their name be listed everywhere(ie the mist debacle). I do understand that work was put in prior to our fork and I do not mean to diminish it in anyway, but at the same time our modifications fundamentally change the original design, intent, and function in many aspects. Linux projects and other floss are a lot more fast and loose with their rules from my experience. |
|
@realcodywburns They vary. You have to understand the license of the software you are copying. For your project https://github.com/realcodywburns/ETC-CX-Wallet you are violating the license by not including it. You must include a copy of the license and You can read the license of the software you are modifying at https://github.com/kvhnuke/etherwallet/blob/mercury/LICENSE.md Specifically:
You are using most of their base code from that plugin, so you must include the license. Just because you don't feel the need to pull in changes that they make doesn't make their license invalid. The intent and functionality of the software is still as it was from the creator. Now if you took a piece or two of their code and incorporated it into a project you created, you most likely would not need to license to remain in tact. Since you are still using "substantial" portions of their software, i.e. their entire browser plugin minus a few variable and image changes I would highly suggest including their license back into the software. |
|
I am all for including the license. It has never been removed. I'm referring to the request to include links to their original fork. The comment was made the because I was working on a fork of a fork( ethereumprojects fork of elaines) that I was being deceptive. |
|
Where is the copy of the license in your version of the software? I do not see it. You took a substantial portion of their software and didn't copy of the license best I can tell... It's an honest mistake, I am in no way faulting you. But you should definitely add the license back into your copy of the software. You in no way have to include links to the original fork, per that license. |
|
Ah, I see the confusion. The repo in my personal git was my editing offline version. The actual project is the ethereumproject/etherwallet. My repo was for offline editing and is not linked in any of the documentation as it is a subset of the actual project. It (the real project) was updated when the offline work was completed. Git hub doesn't allow for forking sections of a project that I know of. I will fix that. The actual project is what I am referring to. |
|
@colibry545 I would like to be readded, was quite busy last month. I should be able to find more time shortly. |
|
@jikkujose That would be great! |
|
tl/dr: Don't just believe me or others when they make statements in areas they have no expertise in. Instead, when in doubt, reach out to the free resources available to free software developers and learn more from unbiased sources. In essence, GPL license is designed to keep free software and all derivatives of the software free. Free as in freedom, as in anyone who obtains it can copy it, modify it and redistribute it with the condition being that it remains free software, by maintaining the license files and a list of authors/contributors. For example, we could remove the .git folder and pass around and modify the source on a floppy, long as the AUTHORS file, the LICENSE file stay included. Handling Github Forks & Licensing Git (with or without github) is very helpful because it provides a complete commit history attributing all authors to their work. The git commit history itself is intact when doing the method above. This is important because (1) it tracks author contributions so copyright ownership is known (2) keeps track of who is responsible for what additions, what were included with those additions, and a commit message that can explain the commit. There are three relevant files important for this discussion found in a lot of open source and/or free software projects. LICENSE, AUTHORS and COPYRIGHT. For clarification, no one should remove or alter the LICENSE file, remove the COPYRIGHT file, remove the AUTHORS files. You should only amend the COPYRIGHT, and AUTHORS file when necessary. If copyrights are found in the headers, you should not remove them unless the file was completely rewritten or it is being moved. You can move copyright attributions, including the ones found in headers, to a central file in the top directory but it is best to do this only when it makes sense to do so. You should consult with the FSF or other free resources when in doubt. Concerns about Mist In the case of Mist, I'm moving the copyright to a COPYRIGHT file in the top level directory of the source code. In this situation, there was only a single attribution in the entire project and it did not even exist within the source code, so I'm proposing an actual COPYRIGHT file to clearly state the status and in the meantime I'm letting the EF developers offer alternative solutions. The EF developers are being encouraged to create the COPYRIGHT file, or add it to AUTHORS, or add the copyrights to the headers of the relevant source files. This allows them to specify their preferred wording. If they do not do this before the first official release, I will be copying in the copyright that was once in the about page into the new COPYRIGHT file and adding additional text above it. I'm not an expert, it is my understanding that the contributors themselves not the Ethereum Foundation holds the copyrights to the commits but I will leave their text as is if they offer no alternative. The contributor list mentioned above is found in both the git commit history in the .git folder and the AUTHORS file. They are linked to in the About page and the AUTHORS file and the new COPYRIGHT file will be included with the binaries. Many of the Ethereum projects we are maintaining for the community are GPL, free software licensed. This license is specifically designed to ensure the software and all derivatives of the software stays free software. All the code is already copyrighted by all the contributors, it is by default even without explicit attribution.
The goal of the license and the copyright is to ensure that all derivative work is free software. The most important parts relevant to us is that (1) all authors are attributed (git commit history is completely intact, AUTHORS file exists) so it is clear who holds the copyrights, AND (2) that the LICENSE file is not removed or modified so everyone knows it is it is free open source software under the GPL lisense. If the application is a GUI application, then you need to link to the source code and specify the license being used somewhere in the UI. If it is a binary CLI release there should be a README including the same information. This is based on the information gathered from the many free software legal resources I reached out to when complaints were levied. I'm actively discussing the issue with lawyers who specialize in this field to understand the fine details. I will update and amend the information in this post as I get more details. When in doubt, ask the FSF. If an issue arises When in doubt, ask the Free Software Foundation (FSF), they are very understanding and helpful in providing clarity with the license. They should be your primary resource but there are many others who offer free support for free software developers. Don't just believe me or others when they make statements in areas they have no expertise in. Instead, when in doubt, reach out to the free resources available to free software developers and learn more. In this ecosystem, more than other areas of the developer community, a lot of people have financial incentives to be disingenuous. It is always better to get help from unbiased experts who offer free resources to free software developers. Free Software (free as in freedom) I'm not just pandering, I actively use free software. I run a distribution of linux which prioritizes free software, I avoid using proprietary software whenever possible. This is why I'm on oftc.net IRC connecting with free software and not Slack. I would even say I'm evangelical about free software, you should all use it, start with your operating system. If you have time here are some good articles on the subject, to help elucidate the subtle differences between free software and simply open source software: https://www.gnu.org/philosophy/free-software-even-more-important.html I think a lot of the writing is relevant to us:
|
|
I will clean that post up and make a separate issue regarding licensing since it is an important topic. |
|
Is there still activity on EthereumJ? |
|
@elaineo Would you mind if I cloned etherwallet and created a new repository and pushed it there with the full commit history. I can rebuild the issues too. I can take full responsibility too, so if anyone complains, you can direct them to me and I will explain the pragmatic reasons for the choice. |
|
@whatisgravity Fine with me, I had stopped working on it because @jsmith-dev was planning to take the lead on further development. @jsmith-dev, you still in? |
|
Hello. I've been watching the development of the classic Ethereum flavor and would like to help. My time is pretty limited right now, but I can contribute to cleaning up docs if that's needed and maybe a bit of coding (JS, Ruby, Python, Go) if the opportunity arises. |
|
@beholder0x2a We would appreciate your help with cleaning up documentation for readme files for some of our projects. Currently readmes contain many links to Ethereum(ETH) like links to issues, wiki, download links. Please take a look at Readme files for Mist, go-ethereum and web3js. |
|
@whatisgravity we made a release with fixes and support for Classic not so long ago. And now we're waiting for new changes from EF. Basically EthereumJ is following upstream master from EF EthereumJ, but they didn't commit much to this branch since last release. We'll merge existing commits, there're just few of them. |
|
Guys, can you please add your pgp public keys https://github.com/ethereumproject/volunteer/tree/master/Keys @avtarsehra @cjdelisle @igetgames @rguiu @jsmith-dev @masonicGIT @Machete3000 @MrComputerCodes @PANGUexe |
|
Done, I just need someone with write access to merge #23.
|
|
@colibry545 thanks for the direction, I'll go through those Readmes this weekend. |
|
@beholder0x2a I sent you an invite, and added you to the groups you listed programming knowledge in. Can you pull the wiki from the EF organization? I have been leaving issues with reasoning for changes and it just gets ignored, I think its a good resource but seems a lot of it is out of date. |
|
@colibry545 @whatisgravity I imported the ethereum/wiki repo to our namespace and so far updated all the links in the geth wiki to point to the ethereumproject namespace. Would it make sense to make a "Wiki" team for eventual community editors? |
|
@beholder0x2a Thank you for your assistance! If you would have more time, you can check https://trello.com/b/aiSzWBm7/ethereum-classic-clients if there is anything you can help us with. |
|
@colibry545 bh0x2a |
|
This issue has been opened a month ago and it has 200 comments. I have opened a new one #27 Please post there if you would like to volunteer. |
|
@colibry545 Please don't close this issue as well, as the link to it has been posted all over the Internet. |
and others
Please post here if you would like to gain membership to the ethereumproject organization which manages the Ethereum Classic development (ETC). Please introduce yourself, tell us your skillset and how you can contribute to the project.
We will try to remain open as possible but everyone will needed to be added on a trial basis to prevent potential abuse.
For volunteers interested in helping with community organization, management and other administrative tasks please visit: https://github.com/ethereumclassic/README
I will be removing inactive members of the organization. This will prevent accounts from being potentially abused later. With our liberal write access policies this is an important policy. We can be less strict when we add more granular access to the repositories.
If you are removed you due to inactivity, you are not penalized or punished, and are welcome to request to be re-invited back into the organization.
The text was updated successfully, but these errors were encountered: