Progress Report for May
What progress was made on your grant this month?
- Worked on query/sort/filter library
- Given all of the planned plugins for the portal, I ended up going on a side quest and rewriting the entire http layer which uses the go echo router at the base. Took longer then I wanted, but the goal was:
- To not use a unmaintained router (gorilla)
- Create a framework for using the routing API to describe itself so
swagger.yamlcan be dynamically generated and served. - In the process of this several repos were worked on:
- httputil library: Still mostly client side http utilities
- gswagger fork: Middle layer that does a lot of the openapi work
- portal-router: a new library
- Created a new portal-middleware library that extracts out from
portaland is a new near-complete rewrite of all the required HTTP needs.
- Did further webapp framework engineering:
- Found simpler solutions to past react issues
- Created unit testing for many core libraries and some of the UI components
- Started an effort on storybook
- Took another side quest and ended creating a small testing framework for portal plugins. I have been working in unit test code with the abuse plugin and dashboard and found it was getting to be too much duplicated effort. Goal is to streamline that aspect of development as much as possible.
- Worked on the abuse plugin. Mainly upgrading it to use new libraries, new routing, verify tests work. Still needs to use the new testing library.
- Worked on the dashboard plugin. Mainly upgrading it to use new libraries, new routing. Still has a bit of work left.
- Worked on the abuse plugin. Mainly upgrading it to use new libraries, new routing.
Summarize any problems that you ran into this month and how you’ll be solving
No issues this month other then I hit a lot more foundation work being required, unexpectedly, in the process of trying to build the admin ui & abuse admin.
Links to repos worked on this month:
- Comparing 8f7e8b6..a12f5ce · LumeWeb/queryutil · GitHub
- Comparing b91644e..5f9b0e5 · LumeWeb/gswagger · GitHub
- Comparing 1655679..bd1bb58 · LumeWeb/httputil · GitHub
- GitHub - LumeWeb/portal-router · GitHub (no hashes needed, this is a new repo).
- GitHub - LumeWeb/portal-middleware · GitHub (no hashes needed, this is a new repo).
- Comparing 2e3a67d..6397bed · LumeWeb/portal · GitHub
- Comparing 6fd9709..9feb1b2 · LumeWeb/portal-plugin-abuse · GitHub
- Comparing 8bde201..be101a1 · LumeWeb/portal-plugin-dashboard · GitHub
- Comparing 02b082a..19712b3 · LumeWeb/portal-plugin-admin · GitHub
- Comparing 2b73939..104c4db · LumeWeb/web · GitHub
What will you be working on next?
- Finish the abuse (I honestly am hoping this takes under a week, the react parts on this are not complicated as I see it)
- Focus on atproto and figure out its requirements
- Get the dashboard webapp onto the new framework (my account, etc)
- Get IPFS back in sync with core, and get a web plugin for it ported over from the legacy webapp.
- Get the community server operational for user testing.
- Work on S5
As of right now I am definitely viewing my milestones as being pushed back overall and my expectations are that I will primarily be doing a lot of plugins/integrations in a short period, so I foresee the next 3-4 months as being very compressed once I am able to get everything back online again. That is why I am trying to make that effort as minimal as possible so if im creating a ton of plugins they aren’t hard to make… be it protocol, informational or misc.
Lastly for a visual on milestone progress here is a screenshot of the abuse admin dash, no real data yet.
