Code-dot-mil / code.mil

An experiment in open source at the Department of Defense.
https://www.code.mil
MIT License
1.28k stars 123 forks source link

Launch website based on ARL policy #92

Closed fulldecent closed 6 years ago

fulldecent commented 7 years ago

This is a starting point for #85

tomberek commented 7 years ago

Let's break out the root LICENSE.md as a separate issue.

fulldecent commented 7 years ago

Thank you for the review and support!

tomberek commented 7 years ago

It's been a busy month. Looking back into this now. We're starting with a blank slate at the code.mil.page repo. I'll start moving some of this over.

fulldecent commented 7 years ago

Sounds good, let me know if/how I can help.

fulldecent commented 7 years ago

Please let me know if there is an interest in publishing this repository to CODE.mil. I can update this PR as necessary to accomplish that.

jordangov commented 7 years ago

Sorry for the delay here. We've had people rolling off of DDS and shifting teams. I'll be looking into this effort more in the coming weeks.

fulldecent commented 7 years ago

Excellent, thanks for the heads up. I'm still around here.

fulldecent commented 6 years ago

Hello @jordangov, @tomberek, please let me know if there is a different person I may address this to.

This PR is a minimal viable product for code.mil. This is ready to release early and release often, so I want to give you something that is shippable. Then we can iterate from there as I am sure the great discussions here will continue to pan out.

jordangov commented 6 years ago

@fulldecent Thank you! We get it, and we want that... but resources are stretched thin. I'm hoping to have time late next week to jump back in. It is not falling off my plate.

jordangov commented 6 years ago

Hi! So I'm generally in favor of this PR, but there are some things I'd like to do before publishing it, and because you're PR'ing into thew gh-pages branch I can't merge it without publishing. :)

Let's switch the branch you're merging into to this new one: static-site and then we can iterate on the development. Thanks!

jordangov commented 6 years ago

Nevermind! I was able to change it. I'll be working on a number of changes before we can merge into gh-pages for publication:

fulldecent commented 6 years ago

Very cool. Thank you! I'll open a new PR now to merge static-site to gh-pages. This will represent the minimally viable product for launch.

jordangov commented 6 years ago

Please make your PRs merge into the static-site branch, not gh-pages. We'll have a few different updates for this that may come in from various sources (you, me, others?). I'll make a PR into gh-pages once it's ready which can then get reviewed by other DDS folks.

fulldecent commented 6 years ago

Oops. Just made https://github.com/deptofdefense/code.mil/pull/126 for the launch party.

And yes. All changes will come into this new static-site branch via new PRs while we're working on it.

fulldecent commented 6 years ago

Here are some bite-sized commits addressing https://github.com/deptofdefense/code.mil/pull/92#issuecomment-337670592

https://github.com/deptofdefense/code.mil/pull/127

missyk5150 commented 6 years ago

"Launch is a beautiful thing, but it's not such a big deal. Once you are launched, it will attract more contributors that get you to where you really want to be" ~fulldecent 2017~

I just thought this was very well said... so i put it in "quotations" and dated it is all.

Every time i learn a little more about coding or feel the information i have obtained since would be enough to suffice....... the less i seem to know for helping this project.. Yet as small as i may feel, I was here from the day it opened and i still have no idea where to start with any of this.. LOL. I 'll figure it out someday. Always looking up to you and much respect for the work you do. ~MK

jordangov commented 6 years ago

Thank you for your comment! You are absolutely right about that quote. And as for where you can help: there are all sorts of opportunities, both technical and not. Comments on our process or guidance, language crafting, design (we still need a logo) and content architecture, and of course the code for the site itself.

Once we have an initial site launched it will be much easier to track enhancements. I'm hoping that will happen sooner rather than later.