Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Add YAML to README generator #26

Merged
merged 5 commits into from
Feb 14, 2019
Merged

Add YAML to README generator #26

merged 5 commits into from
Feb 14, 2019

Conversation

luxas
Copy link
Member

@luxas luxas commented Feb 14, 2019

Fixes: #3
@kaspernissen @netumoliver

@Steiniche
Copy link
Member

Steiniche commented Feb 14, 2019

Looks great @luxas!
One question: Should meetups.yaml be ignored and then the current one could be an example instead?
Or am I missing something?

@luxas
Copy link
Member Author

luxas commented Feb 14, 2019

Now everything is gonna be genersted from meetups.yaml eventually

@ojoggerst
Copy link
Member

Looks very good to me as well.
Did you have in mind to have one yaml per country or all in one?

@luxas
Copy link
Member Author

luxas commented Feb 14, 2019

I'd like to have speakers and companies in the same centralized list, but meetup groups can have their own filw eventually as a follow up indeed

@ojoggerst ojoggerst merged commit 99e6824 into master Feb 14, 2019
@kaspernissen
Copy link
Member

Great work @luxas ! It makes sense to have speakers and companies in a centralized list, but I think we should have a meetups.yaml for each meetup group, otherwise the file will probably get very bloated.

@kaspernissen
Copy link
Member

I was just wondering, would it make sense to have a separate repo for the generator, and let this repo contain the generated markdown and of course presentations etc. as we have them now?

@luxas
Copy link
Member Author

luxas commented Feb 15, 2019

I think we should have a meetups.yaml for each meetup group, otherwise the file will probably get very bloated.

Yep, that makes sense to me. This is just the initial code needed. You can PR that 😉

would it make sense to have a separate repo for the generator, and let this repo contain the generated markdown and of course presentations etc. as we have them now?

I don't think so. It's a very small go program, I'm planning to do CI with the generator, so we'd have pre-merge checks of that the generated code is correct, and then it's way easier to have it centralized. I don't think it bloats this repo to a large extent.

@luxas luxas deleted the generator branch February 22, 2019 13:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants