decredcommunity / events Goto Github PK

@3lian please review

https://github.com/decredcommunity/events/blob/index/index/1599778313.yml

Did I fill people correctly?

Giving proper credit by listing all participants will be useful for automating reporting, e.g. "give me all reports where person X participated".

@3lian please review

https://github.com/decredcommunity/events/blob/index/index/1599779259.yml

description and any notes appreciated. Also the titles look a bit out of sync, I can correct EN or ES version.

Let's use this issue to collect feedback on the events index. Please comment on your experience of writing/editing/using the index entries.

We discuss this:

• pretty published version here
• raw data here
• spec for the data format is here

Ideas to consider:

• is it easy to understand overall?
• is it an improvement over the previous long report format?
• is it easy to write?
• anything inconvenient or slowing you down?
• is it easy to use once published?
• are you using it in the wild, i.e. sharing event links?
• do you see how to improve the rendered pages (check this one as a demo of a complex case)
• any other important data we should start capturing (e.g. background of attendees)?
• what kind of reports generated from the entries would you like to see first (e.g. list events by country, by person, by organizer, etc)?

We need to identify people in several places of the report. There are various identities to use: real name, Twitter name, Matrix name, GitHub name, etc. Which to use and when?

The issue is similar to xaur/decred-news#20

Upcoming Events was removed from the wiki because nobody maintained it. What's left is:

• https://github.com/decredcommunity/events/wiki/Best-Practices
• https://github.com/decredcommunity/events/wiki/Facilitating-A-Meetup-Guidelines
• https://github.com/decredcommunity/events/wiki/Submit-Event-Report

These don't change often, and we might even move some to the guidelines repo (because the guidelines are getting scattered).

This issue is to discuss what we need in the wiki, if anything at all.

" "Akin and Collins"

@3lian let's try another review:

https://github.com/decredcommunity/events/blob/index/index/1599772695.yml

• note the { ok? } review comment - same as those we use in DJ
• I realized that long lines of text have annoying horizontal scrollbars. As a work-around you can click Raw button to get wrapped text.
• do all fields look correct?

@3lian please review

https://github.com/decredcommunity/events/blob/index/index/1599780151.yml

I think I got all but just in case :)

@3lian please review

https://github.com/decredcommunity/events/blob/index/index/1599781359.yml

I think I got all covered, but just in case.

@3lian I made an entry for HablemosDecred 11, please check if all is ok

https://github.com/decredcommunity/events/blob/index/index/1602349160.yml

@Michae2xl please review:

https://github.com/decredcommunity/events/blob/index/index/1599773576.yml

Did I fill everything correctly? Do you want to change/add any interesting details?

@3lian so let's start our "lightweight reports" experiment :)

Please review:

https://github.com/decredcommunity/events/blob/index/index/1599771265.yml

and let me know if all fields look good and what you think of the format.

I designed this format to balance between being readable by humans, relatively easy to fill from a template, and relatively easy to build some automated goodness upon (e.g. list events by month, by country or people involved)

Some reports cover more than a single event. Latest examples are from Vietnam and Argentina. For both of them, I got stuck for a moment thinking whether to split or keep as one report.

The problem with combined reports is any given event is no longer represented by its single file. If you look for Argentina Crypto Fest using filenames, you won't find it. You'll have to remember that it lives in the report for La Conexion or use text search.

The good side of allowing multiple events in one file is that it allows to

• cover multiple related events (e.g. in a single trip to some country)
• cover multiple small events (there's often an afterparty after the main event)
• describe a series of events in a common context
• avoid text duplication by not copying common context in N files
• save time by not thinking how to arrange M events in N files

I suggest to do two things:

• define some criteria when the related reports must be split
• when the reports can be kept in one file, define how to name the file

Here is the link to the draft report. Please review for formatting and typos.
https://gist.github.com/nottrunner/d58a89dbbb4cba5f5c74534b8f6116bf

We might want to "publish" the report documents with better page styling and use these links in tweets and other places.

There are options:

• I can enable GitHub Pages for this repo like we do for Decred Journal (a bit less loaded style compared to raw GitHub)
• we can publish via decredcommunity.org
• or even decred.org

Any ideas or preferences?

@3lian please review

https://github.com/decredcommunity/events/blob/index/index/1599780549.yml

I miss description, but any other info is welcome.