From fe639cea28972e93510900078fcf6b4e183d6218 Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Mon, 23 Jul 2018 09:36:42 -0400 Subject: [PATCH 1/8] Update and rename ROADMAP.md to ROADMAP - MAR18 to SEP18.md Per con with @nellshamrell --- ROADMAP.md => ROADMAP - MAR18 to SEP18.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename ROADMAP.md => ROADMAP - MAR18 to SEP18.md (88%) diff --git a/ROADMAP.md b/ROADMAP - MAR18 to SEP18.md similarity index 88% rename from ROADMAP.md rename to ROADMAP - MAR18 to SEP18.md index 7ff5484..d3abc1a 100644 --- a/ROADMAP.md +++ b/ROADMAP - MAR18 to SEP18.md @@ -14,11 +14,11 @@ Here are my current thoughts on a roadmap for our overall engineering organziati * Open Source Basic Training - this will be a guide to getting started with Open Source. This needs to include lessons (links to particularly good blog post tutorials, etc. are welcome) on Git and Github. Git is often a major hurdle to getting started - we need strong and very visible learning materials on the essentials of git. We also need a repo that users can immediately contribute to to put their git and Github skills in action - perhaps a repo of text files that a user can add their name or something else to? The goal of this basic training is to familiarize someone with the workflow of git and Github - which is critical to contributing to any or our projects. This should also include a brief guide to each of the major Operation Code Open Soure Projects - what technology they use, links to 101 guides to those technologies, etc. Members should receive a link to this training immediately when they join the org. -* Better broadcasting across platforms - our town halls are great, especially now that they can be broadcast over Youtube live. We should look into broadcasting these across other platforms as well - i.e. going live on Facebook or Twitter at the same time as we go live on Youtube, perhaps even including Twitch. We need to look into software that would let us broadcast over multiple platforms - or at the very least push announcements that we are live to multiple platforms. Eventually I would like to see this show on the main home page of the site, but that is not within this six month roadmap. +* ~~Better broadcasting across platforms - our town halls are great, especially now that they can be broadcast over Youtube live. We should look into broadcasting these across other platforms as well - i.e. going live on Facebook or Twitter at the same time as we go live on Youtube, perhaps even including Twitch. We need to look into software that would let us broadcast over multiple platforms - or at the very least push announcements that we are live to multiple platforms. Eventually I would like to see this show on the main home page of the site, but that is not within this six month roadmap. ## Front End -* Policy Page (this is needed for an upcoming event, Jamel Martin will be providing the copy) +* Policy Page (this is needed for an upcoming event, Jameel Matin will be providing the copy) *COMPLETE* * Templates for static pages. One of the biggest bottlenecks over the past year has been React - it can be a difficult framework to get started with, especially when someone is brand new to web development. Rather than attempt to rewrite our front end in a different framework, I’d like to focus on making our particuarly implementation of React more beginner friendly. Adding in static content is a great way for a beginner to get started with contributing - let’s make a template that can be copy and pasted for any new static page. Yes, we might violate the DRY rule a bit here, but I think this is a worthy exception and necessary to our mission. We need the process of using this template very well documented. Any new copy for the front end should go in a Github issue with a link to this guide, and these issues should be reserved for first time contributions whenever possible. @@ -38,7 +38,7 @@ Here are my current thoughts on a roadmap for our overall engineering organziati ## Backend -* Deploy interface for execs to query the database (possibly Active Admin or Forest) +* Deploy interface for execs to query the database (possibly Active Admin or Forest) *COMPLETE* * Add ability to run Cron Jobs (need help of infrastructure) From a854472665d2f0e95373caee75de254dcc3b9105 Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Mon, 23 Jul 2018 10:22:04 -0400 Subject: [PATCH 2/8] Integrate Slack user base into the backend --- ROADMAP.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ROADMAP.md b/ROADMAP.md index 7ff5484..c72ffa8 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -39,6 +39,7 @@ Here are my current thoughts on a roadmap for our overall engineering organziati ## Backend * Deploy interface for execs to query the database (possibly Active Admin or Forest) + * As operations, I want the member list in the backend to contain both signup *and* Slack information, so that I can have a single view of our membership base. * Add ability to run Cron Jobs (need help of infrastructure) From 41617825a38dd44725df4e11ab835fc89397496d Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Mon, 23 Jul 2018 12:06:37 -0400 Subject: [PATCH 3/8] Create ROADMAP OCT18-MAR19.md --- ROADMAP OCT18-MAR19.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 ROADMAP OCT18-MAR19.md diff --git a/ROADMAP OCT18-MAR19.md b/ROADMAP OCT18-MAR19.md new file mode 100644 index 0000000..9f48117 --- /dev/null +++ b/ROADMAP OCT18-MAR19.md @@ -0,0 +1,3 @@ +## Data Analytics +* Retrieve user demographic data from Facebook and LinkedIn social media login +* Integrate Meetup Pro user data to backend From a9983091e74e8b90ee9daf8d9f156aa550009c00 Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Sun, 5 Aug 2018 13:28:15 -0400 Subject: [PATCH 4/8] current product roadmap update notes 5AUG18 --- ...AR18 to SEP18.md => ROADMAP MAR18-SEP18.md | 38 +++++++++++++------ 1 file changed, 26 insertions(+), 12 deletions(-) rename ROADMAP - MAR18 to SEP18.md => ROADMAP MAR18-SEP18.md (63%) diff --git a/ROADMAP - MAR18 to SEP18.md b/ROADMAP MAR18-SEP18.md similarity index 63% rename from ROADMAP - MAR18 to SEP18.md rename to ROADMAP MAR18-SEP18.md index 76a12e6..e1f9629 100644 --- a/ROADMAP - MAR18 to SEP18.md +++ b/ROADMAP MAR18-SEP18.md @@ -13,46 +13,60 @@ Here are my current thoughts on a roadmap for our overall engineering organziati ## Overall * Open Source Basic Training - this will be a guide to getting started with Open Source. This needs to include lessons (links to particularly good blog post tutorials, etc. are welcome) on Git and Github. Git is often a major hurdle to getting started - we need strong and very visible learning materials on the essentials of git. We also need a repo that users can immediately contribute to to put their git and Github skills in action - perhaps a repo of text files that a user can add their name or something else to? The goal of this basic training is to familiarize someone with the workflow of git and Github - which is critical to contributing to any or our projects. This should also include a brief guide to each of the major Operation Code Open Soure Projects - what technology they use, links to 101 guides to those technologies, etc. Members should receive a link to this training immediately when they join the org. + * _still a big priority -conrad_ + * _we have the pieces in place but need to get them all together -ashley_ + * _maybe slackbot pings people about it and directs them to a page -nell_ -* ~~Better broadcasting across platforms - our town halls are great, especially now that they can be broadcast over Youtube live. We should look into broadcasting these across other platforms as well - i.e. going live on Facebook or Twitter at the same time as we go live on Youtube, perhaps even including Twitch. We need to look into software that would let us broadcast over multiple platforms - or at the very least push announcements that we are live to multiple platforms. Eventually I would like to see this show on the main home page of the site, but that is not within this six month roadmap. +* Deprioritized ~~Better broadcasting across platforms - our town halls are great, especially now that they can be broadcast over Youtube live. We should look into broadcasting these across other platforms as well - i.e. going live on Facebook or Twitter at the same time as we go live on Youtube, perhaps even including Twitch. We need to look into software that would let us broadcast over multiple platforms - or at the very least push announcements that we are live to multiple platforms. Eventually I would like to see this show on the main home page of the site, but that is not within this six month roadmap. ## Front End -* Policy Page (this is needed for an upcoming event, Jameel Matin will be providing the copy) *COMPLETE* +* ~~Policy Page (this is needed for an upcoming event, Jameel Matin will be providing the copy)~~ *COMPLETE* -* Templates for static pages. One of the biggest bottlenecks over the past year has been React - it can be a difficult framework to get started with, especially when someone is brand new to web development. Rather than attempt to rewrite our front end in a different framework, I’d like to focus on making our particuarly implementation of React more beginner friendly. Adding in static content is a great way for a beginner to get started with contributing - let’s make a template that can be copy and pasted for any new static page. Yes, we might violate the DRY rule a bit here, but I think this is a worthy exception and necessary to our mission. We need the process of using this template very well documented. Any new copy for the front end should go in a Github issue with a link to this guide, and these issues should be reserved for first time contributions whenever possible. +* Templates for static pages. One of the biggest bottlenecks over the past year has been React - it can be a difficult framework to get started with, especially when someone is brand new to web development. Rather than attempt to rewrite our front end in a different framework, I’d like to focus on making our particuarly implementation of React more beginner friendly. Adding in static content is a great way for a beginner to get started with contributing - let’s make a template that can be copy and pasted for any new static page. Yes, we might violate the DRY rule a bit here, but I think this is a worthy exception and necessary to our mission. We need the process of using this template very well documented. Any new copy for the front end should go in a Github issue with a link to this guide, and these issues should be reserved for first time contributions whenever possible. _does kyle's work negate this?_ -* Host docsify page on docs.operationcode.org - we need to have our docs in one easy to find and easy to navigate place, this is essential to making sure people can find the information they need quickly. +* ~~Host docsify page on docs.operationcode.org - we need to have our docs in one easy to find and easy to navigate place, this is essential to making sure people can find the information they need quickly.~~ _deprioritized, github will suffice for now -nell_ -* Landing Page ReDesign +* *P1* Landing Page ReDesign _we need to communicate who we are and how you become a part of us, how to join. How do they know if we're legitimate? -davidm_ + * Re-think and redo hero banner implementation * Introduce a drop-down item for the navbar. -* Re-think and redo hero banner implementation - * Make sure that all UI components have Jest snapshot tests and Storybook instances + * _in progress with kyle_ * Document how to add a Jest test and a Storybook instance of a component + * _in progress with kyle_ * Discuss moving shared components into UI Lib via NPM + * _check with kyle if this is still necessary -nell_ ## Backend -* Deploy interface for execs to query the database (possibly Active Admin or Forest) +* ~~Deploy interface for execs to query the database (possibly Active Admin or Forest)~~ _done!_ * As operations, I want the member list in the backend to contain both signup *and* Slack information, so that I can have a single view of our membership base. -* Add ability to run Cron Jobs (need help of infrastructure) +* ~~Add ability to run Cron Jobs (need help of infrastructure)~~ + * _need more info, was requested by harry -ashley_ + * _deprioritized until we have a backend lead - nell_ -* Set up new Code Climate account - this will help give us insight into the health of our codebase, and ensure we are using best practices and keeping it beginner friendly! +* ~~Set up new Code Climate account - this will help give us insight into the health of our codebase, and ensure we are using best practices and keeping it beginner friendly!~~ + * _deprioritized - nell_ -* Implement roles/permissions for end users +* ~~Implement roles/permissions for end users~~ _done!_ * Implement an authentication strategy/option to secure and expose the API (for non-signed in user consumers, i.e. Slack, apps, etc.) + * _need more info from long_common_name -nell_ ## Infrastructure -* Staging Environment for operationcode.org - this is the number one priority, currently we can only run operationcode.org components locally or in production, we need a staging environment we can deploy to and test components in a production-like environment before deploying to production. This is essential and gives us a strong safety net for testing the effects of new commits before they go to production. +* *P1* Staging Environment for operationcode.org - this is the number one priority, currently we can only run operationcode.org components locally or in production, we need a staging environment we can deploy to and test components in a production-like environment before deploying to production. This is essential and gives us a strong safety net for testing the effects of new commits before they go to production. + * _still a big priority -nell_ + * _looking at how we can get this done -ashley_ * Log Collection Solution - currently logs can only be viewed through the Kubernetes cli - and it is very difficult to see logs across our Kubernetes pods. We need a centralized logging solution to help quickly troubleshoot errors and watch for patterns. + * _still a priority -nell_ + * _needed for debugging -ashley_ * Secrets Management Solution + * _deprioritized since there is a way to do this through Kubernetes right now -nell_ From 58eb8d8662ef596d605fc64539091bd8f0e93284 Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Sun, 5 Aug 2018 13:43:00 -0400 Subject: [PATCH 5/8] new product roadmap update notes 5Aug18 --- ROADMAP OCT18-MAR19.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/ROADMAP OCT18-MAR19.md b/ROADMAP OCT18-MAR19.md index 9f48117..c1c584b 100644 --- a/ROADMAP OCT18-MAR19.md +++ b/ROADMAP OCT18-MAR19.md @@ -1,3 +1,20 @@ -## Data Analytics +## New User Experience -davidm +* Investigate from a UX/design perspective how we want to handle our own signup vs. Slack signup + * Is there a way we can combine the two? -davidm + * Explore removing autoinvite from Heroku and bringing into our current infrastructure -conrad + * Have an indicator on our landing page that we are on Slack -davidm + * Verification of new member re. Slack for security -nell + +## Infrastructure -ashley +* Assess other infrastructure options besides Kubernetes + * Now? (the platform) -kyle + +## Data Analytics -conrad * Retrieve user demographic data from Facebook and LinkedIn social media login * Integrate Meetup Pro user data to backend +* Means of data collection + * talk to cam -ashley + +## Data Retention Policy -nell +* Research data protection -nell + * #cyber-security can support -ashley From 490d2d72f462a5a02b3f87afbb89f33878e9696f Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Tue, 7 Aug 2018 14:55:45 -0400 Subject: [PATCH 6/8] Consolidate notes re. 05AUG current roadmap me --- ROADMAP MAR18-SEP18.md | 46 ++++++++++++++++++++++++------------------ 1 file changed, 26 insertions(+), 20 deletions(-) diff --git a/ROADMAP MAR18-SEP18.md b/ROADMAP MAR18-SEP18.md index e1f9629..186b294 100644 --- a/ROADMAP MAR18-SEP18.md +++ b/ROADMAP MAR18-SEP18.md @@ -8,14 +8,14 @@ While we have a wonderful and deeply appreciated group of contributors, the time In considering a road map for the next six months I’d like to make one vision front and center. That is “One week to join, code, and contribute a first open source commit.” I would like this principle to be the priority for the next six months. This is not to say there are not other things we need to get done - but when considering priorities or new features, we must think about them in terms of whether they make that first time contribution experience easier. -Here are my current thoughts on a roadmap for our overall engineering organziation, as well as each individual component. +Here are my current thoughts on a roadmap for our overall engineering organazation, as well as each individual component. ## Overall * Open Source Basic Training - this will be a guide to getting started with Open Source. This needs to include lessons (links to particularly good blog post tutorials, etc. are welcome) on Git and Github. Git is often a major hurdle to getting started - we need strong and very visible learning materials on the essentials of git. We also need a repo that users can immediately contribute to to put their git and Github skills in action - perhaps a repo of text files that a user can add their name or something else to? The goal of this basic training is to familiarize someone with the workflow of git and Github - which is critical to contributing to any or our projects. This should also include a brief guide to each of the major Operation Code Open Soure Projects - what technology they use, links to 101 guides to those technologies, etc. Members should receive a link to this training immediately when they join the org. - * _still a big priority -conrad_ - * _we have the pieces in place but need to get them all together -ashley_ - * _maybe slackbot pings people about it and directs them to a page -nell_ + * _05AUG - still a big priority -conrad_ + * _05AUG - we have the pieces in place but need to get them all together -ashley_ + * _05AUG - maybe slackbot pings people about it and directs them to a page -nell_ * Deprioritized ~~Better broadcasting across platforms - our town halls are great, especially now that they can be broadcast over Youtube live. We should look into broadcasting these across other platforms as well - i.e. going live on Facebook or Twitter at the same time as we go live on Youtube, perhaps even including Twitch. We need to look into software that would let us broadcast over multiple platforms - or at the very least push announcements that we are live to multiple platforms. Eventually I would like to see this show on the main home page of the site, but that is not within this six month roadmap. @@ -23,50 +23,56 @@ Here are my current thoughts on a roadmap for our overall engineering organziati * ~~Policy Page (this is needed for an upcoming event, Jameel Matin will be providing the copy)~~ *COMPLETE* -* Templates for static pages. One of the biggest bottlenecks over the past year has been React - it can be a difficult framework to get started with, especially when someone is brand new to web development. Rather than attempt to rewrite our front end in a different framework, I’d like to focus on making our particuarly implementation of React more beginner friendly. Adding in static content is a great way for a beginner to get started with contributing - let’s make a template that can be copy and pasted for any new static page. Yes, we might violate the DRY rule a bit here, but I think this is a worthy exception and necessary to our mission. We need the process of using this template very well documented. Any new copy for the front end should go in a Github issue with a link to this guide, and these issues should be reserved for first time contributions whenever possible. _does kyle's work negate this?_ +* Templates for static pages. *COMPLETE* + * _05AUG - Kyle has made this easier as part of the new frontend, and we're looking at some form of CMS integration for next roadmap._ -* ~~Host docsify page on docs.operationcode.org - we need to have our docs in one easy to find and easy to navigate place, this is essential to making sure people can find the information they need quickly.~~ _deprioritized, github will suffice for now -nell_ +* ~~Host docsify page on docs.operationcode.org - we need to have our docs in one easy to find and easy to navigate place, this is essential to making sure people can find the information they need quickly.~~ _05AUG - deprioritized, github will suffice for now -nell_ -* *P1* Landing Page ReDesign _we need to communicate who we are and how you become a part of us, how to join. How do they know if we're legitimate? -davidm_ +* *P1* Landing Page Redesign + * _05AUG - we need to communicate who we are and how you become a part of us, how to join. How do they know if we're legitimate? -davidm_ + * _05AUG - need a designer for this_ * Re-think and redo hero banner implementation * Introduce a drop-down item for the navbar. * Make sure that all UI components have Jest snapshot tests and Storybook instances - * _in progress with kyle_ - * Document how to add a Jest test and a Storybook instance of a component - * _in progress with kyle_ + * _05AUG - both in progress with kyle_ * Discuss moving shared components into UI Lib via NPM - * _check with kyle if this is still necessary -nell_ + * _05AUG - deprioritized -nell_ ## Backend * ~~Deploy interface for execs to query the database (possibly Active Admin or Forest)~~ _done!_ * As operations, I want the member list in the backend to contain both signup *and* Slack information, so that I can have a single view of our membership base. + * _06AUG - This is a current WIP for both pybot and BE. -william + * 06AUG - BE issues: 312, 319, 320, 322 are all related to this. The idea is use pybot as a way to register email and user information updates from slack api, and transmit this to the BE. -william + * 06AUG - Here's his high level view before it was broke out into individual issues: OperationCode/operationcode_backend#314 -william + * 06AUG - Issues 1 and 5 are done. 2, 3, 4 are waiting. -william + * 06AUG - If this is P1 for @JennWeideman maybe get @dmarchante to review the status and make an epic or something to track this progress? -william_ * ~~Add ability to run Cron Jobs (need help of infrastructure)~~ - * _need more info, was requested by harry -ashley_ - * _deprioritized until we have a backend lead - nell_ + * _05AUG - deprioritized until we have a backend lead -nell_ + * _05AUG - PR needs review from new backend lead OperationCode/operationcode_backend#257 -jhampton_ * ~~Set up new Code Climate account - this will help give us insight into the health of our codebase, and ensure we are using best practices and keeping it beginner friendly!~~ - * _deprioritized - nell_ + * _05AUG - this is already done -conrad_ * ~~Implement roles/permissions for end users~~ _done!_ * Implement an authentication strategy/option to secure and expose the API (for non-signed in user consumers, i.e. Slack, apps, etc.) - * _need more info from long_common_name -nell_ + * _06AUG - harry came up with a good idea for how to integrate pybot into BE. For now we can use that for this one case and treat pybot as a main focal point so I don't have to re-architect in ruby. -william_ ## Infrastructure * *P1* Staging Environment for operationcode.org - this is the number one priority, currently we can only run operationcode.org components locally or in production, we need a staging environment we can deploy to and test components in a production-like environment before deploying to production. This is essential and gives us a strong safety net for testing the effects of new commits before they go to production. - * _still a big priority -nell_ - * _looking at how we can get this done -ashley_ + * _05AUG - done on new frontend -kyle_ + * _05AUG - Ashley and Walt to discuss backend staging env implementation, @kylemh to alias preview builds with backend staging env_ * Log Collection Solution - currently logs can only be viewed through the Kubernetes cli - and it is very difficult to see logs across our Kubernetes pods. We need a centralized logging solution to help quickly troubleshoot errors and watch for patterns. - * _still a priority -nell_ - * _needed for debugging -ashley_ + * _05AUG - still a priority -nell_ + * _05AUG - needed for debugging -ashley_ * Secrets Management Solution - * _deprioritized since there is a way to do this through Kubernetes right now -nell_ + * _05AUG - deprioritized since there is a way to do this through Kubernetes right now -nell_ From fa79fd7cef153617d6107d98f9abbd3cca0ebca1 Mon Sep 17 00:00:00 2001 From: Conrad Hollomon Date: Tue, 7 Aug 2018 16:23:15 -0400 Subject: [PATCH 7/8] Update ROADMAP OCT18-MAR19.md --- ROADMAP OCT18-MAR19.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/ROADMAP OCT18-MAR19.md b/ROADMAP OCT18-MAR19.md index c1c584b..b07f4ae 100644 --- a/ROADMAP OCT18-MAR19.md +++ b/ROADMAP OCT18-MAR19.md @@ -1,20 +1,23 @@ ## New User Experience -davidm * Investigate from a UX/design perspective how we want to handle our own signup vs. Slack signup - * Is there a way we can combine the two? -davidm - * Explore removing autoinvite from Heroku and bringing into our current infrastructure -conrad - * Have an indicator on our landing page that we are on Slack -davidm - * Verification of new member re. Slack for security -nell + * _05AUG - Is there a way we can combine the two? -davidm + * 05AUG - Explore removing autoinvite from Heroku and bringing into our current infrastructure -conrad + * 05AUG - Have an indicator on our landing page that we are on Slack -davidm + * 05AUG - Verification of new member re. Slack for security -nell ## Infrastructure -ashley * Assess other infrastructure options besides Kubernetes - * Now? (the platform) -kyle + * _05AUG - Now? (the platform) -kyle_ + * _05AUG - AWS Elastic Beanstalk? -nell_ ## Data Analytics -conrad -* Retrieve user demographic data from Facebook and LinkedIn social media login +* Retrieve user demographic data from Facebook and Google social media login + * _05AUG - add LinkedIn -conrad_ + * _05AUG - Need backend dev to move forward -davidm_ * Integrate Meetup Pro user data to backend * Means of data collection - * talk to cam -ashley + * _05AUG - talk to cam -ashley_ ## Data Retention Policy -nell * Research data protection -nell - * #cyber-security can support -ashley + * _05AUG - #cyber-security can support -ashley_ From 950fde86d795a3878216250268c8fbcb92ea55bc Mon Sep 17 00:00:00 2001 From: Nell Shamrell Date: Wed, 8 Aug 2018 17:08:31 -0700 Subject: [PATCH 8/8] reprioritizes secrets management solution --- ROADMAP MAR18-SEP18.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ROADMAP MAR18-SEP18.md b/ROADMAP MAR18-SEP18.md index 186b294..f9d5f6b 100644 --- a/ROADMAP MAR18-SEP18.md +++ b/ROADMAP MAR18-SEP18.md @@ -75,4 +75,5 @@ Here are my current thoughts on a roadmap for our overall engineering organazati * _05AUG - needed for debugging -ashley_ * Secrets Management Solution + * _08AUG - this is been reprioritized after further discussion and research (Thank you, Ashley!) -nell_ * _05AUG - deprioritized since there is a way to do this through Kubernetes right now -nell_