-
Notifications
You must be signed in to change notification settings - Fork 10
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
Internet of Ownership #174
Comments
Ping'd on Twitter. |
Hi. |
In. |
Hey @devinbalkind @nathanairplane. :-) Application looks almost good to me. At first I thought that the onboarding and to-do links were the same as the homepage link (something we see fairly frequently). I see now that they're different. While the task list seems somewhat quirky and sparse, it's fine for our purposes here. Looking at the development page, though, the "Submit" link is 404, but the thing I'm most hung up on is "to become involved as a developer, please contact the administrator." It's hard for me to say that that passes muster on our "open work" criterion. Seems like development work is essential to IoO—why have this roadblock to developer involvement? Why isn't the code in {Bit,Git}{Hub,Lab,Bucket}, where it can be easily hacked on? |
Thanks for the ideas. I fixed the Submit link. The main reason that we don't have the code on git is that we don't have code, really. This is currently, for now, a totally default WordPress install and theme. The main content of the site that we're focused on developing at the moment is
Code development will be essential in the future, but it is not now, so we see no need to start a code repository until there is code to put there. |
Fair enough, @nathanairplane, thanks for the additional context. Looks like you've updated the copy on the development page to steer folks to the (open) mailing list rather than your private email. I'm satisfied. :-) I look forward to approving this next week if no-one else objects! :-) |
Approved. |
https://gratipay.com/internet-of-ownership/
(This application will remain open for at least a week.)
The text was updated successfully, but these errors were encountered: