bcgov / gwells Goto Github PK
View Code? Open in Web Editor NEWGroundwater Wells and Aquifers application for the Ministry of Environment
Home Page: https://apps.nrs.gov.bc.ca/gwells/
License: Apache License 2.0
Groundwater Wells and Aquifers application for the Ministry of Environment
Home Page: https://apps.nrs.gov.bc.ca/gwells/
License: Apache License 2.0
When the database pod is not yet available the mid
lifecycle hook fails. We can avoid that by adding a pre
lifecycle hook that will wait (Retry
) until the database pod is up.
something along the lines of the existing Init Containers
which protects the pod form startup if the database is not available, but it doesn't protect against the deployment.
Reference
This issue has been auto-generated to facilitate questions about a paid opportunity that has just been posted on the BCDevExchange.
To learn more or apply, visit the opportunity page. The opportunity closes on Wednesday, September 19, 2018.
When a user is entering a new well record, there should be a check to make sure that one form of geographic coordinates (GPS coordinates, lat/long, or Norting/Easting) has been entered (required field).
We recently came across a new well record (WTN 125242) which had no coordinates entered, so it seems this check is failing or is not implemented correctly.
Please reach out to Carmen Riddel if you require anymore information.
As a Service Owner I want to be able to query the DB So That I can pull data for reports
Additional Context
Acceptance Criteria
Work in an Agile Scrum environment to create an Aquifer application to help support the management of aquifer data and information in the Province of B.C.
Value: $10,000
Work Location: Victoria
On-Site Requirements: Some in-person work required
Tags: API, Microservices, Swagger, Openshift, Docker, JavaScript, Python, Django, Vue, Bootstrap, Postman, Newman, Jenkins
Government Contact: Lindsay Macfarlane
Program: Water Protection and Sustainability
Project: GWELLS
Code: GitHub Repository
Background
The Groundwater Wells and Aquifers (GWELLS) team has released a well search and summary page, and the Register of Well Drillers and Well Pump Installers. We want to build on our success by implementing backend and user interface for entering and editing aquifer data.
This next phase of development will be to set up an API and user interface for aquifer data and information. We have scoped this out into three milestones:
Milestone 1: Search
Create a Django REST API and front end Vue application, which lists, sorts and filters aquifer data and information. Data models will be provided by GWELLS team members, but may require changes based on a user centred iterative process for development.
Milestone 2: CRUD Aquifer Data
Create web views for viewing, creating, editing and deleting aquifer data. Operations will be authenticated and authorized against RedHat Single Sign-On (RH-SSO), an on-premises version of KeyCloak.
Milestone 3: Integrate with the Data BC API Gateway
Deploy to the Data BC API Gateway.
The fixed-price reward is for a total of $10,000* for fulfilling the Acceptance Criteria below, per this payment schedule:
• Completion of milestone 1 - $4,000
• Completion of milestone 2 - $3,500
• Completion of milestone 3 - $2,500
*The full amount is dependent on an evaluation of outputs at the end of milestone 1, and the end of milestone 2. After each milestone, the Province will determine whether or not work will continue.
Acceptance Criteria
This is a fixed-price opportunity governed by the terms of our lightweight procurement model, Code With Us.
To be paid the fixed price for this opportunity, you need to meet all of the following criteria:
• Work with our Agile/Scrum team (2975 Jutland in Victoria, BC):
o The GWELLS team works in 2-week sprints. You will attend in person planning (2 hours) and review (2 hours) meetings for each sprint.
o You will track your work with the team on our GWELLS Trello board
• Milestone 1
o Update aquifer model, based on application development, when required throughout development process.
o Create a Django REST API and front end Vue.js Aquifer single page application (SPA)
i. View all aquifers (list)
o Implement a Vue.js plugin for sorting and filtering grid results
o Document the API using Django REST Swagger
o Write automated tests for our Jenkins pipeline in Postman/Newman
o Submit pull requests for review/acceptance
• Milestone 2
o Create views in the aquifers application to support CRUD operations:
.
i. Add an aquifer (create)
ii. View single aquifer (read)
iii. Edit an aquifer (update)
iv. Delete an aquifer (destroy)
o Display error and success messages where applicable
o Hide/show links to operations
o Authenticate edit/update/destroy end points
o Document the API using Django REST Swagger
o Write automated tests for our Jenkins pipeline in Postman/Newman
o Submit pull requests for review/acceptance
• Milestone 3
o Work with the GWELLS lead technical architect to publish ‘List’ and ‘Read’ end points to the Data BC API Gateway
As a Hydrogeologist or Ground Water Data Specialist I want to be able to search on all Aquifers with Aquifer Notations So That we can compile lists of all aquifers with specific notations at any given time
Additional Context
Acceptance Criteria
Duplicate.
Please see issue #340
As a (User Type/Persona) I want the hydraulic conductivity field to only display numbers so that the data is in the correct format and useful.
Additional Context
The Hydraulic Conductivity field is current a text field. It should be fixed to be a numbers field.
There are 323 records with entries that were all checked to ensure they are numbers, and no text fields.
The remaining records are all blank.
Values range between 0.22 to 0.000000016 --> but for m/s the value could be as low as 10^-12, so i think 12 values behind the decimal make sense
So maybe Number (1,12) for the spatial layer? is that feasible?
Relates to https://apps.nrs.gov.bc.ca/int/jira/browse/WATER-2007
Team Review Comments
Acceptance Criteria
As a Service Owner I want automated certificate renewals So That our digital service doesn't display "your connection is not private" messaging
Additional Context
The cert expired in March and magically renewed (at a later date). Prevailing theory is that Certbot is automated. but for the wrong date.
Acceptance Criteria
https://bcdevexchange.org/opportunities/opp-well-driller---pump-installer-registry-rest-api
Work in an Agile Scrum environment to create a proof of concept for a Well Driller Registry in the GWELLS app.
Background
The GWELLS team released the first version of its Provincial repository for groundwater well data and information. We’d like to build on that success by implementing an API proof of concept which will support external access to groundwater well data and enable future front-end development of GWELLS.
This next phase of development will be to set up an API for a registry of well drillers. We’d like a good base from which to start, and have scoped this out into three milestones:
Milestone 1: Django REST API
Create an API with end points to support basic CRUD operations on a well drillers table. Data models will be provided by GWELLS team members. Operations will be authenticated and authorized against RedHat Single Sign-On (RH-SSO), an on-premises version of KeyCloak.
Milestone 2: Well driller registry integration
Create basic web views for listing all well drillers from the API and a details page for a single driller with basic CRUD operations using Vue.js. These pages will serve as a base for our in-house team to work from.
Milestone 3: Integrate with the Data BC API Gateway
Deploy to the Data BC API Gateway.
The fixed-price reward is for a total of $10,000* for fulfilling the Acceptance Criteria below, per this payment schedule:
Completion of milestone 1 - $4,000
Completion of milestone 2 - $3,500
Completion of milestone 3 - $2,500
*The full amount is dependent on an evaluation of outputs at the end of milestone 1, and the end of milestone 2. After each milestone, the Province will determine whether or not work will continue.
Acceptance Criteria
To be paid the fixed price for this opportunity, you need to meet all of the following criteria:
Proposal Evaluation Criteria
Your proposal will be scored by this criteria:
Required skills: API, Microservices, Swagger, Openshift, Docker, JavaScript, Python, Django, Vue, Bootstrap, Postman, Newman, Jenkins
Questions?
Post a comment here and we'll get back to you as soon as possible.
Describe the task
Developers have GWELLS set up locally.
Acceptance Criteria
Additional context
N/A
Describe the task
The build pipeline is timing out on the tests stage. Need to determine root cause of error and implement fix.
Acceptance Criteria
Additional context
I came across this Jira issue. Not sure how it factors into your own determination of vulnerabilities..?
Review and address vulnerabilities found with GWELLS.
DEVELOPMENT CHECKLIST:
Review attached spreadsheet provided by Nick C on May 28, 2021
Fix the three critical vulnerabilities
Test
Develop plan to address the remainder of the vulnerabilities
Create new Jira tickets to address
Provide feedback to Nick C. on spreadsheet and approach
NOTES:
Risks: this might open up some cans of worms
Nick's recommended approach to prioritization is:
Critical/High with an exploit and a fix
Medium with remote exploit and a fix
Critical/High where possible
Team indicates that this is not technical debt, but regular maintenance that we need to stay on top of
Jira WATER-1873
https://app.zenhub.com/files/83460090/db3058c2-2d31-4694-bf83-7fc8006137e3/download
Describe the task
Review Repo, understand what type of monitoring exists for the app, what it would take to set it up, and what is missing.
Acceptance Criteria
Additional context
Users are not currently able to edit the dates in the "Well Activity" table. They can update the "Well Work Dates", but the "Well Activity" dates are pulled from elsewhere.
Typically, when a user updates the construction date in "Well Work Dates", this change also needs to be in "Well Activity"
As seen in the attached image, a user changed the "Well Work Date" to 1975 and this change was not reflected under "Well Activity" (still says 1974).
Jira GWELLS-56
This issue has been auto-generated to facilitate questions about a paid opportunity that has just been posted on the BCDevExchange.
To learn more or apply, visit the opportunity page. The opportunity closes on Saturday, December 8, 2018.
This issue has been auto-generated to facilitate questions about a paid opportunity that has just been posted on the BCDevExchange.
To learn more or apply, visit the opportunity page. The opportunity closes on Saturday, January 26, 2019.
This issue has been auto-generated to facilitate questions about a paid opportunity that has just been posted on the BCDevExchange.
To learn more or apply, visit the opportunity page. The opportunity closes on Sunday, February 17th, 2019 at 16:00 PST.
Describe the task
Clean up unnecessary images and tags in the ImageStreams asap.
Issue:
Platform team has indicated that our "Your namespace d1b5d2-dev is using more than 50Gi in the image registry on the Silver cluster of the Private Cloud OpenShift platform. When the image registry becomes full, none of the product teams working in the Silver cluster will be able to push images to it which will have a negative impact on their ability to run development activities for their apps. "
Notes:
Original email links attached. When you click the links below, you may get a message that says "This type of file can harm your computer. Do you want to keep .msg anyway?". It's okay to click "keep" to access the message.
Acceptance Criteria
Additional context
There are likely images not being used anymore. Folders with images are taking up space. Currently no automation to remove them (e.g. CRON job)
As a General public user I want a full description of the Aquifer notation rather than the abbreviation So That I can understand what the notation means
Additional Context
Acceptance Criteria
The code change to fix the issue
“Alternative Specs displayed twice on well summary page#1818”
is breaking a front-end unit test.
See a build log file at https://gwells-jenkins.apps.silver.devops.gov.bc.ca/job/gwells/view/change-requests/job/PR-1856/1/console
Search for FAIL tests/unit/specs/wells/WellDetail.spec.js
To resolve the issue, need to regenerate a snapshot at:
app/frontend/tests/unit/specs/wells/snapshots/WellDetail.spec.js.snap
As a Hydrogeologist I want Aquifer Notations displayed when I hover an Aquifer So That I do not need to click into each Aquifer to see notations
Additional Context
Acceptance Criteria
Describe the Bug
What is needed: add Artesian_Conditions flag field to the API.
Why it is needed: The GWELLS application has a new field for an Artesian Conditions flag (Jira ticket WATER-639) that should’ve been added into V2 of the API. Brad searched the new API and didn’t see this new field in there. So a couple questions for Alex:
Is this new Artesian Conditions flag field in V2 API and maybe we just didn’t see it?
Or
Was it excluded intentionally for some reason that we weren’t aware of? E.g., maybe there were issues with it and they didn’t want it added to the API?
If it was an oversight and didn’t get added to the API but should have, the Artesian_Conditions flag field needs to be added to the API.
A bit more background: Up until the end of 2021 GWELLS did not have an Artesian Conditions flag. The only way to indicate artesian conditions was to enter an artesian flow value for a well. If the flow was unknown, then we entered a dummy value (0.01 usGPM). In order to symbolize artesian wells on the spatial layer, we created a temporary “artesian indicator” field (in the spatial layer only) that auto-populated based on calculation of artesian flow (i.e., “N” if artesian flow were null or 0, or else “Y”). Hydrogeologists reported that these dummy values caused issues with skewed data calculations, etc. So we decided to create a new flag that would indicate artesian conditions whether the flow was known or not.
The flag was created in GWELLS and works perfectly there. However, the spatial layer is still using the temporary artesian indicator that is populated based off the Artesian flow calculation. So the spatial layer is only drawing artesian wells for those that have an artesian flow entered (regardless of whether the artesian flag indicates ‘Y’). When the API was updated in December, this new flag should have been added to the API (this step was missed), so that the spatial layer could then be symbolized based on this flag (instead of the temporary calculated indicator).
Timing Implications: A&WS has budget remaining in for FY21/22 for updating the spatial layers. If the API V2 is updated quickly, we may undergo another re-modelling exercise with DataBC to update the spatial datasets this fiscal.
Expected Behaviour
Artesian_Conditions flag has been added to the API and spatial layer is symbolized based on this flag.
Actual Behaviour
The spatial layer is only drawing artesian wells for those that have an artesian flow entered (regardless of whether the artesian flag indicates ‘Y’)
** Steps To Reproduce**
None available
Notes:
Need to create a column in the database and added to API. Or it could still be in the database?
Or API for spatial layer is not calling for this info?
Describe the task
A number of tests need to be updated to account for the recently updated schema.
Acceptance Criteria
Additional context
Describe the task
Review Repo, understand what type of monitoring exists for the app, what it would take to set it up, and what is missing.
Acceptance Criteria
Additional context
This will be the first of the monitoring review tickets and will help the remaining ones when this one is completed.
As a ground water data specialist I want the ability to query the database So That I can compile data for reports and research
Additional Context
Acceptance Criteria
Describe the Bug
When new attachments are added to records all of the attachments disappear. When you return to the well summary after editing it shows "Unable to retrieve file list." When you go back into edit it does not show any attachments.
Initially found with WTN 67013. Noticed the same thing with WTN 114569 and WTN 123917.
Expected Behaviour
When an attachment is added, it is added and all attachments are preserved.
Actual Behaviour
When an attachment is added, other attachments are removed. When they go to view attachments, they can only see the existence of them in "edit" mode.
** Steps To Reproduce**
Look at images below
As a Ground Water Scientist I want to no longer see Pumping Stress Index So That My interpretation of the data isnt tainted by inaccurate data
Additional Context
Acceptance Criteria
https://apps.nrs.gov.bc.ca/int/jira/projects/GWELLS/issues/GWELLS-59
Describe the task
We want a ticket to encapsulate the effort required for our first deployment to production for this repository.
Acceptance Criteria
Additional context
Describe the task
Fix the issues preventing us from deploying to GWELLS with Jenkins
Acceptance Criteria
If a legacy record had "unknown" entered in both the "Class of Well" and "Intended Water Use" fields, then the user will get an error message when they try to save the record (if it is the first time that the record has been opened since it was imported in GWELLS). The error message says "unknown water use only valid for water supply".
If you then change the "Class of Well" field to "water supply" in order to correct this and save your work, you get the following error message, "intended water use is required when class is water supply".
The workaround is to change the "Class of Well" field back to "unknown", at which point the "Intended Water Use" field will become greyed out and you can save the record, but this is time consuming when accessing and saving multiple historical records.
It would be ideal if for historical records, 'Unknown' is allowed for both Class of Well and Intended Water Use (no error message pops up when saving them), but for new records, 'Unknown' Intended Water Use is only available as an option for Class of Well = water supply.
Jira GWELLS-55
Describe the task
Sonarcloud blocked the merging of a PR, we want to understand why and fix those issues.
Acceptance Criteria
Additional context
Describe the Bug
The alternative specs field is displayed twice on the well summary page.
When was it identified?
March 2021, during testing of the flowing artesian well enhancements.
What are the implications?
Implications and risk is low; however, may cause user confusion as to why there are two fields being displayed for the same information. Looks unprofessional.
DEVELOPMENT CHECKLIST:
Remove one of the alternative specs fields from display.
Make sure boolean displayed correctly
TBC - which one should be removed from the form (no significant preference, but does make sense to keep near bottom)
Additional Context:
We want to get rid of the bottom "alternative specs" text because they don't always say the same thing.
Notes:
Additional comments can be found here:
https://apps.nrs.gov.bc.ca/int/jira/browse/WATER-1703
Test account
Describe the task
The Hydraulic Conductivity field is current a text field. It should be fixed to be a numbers field.
There are 323 records with entries that were all checked to ensure they are numbers, and no text fields.
The remaining records are all blank.
Values range between 0.22 to 0.000000016 --> but for m/s the value could be as low as 10^-12, so i think 12 values behind the decimal make sense
So maybe Number (1,12) for the spatial layer? is that feasible?
Acceptance Criteria
Additional context
Relates to https://apps.nrs.gov.bc.ca/int/jira/browse/WATER-2007
Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).
In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.
Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca
email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic
.
That's in, you're done!!!
Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz
to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.
If your org is not in the list below, or the table contains errors, please create an issue here.
While you're doing this, add additional topics
that would help someone searching for "something". These can be the language used javascript
or R
; something like opendata
or data
for data only repos; or any other key words that are useful.
Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.
If your application is live, add the production URL.
Short Code | Organization Name |
---|---|
AEST | Advanced Education, Skills & Training |
AGRI | Agriculture |
ALC | Agriculture Land Commission |
AG | Attorney General |
MCF | Children & Family Development |
CITZ | Citizens' Services |
DBC | Destination BC |
EMBC | Emergency Management BC |
EAO | Environmental Assessment Office |
EDUC | Education |
EMPR | Energy, Mines & Petroleum Resources |
ENV | Environment & Climate Change Strategy |
FIN | Finance |
FLNR | Forests, Lands, Natural Resource Operations & Rural Development |
HLTH | Health |
FLNR | Indigenous Relations & Reconciliation |
JEDC | Jobs, Economic Development & Competitiveness |
LBR | Labour Policy & Legislation |
LDB | BC Liquor Distribution Branch |
MMHA | Mental Health & Addictions |
MAH | Municipal Affairs & Housing |
BCPC | Pension Corporation |
PSA | Public Safety & Solicitor General & Emergency B.C. |
SDPR | Social Development & Poverty Reduction |
TCA | Tourism, Arts & Culture |
TRAN | Transportation & Infrastructure |
NOTE See an error or omission? Please create an issue here to get it remedied.
This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.
To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.
dormant
or retired
life cycle badge.Thank you for your help ensuring effective governance of our open-source ecosystem!
As a Hydrogeologists I want to see the Aquifer Notations on the Aquifer page So That it can Inform decisions on changing licenses or limit the water coming out of an aquifer
Additional Context
Acceptance Criteria
Describe the task
Issue: An alteration report was created and assigned to a Well Tag Number (WTN) 41359.
This alteration report should have a new WTN, and should NOT have been assigned to an existing WTN.
Issue occurred and was reported on 7 Oct 2021.
This is a database entry that needs to be deleted.
Acceptance Criteria
Additional context
Poor data quality, and known misinformation of well data
erodes confidence in data, and its incorrect.
Its only one well, but it shouldnt get forgotten, when we know its wrong, and not within current GWELLS application capacity to easily fix it.
Describe the task
In the attached excel spreadsheet, 34 cells within Column F (only the highlighted yellow fields) require data length.
The example given for data length: For Number type, format using: Precision (total number of digits) and Scale (number of digits to the right of the decimal point), e.g., 9,3
Required by DataBC to complete spatial layer modeling.
Acceptance Criteria
Additional context
Can we get some more clarification on what this ticket is asking? Reach out to GWELLS Service Owner
Action:
As a Hydrogeologist I want *to have a notation indicating "Potential Salt Water Intrusion" added when an aquifer with the Potential Water Shortage notation is indicated and the aquifer is X km from the edge of the coast * So That we do not need to manually ID these Aquifers
Additional Context
Acceptance Criteria
Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.
It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.
I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)
Describe the task
once the pipeline is shifted to Github Actions we still need to figure out how to make it actually deploy. translating the broken pipeline means there is still things that need to be fixed.
Acceptance Criteria
Additional context
Describe the task
The Jenkins Pipeline for GWELLS is failing and we do not have knowledge or resources to repair and make it work, instead we will focus on shifting to a Github Actions Pipeline for this product.
Acceptance Criteria
Additional context
When a new well activity report (with flowing artesian conditions) is submitted (e.g., well construction) and then associated to an aquifer, the aquifer summary report total artesian wells count is not updated until I refresh or bounce between pages several times.
When was it identified?
April 2021 as part of testing of WATER-1753
What is the impact?
Confusion - perception is that the update didn't happen and that the system has a bug or is broken.
DEVELOPMENT CHECKLIST:
'Never cache'
Make sure aquifer data endpoint is set to never cache
Update API tests
NOTES:
Ticket a result of testing of WATER-1753
Standup (April 21, 2021) - team indicated that it might be a caching issue
The auto selected "qualified to drill" section is not being auto populated when a classification is added to an existing driller/pump installer. It appears to work fine when a new one is added.
WHEN WAS IT IDENTIFIED?
January 2021
WHAT IS THE IMPACT?
Applications for registration as drillers or well pump installers are missing information required under the Act.
NOTES:
Identified during testing of OpenShift4 migration; however, issue exists in PROD.
ENHANCEMENT
On the aquifer pages, instead of listing "More Likely" or "Less Likely" for Hydraulically Connected under Knowledge Indicators, put a link the the associated report.
We will also need to remove Hydraulically Connected from the aquifer advanced search page.
https://apps.nrs.gov.bc.ca/int/jira/projects/GWELLS/issues/GWELLS-62
Describe the task
Explore the use of Keycloak with GWELLS.
Acceptance Criteria
Additional context
General information
THE LINKS BELOW WERE COPIED FROM #969. TO BE UPDATED SO THEY ARE RELEVANT TO GWELLS
https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1
https://github.com/bcgov/sso-keycloak/wiki/zorin-notes-to-run-examples-from-our-team
https://oidc.gov.bc.ca/auth/realms/3l5nw6dk/protocol/openid-connect/auth?client_id=security-admin-console&redirect_uri=https%3A%2F%2Foidc.gov.bc.ca%2Fauth%2Fadmin%2F3l5nw6dk%2Fconsole%2F%23%2Frealms%2F3l5nw6dk%2Fusers&state=b35d72b3-d487-41e6-b8f4-030c87810952&response_mode=fragment&response_type=code&scope=openid&nonce=28d12c81-4f7e-49e7-8f22-a30dfba98b30&code_challenge=hkrkKMG3xjEgl5xGKZyZoZ3nzKAZ-o9PimvHuJSEMY4&code_challenge_method=S256
https://bcgov.github.io/sso-requests
https://github.com/bcgov/sso-keycloak/wiki/test-page
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.