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

Project State/Goals #37

Open
RogerTangos opened this issue Dec 2, 2014 · 0 comments
Open

Project State/Goals #37

RogerTangos opened this issue Dec 2, 2014 · 0 comments

Comments

@RogerTangos
Copy link
Contributor

Hi there,

I'm taking a breather from working on openPDS. Here are a few notes on what we've been working on and a roadmap for going forward:

What we're doing (as of December 2, 2014):

These are mostly derived from @bradmontgomery's #22

Things that I would do next:

(This is obviously subject to interpretation and debate)

  • make the code confirm to pep8 standards.
  • I'd remove access control, and replace with a user login. Contentious, I know, but access control creates some complications, and I don't think that the project is ready for it.
    -- at the very least, access control should exist as a separate django app.
  • Remove visualizations and meetup
  • Create a connector to datahub

datahub notes

This is for the creation of a datahub backend, through which users would be able to directly access and edit their data.

  • Create an openPDS user on DataHub.
  • Automatically create accounts and openPDS repositories for new users, including passwords.
  • Create openPDS repositories for each new account
  • grant select, create, insert, update, delete, to openPDS
  • send the user the username/password, remove it from openPDS
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