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

Next step: collaborative database #36

Open
cynddl opened this issue Mar 19, 2014 · 1 comment
Open

Next step: collaborative database #36

cynddl opened this issue Mar 19, 2014 · 1 comment
Labels

Comments

@cynddl
Copy link
Contributor

cynddl commented Mar 19, 2014

I was wondering how to move the database forward, to make it easily editable by everyone.

A json file in the repository or a wiki file… are not right solutions for me. I propose to make a depository on Github only for the database, with a file for each program/attack vector/…

Such architecture would be:

  1. easily editable and collaborative (simple structure in plain text, with comments, issues…);
  2. easily integrable (a small script can parse the files and convert them to json).

Give me is your opinion on this proposal.

@albancrommer
Copy link
Owner

Well, why not. But I am currently in the process of implementing a solution based on keeping versions and drafts proposed by new comers in the database.
So 2 points : 1. I wouldn't have time to code your idea 2. I find it a bit akward on the long run to edit file texts.
But if you come with a solution to import / export, that could work.

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

No branches or pull requests

2 participants