It's not 100% correct, I rushed this a bit :)

I don't wanna maintain this, please submit yourself for consideration with some clear reasoning on this issue

Open source project maintainence experience preferred

Only publish once the list is accepted into the official Awesome list

Create the following github workflows:

• Run the awesome-lint tool on prs
• Run a spellchecker on the documents
• Check for broken external links
• Update CONTRIBUTORS.MD
• Optimize images

I just copied the ones that came with the awesome repo, we need ones that we can all agree on

we might even have them in discord already

either way these need to get updated

Additional details in the Awesome list guidelines

Project Awesome

in the spirit of experimentation i've made this repository to get a feeling of what might be possible in terms of collectively contributing to both hic et nunc proper and the broader hic et nunc ecosystem

if you feel contributing is something that would interest you then please participate

What?

an "Awesome List" is a list of cool projects centered around a central topic. If the list is Awesome enough it gets included in the Awesome Awesome List which is, you guessed it, a list of Awesome Lists.

Why?

i'm interested in guaging the state of the members of the community who are onboard and aligned with hic et nunc, and i think this little experiment will help paint a bigger picture for me

it's loosely based on my own personal recruitment techniques and i'm interested to compare the response when the reward is not disproportionately financially motivated, and to see what kind of self-organisation happens in instances like this

How?

i've added issues that test aspects i feel are important. but please feel free to add your own issues as this is a matter of community

there are tags outlining the categories i feel this repository needs help with - code, administration, and design

tasks that are currently blocked are marked as such. their dependencies need to be resolved before they can begin

the main code task has a tasklist. each task must only be 1 PR (i.e. there should be 5 PRs for a 5-point list)

Who?

coders, designers, administrators, community managers, authors... everyone is welcome and you'll find something you can do if you're inclined to do so

When?

this repository will be transferred to the official hen repository if (a) the tasks are complete, and (b) if hic et nunc feels this repository should be hosted there. the decision should happen before submission of the list to Awesome List themselves.

It's going to need some cleanup as it has to match the standards as laid out in the official Awesome list rules

This is on me, I'll do it as soon as we've settled on a process :)

We need to popilate the readme and get all the tools into place