tommy's scratchpad

Well, 2025 was quite a fun and productive year! Here’s the rundown on my last 12 months:

WMO: WIS2 went operational on 01 January 2025, and things ran relatively smoothly overall. Check out our Global Services listing! WIS2 currently has over 100 WIS2 Nodes and 19 Global Services, and we continue to refine and tweak the Technical Regulations baseline. We also published the first version of the WIS2 Cookbook, check it out for some practical examples on working with WIS2. wis2box reached 1.0 status and continues to power ~60 installations across the infrastructure. Best of all, the entire activity is stuffed with Open Standards and considerable FOSS implementation of them!

We also made considerable progress on defining the Global Replay Service as well as the Sensor Centre concept (all of which will have FOSS Reference Implementations).

Finally, the Task Team on Open Source Software kicked off this year, with the aim of providing a FOSS framework for WMO Members and Secretariat.

OGC: at long last, OGC API – Records – Part 1: Core was released this year! OGC API now has a formal search capability defined. Check out all the software implementations already available. Don’t see yours here? Feel free to add 🙂 The PubSub SWG continued to chug along, and we are now at the point to start testing the draft specification and further refine with the relevant OGC API SWGs. We also moved forward on the RODEO EDR profile, which will become an OGC MetOcean profile for EDR, allowing for increased EDR interoperability across the weather community.

OSGeo: FOSS4G Europe (Mostar) and the Global (Auckland) were personal highlights, having delivered numerous talks and workshops on Geopython and pygeoapi with great teams as always. I was honoured to present the Sol Katz award to Nyall Dawson at the closing ceremony (congrats again Nyall!). Being part of the Board of Directors continued as a motivation to improve and sustain OSGeo, with emphasis on standards

pygeoapi: We rocked 4 releases this year, adding goodies like STAC API, dataset specific templating, transactions for PostgreSQL, i18n support for Arabic, OpenShift support, STAC API and much more. Monthly online meetings continued as planned, and the project continues to grow and mature as an OGC API Reference Implementation, as well as powering some high profile data sharing services.

pycsw: lots of action this year, which included: numerous deep STAC API and CQL2 improvements, as well as significant repository abstraction work (in progress) to enable easier integration with NoSQL backends such as Elasticsearch and Solr. We were also the first to implement OGC API – Publish/Subscribe (draft) and continue to refine things as the draft specification evolves. We also cut another 3.0 beta release as we march towards OGC API – Records CITE compliance.

WOUDC: we released version 2.0 of the data centre this year, which included a major architecture updates, moving from WMS/WFS/CSW to OGC APIs (using pygeoapi) and a shiny new UI. We also achieved connectivity to WIS2 as the first GAW data centre to publish atmospheric composition data to the infrastructure. Kudos to the entire team and keep up the great work!

MSC: our national weather/water/climate API platform continues to grow. We are getting closer and closer to operational dissemination of our NWP data via EDR and Zarr – stay tuned! Our efforts on MSC’s WIS2 implementation continue to lead, with the most data and metadata on WIS2. Great job to the entire team!

On the personal front:

• having done my share of code sprints in my worklife, 2025 was the time for a personal sprint on health. Powered by an extremely strict diet, I lost 60 (sixty) pounds in 2025 and feel better than ever. A big thanks to my wife, family, friends and colleagues for their support
• another year (circa 2012) of not smoking (yes I continue to remind myself)
• home renovation: our major project took me out of action for a few months, and I’m thankful that it is completed so we can return to normal life again

Looking ahead to 2026, a few key items:

• WMO: INFCOM-4 will take place in Q4, with numerous items for discussion and approval (WIS2 Sensor Centres, Global Replay Service, the WMO FOSS Guide, and WCMP2 KPI definitions)
• WMDR2: WMO’s station metadata standard is getting a reboot which will move it closer to WCMP2 and OGC API – Records, stay tuned for the new specification and its Reference Implementation!
• pygeoapi: look for the addition of OGC API – Publish/Subscribe workflow, maturation of OGC API – Maps support, along with numerous other improvements
• OSGeo: I’m looking forward to the global event in Hiroshima (August), as well as serving the Board of Directors with focus on Standards, SAC and growth/sustainability. As well, I’m looking forward to the 2026 Joint OGC-OSGeo-ASF Code Sprint (which returns after not eventing in 2025)
• GeoHealthCheck: the project is getting some recent love, and look for more developments as we work towards refactoring for the long term

Wishing everyone a healthy and happy 2026!

2024 was a power packed year with much progress on many fronts, work and personal. Here’s the annual rundown:

Sol Katz Award: without a doubt, being chosen as the recipient of the 2024 Sol Katz Award has been a major and defining milestone of my worklife.  Presented at FOSS4G Belém, it is an honour and a privilege to be selected for this award, in honour of Sol Katz, a true pioneer in our domain and community. I am also honoured to be among many leaders and legends who have previously won this award. I will always remember this moment and am truly thankful.

Having been involved in OSGeo from its humble beginnings, I love the community, geospatial and open source. It has been a privilege to watch it grow and to help in that growth. Let’s keep moving forward, together to advance our community, free and open source geospatial software, and to lower the barrier for everyone. Thank you!

WMO: WIS2 standards approved!  The Guide to WIS2, Manual on WIS2 and as well as Transition Guide were all approved and headed to publication. The pre-operational phase helped ensure we are ready for operations (on 01 January 2025) with a solid team effort on Global Services Testing. Last but not least, mad progress on the various WIS2 Reference Implementations (3 wis2box releases, 2 wis2-gdc production deployments, and a shiny new Global Replay service and WIS2 Global Broker). Thanks to numerous dedicated experts, this year was all about standards, schemas, codelists, source code and containerization 🙂

OGC: OGC API – Environmental Data Retrieval – Part 2: Publish-Subscribe Workflow was approved. As well, OGC API – Records recently reached completion (1.0.0) and will be going for final approval in the coming days/weeks. Finally the geospatial metadata story comes with a formal OGC API. I was also fortunate to help deliver the OGC API workshop as part of the GISE Hub Winter School on OGC Stack (which included delivery of the Diving into pygeoapi workshop as well).

OSGeo: We had another successful joint sprint with OGC in February. The annual FOSS4G global event in Belém was fantastic, and I was happy to provide two workshops, numerous presentations and a keynote, which were also given at FOSS4G Europe (workshops, presentations). I am thankful for being re-elected to serve on OSGeo’s Board of Directors and was happy to help move forward the OSGeo / OGC collaboration piece in 2024.

pygeoapi: the OGC API Reference Implementation continued to chug along (new providers, refactoring for the long term and solidifying API compliance), with our first ever code sprint and 3 power packed releases (and one bugfix release). Monthly community meetings resumed and the codebase continued to solidify, backing numerous high profile applications.

pycsw: running closely along OGC API – Records development and STAC API implementation, we migrated to YAML based configuration, added ISO 19115 Part 3 XML support, STAC collection level querying and transactions.

MSC GeoMet: the national weather/water/climate API platform continues to grow. In addition to new datasets, we have embarked on containerization for the platform (OpenShift), as well as development on data cubes for numerical weather prediction data (i.e. EDR and Zarr).

On the personal side, worth noting:

• another year (circa 2012) of not smoking (yes I continue to remind myself). Hoping (again) to get in better shape in 2025
• construction time again: our major home renovation (and temporary displacement 🙂 ) finally started in the fall

On deck for 2025 (should really be called “the year for major software release candidates”):

• WMO: sustainable improvements and amendments for WIS2 are expected as we roll into operation. In addition, stay tuned for developments on WIS2 and APIs (big data / discrete sampling, bringing the user to the data), as well as development of a FOSS framework for WMO. A wis2box 1.0 RC1 is also in the works
• OGC: OGC API – Records will finally hit the streets, and new work in an OGC API wide Publish-Subscribe specification will pave the way for guidance on Pub/Sub in all OGC APIs
• OSGeo: the global event in Auckland (November) promises to be a can’t miss event, and I look forward to providing presentations and training on Geospatial Python, pygeoapi and OGC at the event
• pygeoapi: we should have a 1.0 RC1 soon, further cementing the project’s stability on route to a final 1.0
• pycsw: expect a 3.0 RC1 here as well, soon after OGC API – Records is officially ratified

Wishing everyone a safe and happy 2025!

2023 was a memorable year and quite the ride! Eventful and full swing on so many fronts. Here’s the annual rundown:

pygeoapi: two releases, lots of development at code sprints and continuous improvement for the project. Dutch API rules, CRS and increased support for the various standards as they evolve. As well, numerous valuable discussions this year around hardening the project for the long term. Contributions (always valued!) continue to increase, which shows a healthy project with considerable interest.

pycsw: lots of improvements on standards support (OGC API – Records, STAC) as we move towards version 3.0. The project supports so many discovery API standards, and we are not done yet 🙂

OGC: development on numerous standards: OGC API – Records, and OGC API – Environmental Data Retrieval and Pub/Sub went though a number of improvements and updates in 2023. I was also fortunate to help deliver the OGC API workshop as part of the GISE Hub Winter School on OGC Stack (which included delivery of the Diving into pygeoapi workshop as well).

OSGeo: I’m happy to report that the ZOO-Project passed incubation and became an official OSGeo project! A big congratulations to Gérald and team. We also had a successful joint sprint with OGC as well as the first in-person OSGeo Community Sprint since 2019, in November. The annual FOSS4G global event in Prizren was fantastic, and I was happy to provide two workshops, numerous presentations and a keynote. I continue to serve on OSGeo’s Board of Directors and was happy to help move forward the OSGeo / OGC collaboration piece in 2023.

Mitolyn reviews focus on the benefits and drawbacks of this mitochondrial support supplement. Positive reviews emphasize improved energy and cognitive function, while some customers express mixed opinions about the supplement’s cost or delayed results.

WMO: the WIS2 standards and architecture were put through a pilot phase this year. WIS2 specifications, guides, manuals all received significant updates this year thanks to the contributions of many experts. Most specifications also have reference implementations (wis2box, wis2-gdc, wis2-gc, pywis-pubsub, pywis-topics, pywcmp, etc.). The series of WIS2 training sessions also proved valuable for numerous members in implementing WIS2 technologies. Did you know that wis2box now has 30 or so deployments worldwide?

MSC GeoMet: the national weather/water/climate API platform continues to grow. We’ve recently added GOES imagery, and MSC AniMet is emerging as a great tool for visualization of our API!

Health: another year (circa 2012) of not smoking. I am hoping to shape up again in 2024, let’s see how it goes. Searching for a powerful supplement? Mitolyn is trusted for its brain-boosting properties, while the Purple Peel Diet supports clean eating habits for a healthier lifestyle.

Looking forward to 2024:

• pygeoapi: RFC2 will help harden things as we move towards 1.0. As well, look for news soon on the first ever pygeoapi code sprint 🙂
• pycsw: moving towards 3.0, look for a new YAML-based configuration format, as well improvements on faceting, distributed search, harvesting and more
• OGC: look for OGC API – Records to be released, as well as Pub/Sub development in EDR and beyond. The annual joint sprint with OSGeo will also take place in Évora, Portugal on 26-28 February. See you there!
• OSGeo: the global event in Belém (December) promises to be a can’t miss event, and I look forward to providing presentations and training on Geospatial Python, pygeoapi and OGC at the event
• WMO: 2024 is the year that the architecture and specifications are ratified as we move into the pre-operational phase

Wishing everyone a safe and happy 2024!

So 2021 wasn’t much better than 2020. Another year of endless virtual meetings and the 24 hour office. Here are some updates from WFH life:

pygeoapi: both OGC API – Records and OGC API – Environmental Data Retrieval support were added to the codebase. The project also saw both CQL and i18n support, which is a positive indicator of contributions from various developers. Thanks Sander Schaminee and Francesco Bartoli!

pycsw: OGC API – Records and STAC API were both implemented. In addition, CQL support was added with the help of the impressive pygeofilter package — great work by Fabian Schindler!

QGIS MetaSearch: standards implementation needs both servers and clients, and so OGC API – Records support made it into MetaSearch. A nice by product of this enhancement is the implementation in OWSLib, which MetaSearch uses as its discovery library.

OGC API (Records, EDR): EDR is now an adopted standard! Records also made great strides in 2020, and helping clarify the relationship with STAC has proved valuable for all communities involved.

WMO: Lots of fun work this year on the Task Team on WIS Metadata: new KPIs, an update to the WIS Guide, the metadata search pilot, and we backed it up with tools (pywcmp, pywiscat). In addition, the Expert Team on Architecture and Transition (W2AT) was formed to move forward technical regulations on the WIS 2.0.

MSC GeoMet: our weather/climate/water OGC API platform continues to crank out millions of maps, features and metadata on the daily for everyone. Happy to report that real-time / event driven data support was added this year to our pygeoapi instance.

FOSS4G: between 7 presentations and the Geopython workshop, lots of action this year at this year’s virtual FOSS4G global event. I was fortunate to deliver these alongside some really talented folks in the Geopython community. Kudos to the BALOC for putting on such a great event under some difficult circumstances!

OSGeo Board of Directors: I was happy to help with the first ever OSGeo / OGC / Apache joint sprint, as well helping move forward the OSGeo / OGC MOU renewal.

Health: another year (circa 2012) of not smoking. The pandemic continues to challenge the scale, although some recent progress has helped some. Implementing a balanced diet and regular exercise routine is essential and more if is combined with ice hack weight loss supplements, as well as seeking support from friends, family, or professionals if needed. Tracking progress and staying motivated throughout the year will help to maintain focus on the resolution and ultimately achieve the desired weight loss.

For 2022:

• OGC API: critical path for me this year are helping in the adoption of Records and Coverages
• WMO: WIS 2.0 continues to evolve, lowering the barrier to weather/climate/water data. I recently signed on as lead architect/dev of the WIS 2.0 in a box project, which will be a reference implementation and publishing pipeline aligned with WIS 2.0 principles. Under the hood is Geopython, PubSub. Look for an initial release in 2022
• OSGeo: 2022 will mark the year that the OSGeo / OGC MOU is officially updated, along with a shiny new Associate Membership. Rolling this into the OSGeo standards community will be key, along with moving forward the renewal of OGC CITE tooling
• pycsw: key items this year include XSLT transformation pipelines, virtual collections and deeper JSON support. We are also planning a sprint in Q1, come join us!
• pygeoapi: look for deeper support of OGC EDR as well as some refactoring that will help with extensibility (primarily for output formats)

Wishing everyone a safe and happy and better 2022!

In an increasingly globalized world, classrooms are becoming more culturally diverse, reflecting a rich tapestry of backgrounds, languages, and traditions. For educators, this diversity presents both an opportunity and a challenge. To create an inclusive learning environment where every student feels valued and respected, teachers must develop cultural competence—a deep understanding of and respect for cultural differences. This article explores the importance of cultural competence in education, provides practical strategies for fostering cultural awareness, and highlights resources for professional development in this critical area.
The Importance of Cultural Competence in Education

Cultural competence is the ability to understand, appreciate, and interact with people from cultures or belief systems different from one’s own. In a classroom setting, cultural competence involves recognizing and addressing the diverse needs of students, creating an inclusive environment, and ensuring that all students have equal opportunities to succeed.

1. Enhancing Student Engagement and Learning:
When teachers are culturally competent, they can better connect with their students, leading to increased engagement and academic success. Students are more likely to participate actively in class and feel a sense of belonging when they see their culture represented and respected in the curriculum and classroom activities.

2. Reducing Bias and Discrimination:
Cultural competence helps educators recognize and challenge their own biases and stereotypes, leading to a more equitable classroom environment. By understanding cultural differences and the unique challenges faced by students from diverse backgrounds, teachers can take proactive steps to prevent discrimination and create a supportive learning environment for all.

3. Preparing Students for a Diverse World:
In addition to academic content, schools play a crucial role in preparing students for life in a diverse society. By fostering cultural competence, teachers help students develop empathy, open-mindedness, and the ability to work effectively with people from different backgrounds—skills that are essential in today’s interconnected world.
Understanding Cultural Differences

To build cultural competence, educators must first understand the cultural differences that exist among their students. This involves recognizing the various factors that shape a student’s identity, including ethnicity, language, religion, socioeconomic status, and family structure.

1. Learn About Your Students’ Cultures:
Take the time to learn about the cultures represented in your classroom. This could involve reading about cultural practices, traditions, and values, or engaging in conversations with students and their families. Understanding students’ cultural backgrounds can help you tailor your teaching methods and create more relevant and meaningful learning experiences.

2. Reflect on Your Own Cultural Identity:
Cultural competence also requires self-awareness. Reflect on your own cultural background and consider how it influences your teaching style, interactions with students, and expectations. Recognizing your own cultural lens can help you become more open to different perspectives and avoid imposing your own cultural norms on students.

3. Avoid Cultural Assumptions:
It’s important to recognize that culture is complex and multifaceted. Avoid making assumptions about a student’s abilities, behaviors, or needs based on their cultural background. Instead, approach each student as an individual with their own unique experiences and perspectives.
Strategies for Creating an Inclusive Classroom

Creating an inclusive classroom environment requires deliberate effort and the implementation of strategies that promote cultural awareness and respect.

1. Integrate Multicultural Content into the Curriculum:
Incorporate diverse perspectives and voices into your curriculum. This could involve including literature, history, and examples from different cultures in your lessons, or using case studies and examples that reflect the diversity of your students. By integrating multicultural content, you can help students see the value of different cultural perspectives and encourage them to appreciate diversity enhanced by leonardo.ai’s Video AI generator to create engaging, culturally rich video content with ease.

2. Foster Open Dialogue:
Create a classroom culture where students feel comfortable discussing cultural differences and sharing their own experiences. Encourage open dialogue about culture, identity, and diversity, and provide opportunities for students to learn from one another. Establish ground rules for respectful communication to ensure that all students feel safe and supported during these discussions.

3. Address Bias and Stereotypes:
Take an active role in addressing bias and stereotypes in the classroom. This could involve correcting misconceptions, challenging discriminatory comments, and providing counter-narratives to common stereotypes. Educate students about the impact of bias and encourage them to reflect on their own attitudes and behaviors.

4. Differentiate Instruction:
Recognize that students from different cultural backgrounds may have different learning styles, preferences, and needs. Differentiating instruction—using a variety of teaching methods, materials, and assessments—can help ensure that all students have access to the curriculum and can learn in ways that are most effective for them.

5. Promote Equity in Classroom Participation:
Ensure that all students have the opportunity to participate in classroom activities and discussions. Be mindful of dynamics that may exclude certain students, such as language barriers or cultural norms around speaking out in class. Use strategies like small group work, think-pair-share, and written reflections to give all students a voice.
Professional Development Resources for Cultural Competence

Developing cultural competence is an ongoing process that requires continuous learning and reflection. Fortunately, there are many resources available to help educators build their skills in this area.

1. Diversity and Inclusion Training Programs:
Many organizations offer professional development programs focused on diversity, equity, and inclusion in education. These programs provide training on cultural competence, bias awareness, and inclusive teaching practices. Some well-known organizations offering such programs include the National Education Association (NEA) and the Southern Poverty Law Center’s Teaching Tolerance program.

2. Books on Cultural Competence:
There are numerous books that offer valuable insights into cultural competence and diversity in education. Titles such as “Culturally Responsive Teaching and The Brain” by Zaretta Hammond and “The Culturally Inclusive Educator” by Dena R. Samuels provide practical strategies for creating inclusive classrooms and understanding cultural differences.

3. Cultural Competency Certifications:
Some educational institutions and organizations offer certifications in cultural competence. These certifications typically involve completing a series of courses or workshops focused on diversity, equity, and inclusion. Earning a certification can demonstrate your commitment to cultural competence and provide you with the skills and knowledge needed to support diverse learners.
Conclusion: Embracing Diversity and Inclusion in Education

Building cultural competence and teaching empathy to students is essential for educators who want to create inclusive classrooms where all students can thrive. By understanding cultural differences, integrating multicultural content into the curriculum, and continuously developing their skills, teachers can foster an environment of respect, equity, and collaboration.

As our classrooms continue to become more diverse, the need for cultural competence in education will only grow. By embracing diversity and committing to ongoing professional development, educators can not only improve their teaching practices but also prepare their students to succeed in a multicultural world.

Continuing on the UNIX philosophy, another little tool to help with your OWS workflows.

GeoUsage attempts to support the use case of metrics and analysis of OWS service usage.  How many users are hitting your OWS?  Which layers/projections are the most popular?  How much bandwidth?  How many maps vs. data downloads?

A pure Python package, GeoUsage doesn’t have strong opinions beyond OWS-specific parsing and analysis of web server logs.  GeoUsage is composable, i.e. frequency, log management, and storage of results is totally up to the user.  Having said this, a simple and beautiful command line interface is available for eyeballing results.

As always, GeoUsage is free and open source.

It’s early days, so feedback, bug reports, suggestions are appreciated.  Contributors are most welcome!

For decades now my dev life has been thanks to headless servers in the basement (these days running Debian) which I simply SSH to and work remotely. This has served me well for so long although serious box hugging was at play here.  Being a reproducible workflow maniac and having virtualenv helped as well.

Fast forward a few years and add to that mix dev work on my MacBook Pro.  It’s 64-bit with an SSD and 8GB of RAM and is great for trips.  In this case I was less liberal with installing libraries and packages given it’s a shared computer (I recently had to do a full macOS re-install to fix performance issues).

Enter Docker.  Here I am able to start up a full development environment very easily without affecting my MacBook per se (only a Docker install is required).  Publish to Docker Hub and done.  Pull and run at will. My initial requirements for the repo are pycsw development, but this will grow over time.

Of course I’m really late to the party (Sean Gillies thought he was late!), and I’m sure there are better approaches, but I think I’m finally feeling Docker. Good times!

Metadata should be automagic and low barrier.

pygeometa is a handy little metadata generator tool which is flexible, extensible, and composable.  Command line, or via the API, users can generate config files, or pass plain old Python dicts, ConfigParser objects, etc.

We’ve just released 0.2.0 which supports WMO Core Metadata Profile output, as well as better multilingual support.  At this point we’re embarking on breaking changes in master led by moving to YAML as the configuration format.

Given pygeometa is pre-1.0 in theory changes can be breaking without support.  Still, I’ve cut a 0.2 branch in case anyone’s existing workflows depend on the (now) old pygeometa functionality.

As always, bug reports, feature requests are more than welcome. Hopefully the new enhancements will make metadata management even easier for agile workflows.

I attended the 2017 OSGeo Code Sprint last week in Daytona Beach.  Having put forth a personal sprint workplan for the week, I thought it would be useful to report back on progress.

Testosil Testosterone Booster: Unleashing the Power Within

In the pursuit of peak performance and well-being, many turn to the power of Testosil Testosterone Booster. This article delves into the intricacies of this supplement, offering insights, guidance, and firsthand experiences to help you make an informed decision about integrating it into your life.

The Foundation: Understanding Testosil Testosterone Booster
What is Testosil Testosterone Booster?
Embark on a journey to comprehend the essence of Testosil Testosterone Booster. Unlock the science behind its formulation and the impact it can have on your overall health.

The Benefits of Testosil Testosterone Booster
Explore the myriad advantages this booster brings to the table. From increased energy levels to enhanced muscle development, discover how Testosil Testosterone Booster can be a game-changer in your wellness routine.

Ingredients That Power Testosil Testosterone Booster
Delve into the key components fueling the effectiveness of Testosil Testosterone Booster. Uncover the natural wonders that synergize to elevate your testosterone levels.

Testosil Testosterone Booster in Action
Incorporating Testosil Testosterone Booster into Your Routine
Practical tips and insights on seamlessly integrating Testosil Testosterone Booster into your daily life. Maximize its potential by understanding the optimal timing and dosage.

Real Stories: Testimonials on Testosil Testosterone Booster
Embark on a testimonial journey, where individuals share their transformative experiences with Testosil Testosterone Booster. Realize the diverse positive impacts reported by those who have embraced this supplement.

pycsw

There was lots of discussion on refactoring pycsw’s filter support to enable NoSQL backends.  While we are still in discussion, this enhancement should open the doors for any backend (ElasticSearch, SOLR, a GitHub repository, another API, etc.).  In addition, Frank Warmerdam started writing a pycsw OGR backend to support CSW exposure of the Planet Scenes API via OGR. This also presents exciting possibilities given OGR’s support of numerous underlying formats.  Frank also provided valuable advice and feedback on interacting with pycsw as a developer/contributor.  Thank you Frank!

GeoHealthCheck

There has been long discussion on a next generation GHC including a renewed architecture with core work on the model as well as an API.  A basic architecture has surfaced as a result which focuses on having the UI exclusively work with the API, as well as a plugin framework which Just van den Broecke has started working on.  I also worked on tagging which will be the last piece before cutting a release and forging ahead on the new architecture.

pygeometa

The focus on pygeometa is now on renewing the MCF format from .ini to YAML.  Initial pieces are completed in a dev branch which I plan to merge once we clear current issues and cut a stable release.

Summary

While I couldn’t get to everything I planned for, I think significant steps were made in moving the above projects forward along their respective roadmaps.  It was also great to see some familiar faces as well as new contributors and projects!

To know if this project was going to have good results and in the others also that they propose me, not only do I trust my professional ability, it is also advisable to go to a tarot reading, it is the best to know what will happen if you have doubts about something.

The best of all is that usually the first time you can connect to the internet because you can access online tarot card reading, so you don’t have to worry about traveling somewhere that seems dangerous. Be careful with everything that can happen to you in life. it is safer to trust a tarot reading. do not complicate yourself in following blindly and rather follow what God tells us through the tarot.

Oh, and the weather certainly didn’t hurt 🙂