Make a tool to automate much of the proofs. #42

Open
opened 2 years ago by yisraeldov · 7 comments

The adding off proffs right now is pretty tedious, and it seems like it would be a good idea to reduce the barrier of entry and have a tool (command line or gui) that would automate much of the process.

The adding off proffs right now is pretty tedious, and it seems like it would be a good idea to reduce the barrier of entry and have a tool (command line or gui) that would automate much of the process.
yarmo added the
enhancement
label 2 years ago
Owner

Completely agreed, we need simpler tools! I'll have some news about this front soon :)

Completely agreed, we need simpler tools! I'll have some news about this front soon :)
Poster

There was one on github, I asked him to move it here.

There was one on github, I asked him to move it here.

@yisraeldov

There was one on github, I asked him to move it here.

It has been moved here: https://codeberg.org/shom/keyoxidizer

@yarmo I chose an Apache v2 license for this to begin with. I read your reasoning behind AGPL for keyoxide and that makes a lot of sense. I think it might make sense to leave the driver/interface like keyoxidizer as Apache v2 so non-GPL software can use the utility to interface without concern (and it's all client-side). This is the same model that MongoDB uses where the core DB is AGPL but the drivers are Apache.

I wanted explain my rationale and wanted to check if I was missing anything.

@yisraeldov > There was one on github, I asked him to move it here. It has been moved here: https://codeberg.org/shom/keyoxidizer @yarmo I chose an Apache v2 license for this to begin with. I read your reasoning behind AGPL for keyoxide and that makes a lot of sense. I think it might make sense to leave the driver/interface like keyoxidizer as Apache v2 so non-GPL software can use the utility to interface without concern (and it's all client-side). This is the same model that MongoDB uses where the core DB is AGPL but the drivers are Apache. I wanted explain my rationale and wanted to check if I was missing anything.
Owner

Great to see Keyoxidizer move to Codeberg \o/ with regards to license choice, sounds good to me!

Great to see Keyoxidizer move to Codeberg \o/ with regards to license choice, sounds good to me!

@yarmo

Great to see Keyoxidizer move to Codeberg \o/

For full transparency, I'm pushing to both github and codeberg in the utility's spirit of making things easier for users. But codeberg will be a first class citizen (I've self-hosted gitea for a while and really like it and I'm in support of codeberg in mission and donating).

@yarmo >Great to see Keyoxidizer move to Codeberg \o/ For full transparency, I'm pushing to both github and codeberg in the utility's spirit of making things easier for users. But codeberg will be a first class citizen (I've self-hosted gitea for a while and really like it and I'm in support of codeberg in mission and donating).
Owner

Update on this: I tried to include key management features in the https://codeberg.org/keyoxide/cli project but it turned out to be slightly too complicated for now. Keyoxidizer is still the only claim management tool for now.

I'm still looking into ways to add this to the "official" keyoxide cli but if I find the time soon, I will contribute to keyoxidizer.

Update on this: I tried to include key management features in the https://codeberg.org/keyoxide/cli project but it turned out to be slightly too complicated for now. Keyoxidizer is still the only claim management tool for now. I'm still looking into ways to add this to the "official" keyoxide cli but if I find the time soon, I will contribute to keyoxidizer.
shom commented 1 year ago

I'm still looking into ways to add this to the "official" keyoxide cli but if I find the time soon, I will contribute to keyoxidizer.

@yarmo if you'd like to and it makes sense with your vision/architecture, the keyoxide cli could call the keyoxidizer script and keyoxidizer can exit back to keyoxide cli. If you're interested in doing that and want to package keyoxidizer and make it a part of keyoxide, I would be happy to make keyoxide cli the owner. I also welcome any other ideas on collaborating!

If you do find some time to contribute to keyoxidizer, I could absolutely use some help on this issue: shom/keyoxidizer#1!

> I'm still looking into ways to add this to the "official" keyoxide cli but if I find the time soon, I will contribute to keyoxidizer. @yarmo if you'd like to and it makes sense with your vision/architecture, the keyoxide cli could call the keyoxidizer script and keyoxidizer can exit back to keyoxide cli. If you're interested in doing that and want to package keyoxidizer and make it a part of keyoxide, I would be happy to make keyoxide cli the owner. I also welcome any other ideas on collaborating! If you do find some time to contribute to keyoxidizer, I could absolutely use some help on this issue: https://codeberg.org/shom/keyoxidizer/issues/1!
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.