Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Direction of the project #13

Open
kinggoesgaming opened this issue Oct 14, 2022 · 1 comment
Open

Direction of the project #13

kinggoesgaming opened this issue Oct 14, 2022 · 1 comment

Comments

@kinggoesgaming
Copy link
Member

I want to work on this project now that uuid@1 has been out. I did start out here, but as I have done work on it, I have realized that there a couple of issues

Issues

  • The pesky .idea directory: While not a high priority in itself, this is adding of unnecessary git diff churn and that will an issue over the long term.
    • I have tried to remove the file, but somehow it keeps coming back.
  • When I started, it was unplanned development. Essentially when I initially started work on this, I had certain ideas, but with me gone for this long, have completely forgotten them. I figured as I developed this, I would get that back, I guess not!

Structure

For the sake of discussion, I am going to refer the project as ruuhid

What I was thinking was having 3 binaries:

  • ruuhid: The primary project, that this repository was created for. Will have its own subcommands and options.
  • ruuhidgen: Will be equivalent of man 1 uuidgen, but just using uuid as the library.
  • ruuhidparse: Same as above, but for man 1 uuidparse.

Direction

This has given me a couple of ways we can go forward on this, but need advice on it:

  • We continue work here, as is, including figuring out how to get rid of the .idea directory.
  • We purge the current work in directory. This will mess up the entire working tree, but as only one fork (and I know the person, is fine with it), this should theoretically work fine.
    • I am still iffy about purging the working tree though.
  • Archive this repository and start anew. We can go 2 ways here:
    • Just create another repository and start work there.
      • This allows independent development from the uuid crate.
    • Incorporate this directly into the uuid repository as binaries.
      • Allows to stay on the latest version of uuid if we need to, but this may not be desirable, if not now, in the future.

cc @KodrAus, what do you say?

@kinggoesgaming
Copy link
Member Author

@KodrAus pinging you again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant