20 Nov 2018 |
bridge-bot | [rocketchat] <geleeroyale> 2 | 13:32:36 |
| geleeroyale invited Tatu. | 13:32:58 |
| geleeroyalechanged room power levels. | 13:33:04 |
21 Nov 2018 |
| Tatu joined the room. | 09:35:19 |
| Room Avatar Renderer. | 09:42:55 |
| Tatu changed the room name to "Monthly" from "monthly". | 09:43:15 |
| Tatu set the room topic to "Collaboration on the Aragon Monthly newspaper. https://monthly.aragon.org". | 09:43:15 |
| Tatu changed the join rule to "public" from "public". | 09:44:05 |
22 Nov 2018 |
bridge-bot | [rocketchat] <marikio> [ ](https://aragon.chat/channel/monthly?msg=ERQq6YczqtJs9DPZZ) @light Thanks @light! Hi @kris, will reach out via DM and ask a couple questions :). | 14:24:19 |
26 Nov 2018 |
| Tatuchanged room power levels. | 10:44:32 |
| light joined the room. | 21:54:01 |
| joshafairhead joined the room. | 22:26:23 |
30 Nov 2018 |
bridge-bot | [rocketchat] <kris> [The Aragon Monthly 10 is out!](https://monthly.aragon.org/) - Do read up and don't hesitate to help us spread the message, very welcome to [like, retweet](https://twitter.com/AragonProject/status/1068557986824691712) and [upvote](https://www.reddit.com/r/ethtrader/comments/a1unbj/aragon_monthly_issue_10_is_out_the_latest_issue/) <3 | 17:48:21 |
| krrisis joined the room. | 17:53:18 |
| gabi joined the room. | 19:47:29 |
5 Dec 2018 |
| lightnode joined the room. | 17:19:41 |
krrisis | Issue 11 is up to compiled by an editor! https://gitcoin.co/issue/aragon/aragon-monthly/292/1911 | 21:05:27 |
krrisis | We also still have a bounty out for an article https://gitcoin.co/issue/aragon/aragon-monthly/273/1776 | 21:05:58 |
krrisis | I optimized the editor guide slightly to make it easier to contribute, if you find certain things unclear, don't hesitate to ping me here and I'll edit this, all feedback very welcome. | 21:10:52 |
7 Dec 2018 |
| louis.grx joined the room. | 09:46:51 |
krrisis | Hey, so I have some thoughts. I would like to simplify the submission process for the aragon monthly a bit and would love some input. I started to update the guides but I get stuck because if I'd want to change parts I'd have to change the entire logic. @marikio wanted to create video tutorials (sent you a dm last week!) but maybe it's interesting to get some community feedback on the process itself before we create those. | 17:15:10 |
krrisis | I see the people who take up the editing process don't have a lot of issues, they most of the time 'get' markdown and Tatu's instructions are super clear, so no prob there. | 17:15:49 |
krrisis | However, when it comes to submitting content (articles, news, classifieds), the process is a bit less straightforward. I was wondering if there are people in this room who have done this already and what their thoughts are. | 17:16:41 |
krrisis | The correct process is to take the appropriate template, create an .md file and to submit this as a pull request to the right folder. The biggest content contributor right now is without a doubt @light / light - you submit virtually all of the news, which is fantastic. However, you submit this as new issues. Not as a PR to the right folder, using the template described here - https://monthly.aragon.org/guides/guide_for_submitting_news/ | 17:19:37 |
krrisis | This makes sense to me, bcs that would be a whole lot of extra work for you, bcs you'd have to copy the image source, add the author etc etc, which is more time intensive for you, which could mean less news content. Now this adaptation is done by the editors. | 17:21:51 |
krrisis | If I now would push more people to submit news, articles & classifieds, they would prob prefer to do this the way you do this, through a simple issue, not creating a pull request in the format we require. To me this is fine, bcs esp. for classifieds and news, the PRs would never match up anyways (because we work with columns). I think it's easier if we do this through simple issues. | 17:26:51 |
krrisis | Any thoughts on this? By you john, or @tatu or others? | 17:27:45 |
krrisis | It would make the guides way simpler and I could move 90% of the guides to one guide for the editors, not for the people who submit content. | 17:28:27 |
krrisis | For articles I would propose to also work with issues only, where they just refer to a google doc, advantage of this is that it is easier to comment on a google doc, and the person submitting does not need to know github at all, he just needs to have an account and be able to hit 'new issue'. John created an issue with a similar suggestion a while back with some good feedback on it, for people interested https://github.com/aragon/aragon-monthly/issues/19 | 17:41:27 |
krrisis | All of the above is just me thinking out loud, I just want to make it as easily as possible for the community to contribute. All feedback here or on that issue are very welcome! | 17:42:10 |