Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Parity node clean-up tracker ticket. #8649

Closed
4 of 5 tasks
5chdn opened this issue May 17, 2018 · 5 comments
Closed
4 of 5 tasks

Parity node clean-up tracker ticket. #8649

5chdn opened this issue May 17, 2018 · 5 comments
Labels
F6-refactor 📚 Code needs refactoring. F9-meta 🔮 A specific issue for grouping tasks or bugs of a specific category. M4-core ⛓ Core client code / Rust. M5-dependencies 🖇 Dependencies. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@5chdn
Copy link
Contributor

5chdn commented May 17, 2018

The next release shall not happen if we did not address the following points.




  • Enforce consistency of crate naming, rename ethcore-* crates to parity-*
@5chdn 5chdn added F6-refactor 📚 Code needs refactoring. M4-core ⛓ Core client code / Rust. F9-meta 🔮 A specific issue for grouping tasks or bugs of a specific category. M5-dependencies 🖇 Dependencies. labels May 17, 2018
@5chdn 5chdn added this to the 1.12 milestone May 17, 2018
@folsen
Copy link
Contributor

folsen commented May 21, 2018

I would argue the last point is not a release blocker. That is strictly behind-the-scenes and could actually be a lot of work.

@tomusdrw
Copy link
Collaborator

Yeah, I had also a discussion with @debris where we think that parity-* should be reserved for potential secondary product names (like parity-evm, etc) and not necessarily internal crates. Most of the crates are sort of "ethereum core" and that's where the name came from (suprisingly colliding later with the company name).

@debris
Copy link
Collaborator

debris commented May 22, 2018

Crate renaming definitely shouldn't be a release blocker. I would also reorganize location of our executables. Now they are difficult to find for people not familiar with the project. It would be cool if we place all of them in a single directory

@5chdn
Copy link
Contributor Author

5chdn commented May 31, 2018

Makes sense, thanks for your input.

@sorpaas
Copy link
Collaborator

sorpaas commented Jun 1, 2018

I'm going to take a look at UI and Public Node removal if no one else is working on that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F6-refactor 📚 Code needs refactoring. F9-meta 🔮 A specific issue for grouping tasks or bugs of a specific category. M4-core ⛓ Core client code / Rust. M5-dependencies 🖇 Dependencies. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

5 participants