Closed lianplass closed 3 years ago
I figured it was because of that list integration issue. I'm not overly familiar with awesome lists, but I did take a mo' to check out the running threads on this repo and some of the documentation on their end. I like the idea of conforming to the awesome list standard as it would improve the accessibility of the repo. I mentioned this on the webinar via the OH section, but I'm happy to help as a maintainer of this repo regardless of the format it takes. This is an invaluable resource for the planning community and a wonderful way for planners (myself included) to start to learn the value of open source. edit to answer your question, it wouldn't affect my ability to contribute at all.
I have been reluctant to do a full switch (renaming the repo), but I emailed the awesome list maintainer and that is not required. I think I generally agree on conforming to everything else though. That is what that branch is for. I am working on getting it so that branch passes all tests before a full merge. I will investigate making you a maintainer offline with you. Thank you for your interest.
You can ignore the errors. I will get this integrated soon. Basically looking at some major format changes in this branch. https://github.com/APA-Technology-Division/planning-technology-resources/tree/awesome-compliance While outside the scope of your PR, any feedback you have on it is appreciated. Would it make contributions easier? Harder?