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

Extend/integrate/possibly reimplement opendefinition.org website #5

Closed
3 of 5 tasks
rufuspollock opened this issue Nov 3, 2012 · 12 comments
Closed
3 of 5 tasks

Comments

@rufuspollock
Copy link
Member

@mlinksva
Copy link
Contributor

mlinksva commented Nov 6, 2012

What does "integrate licenses.opendefinition.org" mean? Link to record there where license mentioned on opendefinition.org? This could be a place to put "text of licenses". Make opendefinition.org driven by data in licenses.opendefinition.org, such that former is only representation (cool, but lots more work)?

There's probably a lot of work that could be done on licenses.opendefinition.org regardless. For example, it'd be nice to use same short identifiers as https://spdx.org/licenses/ where there's overlap, and same style where not.

I don't see much need for an opendefinition-specific blog, which would rarely see posts, but if blog-per-project is generally how OKFn does it, great.

@rufuspollock
Copy link
Member Author

By integrate I would mean have on the same domain (or share at least same theme). e.g. licenses.opendefinition.org could be at /licenses/.

Re blog: agree it is not needed IMO.

Re license ids: would definitely be nice to consolidate only issue is that the ids are already in use somewhere in the wild so we could need a backwards compatibility plan.

@rufuspollock
Copy link
Member Author

@mlinksva PS I've just made sure that everyone with access to this repo has access to http://github.com/okfn/licenses

@mlinksva
Copy link
Contributor

mlinksva commented Jun 4, 2013

Renamed for clarity: Extend/integrate/possibly reimplement opendefinition.org website

Good idea, but needs some people's committed time to do.

@rufuspollock
Copy link
Member Author

Note we could merge licenses repo and this repo without merging opendefinition.org and licenses.opendefinition.org ...

@rufuspollock
Copy link
Member Author

OK, I'd like to revisit this and make it 2 specific suggestions:

  1. We merge https://github.com/okfn/licenses into this repo. I'd suggest that we relocate most of the content in that repo to /api (though possibly moving the index.html page to our licenses/ directory)
  2. We change opendefinition.org to run off github pages using this repo (with licenses.opendefinition.org relocated to opendefinition.org/api/ probably ...)

I don't think this is a lot of work and I'd volunteer to help move this forward.

@hlainchb @mlinksva @enyst what do you think ...

@mlinksva
Copy link
Contributor

Sounds good to me.

@mlinksva
Copy link
Contributor

Migrating content to gh-pages is easier than I'd though. Unstyled, but content from wordpress is now extracted into gh-pages in this repo. I've set CNAME to beta.opendefinition.org, hopefully OK sysadmins can set up DNS for that, I think this:

beta.opendefinition.org. 3592 IN CNAME okfn.github.io.

Edit: now at http://beta.opendefinition.org

@rufuspollock
Copy link
Member Author

@mlinksva booted a dedicated issue for github pages migration - see #47

@rufuspollock
Copy link
Member Author

@mlinksva as i understand it of the remaining checkboxes above #2 is probably WONTFIX as we don't want to dupe the other project. #7 is in progress but is a bit item and can be dealt with separately.

If this sounds right, can we note this and close this as DONE

/cc @hlainchb

@mlinksva
Copy link
Contributor

Makes sense to me.

@rufuspollock
Copy link
Member Author

FIXED.

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

No branches or pull requests

2 participants