1512 lines
386 KiB
HTML
1512 lines
386 KiB
HTML
<html><body><style>
|
|
* {
|
|
font-family:sans-serif;
|
|
}
|
|
body {
|
|
text-align:center;
|
|
padding:1em;
|
|
}
|
|
.messages {
|
|
width:100%;
|
|
max-width:700px;
|
|
text-align:left;
|
|
display:inline-block;
|
|
}
|
|
.messages img {
|
|
background-color:rgb(248,244,240);
|
|
width:36px;
|
|
height:36px;
|
|
border-radius:0.2em;
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
margin-right:0.65em;
|
|
}
|
|
.messages .time {
|
|
display:inline-block;
|
|
color:rgb(200,200,200);
|
|
margin-left:0.5em;
|
|
}
|
|
.messages .username {
|
|
display:inline-block;
|
|
font-weight:600;
|
|
line-height:1;
|
|
}
|
|
.messages .message {
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
line-height:1;
|
|
width:calc(100% - 3em);
|
|
}
|
|
.messages .message .msg {
|
|
line-height:1.5;
|
|
}
|
|
</style><div class="messages"><div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-20 04:55</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-20 06:29</div><div class="msg">Please use the link to edit the file: <a href="https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit">https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-18/289102127286_0d00b7c17b8a24fd6f37_72.jpg" /><div class="message"><div class="username">zahary</div><div class="time">2018-04-20 06:34</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-04-20 06:34</div><div class="msg">Happy to have this channel! Thank you @alexmandel</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-20 06:35</div><div class="msg">My pleasure, @rachel! Please feel free to invite more people.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-22 05:03</div><div class="msg">@alexmandel set the channel purpose: Let?s discuss how to move Status documents under one roof!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-04-22 13:44</div><div class="msg">:raised_hands::skin-tone-4:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-04-23 11:07</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-24 09:47</div><div class="msg">Amazed by the aragon wiki everytime I come by: <a href="https://wiki.aragon.one/press/press-kit/">https://wiki.aragon.one/press/press-kit/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 04:52</div><div class="msg">I have been working on creating some test web pages in Docusaurus. Could anyone recommend where I can upload my builds for Status people to check?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 04:58</div><div class="msg">Nice! MkDocs... I'll check. Thanks!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-25 06:03</div><div class="msg">throw-away git repo?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-25 06:06</div><div class="msg">on that note, I've seen hackmd has some pretty cool diagramming integrations, does docosaurus offer the same? <a href="https://hackmd.io/features#UML-Diagrams">https://hackmd.io/features#UML-Diagrams</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-25 06:06</div><div class="msg">nice indeed!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:24</div><div class="msg">I know Docusaurus renders images. Diagramming, as in letting the user create a diagram?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-25 06:26</div><div class="msg">yeah, they integrate <a href="https://mermaidjs.github.io/">https://mermaidjs.github.io/</a> from what I remember, and `graphviz` and a bunch of others, so you can type up diagram source data in your markdown file (purely text) and it renders the text into a nice diagram</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-25 06:26</div><div class="msg">fantastic for describing protocols, flows and other techy stuff</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:29</div><div class="msg">What a concept! (and a great tool)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-25 06:49</div><div class="msg">@alexmandel if it's mostly about seeing the result an S3 website bucket might be easier than github pages </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-25 06:50</div><div class="msg">Actually not sure if that's true or I?m just too used to it :sweat_smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:51</div><div class="msg">Thanks. Isn't it paid service, though?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-25 06:54</div><div class="msg">Yeah but it costs like 15ct to deploy a few files as a website </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:54</div><div class="msg">Oh, okay :slightly_smiling_face: I'll check</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-25 06:54</div><div class="msg">Anyway probably GH pages branch is easier if you're already familiar with this </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:55</div><div class="msg">Will explore</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-04-25 06:55</div><div class="msg">@alexmandel let me know if you want to give S3 a shot and I can set it up for you </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-25 06:55</div><div class="msg">I appreciate it. I'll be in touch.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-25 09:12</div><div class="msg">Can setup GH pages easily too, we already use this for a bunch. Just create static site repo and ping </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-26 15:09</div><div class="msg">I have created <a href="https://alexm-status.github.io/energy-efficient-bok/">https://alexm-status.github.io/energy-efficient-bok/</a> with the.md files from status-im/energy-efficient-bok. It?s a lo-ong way from a nice API documentation tree, which usually has a side bar, an expandable structure, as well as other bells and whistles. I am sure GitHub has this and more, just not as part of the basic setup (<a href="https://pages.github.com/">https://pages.github.com/</a>), so this will take more time to figure out.
|
|
|
|
With Docusaurus, I have created a ?build? folder. @martin487 or @oskarth, I'd need help getting it (for what it's worth) to S3 or GitHub. The page has a side bar that I have been trying to populate with links to the MD content, and that's where I am stuck at the moment, because attempting to link to the .md files from sidebars.json messes everything up! (Is it possible MkDocs would make this less painful, even if for a newb at this? :sweat_smile:)
|
|
|
|
I'll keep on keeping on, but if any ideas come to mind on how to do this faster and more efficiently, please let me know.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-26 15:20</div><div class="msg">Can look at this tomorrow, is it also open source? On phone so can't see. What do you think a good short domain game would be? <a href="http://docs.status.im">http://docs.status.im</a>?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-26 15:22</div><div class="msg"><a href="http://docs.status.im">http://docs.status.im</a>? Short and sweet, yes :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 02:26</div><div class="msg">@alexmandel <a href="https://status-im.github.io/docs/">https://status-im.github.io/docs/</a> <a href="https://github.com/status-im/docs">https://github.com/status-im/docs</a> - can push your stuff to this repo</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 02:26</div><div class="msg">will ask Carl about CNAME soon/later</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 03:08</div><div class="msg">Just attempted to send/attach a large zip, but it's not appearing in this thread--taking a while to upload? I'll wait and try again if needed.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 03:11</div><div class="msg">@alexmandel you can push directly to that GH repo I think</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 03:12</div><div class="msg">do you need any help with git or github or so?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 03:18</div><div class="msg">actually, drag-n-drop is all it took, but I don't see anything there, probably not yet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 03:18</div><div class="msg">256 MB might take a while. i'll keep you posted.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 03:20</div><div class="msg">kk</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 03:20</div><div class="msg">256 MB sounds like a lot?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 03:28</div><div class="msg">acc. to the Docu instructions, the build had to be done from inside a cloned repo. also, i vaguely remember not being able to generate the site yesterday simply by running the command from the build folder--had to be inside the cloned repo (which includes the build)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 05:42</div><div class="msg">Just tried to upload again and noticed something: "Yowza, that's a big file. Try again with a file smaller than 25MB." I'll need to think of a way around this...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 13:49</div><div class="msg">@alexmandel hm I'm a bit confused, <a href="https://github.com/alexm-status/energy-efficient-bok">https://github.com/alexm-status/energy-efficient-bok</a> looks quite small</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 13:49</div><div class="msg">I feel like I'm missing some context here around Docusaurus</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 13:51</div><div class="msg">I just see artifacts in that repo as well, I think we want the docusaurus scaffolding as well? and then .gitignore will ignore artifacts, which I'd guess is the majority of all the big stuff you have</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 14:03</div><div class="msg">What do people think of brainstorming what we want and don't want from a documentation tool? Might be useful to look at pros and cons of existing solutions and see what is currently missing, what constraints of the problem are, etc.
|
|
|
|
I'm sure this has been done to some extent already, but it'd be useful if we had a shared doc for how we are thinking about picking the right tool for the job - apologize if this doc exists already!
|
|
|
|
@alexmandel @rachel @arnetheduck.slack</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-27 14:10</div><div class="msg">Added a section to above doc <a href="https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit#">https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit#</a> with some questions to explore the problem space</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-01-09/125597416918_4b7b095b4e695e7a8be1_72.jpg" /><div class="message"><div class="username">carl</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-04-27 14:11</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-27 17:07</div><div class="msg">@oskarth I'll get back to you on this</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-04-29 08:49</div><div class="msg">That would be fantastic, and thank you for taking the initiative. Iuri commented to me that he found readthedocs to be a bit lacking and that Embark outgrew it, hence the static site. Any options that are open and scalable in an organized way are equivalent to me.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-30 13:32</div><div class="msg">talking criteria first seems like a not bad at all way to go about it :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-30 13:41</div><div class="msg">Additional constraint from devops POV brought up by @jakub (possibly separate documentation effort entirely): desire to have it be ?closed source? by default to avoid potential security leakage, as opposed to open by default for general docs. Maybe best to have these questions treated separately but just useful to be aware of</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-30 13:50</div><div class="msg">I like the idea of a version controlled static site whenever possible. Easy to contribute, decentralized but with the possibility to leverage existing stuff like Github to reduce transaction cost for now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-23/422058362675_dc3e307b6e9052d90b4c_72.jpg" /><div class="message"><div class="username">kim196</div><div class="time">2018-04-30 13:51</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-04-30 13:51</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-04-30 13:51</div><div class="msg">I agree, and formats like markdown have pretty much a flat learning curve so it would lower the entry point for anyone</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-04-30 13:52</div><div class="msg">Also makes it easier to change way of hosting such documentation easily if need be</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-30 13:56</div><div class="msg">so far, I find the prolific use of gdocs a bit problematic. if we're an privacy sensitive open-first shop, gdocs's access restriction settings are annoying at best and prohibitive to outside collaborators. one way to solve that dilemma would be to _only_ use gdocs for the secret stuff.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-30 13:56</div><div class="msg">I imagine that most tech docs for example are actually not that secret</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-04-30 14:00</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-04-30 14:41</div><div class="msg">I think gdocs is ok for the live collaboration aspect. for the infancy of a document, but it should be moved to the repos asap.
|
|
Regarding the way to change the hosting as easelily as possible I don't see how it can be made easier that with repos that can be cloned easily</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-30 14:43</div><div class="msg">I've been experimenting with hackmd lately for that purpose, which has the added benefit of being in markdown already, making the move-to-repo step much easier</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-04-30 16:50</div><div class="msg">Okay, I have uploaded the build folder to <a href="https://github.com/status-im/docs">https://github.com/status-im/docs</a>.
|
|
|
|
The index.html file is there, as are the .md files whose content I want to mock-publish.
|
|
|
|
That?s not enough, though. GHP does not just automatically transform all that into a website. :slightly_smiling_face:
|
|
|
|
The expected result is as shown in capture1 (<a href="https://github.com/status-im/docs/blob/master/build/test-site/Capture1.JPG">https://github.com/status-im/docs/blob/master/build/test-site/Capture1.JPG</a>) and capture2 (<a href="https://github.com/status-im/docs/blob/master/build/test-site/Capture2.JPG">https://github.com/status-im/docs/blob/master/build/test-site/Capture2.JPG</a>). Clicking the NIM button on the page shown in capture1 would get the user to the page shown in capture2.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 02:14</div><div class="msg">hm, where is the source code?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 02:16</div><div class="msg">I also don't quite understand why are definitely going with Docusaurus, has it been established this is the best solution for all our needs? we started a discussion above. Maybe we can save time if we consider, or at least make explicit, what type of solution we need?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 02:17</div><div class="msg">I'm sure it is great, I just don't see rationale or trade-offs vs other solutions having been discussed anywhere</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 02:17</div><div class="msg"><a href="https://docusaurus.io/blog/2017/12/14/introducing-docusaurus.html">https://docusaurus.io/blog/2017/12/14/introducing-docusaurus.html</a> according to this doc `docusaurus-init` should result in a folder structure of markdown files</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 02:19</div><div class="msg">aside from the readme I don't see any markdown files in that repo</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:35</div><div class="msg">saw some discussion in the google doc</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:44</div><div class="msg"><a href="https://github.com/facebook/Docusaurus/blob/master/docs/getting-started-publishing.md#using-github-pages">https://github.com/facebook/Docusaurus/blob/master/docs/getting-started-publishing.md#using-github-pages</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:44</div><div class="msg">didn't run whole setup but it should probably look something like this <a href="https://github.com/oskarth/hello-docusaurus">https://github.com/oskarth/hello-docusaurus</a> (+ config stuff and whatever else that gh publish does)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 03:47</div><div class="msg">I gave Docusaurus a try because several people had mentioned it in Slack. That was before a formal discussion started in #documentation. I am not in any way expressing my preference for it.
|
|
|
|
The markdown files are all in <a href="https://github.com/status-im/docs/tree/master/build/test-site/docs">https://github.com/status-im/docs/tree/master/build/test-site/docs</a>. The folder also contains a few Docusaurus .md files. I could not delete them without altering the page in capture2 (e.g., the sidebar would go away). Why that kept happening? I have never found an answer in the instructions.
|
|
|
|
<a href="https://docusaurus.io/blog/2017/12/14/introducing-docusaurus.html">https://docusaurus.io/blog/2017/12/14/introducing-docusaurus.html</a> looks like an overview or intro. The actual setup steps I used start here: <a href="https://docusaurus.io/docs/en/installation.html">https://docusaurus.io/docs/en/installation.html</a>. I went up to `Building Static HTML Pages`, here <a href="https://docusaurus.io/docs/en/publishing.html">https://docusaurus.io/docs/en/publishing.html</a>
|
|
|
|
According to the instructions on that page, a `build` folder is all I need: ?generate a build folder inside the website directory containing the .html files from all of your docs and other pages included in pages?.
|
|
|
|
I don't know where Docusaurus stores the source code. If you like, I can send you the `website` folder, which includes everything. That folder is about 50 MB.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:51</div><div class="msg">by source code I mean `.md` markdown files that people edit - <a href="https://github.com/status-im/docs/tree/master/build/test-site/docs">https://github.com/status-im/docs/tree/master/build/test-site/docs</a> looks like it is just artifacts (html files)?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:52</div><div class="msg">so as far as I understand it the `build` folder is just the artifact that GH pages might use for rendering HTML</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 03:53</div><div class="msg">Yes, I think so</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:54</div><div class="msg">so we want to store the markdown in git so people can edit it right</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:54</div><div class="msg">and then we also want to render the HTML using GH pages right now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:57</div><div class="msg"><a href="https://github.com/status-im/docs/commits/master">https://github.com/status-im/docs/commits/master</a> also a bit confused by this - are you uploading the files somehow? as opposed to using git and committing changes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 03:59</div><div class="msg">aside from the markdown files the repo also needs siteConfig.js etc</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:02</div><div class="msg">The only time I used MD files with Docusaurus was to store our API documentation. I did not use MD files to edit code as part of building this test site. I ran a few commands from the command line, then modified some .json and .js files to change a few buttons and to add content to the sidebar.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:04</div><div class="msg">So we want anyone to be able to write documentation and customize things right? This means the markdown files have to be easily accessible, which means via source control, i.e git. Anyone should be able to do `git clone <REPO>` and change things. Right now all that's in repo is the artifact of the build process, so it's missing the actual meat</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:04</div><div class="msg">The instructions don't go into siteConfig.js and other things, at least not at the point I stopped (and that should be enough, as far as I understand)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:06</div><div class="msg">Yes, it should be as easy as you described :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:06</div><div class="msg">have you used git much before?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:06</div><div class="msg">Yep</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:07</div><div class="msg">Why? The problem is not with that.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:07</div><div class="msg">ok, so you should be able to make <a href="https://github.com/status-im/docs">https://github.com/status-im/docs</a> look like your current folder structure right</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:07</div><div class="msg">well, the code isn't in that repo :smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:07</div><div class="msg">It's with making GH Pages create a site</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:07</div><div class="msg">it's both for source code and hosting artifact</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:08</div><div class="msg">but step 1 is to actually capture the source code</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:08</div><div class="msg">there should be no need to "send zip files", this is what git is for</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:08</div><div class="msg">right now I don't know the state of your json or js config, so it's impossible to debug like this</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:09</div><div class="msg">Just following whatever GH Pages and Docusaurus told me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:09</div><div class="msg">There was no zip involved</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:09</div><div class="msg">I uploaded `build`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:10</div><div class="msg"><a href="https://github.com/status-im/ideas/">https://github.com/status-im/ideas/</a> this is an example of a static site</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:10</div><div class="msg"><a href="https://github.com/status-im/ideas/blob/master/_config.yml">https://github.com/status-im/ideas/blob/master/_config.yml</a> it has a config file</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:10</div><div class="msg">anyone can clone it, edit markdown, run the site locally, whatever</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:10</div><div class="msg">it is also configured, with the help of config.yml and GH in general, to serve HTML artifacts at <a href="http://ideas.status.im/">http://ideas.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:10</div><div class="msg">right now <a href="https://github.com/status-im/docs">https://github.com/status-im/docs</a> doesn't include anything but artifacts, this is wrong, the first step is to fix this and make sure it actually has everything needed to run this setup</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:11</div><div class="msg">once that's done we can figure out what needs to be done in terms of getting the HTML to render, and according to <a href="https://github.com/facebook/Docusaurus/blob/master/docs/getting-started-publishing.md#using-github-pages">https://github.com/facebook/Docusaurus/blob/master/docs/getting-started-publishing.md#using-github-pages</a> this involves siteConfig.js and some node script</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:13</div><div class="msg">again, all that goes well beyond what's in the instructions I have used, and it's not something I'd know how to do right now.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:17</div><div class="msg">Okay, I see now, yes. I did not go that far</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:18</div><div class="msg">I just followed some tutorial and googled for gh pages, it doesn't render yet but it looks roughly correct</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:18</div><div class="msg">It's something I'll try, but probably not today</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:18</div><div class="msg"><a href="https://github.com/oskarth/hello-docusaurus">https://github.com/oskarth/hello-docusaurus</a> code</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:18</div><div class="msg"><a href="https://github.com/oskarth/hello-docusaurus/tree/gh-pages">https://github.com/oskarth/hello-docusaurus/tree/gh-pages</a> artifacts</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:18</div><div class="msg">`> #GIT_USER=oskarth CURRENT_BRANCH=master USE_SSH=true npm run publish-gh-pages`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:20</div><div class="msg"><a href="https://oskarth.github.io/hello-docusaurus/index.html">https://oskarth.github.io/hello-docusaurus/index.html</a> some relative url or whatever but basic works</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:21</div><div class="msg">shouldn't be too much work to get it setup, if you get stuck I can do it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:22</div><div class="msg">Okay, I'll try it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:25</div><div class="msg"><a href="https://github.com/oskarth/hello-docusaurus/commit/bfd9877ca0d0a63d553bc02c5131a36a2f7f94b0">https://github.com/oskarth/hello-docusaurus/commit/bfd9877ca0d0a63d553bc02c5131a36a2f7f94b0</a> something like this is necessary, also changing so it publishes from `gh-pages` branch as this is what the `publish-gh-pages` script seems to expect</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:25</div><div class="msg">actually I can't do it until it exists, so ping and I can set it up</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:28</div><div class="msg"><a href="https://oskarth.github.io/hello-docusaurus/">https://oskarth.github.io/hello-docusaurus/</a> here it is, so this works fine generally speaking, just make sure master branch and gh-pages branch (automatically generated through docusaurus gh publish script) look similar in structure, once this is done we can change GH pages branch target to use gh-pages branch instead of master branch. Does this make sense?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 04:29</div><div class="msg">It will :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 04:35</div><div class="msg">kk great</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 05:17</div><div class="msg">Okay, I pushed siteConfig.js to <a href="https://github.com/status-im/docs/tree/master/build/test-site">https://github.com/status-im/docs/tree/master/build/test-site</a> and tried to modify it by following your suit</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 05:17</div><div class="msg">Not working</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 05:19</div><div class="msg">Could you check my changes on lines 24, 25, and 32?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 05:35</div><div class="msg">the structure of this <a href="https://github.com/status-im/docs">https://github.com/status-im/docs</a> looks very different from my repo, also no gh-pages branch</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 05:36</div><div class="msg">maybe easier to start from scratch? not sure what your folder structure looks like tbh</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-01 05:36</div><div class="msg">have to go afk for a while now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 05:37</div><div class="msg">Okay, I'll give it another shot</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-01 12:58</div><div class="msg">Added a table: Where we store our docs now, and how that will change</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-03 09:49</div><div class="msg"><!here> is there any argument against using GitHub Pages/Jekyll for our docs? Static, free, easy-to-use (md). Indexable, with version control. Integrated with our codebase, same work flow. There are some usage limitations?sites no larger than 1 GB, limit of 10 builds per hour, etc.
|
|
|
|
The most compelling alternative imo is <a href="http://readme.io">http://readme.io</a>, which has a GUI and supports live examples, but is not free and requires registration to contribute.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-05-03 10:13</div><div class="msg">So far no experience with this combination but often heard positives about it. Markdown and versioning always sound good to me. Only the dependency to GitHub (already have enough). That's why I like similar working self-hosted solutions like with Hugo.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 10:45</div><div class="msg">@rachel Are you familiar with <a href="https://www.gatsbyjs.org/">https://www.gatsbyjs.org/</a> ? Similar to jekyll but much more extensible</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 10:45</div><div class="msg">Also combines nicely with <a href="https://www.netlifycms.org/">https://www.netlifycms.org/</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 10:51</div><div class="msg">@themue If you have a bunch of html files you can host anywhere, not only github</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-05-03 10:53</div><div class="msg">@jeluard So GitHub Pages/Jekyll is only for raw docs/templates and workflow but target can be chosen? Eg push via WebDAV? Nice, didn't know.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-05-03 10:54</div><div class="msg">So far thought that the resulting HTML (and other artifacts) are also hosted on GH.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 10:55</div><div class="msg">Jekyll can be used standalone, like hugo. But GH has builtin support of jekyll so you can bypass the generation step and let GH handle it</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-05-03 10:57</div><div class="msg">And then push it - if wanted - to an own server? Or periodically pull the generated HTML?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 11:00</div><div class="msg">Right</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/b11645e09683360c0849df16c77e9980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">themue</div><div class="time">2018-05-03 11:01</div><div class="msg">Thx for the info.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-03 11:01</div><div class="msg">@martin487 has a tool to do that with AWS stack: <a href="https://github.com/confetti-clj/confetti">https://github.com/confetti-clj/confetti</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-03 11:01</div><div class="msg">^ @divan @arnetheduck.slack</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-05-03 11:21</div><div class="msg">I'm in support of this - both <a href="http://ethprize.io">http://ethprize.io</a> and <a href="http://artproject.io">http://artproject.io</a> are hosted directly through GH pages too</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-05-03 11:34</div><div class="msg">I can help provide a reproducible setup for static sites based on AWS but I'd suggest the following:
|
|
|
|
1. Use GitHub pages until it fails you
|
|
2. Try something like Netlify
|
|
3. Go full-blown AWS w/ S3/CloudFront</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-18/289102127286_0d00b7c17b8a24fd6f37_72.jpg" /><div class="message"><div class="username">zahary</div><div class="time">2018-05-03 11:43</div><div class="msg">Using markdown for documentation is a relatively fine solution, but what the specialized systems usually add on top of it are things like:
|
|
|
|
* search
|
|
* automatic generation of things like "table of contents", "Index", etc
|
|
* the possibility to package the documentation in other forms (books, dash docsets, etc)
|
|
|
|
If you are not familiar with Dash, this was a popular offline documentation viewer for macOS with a format that got picked up by several similar products for other OSes</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-01/308563433637_bac31bc179bd2f35cf1e_72.jpg" /><div class="message"><div class="username">martin487</div><div class="time">2018-05-03 11:43</div><div class="msg">If we plan on having lots of different sites option 3 might be preferable due to reproducible/automated setup.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-05-04 02:35</div><div class="msg">well, looks like there's no hard opposition to having markdown at the bottom layer at least :slightly_smiling_face: great format, low barrier of entry, easy to edit, possible to annotate with extras for the bells and whistles @zahary mentions and everyone else is using it already so lots of tooling both for viewing, editing and all that - fantastic for developers because there's no need to learn yet another format.. no particular opinion on which generator to use on top of that.
|
|
a quick look at the `dash` web site reveals that oddly, it doesn't support markdown even though it has a bunch of other source formats (corrections please!), not directly at least..
|
|
if we want to seek outside contributions (well, and broaden the base internally as well), might make sense to align ourselves with other notable projects in the space, and pick something beautiful, but not too unique and snowflaky - unless there's a jawdropping, absolutely awesome tool that comes with a champion white knight that will convince the masses and everyone here, it's a big ask to make people learn something new, given that doc generation isn't our core business
|
|
I would also check with @jakub to make sure it fits whatever infrastructure we're going prioritize so that we don't end up with too much fragmentation on the hosting side</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-04 09:21</div><div class="msg">Thanks for all the discussion, guys!
|
|
|
|
I'm impartial with regards to generator but @jeluard, Gatsby sounds nice - more powerful than Jekyll, react based.
|
|
|
|
@zahary brings up some good points in favor of a system, but would it be difficult to migrate content into something like readme if static sites proved too basic?
|
|
|
|
Great point @martin487 about the number of sites. Plan on starting minimally; Embark is using github pages too, we should be fine starting there.
|
|
|
|
That said, next step is to spec out a potential structure for our docs. We should do that by deciding what we want people to do with them - <a href="https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit?usp=sharing">https://docs.google.com/document/d/1-4dSomkxe6BDBYryyyCHubodkZOe08MpHbQ5nlHKiG0/edit?usp=sharing</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-18/289102127286_0d00b7c17b8a24fd6f37_72.jpg" /><div class="message"><div class="username">zahary</div><div class="time">2018-05-04 10:19</div><div class="msg">Besides Markdown, the only other popular format is RST (reStructuredText). There is a good write-up comparing them here:
|
|
<a href="http://www.zverovich.net/2016/06/16/rst-vs-markdown.html">http://www.zverovich.net/2016/06/16/rst-vs-markdown.html</a>
|
|
|
|
If I have to summarize, RST is a bit more tailored to producing documentation and it's usually paired with a documentation generator called Sphinx, which has a relatively well defined extensibility model (it's easy to define new types of objects such as diagrams, etc)
|
|
|
|
With Markdown, you usually end up creating SVG files when you want some custom graphics, but being in this mindset enables you to create almost anything. The advantages of Markdown are that it's more widely known by the average developer/contributor and its simplicity works a bit better with Github readme files and wiki pages (A well-structured RST documentation will usually take advantage of things like include files, which are not visualized properly in Github)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-18/289102127286_0d00b7c17b8a24fd6f37_72.jpg" /><div class="message"><div class="username">zahary</div><div class="time">2018-05-04 10:20</div><div class="msg"><a href="http://ASP.NET">http://ASP.NET</a> is a high-profile project that switched from RST to Markdown recently:
|
|
<a href="https://github.com/aspnet/Docs">https://github.com/aspnet/Docs</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-18/289102127286_0d00b7c17b8a24fd6f37_72.jpg" /><div class="message"><div class="username">zahary</div><div class="time">2018-05-04 10:22</div><div class="msg">@arnetheduck.slack, it should be possible to create Dash docsets from Markdown too. Usually, the same system producing the searchable database and index file should be responsible for this, but I'm also able to find some low-level tools such as:
|
|
<a href="https://www.npmjs.com/package/dash-docset-generator">https://www.npmjs.com/package/dash-docset-generator</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-05-04 12:31</div><div class="msg">@zahary ah great - I was looking at <a href="https://kapeli.com/docsets">https://kapeli.com/docsets</a> where weirdly, it's missing</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-04 12:53</div><div class="msg">Switching tracks from system discussions, it would be awesome if we could map out a high-level view of everything that we need to document (that we know of). Something like this: <a href="https://developer.atlassian.com/docs/">https://developer.atlassian.com/docs/</a> -- @jeluard @arnetheduck.slack @themue @andrey @oskarth maybe this is something you could help with?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-05-16 06:39</div><div class="msg">doh - opened the wiki and typed a search term in the big white box in the middle.. turns out it was "create page" and not "search" :open_mouth:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-05-16 09:29</div><div class="msg">happened to me as well a few times</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-05-22 17:19</div><div class="msg">worth seeing these designs @alexmandel <a href="https://cl.ly/232R0u232r43">https://cl.ly/232R0u232r43</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-22 17:40</div><div class="msg">Thanks @cryptowanderer. Looks good and is worth considering. I can't find the company's website though, where I could click through the documentation tree. ...Unless that was only a design for now.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-05-22 17:43</div><div class="msg">only a design, it's these guys though: <a href="https://balance.io/">https://balance.io/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-22 17:49</div><div class="msg">ah, okay</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-02/293014428163_b01bcf59624d5102f799_72.jpg" /><div class="message"><div class="username">vitaliy</div><div class="time">2018-05-28 10:06</div><div class="msg">Hi guys, is there some kind of ?Beginner gripes? document for status-react mobile? Similar in nature to <a href="https://github.com/status-im/react-native-desktop/wiki/Dev-troubleshooting">https://github.com/status-im/react-native-desktop/wiki/Dev-troubleshooting</a> for desktop version</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-05-29 21:40</div><div class="msg">Is there an update on where we are regarding documentation? i.e. moving away from wiki into a new platform?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-30 06:48</div><div class="msg">Thanks for the nudge?based on previous discussions I think we can start with a static site hosted on GH pages, similar to Embark. @alexmandel maybe we can work together to review the wiki content, and see what can be migrated to a new site. This work can live under DApp/Dev team, but I think we may need addtl support. Swarm?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-30 14:24</div><div class="msg">Yeah, I like what Embark have done, and moving to GH seems like a viable option, so reviewing Wiki content would be a good first step. Are you aware of anyone expressing concerns over GH?s usage limitations?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-05-30 15:03</div><div class="msg">Nothing im aware of</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-15/346893164260_0a370a8a1614301a6877_72.jpg" /><div class="message"><div class="username">alexmandel</div><div class="time">2018-05-30 15:16</div><div class="msg">Okay, thanks</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-31 13:25</div><div class="msg"><!here> Embark is setting a really great example with documentation and I'd love to get the wiki content up to par.
|
|
|
|
We already have some traction, as @andmironov is working on a site for our design guides right now. We can borrow those designs for our global docs when they're ready.
|
|
|
|
In the meantime, we should review the wiki content to decide what's irrelevant, what can be updated, what's missing, etc. For the site itself we can host on gh pages and use a generator like <a href="https://hexo.io/">https://hexo.io/</a> (used by Embark) or <a href="https://www.gatsbyjs.org/">https://www.gatsbyjs.org/</a> (Andrei will likely use).
|
|
|
|
I've set up a swarm for this - <a href="https://github.com/status-im/ideas/pull/274">https://github.com/status-im/ideas/pull/274</a> - and to get started we need 1-2 technical team members who can review the wiki. Any feedback on this idea?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 13:26</div><div class="msg">hey folks, i?ll be using `Gatsby.js` for the design docs so i?ll be setting it up and theming it so that the the theme could be reused for the global docs website</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-05-31 13:28</div><div class="msg">cc @iuri because it will make sense for us to discuss content architecture for global docs, embark, and other projects</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 13:28</div><div class="msg">already started working on it at the beginning of the week, have a few mockups and setting up Gatsby at the moment, will be finished in ~week, will provide updates next Thursday</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 13:44</div><div class="msg">maybe there are some technical details/suggestions i should know? for example, i noticed there?s a way to use `markdown` files to create pages. Using Markdown might be useful to simplify the external contribution to the docs</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 13:44</div><div class="msg">@jeluard i believe you can provide some insight on this</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 13:46</div><div class="msg">although markdown is great for text-only content, but might not work great for complex pages with code embeds etc.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-31 14:06</div><div class="msg">Awesome I was considering it for the first iteration of extensions docs. Do you have a specific layout in mind?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-05-31 14:08</div><div class="msg">Markdown sounds perfectly fine to me. It works great for tech documentation and you can always embed html for complex cases.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 15:05</div><div class="msg">yep, i have a draft mockup,a regular one with a sidebar as nav</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-05-31 15:05</div><div class="msg">:+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-05-31 17:40</div><div class="msg">Tbh I thought this was Alex's responsibility, but seems not?
|
|
|
|
More than happy to help seeing as I wrote a lot of that original, outdated stuff.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-01 12:32</div><div class="msg">Would be fantastic to have your help @cryptowanderer. I just want to move it forward by whatever means necessary, but @alexmandel and I are going to do an initial audit of the wiki content today.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-01 12:49</div><div class="msg">ok cool - how can I help with that? Do I need to hop on a call or something?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-01 15:02</div><div class="msg">@cryptowanderer what do you think about going through the wiki page-by-page and marking content as `irrelevant`, `needs updating` or `up-to-date`? Sounds like a lot of it falls in the first camp and we can probably cut whole pages. I'm happy to talk through it on a call but you'll probably want to take a first pass on your own, right?
|
|
|
|
@alexmandel will help to gather a list of any readmes that might have relevant content to *add* from our github repos.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-02 10:21</div><div class="msg">yeah, can do. Have some other stuff I want to get through this weekend, but will start on Monday morning.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-02 17:11</div><div class="msg">Aragon's new developer portal is a great reference: <a href="https://hack.aragon.org/">https://hack.aragon.org/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-02 17:12</div><div class="msg">BIG thank you Andy! That will be really amazing.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-04 17:25</div><div class="msg">@rachel still going through the wiki to review things. Have done everything in the first 2 tabs (barring some questions to some relevant people).
|
|
|
|
I think the `Status Culture` stuff is a) out of date, b) all better suited to living on the main website with the coming refresh (cc @jonny.z) and c) it's good in general to have separate (but linked) places for vision and mission stuff and technical docs.
|
|
|
|
I think the `Status Go` stuff is likely relevant and maybe still fairly up to date, but needs to be completely overhauled and is presented in a readbale and easily digestible way, not with crazy links all over the place.
|
|
|
|
Will move on to the left sidebar soon :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-04 18:00</div><div class="msg">Everything under Status Organization needs to live elsewhere, either on the community/marketing page on the web refresh or as a part of the people handbook and with peopleops stuff.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-04 18:01</div><div class="msg">What do you mean?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-04 18:01</div><div class="msg">?Status Organization??</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-05 06:53</div><div class="msg">Agreed. It's all about our hiring processes and culture @oskarth. The referral program definitely lives with peopleops. Hiring process can live on hiring site/peopleops. Not sure about the launch content but I don't think it belongs with our technical docs either?more internal wiki or handbook.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-05 06:54</div><div class="msg">Amazing. THANKS ANDY! How are you tracking your suggestions? Agreed on Culture and Status Go?we can talk about the latter as part of the global dev picture on our call today.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-05 08:26</div><div class="msg">They are in the wiki on the top of each page and here :wink: Not such an active channel, so we should be good plus it will motivate us even more to get it done before we lose this thread!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-05 08:27</div><div class="msg">Left hand menu Oskar - it's one of the sub headings there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-05 10:11</div><div class="msg">I aspire to be a left handed Mensch, not a menu thank you very much</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-05 12:52</div><div class="msg">@iuri @jeluard @cryptowanderer here's a quick outline for our call in a few minutes: <a href="https://docs.google.com/document/d/1a9sF-sERC7JiwTtoklR6KwsV6j29EyiZtCGSnv67eRg/edit?usp=sharing">https://docs.google.com/document/d/1a9sF-sERC7JiwTtoklR6KwsV6j29EyiZtCGSnv67eRg/edit?usp=sharing</a>
|
|
|
|
It would be great to talk through the big picture of our developer tools, and then figure out opportunities for the Embark and DApps/Developers teams to work together.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 10:33</div><div class="msg"><a href="https://github.com/status-im/status-react/issues/2934#issuecomment-355803964">https://github.com/status-im/status-react/issues/2934#issuecomment-355803964</a> what do people think?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 10:34</div><div class="msg">@yenda thoughts?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-06-11 10:39</div><div class="msg">I'm not against it :sweat_smile:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-06-11 10:39</div><div class="msg">I can work on that later this week</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 10:41</div><div class="msg">No I mean the persons reply </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 10:41</div><div class="msg">Because we moved things around since that bounty IIRC?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-06-11 10:42</div><div class="msg">yeah it was even before the refactoring of the protocol, and the protocol namespaces are already much more documented than the rest of the code (but can still be improved)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 10:44</div><div class="msg">So you know current state better than me, what do you think we should reply to that person? Do you want to comment on GHI?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-06-11 10:56</div><div class="msg">I'm rather curious how someone who is not familiar with the whole codebase could effectively document it</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/fcc4675bd0ade27de9baefb82098e500.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0002-72.png" /><div class="message"><div class="username">yenda</div><div class="time">2018-06-11 10:58</div><div class="msg">Maybe we can just ask him if he find anything to add to it and eventually extend the scope to utils namespaces as well ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-11 11:12</div><div class="msg">sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-12 06:01</div><div class="msg">@jakub how are we doing with Discourse set up?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 06:02</div><div class="msg">Still eating for Nabil to upgrade our MailGun account</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-12 06:06</div><div class="msg">gahd damn Nabil :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 06:40</div><div class="msg">you should get an invite</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-12 07:30</div><div class="msg">@jakub cool, got the invite. How do i create new categories and generally go about setting things up?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 07:32</div><div class="msg">just gave you admin rights</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 07:32</div><div class="msg">I assume it's gonna be somewhere in Admin >> Settings</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 07:34</div><div class="msg"><a href="https://discuss.status.im/categories">https://discuss.status.im/categories</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 07:34</div><div class="msg">right button dropdown</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 07:34</div><div class="msg">"New Category"</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-12 07:35</div><div class="msg">nice, thank you so much :heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 08:27</div><div class="msg">It might be worth updating things here too: <a href="https://discuss.status.im/admin/customize/site_texts?q=">https://discuss.status.im/admin/customize/site_texts?q=</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 08:27</div><div class="msg">same goes for <a href="https://discuss.status.im/admin/customize/email_templates">https://discuss.status.im/admin/customize/email_templates</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-06-12 08:27</div><div class="msg"><a href="https://discuss.status.im/admin/site_settings/category/trust">https://discuss.status.im/admin/site_settings/category/trust</a> - this might need review too</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-12 14:39</div><div class="msg">:wave::skin-tone-4:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-14 05:52</div><div class="msg"><a href="https://status-im.slack.com/archives/C8QP8S5UH/p1528923964000301">https://status-im.slack.com/archives/C8QP8S5UH/p1528923964000301</a> <-- just for reference in this channel</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 07:48</div><div class="msg">Hey @andmironov! How's the design doc site coming? @jeluard had a look into docusaurus and felt it might be an even better fit than Gatsby for the moment, as we could probably ship faster with it</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-18 07:54</div><div class="msg">Example of what it looks like: <a href="https://loomx.io/developers/docs/en/prereqs.html">https://loomx.io/developers/docs/en/prereqs.html</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-18 07:54</div><div class="msg">Pretty much nothing to do but writing markdown files</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-06-18 07:58</div><div class="msg">cool, yeah, the gatsby site setup and customization appeared to me not that easy (for me) and it slowed me down to be honest, so i?ll be happy to help @jeluard with customizing and theming up the site on docusaurus</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 08:06</div><div class="msg">Excellent. We'll go with it then.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-18 09:37</div><div class="msg">yay! Let's get moving on this :cattyping: Happy to help this week and lead the charge if your focus is DApps specifically @rachel</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 15:13</div><div class="msg">That'd be awesome @cryptowanderer. @alwx?s improvements to `Build Status` look great. I could also improve `Add your DApp to Status` with some more incentive for developers to use our Status web3 method, links to logos, etc. We could spin up a site with just that material to start. wdyt?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 15:16</div><div class="msg">@jeluard wdyt would be the best mechanism for collecting feedback? I would love for people to be able to submit feedback while on site</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 15:17</div><div class="msg">Example from Square</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-18 15:17</div><div class="msg">Yeah, sounds good to me. Let's focus on getting that right and then I will add the rest of what needs to come across from the wiki in (i.e. some testing stuff, and a few other odds and ends). Are those improvements on the wiki already?
|
|
Also, when can we hope for a simple design for docusaurus @andmironov - I know you have a bunch of other things going on. So maybe we start to populate content on a bare bones instance so as to parallelize things...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-18 15:21</div><div class="msg">Yeah, seems like a fair start. Wdyt about also having a link:
|
|
`Have an in-depth question not answered here? Create it on Kauri and we'll put a bounty on it` or do we not want to go there? We could also say `ask it on <a href="http://discuss.status.im">http://discuss.status.im</a> and we'll create an Open Bounty for more documentation` if we want to keep things more local :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 15:22</div><div class="msg">_what's Kauri?_ :flushed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-18 15:23</div><div class="msg">something like that would be cool short-term, but in my experience, people drop off immediately when they can't leave feedback in context. although our community is already weighing in on developer business on riot, so let's make that an option :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-18 15:28</div><div class="msg">It's a bounty platform for documentation we looked at a while ago... Sgtm otherwise :+1:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-18 15:40</div><div class="msg">Great idea! We definitely need something like that</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-06-18 19:12</div><div class="msg">for sure, i guess it would be even better this way since it will make it more clear how it should look like!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-19 07:06</div><div class="msg">@patrick771 for getting feedback on the site</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 07:41</div><div class="msg">No other improvements to the wiki yet, @cryptowanderer. I think if we get that Build Status quickstart into better shape and feature it on a nice new site, we'll encourage contribution on the other material.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-19 07:48</div><div class="msg">yeah I'm with you. Where are the improvements you mentioned earlier in this thread?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 07:49</div><div class="msg">This gist from Alex?good start: <a href="https://gist.github.com/alwx/ee41d5bf972cd224e5e666b18eef2953">https://gist.github.com/alwx/ee41d5bf972cd224e5e666b18eef2953</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-19 07:53</div><div class="msg">So, it's only for OSX, there are some unnecessary steps there (around nvm for eg which is nice, but will need clearer explanantion), it assumes genymotion later down in the script. What if I want to build with the Android SDK and free emulator on a Linux machine?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-19 07:55</div><div class="msg">You see, the problem with the build instructions in general is that
|
|
|
|
a) There are SO many different ways to do it, and so many different tools, emulators, SDKs and NDKs that people use for mobile dev
|
|
b) Our codebase is complicated and Clojure tooling in general is pretty tough to get used to
|
|
|
|
Making it easy to follow is going to be significantly more challenging that a gist which just rehashes what is in the wiki already :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-19 08:40</div><div class="msg">I just looked at Instabug and it looks like they only are able to target mobile apps. Although am following up with support to see what?s possible with websites. I?m not up to speed on this thread. Would we be targeting a GH gist or whatever is built with docasaurus?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 08:41</div><div class="msg">Docusaurus @patrick771 :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-19 08:42</div><div class="msg">ok, so would we hosting static pages somewhere or pushing to GH?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 08:43</div><div class="msg">Yeah, not to say it's a finished doc by any means. We still need work on it! But it reads so much better already.
|
|
|
|
From:
|
|
```
|
|
Build and Run
|
|
Requirements
|
|
Note: You should be able to build all of the requirements by running the setup script:
|
|
$ scripts/setup
|
|
```
|
|
|
|
To:
|
|
```
|
|
Building Status on OS X
|
|
1. Install the dependencies
|
|
1.1. Node.js and npm
|
|
There are several ways of installing Node.js on your machine. One of the most convenient and easy is by using Node Version Manager (nvm).
|
|
|
|
Versions of both node and npm don't really matter, but there are known issues with some of them. In this manual we're going to install node v7.10.1 and npm 5.5.1, just because these versions are guaranteed to work.
|
|
```
|
|
|
|
The latter has the kind of format and exposition that we should aim for!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 08:44</div><div class="msg">Exactly, gh-pages to host</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-19 08:49</div><div class="msg">ok. mmm ? might be a tricky to trigger a contextual survey on gh-page. i?ll see if I can find any prior examples.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-19 09:05</div><div class="msg">Also, what were you thinking in terms of type of questions we?d like to ask?
|
|
- Was this page helpful?
|
|
- Did you find what you're looking for?
|
|
- In a few words, can you let us know what you're looking for [Open end text box + links <a href="http://discuss.status.im">http://discuss.status.im</a>]</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-19 09:24</div><div class="msg">Exactly?some combo of those. Would love an open-ended space for people to quickly vent their problems, if something was confusing or caused them to drop off. Pointing to <a href="http://discuss.status.im">http://discuss.status.im</a> is a fine solution if on-site collection isn't feasible right away</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-19 10:00</div><div class="msg">Did a little digging around and it's not clear how strict GH is with integrating with survey tools like surveypal or typeform (we have a Status shared account). So I've emailed GH support and will let you know if I find out anything this afternoon or tomorrow. Pointing to <a href="http://discuss.status.im">http://discuss.status.im</a> might be the right option atm.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-06-19 18:15</div><div class="msg">devs typically hang out at stackoverflow, no?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-20 07:11</div><div class="msg">Sounds right. Where you going with this?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-20 11:20</div><div class="msg">Hey @rachel do you have some time today to do a quick demo of the new site. It's ugly, and it needs some designer loving, but mostly functional at least...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-20 12:24</div><div class="msg">:clap::skin-tone-2: End of day some time work for you? Progress is great, no matter how ugly. </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-20 12:53</div><div class="msg">Sure, lmk when is best. 5pm here would be great</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-20 13:21</div><div class="msg">Same - sent you an invite</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-06-20 15:03</div><div class="msg">that it's a good place to monitor when doing devrel, and to send people to when they have unanswered questions</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-20 15:26</div><div class="msg">yup, 100%. It would be good to have a dev real team member on there daily.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-20 20:54</div><div class="msg">I saw it today. Very happy to see progress on this :heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-20 21:40</div><div class="msg">@andmironov would you like to join a call at 1pm tomorrow CEST to go over the bare bones docs site and see what can be done in terms of design, some images etc.?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 07:51</div><div class="msg">OK, so I think our call at 1pm CEST today should be a general demo of the docs so far. I have a website functioning and brief set of design notes that explain what I think would be awesome to see there. @andmironov would be really awesome if you can join:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 07:51</div><div class="msg"><a href="https://docs.google.com/document/d/1vMG-ZNbDeCcEzEAm52SqQxHmIpLGejf71FuwEsvbZ8w/edit?usp=sharing">https://docs.google.com/document/d/1vMG-ZNbDeCcEzEAm52SqQxHmIpLGejf71FuwEsvbZ8w/edit?usp=sharing</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-21 07:56</div><div class="msg">Big fan of the Joseph Campbell reference</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-21 08:56</div><div class="msg">Just to confirm. *This will replace our current <a href="http://wiki.status.im">http://wiki.status.im</a>*, correct?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-21 08:57</div><div class="msg">The one we should shut down ASAP is <a href="https://docs.status.im/">https://docs.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 08:57</div><div class="msg">yeah, and also <a href="http://docs.status.im">http://docs.status.im</a> - we should pick one and stick with it</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-21 08:58</div><div class="msg">Also some git repo we should hide / archive. Can you help with that?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 09:00</div><div class="msg"><a href="http://docs.status.im">http://docs.status.im</a> is already being served with GH pages, so it might be easier just to use that (I am working on a new branch in that repo) and sunset the wiki entirely. That way, no real added setup costs, just change the branch it is serving</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-21 09:00</div><div class="msg">I like that idea</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 09:00</div><div class="msg">Like I say, I think we should be using that repo seeing as it is all set up already, not hiding it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-21 09:00</div><div class="msg">Will we keep the wiki then?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 09:01</div><div class="msg">kill the wiki!!! :angry_trump:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-21 09:01</div><div class="msg">Yes ok great. Thank you! :raised_hands:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-06-21 09:01</div><div class="msg">I meant repos like <a href="https://github.com/status-im/truffle-box-status">https://github.com/status-im/truffle-box-status</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 09:02</div><div class="msg">fair point - @carl can we kill that repo?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 10:53</div><div class="msg">Gonna be five mins late for this call</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-21 11:30</div><div class="msg">OK, @andmironov and everyone else, the docs are here: <a href="https://github.com/status-im/docs.status.im/tree/NewSite">https://github.com/status-im/docs.status.im/tree/NewSite</a>
|
|
|
|
You need to:
|
|
|
|
```
|
|
git clone <a href="https://github.com/status-im/docs.status.im.git">https://github.com/status-im/docs.status.im.git</a>
|
|
cd <a href="http://docs.status.im">http://docs.status.im</a>
|
|
git checkout NewSite
|
|
cd website/
|
|
npm install
|
|
npm run start
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-21 11:37</div><div class="msg">Thanks!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-21 15:30</div><div class="msg">Archive or completely delete? I might just archive it and make it private</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-06-21 15:31</div><div class="msg">have archived and made it private :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-06-22 15:05</div><div class="msg">To follow up, GitHubs response:
|
|
```
|
|
Hey Patrick,
|
|
Pages doesn't support any server side processing which means it wouldn't be possible to implement a form.
|
|
```
|
|
So maybe we could link to a form? Not ideal but a workaround.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-22 15:48</div><div class="msg">Alright cool, thanks for digging into it @patrick771. Let's park this idea for now. Maybe we just direct people to channels like Github, Riot and Status itself to start.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-06-25 14:47</div><div class="msg">Is the . new docs site live somewhere? Would be great if we could point it to <a href="https://docs.status.im/">https://docs.status.im/</a> even if it isn't ready, as that old site isn't exactly ready either</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-26 07:05</div><div class="msg">@cryptowanderer @oskarth thoughts on this for a content structure starting out?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-26 09:32</div><div class="msg">Yeah, I'm happy with that if it's what you want. I don't really see why we wouldn't just put up everything I already have there (which I laboriously updated and edited, just for you :wink:)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-06-26 12:28</div><div class="msg">heeeyyy now! in fairness, I only asked for an audit. :slightly_smiling_face: I would rather have a small, easily navigable MVP with clean content</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-06-26 14:13</div><div class="msg">Sometimes not getting what you asked for is more exciting though :trollface: Happy for you to lead this though :+1:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-03 22:29</div><div class="msg">Do we have (or plan to have) step-by-step instructions for users that have existing wallets (both hardware and software) and want to try their account in Status? I.e. something that shows up on top of google search for "How to add my Trezor/Metamask/etc account in Status"?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-04 17:05</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-04 17:05</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-09/343509920658_ec01d8ba063ba939686b_72.jpg" /><div class="message"><div class="username">rob018</div><div class="time">2018-07-04 17:05</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-05-11/363235195815_bbe7d055e1883e756d9b_72.jpg" /><div class="message"><div class="username">maxr</div><div class="time">2018-07-04 17:05</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-07-04 17:05</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-04 17:07</div><div class="msg"><!here> slightly belated follow-up on the docs kick-off call yesterday :slightly_smiling_face:
|
|
|
|
We set a *goal date* of *Friday, July 20th* to have an *MVP of <a href="http://docs.status.im">http://docs.status.im</a>* live.
|
|
|
|
The MVP will be focused on a few core pieces of content?for *building Status* and *contributing to Status*?as well as some sort of *archive for the Wiki content*.
|
|
|
|
*Potential blocker* is *design*, with Andrei on vacation from the 6th.
|
|
|
|
We've made good progress on other fronts. Namely product fixes - see @alwx?s update in #core-developers.
|
|
|
|
Does *3 pm CEST* next *Thursday, July 12th* work for our *next call*?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-04 17:47</div><div class="msg">April?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-04 17:49</div><div class="msg">:thinking_face: that's an interesting one.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-09/343509920658_ec01d8ba063ba939686b_72.jpg" /><div class="message"><div class="username">rob018</div><div class="time">2018-07-05 15:29</div><div class="msg">any place we should update, place documentation while this is gaining steam prior to July 20th? :eyes:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-05 16:30</div><div class="msg">I mentioned it already in #core-developers, but not sure if you noticed: I cannot push to <a href="https://github.com/status-im/docs.status.im">https://github.com/status-im/docs.status.im</a>, would be nice if you give me rights to do this</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-05 16:45</div><div class="msg">Once you get access and while you are at it, WDYT about pushing docs more and testing with automated published on some public URL?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 06:34</div><div class="msg">@alwx I might have perms actually. Do you want to share your changes so that I can try?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-06 07:34</div><div class="msg">no, still can't</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 07:37</div><div class="msg">No but with me I mean. So that I can push them</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-06 07:50</div><div class="msg">oh, actually everything was okay, it's my git configuration on new machine :disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-06 07:50</div><div class="msg">very weird stuff, but I fixed it now, and can push</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 07:56</div><div class="msg">We are about to take down <a href="http://docs.status.im">http://docs.status.im</a> and bring <a href="http://docs-staging.status.im">http://docs-staging.status.im</a> up with the new content.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 07:56</div><div class="msg">Please yell now if you are against this change!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-06 08:10</div><div class="msg">All for it :+1:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 08:14</div><div class="msg">Hey @rob018 !</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 08:14</div><div class="msg">Yes please, here! <a href="https://github.com/status-im/docs.status.im">https://github.com/status-im/docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 08:16</div><div class="msg">Also will swap branches in <a href="https://github.com/status-im/docs.status.im">https://github.com/status-im/docs.status.im</a>
|
|
? develop -> OldSite
|
|
? NewSite -> develop</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 08:20</div><div class="msg">Done</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 09:01</div><div class="msg"><a href="https://docs-staging.status.im/">https://docs-staging.status.im/</a> :rocket:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-24/304281668629_99d09ae86c8e0a04b52d_72.png" /><div class="message"><div class="username">growbot</div><div class="time">2018-07-06 09:03</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-06 09:03</div><div class="msg">/kudos @jeluard!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-06 09:11</div><div class="msg">@denis-sharypin ^</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-07-06 09:12</div><div class="msg">dunno who made this illustration</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-06 09:13</div><div class="msg">i know you made some work on diagrams maybe this one can be reworked as well</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-06 09:13</div><div class="msg">idk</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-07-06 09:14</div><div class="msg">ah right</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-16/346978770624_9e34aabb0e7c70909e09_72.jpg" /><div class="message"><div class="username">denis-sharypin</div><div class="time">2018-07-06 09:14</div><div class="msg">thanks!</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 09:43</div><div class="msg">Who can give @jakub admin perms to the <a href="http://docs.status.im">http://docs.status.im</a> repo? He needs to do some ops magic! :magic:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 09:43</div><div class="msg">@oskarth?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 10:31</div><div class="msg">/kudos @jakub for providing content to our docs site! That might be the first time ever an ops writes doc! :mindblown:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-07-06 10:32</div><div class="msg">very funny =]</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-07-06 10:35</div><div class="msg">and as much as I appreciate the joke:
|
|
```
|
|
infra-hq% find ./ -iname 'README.md' | wc -l
|
|
15
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-09/343509920658_ec01d8ba063ba939686b_72.jpg" /><div class="message"><div class="username">rob018</div><div class="time">2018-07-06 12:00</div><div class="msg">oh great! thanks for this @jeluard!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-06 12:29</div><div class="msg"><a href="https://github.com/status-im/docs.status.im/pull/26">https://github.com/status-im/docs.status.im/pull/26</a>
|
|
@jeluard you just closed it, why?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 12:42</div><div class="msg">Sorry by mistake </div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-06 12:56</div><div class="msg">Apparently can't reopen :disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-07-06 16:00</div><div class="msg">ops? code? same sentence?? maybe he secretly outsourced it..</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-07 21:05</div><div class="msg">This is now done</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 07:46</div><div class="msg">Morning @alwx! I made some changes to the documentation structure (removed versions).
|
|
Could you re-create your PR?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-09 07:47</div><div class="msg">yes, sure</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 07:47</div><div class="msg">Also we have one person trying to build and having some issues. Maybe a great way to validate our new scripts?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-09 08:03</div><div class="msg">who is this person?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 08:04</div><div class="msg">Someone outside core team.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 08:41</div><div class="msg">@alwx He is in @dev-status-riot . Can you give him a hand?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 10:04</div><div class="msg">I understand @jakub has issues accessing the `settings` tab. For info in another repo I added `jakubgs` as Collaborator with `Admin` rights</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-09 10:14</div><div class="msg">That?s me :smile:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 10:18</div><div class="msg">lol</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 10:18</div><div class="msg">You use anonymous accounts to make sure we don't recognize you ? :joy:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-09 10:20</div><div class="msg">I don't know, maybe Siri was watching my struggles with build and decided to help? Modern AI is, you know, shows some signs of empathy :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-09 14:14</div><div class="msg">/kudos @jakub for improving the documentation automation! Now every changes to the docs repo will automatically get pushed live!</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-11 06:31</div><div class="msg">Morning @alwx! Could you take a look at the few comments in your doc PR: <a href="https://github.com/status-im/docs.status.im/pull/31">https://github.com/status-im/docs.status.im/pull/31</a> ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-11 07:55</div><div class="msg">ok</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-11 10:05</div><div class="msg">will finish this one today</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-11 10:05</div><div class="msg">and yarn story as well</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-11 12:29</div><div class="msg">Hey! I just did some improvements to the `status-react` setup process. Should I update the page in <a href="http://wiki.status.im">http://wiki.status.im</a> for the time being, or is someone working already on the new <a href="http://docs.status.im">http://docs.status.im</a> content and could adapt?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-11 12:39</div><div class="msg">Hey Pedro, that's great! I consider this file from Alex to be a good basis for the new docs (at least for OSX): <a href="https://github.com/status-im/docs.status.im/pull/31">https://github.com/status-im/docs.status.im/pull/31</a> - how significant are your changes? </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-11 12:39</div><div class="msg">I can help to adapt</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-11 12:42</div><div class="msg">ah good to now, I've started adding comments there. I'm trying not to make significant changes, but instead reduce the amount of documentation required by automating some things (in this case, I prepared the setup script to detect if the Android NDK is installed and install it if needed).</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-11 12:43</div><div class="msg">Perfect. That?s super helpful.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-11 15:27</div><div class="msg">thanks @pedro</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-12 13:06</div><div class="msg">Bounty waiting for approval: <a href="https://github.com/status-im/status-github-bot/issues/27">https://github.com/status-im/status-github-bot/issues/27</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-12 13:41</div><div class="msg">@alwx Do you think we could merge both linux ans osx build pages? There shouldn't be that much differences right?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 13:41</div><div class="msg">Ideally, there should be just one command
|
|
`make setup` or `scripts/setup`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 13:42</div><div class="msg">so system shouldn?t matter</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 13:42</div><div class="msg">it means you're right, we can merge these pages together</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-12 13:47</div><div class="msg">Cool! Could you do it as part of your current work? Like dropping the linux one, and renaming the osx one?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 13:47</div><div class="msg">yep</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-12 13:52</div><div class="msg">@rachel can you share that diagram, i would like to have a closer look at it :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-12 13:54</div><div class="msg">Sorry to come across as harsh, but I am really frustrated by the changes that have been made, and I would like to ask people here to reconsider our stance on what an MVP really means.
|
|
|
|
On a personal note first, we've been doing MVPs for a year now and I am sick of them.
|
|
|
|
On a professional note, I just don't buy the sole focus on 'building status', because that is not the only focus of our technical community. We have these great docs on testing - why are they excluded? We have these great docs on SOB, which is a most important funnel for developers, why are they excluded? (I know we'll work them back in, still making a point though)
|
|
|
|
We have these great docs on the research we're doing - if they don't live with our technical docs, where do they live, and how quickly can we get it up? Jarrad et al have BEEN asking for more viz for Nimbus for nearly 2 months now.
|
|
|
|
Yeah, maybe we eventually have separate sites for testing and research in particular, but top level navigation here to their own separate pages with separate sidebars is a definite win, and a definitely interesting thing for the technical community, who are the people I feel this is aimed at, not just those developers capable of actually building Status, which is very, very few. Why would we limit ourselves to that subset, even for yet another "MVP"?
|
|
|
|
I know, from many past experiences here, that it's all well and good to speak about information architectures and assign leads to handle content generation, but it just does not happen. Sorry to be cynical, but I do really think that this is maybe the one time when experience in Status actually might count a bit. This is exactly why I spent so much of my time combing through the wiki, marking relevant content and then pulling that across and editing it so it is as up to date as I can make it. While I subscribe to Goran's view that the day I become attached to a piece of code I write is the day I sell everything I own and take up goat farming, I do feel strongly that having as much content on the docs site as we can (arranged sensibly) is the way to go here, because it provides a solid basis from which to encourage other work and doesn't leave developers feeling like they have to build out an empty skeleton. There's already a bunch of stuff there and they just occasionally have to make sure it is up-to-date and reflects all the latest and most awesome things.
|
|
|
|
</rant></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-12 14:09</div><div class="msg">btw `technikon` comes from the Greek, and is the noun use of the neuter of `tekhnikos`, meaning ?relating to skills?.
|
|
|
|
This site ought to be all about teaching, discovering and sharing the skillz to build a new web. I want to see interactive content and tutorials here one day, I want channels linked directly to #social-coding channels in Status itself so you can ask another community member for help as you're working through stuff (and then tip them for it directly in the chat!!). I want our Education people (coming soon) to be a big part of it, and use it as their base for the amazing work they end up doing. I want to see Status Studio/an interactive fiddle directly integrated into it.
|
|
|
|
The technikon is the hub where we teach how to take part in a new kind of social narrative; it is a place for dialogue aimed at co-discovering what web3 is really all about, and the MVP needs to reflect that, not just be about building Status, which maybe 500 people in the world can actually do themselves (with maybe a couple 1000 more that might want to. But we want audiences much bigger than just 1000s).</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-12 14:14</div><div class="msg">MVP is just a pragmatic way of bootstrapping tech things and making sure new content can be pushed seamlessly.
|
|
Have it live ASAP by nailing a very specific set of priority content.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-12 14:15</div><div class="msg">>We have these great docs on testing - why are they excluded? We have these great docs on SOB, which is a most important funnel for developers, why are they excluded?
|
|
|
|
> We have these great docs on the research we're doing - if they don't live with our technical docs, where do they live, and how quickly can we get it up?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-12 14:15</div><div class="msg">Nothing that precludes any of what you list.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-12 14:16</div><div class="msg">Maybe too much has been removed. Can be re-added pretty quick.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-12 16:43</div><div class="msg">> On a personal note first, we've been doing MVPs for a year now and I am sick of them.
|
|
|
|
Although I understand your sentiment, I hope we never stop shipping MVPs and moving quickly.
|
|
|
|
We can't ship the perfect education platform for all of web3 by next week, but we can offer a very good guide to building Status.
|
|
|
|
>> the MVP needs to reflect that, not just be about building Status, which maybe 500 people in the world can actually do themselves (with maybe a couple 1000 more that might want to
|
|
|
|
Isn't it one of our principles to make it as easy as possible for anyone to build Status? Although it may be only 500 people who can do so now, I wouldn't discount that as a critical objective to making our platform accessible and inclusive, and ensuring continuance.
|
|
|
|
>> We have these great docs on the research we're doing - if they don't live with our technical docs, where do they live, and how quickly can we get it up? Jarrad et al have BEEN asking for more viz for Nimbus for nearly 2 months now.
|
|
|
|
Developers want to build shit. Docs need to be to the point and help them accomplish something. The more content we add just because it exists, without thinking about how it is meant to be used, by whom, in what context, the less appealing our docs will become.
|
|
|
|
I'm not up-to-date on Nimbus, but that's why putting together a comprehensive view of our tech is important?so we can decide how each piece of it helps developers, and present the right information in the right place.
|
|
|
|
>> I know, from many past experiences here, that it's all well and good to speak about information architectures and assign leads to handle content generation, but it just does not happen.
|
|
|
|
Let's see how the Docusaurus workflow works for people once we have something live. To Julien's point, it's easy to add existing content to the site once we've validated that that is indeed what we want to do.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-12 19:12</div><div class="msg">OK cool, thanks for engaging @rachel. I feel like I probably woke up on the wrong side of my bed this morning, and - having now had my say - am feeling much more relaxed about it all. Also, I love and trust you guys, so that counts for a lot too and I do actually agree with most of the above. Maybe Nimbus in particular needs to live elsewhere, though I am still unsure where that is. Sure we can figure it out together :heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 21:59</div><div class="msg">@pedro I missed it completely, but I don't understand why it was merged: <a href="https://github.com/status-im/status-react/pull/5126/files">https://github.com/status-im/status-react/pull/5126/files</a>
|
|
It installs Android NDK, but it's better to just execute `brew install android-ndk` on Mac, isn't it? Also, this script doesn?t add `export ANDROID_NDK='<path>'` to env</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-12 22:26</div><div class="msg">:tada: The docs were updated (<a href="https://github.com/status-im/docs.status.im/pull/31">https://github.com/status-im/docs.status.im/pull/31</a>). I also extended the Android section and made the doc universal (for both Mac and Linux).</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-13 05:51</div><div class="msg">I don't have a Mac or experience developing on it, so I asked @dmitryn to test the script for me. The way the script is handling the path is to add ndk.dir to local.properties, to avoid relying on environment variables and having to change and reload ~/.profile for instance. If we can detect where the NDK gets installed with brew, then it should be easy to adapt the script.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-13 05:59</div><div class="msg">Looking at the documentation, I'm not sure why the script isn't installing the android sdk on Linux, if indeed it can be installed with apt-get</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-13 06:39</div><div class="msg">@andrey set the channel topic: <a href="http://docs-staging.status.im">http://docs-staging.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-13 06:42</div><div class="msg">We won't let any of it drop :slightly_smiling_face: And love how much you care. I could do with a Nimbus update. Let's figure out contribution guide together today, too.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-13 06:50</div><div class="msg">Awesome! Thank you Alex.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-13 08:01</div><div class="msg">fantastic - how best to do that? The wiki docs on SOB are up to date, the video is here <a href="https://www.youtube.com/watch?v=edfQd_urHBc&list=PLbrz7IuP1hrg_80Iwllq_lXASZ4HDbufZ">https://www.youtube.com/watch?v=edfQd_urHBc&list=PLbrz7IuP1hrg_80Iwllq_lXASZ4HDbufZ</a> and I agree that we should use Moz as a template :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-13 08:40</div><div class="msg">This was a great read. I can see both sides of the argument. :heart: the discussion quality</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-13 08:45</div><div class="msg">is it because it might not be available in a particular linux distro that the user might be running?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-07-13 08:46</div><div class="msg">hmm, it seems to be a bit old (v23)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-16 10:16</div><div class="msg">I will update both parts later today and submit a PR</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-16 13:57</div><div class="msg">Hey <!here>, following up!
|
|
|
|
To publish an initial version of <a href="http://docs.status.im">http://docs.status.im</a> by this Friday the 20th, we need content for the contribution guide (@cryptowanderer on the job) and a revised version of the `Add Your DApp to Status` guide, which I'll provide. Not sure if we'll be able to incorporate any designs that @andmironov is ready to share, but maybe. :crossed_fingers:
|
|
|
|
@adria has started drawing out the Status architecture, based off the diagram that Igor shared in Basel. We'd love to get some more eyes on it...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-16 13:59</div><div class="msg">Let's consider that our next priority after publishing the site. We'll use the system architecture to determine the information architecture. Perhaps @igor680 could help with this? @oskarth a good candidate as well.</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 13:59</div><div class="msg">@jakub commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: nice, I like it</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:01</div><div class="msg">@jeluard commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: Is that @adria diagram?</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:01</div><div class="msg">@rachel commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: @jeluard yes, he's an artist</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:01</div><div class="msg">@adria commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: :joy:</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:02</div><div class="msg">@jeluard commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: Very nice! What tool do you use? Hands only? :sweat_smile:</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:02</div><div class="msg">@jeluard commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: Do you mind if I outsource you my diagrams needs?</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:03</div><div class="msg">@adria commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: sure, that will be very helpful</div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:03</div><div class="msg">@adria commented on @rachel?s file <a href="https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg">https://status-im.slack.com/files/U9K904A22/FBQV9DFJQ/20180713_134657.jpg</a>: app is <a href="https://procreate.art/">https://procreate.art/</a> which i basically use for simple drawing</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-16 14:16</div><div class="msg">@adria Very nice work! Definitely readable! And go team finally acknowledges that clojure is the center of it all.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-16 14:16</div><div class="msg">I would probably clarify go with go-ethereum</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:17</div><div class="msg">yep, still needs a lot of changes, just trying to get the whole idea on the same diagram</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-16 14:19</div><div class="msg">It's a very network centric vision and we might consider others complementary perspectives too (more ethereum oriented, features). Those could be simpler to read at first glance</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-16 14:23</div><div class="msg">:joy_cat: so react won't be nested inside go @adria? </div></div></div><br/>
|
|
<div><img src="" /><div class="message"><div class="username"></div><div class="time">2018-07-16 14:25</div><div class="msg">@adria commented on @adria?s file <a href="https://status-im.slack.com/files/U8WG0NWR2/FBS8QR7M5/img_20180716_162443.jpg">https://status-im.slack.com/files/U8WG0NWR2/FBS8QR7M5/img_20180716_162443.jpg</a>: last version</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:25</div><div class="msg">yeah, just shared the last version which reflects react-go communication</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-16 14:26</div><div class="msg">I'd like to see Infra collapse down into a single node, we'll need to be able to achieve that if we are to be decentralized</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-16 14:26</div><div class="msg">(in other words all infrastructure is supported by a p2p network)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-16 14:30</div><div class="msg">@adria why https from status-go? and it's not only mixpanel, we have collectibles api, etherscan, faucet</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:32</div><div class="msg">ah, just saw there is a correction on the original diagram, I'll correct mixpanel to start from react</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:32</div><div class="msg">about other collectibles, I'm still working on it, so they will be there soon</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:33</div><div class="msg">I'll probably need a hand understanding how they interact with status, do you mind if i ping you for help?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-16 14:33</div><div class="msg">yes sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:33</div><div class="msg">cool, cheers :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:36</div><div class="msg">don't you think it makes sense to have it split by peer type? mail servers for example are a really specific nodes with a clear functionality.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 14:37</div><div class="msg">maybe i can add a first layer `infra` and link that layer with every specific peer type</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-16 15:24</div><div class="msg">Status Desktop clients are also supposed to be mailservers and bootstrap functionality</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-16 15:26</div><div class="msg">it's kinda of weird we define shh subprotocol in this picture but not eth or bzz ?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-16 15:27</div><div class="msg">While definitely a nice work from aesthetics perspective, but I find this graph hard to understand. Sunburst layout is good to represent hierarchical data, and here I see a lot of mixing concepts in the same graph ? protocols, software layers of app, different types of deployed servers, etc.
|
|
|
|
Deployed servers are definitely not a "react -> go -> infra" subtree. "Go->HTTPS->Mixpanel" hierarchy is simply misleading, UDP discovery and Whisper are more likely to be a on different hierarchy levels (as Whisper is a layer above P2P layer, which itself is a layer over status physical nodes). The sizes of the nodes in such graphs also usually play an important role, but here they seem to be random.
|
|
|
|
@adria I feel like this could be 2 or 3 different graphs, showing separate domains. For example:
|
|
1) actual software entities layer ? here we put all servers, ethereum network, status apps. in this graph we can elaborate on protocols apps/servers use to communicate.
|
|
2) software layers ? here we show status-react/status-go/go-ethereum layers, and it's major parts.
|
|
3) protocol stacks ? elaborate on p2p, devp2p, discovery, whisper. status messaging protocol. could be something similar to OSI model.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-16 15:27</div><div class="msg">agreed</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-07-16 15:33</div><div class="msg">ok, i'll try to split it, @rachel does that work for you?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-16 15:44</div><div class="msg">Feel free to start discussions on all layers and poke people around to help, because it's not just graph - it's a mental map of what we're all work with, so it's important to be in sync here.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-16 16:45</div><div class="msg">absolutely, ideally it can be viewed together as one system @adria. looks like you've gotten some input from Andrey, do you need any other help though?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-17 07:31</div><div class="msg"><a href="https://status-im.slack.com/archives/C846J9HTJ/p1531811776000059">https://status-im.slack.com/archives/C846J9HTJ/p1531811776000059</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-17 08:08</div><div class="msg">It might also useful to start with a digitized network diagram (similar to Toshi one above). Then we can make it aesthetically beautiful :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-17 08:15</div><div class="msg">Also want to be mindful not to overburden @adria with something tangential like this. I like the Toshi example and assume it will be less time-consuming, and a good start.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-17 08:30</div><div class="msg">The Toshi architecture is naive compared to what we're trying to do</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-17 08:33</div><div class="msg">Well, at least what we used to do...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-10-03/448433513781_35b198abdf960e874693_72.png" /><div class="message"><div class="username">jarradhope</div><div class="time">2018-07-17 08:34</div><div class="msg">Now we're not really much different from a toshi or inzhoop clone, so weird</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-17 08:35</div><div class="msg">do you have a bit of time to do a rough sketch of the future state @jarradhope?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-17 13:16</div><div class="msg">Hey there!
|
|
I want to create a security-related section of the documentation. Do I just make a PR to the `<a href="http://docs.status.im">http://docs.status.im</a>` github repo for that?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-17 13:17</div><div class="msg">Yes please! But do not reference it yet (so just markdown) as we are planning a basic MVP soon.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-17 13:18</div><div class="msg">yeah, I'm basically writing a bunch of markdown files</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-17 15:18</div><div class="msg">pretty cool example of an in-depth engineering post wdyt @jeluard @exiledsurfer <a href="https://codeburst.io/doing-without-databases-in-the-21st-century-6e25cf495373">https://codeburst.io/doing-without-databases-in-the-21st-century-6e25cf495373</a> (promise I am getting to discuss tomorrow when I have a moment)</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-17 16:23</div><div class="msg">#java #database #orm #verbiage
|
|
You really want me to suffer, do you?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-17 16:35</div><div class="msg">:trollface:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-17 16:36</div><div class="msg">damn it, this is why I can't work with people for too long, they get to know my tricks, even when I just put them out there with the straightest face...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-07-17 18:18</div><div class="msg">that IS an extensive post. </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:11</div><div class="msg">Hey team. @jeluard thanks for making some minor stylistic changes to the site - tis much appreciated (though I still think you must be button-blind or something :wink: )
|
|
|
|
@rachel I am taking a first run at the contributor guide based on some others that I really like and could use some help with writing clearly about how best to handle submitting, naming the branch (just `fix/#3404` etc?), asking for review and collaborating with the reviewer/developer etc.
|
|
|
|
<a href="https://docs.google.com/document/d/1zN428eRCMOcJDDSh_aZLX_U-TJe2n36ekmjUXTmTzdM/edit?usp=sharing">https://docs.google.com/document/d/1zN428eRCMOcJDDSh_aZLX_U-TJe2n36ekmjUXTmTzdM/edit?usp=sharing</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:17</div><div class="msg">I wrote some semi relevant stuff here: <a href="https://status-im.github.io/pluto/docs/Development.html">https://status-im.github.io/pluto/docs/Development.html</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:18</div><div class="msg">Specifically for branch names it doesn't really matter as they are super short lived.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:19</div><div class="msg">Something like `#3404` could do it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-18 12:20</div><div class="msg">Are contributors also expected to ask for reviewers, @jeluard, or just submit?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:21</div><div class="msg">I would say they are not as it would require knowing who knows which part</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:21</div><div class="msg">We could experiment with `CODEOWNERS` <a href="https://help.github.com/articles/about-codeowners/">https://help.github.com/articles/about-codeowners/</a> . We do this for pluto :sunglasses:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-18 12:22</div><div class="msg">Agreed. As for collaboration, I guess that happens on an ad hoc basis, but the contributor should expect a response in any case. If there's more work to be done, they'll receive specific feedback/assistance until the request is satisfied.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:22</div><div class="msg">@cryptowanderer Which buttons you don't like specifically? Not that I want to challenge your aesthetic sense but .. :troll:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-18 12:22</div><div class="msg">And then if the PR is merged, we're all happy and they can check it out on a dev branch?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:24</div><div class="msg">Literally all of them @jeluard :wink: I can live with the ones on the home page, but not the Edit ones on any of the other pages :trollface:
|
|
|
|
And no offence intended (seriously this time) but those development docs don't help me understand at all well how to contribute to Pluto...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:25</div><div class="msg">I don't think contributors need to ask for reviewers, agreed :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-18 12:26</div><div class="msg">Ivan likes them? :sweat_smile: <a href="https://status-im.slack.com/archives/C87MN9M4Z/p1531853865000136">https://status-im.slack.com/archives/C87MN9M4Z/p1531853865000136</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:33</div><div class="msg">I'm not talking about the action they perform - I was the one who implemented that. I am talking only about Julien's decision to change their style from more rectangular and see through to solid blue... uggghhhh :stuck_out_tongue_winking_eye:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:40</div><div class="msg">But I take back what I said about Pluto - it is actually helpful, just maybe needs to be laid out a touch better and made a bit more explicit as far as actions required from developers goes :+1:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:43</div><div class="msg">No one wants to contribute to pluto anyway</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 12:44</div><div class="msg">hahaha, I do! :heart: Have to write more docs, work with Embark, organise a major hackathon, figure out a few more pieces of the dapp curation stuff, launch ETHprize website, do a podcast, and learn Spanish in between figuring out the best way to though...</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 12:47</div><div class="msg">Ok so next week then? :man-lifting-weights:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:23</div><div class="msg">@cryptowanderer If you want to push latest docs site you should find new fancy buttons :smile: (auto build is broken somehow)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:25</div><div class="msg">:nabil:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:25</div><div class="msg">^ that's still my fav button :joy:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:52</div><div class="msg">Look @cryptowanderer fancy buttons!! <a href="https://docs-staging.status.im/docs/build_status.html">https://docs-staging.status.im/docs/build_status.html</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:52</div><div class="msg">So how do you like the docs site now ?? :heart_eyes:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:54</div><div class="msg">Well, it turns out that you revert the colour changes to the headings on the home page, and also the colour and top margin of the headings on each page :facepalm:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:54</div><div class="msg">but the buttons are great :joy:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:58</div><div class="msg">eh you can't get all the fancy things</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:58</div><div class="msg">:zany_face:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:58</div><div class="msg">Like what colors changes? I thought white background was an issue?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:59</div><div class="msg">`Web3` is black instead of blue, that's all</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 15:59</div><div class="msg">Are you sure you are not color blind ?? :male-doctor:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 15:59</div><div class="msg">also, the top margin of the main headings</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:00</div><div class="msg">though that can't have come for your commit - wonder when it was introduced</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:00</div><div class="msg">hmm</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:00</div><div class="msg">oh no, there it is, why did you change `mainContainer`</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:01</div><div class="msg">But you want light grey background for the logos?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:01</div><div class="msg">yeah, that's fine :+1: It's just the literal colour of the heading</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:01</div><div class="msg">I just changed the padding</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:02</div><div class="msg">yeah, will drop a screenshot in channel now - it doesn't look good to me...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:03</div><div class="msg">why `padding: 0` @jeluard? Doesn't that look bad and squashed to you too?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:06</div><div class="msg">I am minimalistic</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:06</div><div class="msg"><a href="https://www.uxbrutalism.com/">https://www.uxbrutalism.com/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:06</div><div class="msg">aaaarrrrrgggghhhhhh :trollface:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:06</div><div class="msg">Well I wanted to fix the main page only ..</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:07</div><div class="msg">What else is hurting your eyes?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:07</div><div class="msg">Like you mentioned colors</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:08</div><div class="msg">It might be nice to make `h1`s the same blue, but otherwise its just that, then I promise to stop complaining (for today :wink:) I also need to update one image and some other things, but will get to that when I push to contributor guide etc...</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:13</div><div class="msg"><a href="https://github.com/status-im/docs.status.im/commit/b4e7d1f08792b6a4eb81c0acb3bc52c0d2a960c7">https://github.com/status-im/docs.status.im/commit/b4e7d1f08792b6a4eb81c0acb3bc52c0d2a960c7</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:17</div><div class="msg">you da best Julien :heart:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-18 16:24</div><div class="msg">Not sure my change is being pushed.. Will see</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-18 16:30</div><div class="msg">I can see it my side :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-19 12:13</div><div class="msg">@cryptowanderer the contribution guide looks awesome. My comments were minor. Let me know what you think. @jeluard if you have a chance to give it a read through, that'd be great. And then we can publish it?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-19 13:18</div><div class="msg"><a href="https://github.com/status-im/docs.status.im/commit/455f2988f65ade5ed58b6733db801972cf4e2aab">https://github.com/status-im/docs.status.im/commit/455f2988f65ade5ed58b6733db801972cf4e2aab</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-20 14:27</div><div class="msg"><!here> I think I'm done with editing
|
|
<a href="https://github.com/status-im/docs.status.im/pull/35">https://github.com/status-im/docs.status.im/pull/35</a>
|
|
what do I do next? :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:41</div><div class="msg">Looks perfect!</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:42</div><div class="msg">@cryptowanderer How about readding it to the sidebar?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:42</div><div class="msg">And I guess we can just merge?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:43</div><div class="msg">Request reviews from relevant people, then merge?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-20 14:45</div><div class="msg">It was reviewed by @cologic, pretty relevant I think :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-20 14:45</div><div class="msg">It's already merged and showing up on staging. It's in the sidebar in its own category - feel free to change if you don't like that.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:45</div><div class="msg">Then you can just merge?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-20 14:46</div><div class="msg">oki, I'll do that :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-20 14:47</div><div class="msg">@jeluard there is your review that I already addressed :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:50</div><div class="msg">Perfect! Can?t accept now. Maybe you can dismiss ot?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-20 14:50</div><div class="msg">It</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-20 14:52</div><div class="msg">sure</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-23 15:39</div><div class="msg">Documentation is now live : <a href="http://docs.status.im">http://docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-23 15:41</div><div class="msg">and it looks like @andmironov might be back (he posted in another channel), so maybe we can get some design eyes on it ASAP?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-23 15:44</div><div class="msg">I swear there are no popups here!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-24 10:23</div><div class="msg"><!here> documenting the release processes for different projects (mobile app, the cluster, etc) in `<a href="http://docs.status.im">http://docs.status.im</a>` vs in the repo. wdyt?
|
|
|
|
:one: for <a href="http://docs.status.im">http://docs.status.im</a>
|
|
:two: for keeping them in the repos</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-24 13:53</div><div class="msg">Hey team. So, seeing as we have no response yet to questions about design of the site, can I ask what the next steps here are @jeluard @rachel? We have questions like the above, and we have docs like this from @anna <a href="https://docs.google.com/document/d/1gvQ-dbDGFtLsiBDA6o-YtF9jXAa2-JNAQI9dMz8Sw1Q/edit?usp=sharing">https://docs.google.com/document/d/1gvQ-dbDGFtLsiBDA6o-YtF9jXAa2-JNAQI9dMz8Sw1Q/edit?usp=sharing</a>
|
|
|
|
And I feel like the (imo) arbitrary distinctions you have placed on the site mean that we will be left answering questions about what goes where for some time to come (which is just one more cognitive barrier potential contributors have to overcome). This especially after Adria left, so those diagrams are going nowhere, right? I would far rather see a lot of content go up there (under different navigational items in the header, with their own sidebars, and no need to get in the way of the main thrust to build and contribute) and watch things evolve as we need them to, rather than trying to figure out up front exactly what we need and then impose this from on high (which is being done between a whole bunch of other stuff, anyway).</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-24 14:01</div><div class="msg">Correct that we need to make another push on the Status architecture diagram. I actually just got off the phone with @naghdy, and I think we (and @jarradhope) are in agreement that that's an important thing for us to have. I'd like to have those involved with the docs swarm team up to work on it.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2018-07-24 14:02</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-24 14:03</div><div class="msg">OK, who is in the docs swarm that can work on this in the near future?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-24 14:04</div><div class="msg">`Docs` is just one big swarm of all of us! :heart_eyes:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-24 14:07</div><div class="msg">Yeah - despite the heart eyes (and you know what a fan I am :heart_eyes:) - but that's the exact opposite of what a swarm is supposed to be and how it is supposed to function.
|
|
|
|
And having no point person for this means that it will not happen - and **I feel like I can't stress this enough** - I just spent months gathering data from all the best developers in Ethereum and the single biggest thing they agreed about was that documentation sucks. It's such an easy way to get developer mindshare if we just nail it once and keep the momentum from there, so you'll need to forgive my lack of humour in this channel recently :disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-24 14:15</div><div class="msg">Feel free to corral people @cryptowanderer ? I haven't forgotten, but the swarm participants are the people who've been on this calendar invite: <a href="https://calendar.google.com/event?action=TEMPLATE&tmeid=MTRubDF0bDQxbGZ1a20xdGdvYTBkcm0yZ2sgcmFjaGVsQHN0YXR1cy5pbQ&tmsrc=rachel%40status.im">https://calendar.google.com/event?action=TEMPLATE&tmeid=MTRubDF0bDQxbGZ1a20xdGdvYTBkcm0yZ2sgcmFjaGVsQHN0YXR1cy5pbQ&tmsrc=rachel%40status.im</a>
|
|
|
|
Adria has left, Oskar was on vacation, Pedro is now on vacation, Julien is obviously actively involved but we're busy working on DApp and dev tools work after having pushed <a href="http://docs.status.im">http://docs.status.im</a> on Friday, and Andrei, as you know, we are waiting to hear from. I literally just spoke with Nabil about how I'll try to drum up more effort on the architecture diagram though.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-24 15:19</div><div class="msg">imo - this is something that the Tech Writer (used to be Alex Mandel) should have owned</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-24 15:19</div><div class="msg">We are simply under resourced to handle this properly.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-24 15:20</div><div class="msg">@cryptowanderer I understand your frustration</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-07-25 11:32</div><div class="msg">Of the user stories we identified as high impact, how far along are we in solving them? What's missing/blocking?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-25 13:36</div><div class="msg">@rachel @divan might be our diagram man!
|
|
```
|
|
Got it, thanks. So it's mostly for the developers, and so diagram should be more about how code is structured/organized in terms of projects/components/etc. Is this correct?
|
|
```
|
|
I think so... Would you add anything specific Rachel?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-25 13:41</div><div class="msg">Yeaaaaah no, that'd be great. I know that Status is much more complex than Toshi, but this is still a good example of a clear and easy-to-grok architecture diagram: <a href="https://developers.toshi.org/docs/architecture-overview">https://developers.toshi.org/docs/architecture-overview</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-25 13:44</div><div class="msg">I actually started drawing similar diagram last year, but it's not finished and a lot of things changed now.
|
|
<a href="https://docs.google.com/drawings/d/1D2wukqYWockdMe3zQK4Y600nAIxp9weV5AdWCuCtzgI/edit">https://docs.google.com/drawings/d/1D2wukqYWockdMe3zQK4Y600nAIxp9weV5AdWCuCtzgI/edit</a>
|
|
|
|
But I got the idea, will try to come up with something asap.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-07-25 13:55</div><div class="msg">Maybe we could have a GH project to track what?s to be done? I forgot specifics but IIRC some specific actions were agreed upon a few weeks ago, and seems like there?s some kind of design blocking but not clear how or why</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-07-25 13:56</div><div class="msg">^ @rachel wdyt</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-25 14:06</div><div class="msg">Probably a good idea. Last call, we?d decided to work on a system architecture (an artifact we generally need to have) and then determine an information architecture and build out the docs based on that.
|
|
|
|
The user story we decided to focus on first was building Status. There?s been a good number of fixes made to the set-up, and the docs themselves were updated by Alex and Andy. So now we?d like to build out the reference materials.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-07-25 14:10</div><div class="msg">It?d be great if we could find a way to represent this diagram in source control so anyone can make edits, I believe Pedro did some stuff like this before? Dot diagram or whatever they are called. Just a thought. </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-25 14:11</div><div class="msg">Will set something up later @oskarth - afk for 1 hr</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-25 14:13</div><div class="msg">Like that <a href="https://github.com/Frimkron/Ascidia">https://github.com/Frimkron/Ascidia</a> ? :grin:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-25 16:09</div><div class="msg">Ascidia is definitely cool.
|
|
|
|
@oskarth those tools are on my radar for years, and so far I haven't seen anything really good. For intuitive and easy drawing the most accessible and easy to use tool is, accidentally, Keynote, but it's binary format so versioning is hard. Convertors like Julien mentioned are cool, but often very limited.
|
|
|
|
So I guess the best choice is to use visual and intuitive to create diagram, and only then, use it as a blueprint for something gittable.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-07-25 16:10</div><div class="msg">I'm desperate to find the tool that not only draws diagrams, but also animates them (like when I want to show the data flow between components)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-07-27 02:41</div><div class="msg"><a href="http://js.cytoscape.org/">http://js.cytoscape.org/</a> claims some animation capabilities</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-27 11:08</div><div class="msg">Hey @hester any chance you could add this issue: <a href="https://github.com/status-im/design/issues/19#issuecomment-408367009">https://github.com/status-im/design/issues/19#issuecomment-408367009</a> to the Developer Docs project board I just created? <a href="https://github.com/orgs/status-im/projects/38?add_cards_query=is%3Aopen">https://github.com/orgs/status-im/projects/38?add_cards_query=is%3Aopen</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-27 11:09</div><div class="msg">I can't seem to edit the projects it's associated with</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-07-27 12:39</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 09:49</div><div class="msg">Not a pleasant message to see when running `make setup`:
|
|
```
|
|
npm WARN saveError ENOENT: no such file or directory, open '/Users/andrewtudhope/package.json'
|
|
npm WARN enoent ENOENT: no such file or directory, open '/Users/andrewtudhope/package.json'
|
|
npm WARN andrewtudhope No description
|
|
npm WARN andrewtudhope No repository field.
|
|
npm WARN andrewtudhope No README data
|
|
npm WARN andrewtudhope No license field.
|
|
|
|
audited 240687 packages in 12.917s
|
|
found 4665 vulnerabilities (95 low, 3765 moderate, 804 high, 1 critical)
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 09:52</div><div class="msg">Also, I always get this error and am at a loss now how to fix it :cry:
|
|
```
|
|
Fetching podspec for `RNKeychain` from `../node_modules/react-native-keychain`
|
|
[!] No podspec found for `RNKeychain` in `../node_modules/react-native-keychain`
|
|
Error running dependency install
|
|
```</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 09:54</div><div class="msg">@alwx Any idea what this could be?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 09:57</div><div class="msg">I mean, this file just looks like a mess to me :sweat_smile: <a href="https://github.com/status-im/status-react/blob/develop/ios/Podfile">https://github.com/status-im/status-react/blob/develop/ios/Podfile</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:04</div><div class="msg">Some other error notes:
|
|
```
|
|
ERROR: While executing gem ... (OptionParser::InvalidOption)
|
|
invalid option: --silent
|
|
```
|
|
^^ not sure that's critical
|
|
```
|
|
+ android-sdk already installed... skipping
|
|
grep: ./android/local.properties: No such file or directory
|
|
sdk.dir=HOME/Library/Android/sdk
|
|
Downloading Android NDK.
|
|
/Users/andrewtudhope/status-react/scripts/lib/setup/installers.sh: line 325: wget: command not found
|
|
```
|
|
^^ need to add `wget` as a dep clearly.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 10:07</div><div class="msg">Great point about `wget`. Could you create an issue for that? Should be part of the script itself</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 10:07</div><div class="msg">Also the grep error sounds wrong</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 10:08</div><div class="msg">gem one too actually :sweat_smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:12</div><div class="msg">will create an issue once @alwx has commented - he may have some secret sauce I need (though, tbh, from messing around with this at various stages, I've prob screwed my environment more than anyone else in the world :wink: )</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:19</div><div class="msg">Just did it, because I am busy for the rest of the day likely... <a href="https://github.com/status-im/docs.status.im/issues/39">https://github.com/status-im/docs.status.im/issues/39</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:44</div><div class="msg">Hey!
|
|
Hate Slack threads ? I received a notification, but was unable to find where is was after that :disappointed: Sorry, that's why it took me some time to find it and answer.
|
|
But, no ? I don't know why you have an error with RNKeychain, maybe it was removed or renamed in one of the commits?
|
|
Regarding this one:
|
|
```
|
|
ERROR: While executing gem ... (OptionParser::InvalidOption)
|
|
invalid option: --silent
|
|
```
|
|
It?s indeed not a critical one, but it's easy to fix, of course.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:44</div><div class="msg">@cryptowanderer @jeluard</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:45</div><div class="msg">I will add wget as dependency</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 10:45</div><div class="msg">:+1::skin-tone-2:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:55</div><div class="msg">@alwx what about the `npm` error though? I know what I pasted suggested that I wasn't in the right dir, but I was definitely in `status-react`. Running it after cleaning out, restarting and sorting out the `wget` problem still results in this error:
|
|
```
|
|
npm WARN saveError ENOENT: no such file or directory, open '/Users/andrewtudhope/status-react/package.json'
|
|
npm notice created a lockfile as package-lock.json. You should commit this file.
|
|
npm WARN enoent ENOENT: no such file or directory, open '/Users/andrewtudhope/status-react/package.json'
|
|
npm WARN status-react No description
|
|
npm WARN status-react No repository field.
|
|
npm WARN status-react No README data
|
|
npm WARN status-react No license field.
|
|
```
|
|
And there is no `node_modules` folder installed anywhere... Any ideas on what might be going wrong?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:57</div><div class="msg">weird stuff again!
|
|
how does the package.json look like in your case? does it exist?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:57</div><div class="msg">because it looks like it cannot even find the description, repository, etc</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:58</div><div class="msg">no, there is nothing there. It does write out a `package-lock.json`, but it just looks like this...
|
|
```
|
|
{
|
|
"lockfileVersion": 1
|
|
}
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:58</div><div class="msg">maybe you accidentally removed package.json?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 10:58</div><div class="msg">There is no `package.json` here though? <a href="https://github.com/status-im/status-react">https://github.com/status-im/status-react</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:59</div><div class="msg">oh nice</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:59</div><div class="msg">it was moved to mobile_files by someone</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 10:59</div><div class="msg">??</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 10:59</div><div class="msg">for some reason</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-07-30 10:59</div><div class="msg">#desktop</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 11:00</div><div class="msg">how are we supposed to use it now?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:00</div><div class="msg">@alwx Can you follow up on this in #desktop ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 11:04</div><div class="msg">ok got it
|
|
so now you need to run
|
|
```
|
|
make setup
|
|
make prepare
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 11:05</div><div class="msg">I will later simplify it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:06</div><div class="msg">Ran the prepare script, next problem:
|
|
```
|
|
Failed to notify ProjectEvaluationListener.afterEvaluate(), but primary configuration failure takes precedence.
|
|
java.lang.IllegalStateException: compileSdkVersion is not specified.
|
|
```
|
|
resulting in:
|
|
```
|
|
FAILURE: Build failed with an exception.
|
|
|
|
* Where:
|
|
Build file '/Users/andrewtudhope/status-react/android/app/build.gradle' line: 3
|
|
|
|
* What went wrong:
|
|
A problem occurred evaluating project ':app'.
|
|
> Could not read script '/Users/andrewtudhope/status-react/node_modules/react-native-config/android/dotenv.gradle' as it does not exist.
|
|
|
|
* Try:
|
|
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
|
|
|
|
* Get more help at <a href="https://help.gradle.org">https://help.gradle.org</a>
|
|
|
|
BUILD FAILED in 19s
|
|
Error running dependency install
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 11:08</div><div class="msg">this is something I cannot fix in 2 mins :disappointed: looks like something with one of our dependencies (`react-native-config`), have to check</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:09</div><div class="msg">@cryptowanderer Can you try to re-run the same command?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:10</div><div class="msg">doing so now - the "command" was running that whole script :sweat_smile: It got through everything else fine though :+1: Will paste full error here for ref now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:11</div><div class="msg">@jeluard now the error is:
|
|
```
|
|
> Configure project :app
|
|
Reading env from: .env
|
|
Configuration 'compile' in project ':app' is deprecated. Use 'implementation' instead.
|
|
|
|
|
|
FAILURE: Build failed with an exception.
|
|
|
|
* What went wrong:
|
|
A problem occurred configuring project ':app'.
|
|
> The SDK directory '/Users/andrewtudhope/status-react/android/HOME/Library/Android/sdk' does not exist.
|
|
|
|
* Try:
|
|
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
|
|
|
|
* Get more help at <a href="https://help.gradle.org">https://help.gradle.org</a>
|
|
|
|
BUILD FAILED in 10s
|
|
Error running dependency install
|
|
```</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:13</div><div class="msg">Your NDK installation is wrong. Are you trying to run this for iOS or android?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:13</div><div class="msg">(And please create issues for all those :sweat_smile:)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:15</div><div class="msg">Are you sure/ can you provide more details? It seems to me that the config is setting my `sdk` directory wrongly - appending it to the `cwd`, rather than reading it from `HOME`...</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:21</div><div class="msg">Right might be that the script creates it incorrectly. So many changes recently don't remember if it's supposed to be done automatically or not.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-07-30 11:21</div><div class="msg">@alwx WDYT?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 11:23</div><div class="msg">it's likely
|
|
I don't like the way NDK installation is done, and also don't like that people simply introduce changes to our build scripts without even asking.
|
|
everything was fine about two weeks ago, now there are problems again :disappointed:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:30</div><div class="msg">Could also be that I only set `ANDROID_SDK` in my `bash_profile` and not `ANDROID_SDK_ROOT` - will give that a go after the TH too</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-07-30 11:33</div><div class="msg">offtopic: i think building status is needed in really rare cases , dapps devs could use nightly, for status contributors we could provide special build</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:34</div><div class="msg">Yeah, the reason I'm going through this pain is precisely that I couldn't get the latest nightlies to install on my android emulator (using AVD), so decided to try this (and now regret it :wink: )</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-30 11:40</div><div class="msg">At least iOS works :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 12:00</div><div class="msg">yay</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 12:00</div><div class="msg">iOS is always a bit easier</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-30 12:01</div><div class="msg">but it's good ? at least now we have better understanding of what works and what doesn?t</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-05-11/363235195815_bbe7d055e1883e756d9b_72.jpg" /><div class="message"><div class="username">maxr</div><div class="time">2018-07-30 13:01</div><div class="msg">probably, not for those who came with Windows only background :smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-07-30 13:04</div><div class="msg">Blockstack just redesigned their dev docs: <a href="https://blockstack.org/">https://blockstack.org/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-07-31 08:53</div><div class="msg">@alwx is this happening frequently?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-07-31 08:54</div><div class="msg">not frequently, but it just happens without anybody noticing it :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-07-31 13:51</div><div class="msg">I know you're OOO @divan but when you get the chance, have you seen this? <a href="https://mermaidjs.github.io/">https://mermaidjs.github.io/</a> and how is that diagram coming along?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-01 10:57</div><div class="msg">Hey, I'm back. Checking it out. Well, when I was OOO I trapped between Nice and Monaco without laptop, so diagram is on my backlog for these days.
|
|
Do you have any deadlines? (I like deadlines)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-01 12:02</div><div class="msg">OK, how about Friday? :wink:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-01 12:04</div><div class="msg">I'm flying on Friday all day :confused: Monday perhaps? I'll have a whole weekend to work on it.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-01 12:17</div><div class="msg">Sounds good to me :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-08-02 14:03</div><div class="msg">Hey <!here> ?swarm update and recap from a call between myself, @jeluard @naghdy & @cryptowanderer:
|
|
|
|
We're still working to bring on a new technical writer who can take more ownership of this project, and help determine the process we use to continuously document Status.
|
|
|
|
In the meantime:
|
|
|
|
+ @cryptowanderer to work w/ clojure team on getting Whisper docs onto <a href="http://docs.status.im">http://docs.status.im</a>
|
|
+ @divan / @cryptowanderer to produce Status system architecture for Monday, 6/8. If we need design on this, @denis-sharypin has a friend who might be interested in helping?
|
|
+ Design team working on a swarm for our web assets?look/feel of <a href="http://docs.status.im">http://docs.status.im</a> are dependent upon this work kicking off: <a href="https://status-im.slack.com/archives/C8EQ3SH0E/p1532699700000213">https://status-im.slack.com/archives/C8EQ3SH0E/p1532699700000213</a> (cc @andmironov)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-08-02 14:03</div><div class="msg">Question: did we solve the basic 2-3 or so user stories we outlined earlier?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-08-02 14:13</div><div class="msg">I don't think those high level stories will ever be finished, but you could say we've checked the box for #1 `Build Status`. Developer tools to support `Build DApps` are still in early stages, but we do have our first docs for that live as well: <a href="https://docs.status.im/docs/status_web_api.html">https://docs.status.im/docs/status_web_api.html</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-08-02 14:13</div><div class="msg">The `Learn web3` story is not something we've touched on yet, not through this swarm.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-03 10:09</div><div class="msg">Do we have some plan to sunset the docs on the wiki?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-03 10:26</div><div class="msg">I think we should burn the wiki in a ceremony in Berlin :fire:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-03 10:31</div><div class="msg">I'll just pretend I have not read that comment</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-03 10:33</div><div class="msg">I will start by removing mentions of the wiki docs from status repos</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-06 08:50</div><div class="msg">@cryptowanderer I've been working yesterday and will continue today on three diagrams (status software composition, infrastructure design, network protocols). Will be posting some drafts closer to the evening.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-08-08 12:52</div><div class="msg">Would be a great resource to get status docs on to...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-08 16:50</div><div class="msg">Docusaurus comes with its own translation tool built in. Julien and Rachel disabled it though, for the initial version. Let's just get the docs right first and get an actual design together.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-08-09 19:26</div><div class="msg">This is what I've been using for the ideas repo: <a href="https://www.graphviz.org/gallery/">https://www.graphviz.org/gallery/</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-10 07:59</div><div class="msg">I started using <a href="http://draw.io">http://draw.io</a> - seems like a good fit: nice UI/UX and stores diagram in XML files</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-08-10 08:05</div><div class="msg">The nice thing about GraphViz is that it is meant to be edited without any tools, since the textual format is so simple. Even though XML is textual and can be easily versioned, I'm not sure if it will end up being easy to compare 2 versions of the same file by looking at the XML (if that's a requirement for us).</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-10 08:07</div><div class="msg">Luckily, it's not a requirement at all.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-10 09:22</div><div class="msg">Nice `increment` issue about documentation: <a href="https://increment.com/documentation/">https://increment.com/documentation/</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-13 16:01</div><div class="msg">Okay, sorry folks for the silence. I have three diagram drafts, and I don't really like any of them, but anyway I guess they should be shared so we can have starting point. I used <a href="https://draw.io">https://draw.io</a> (they have Desktop client) which allows to import/export XML files and easily generate PNG images.
|
|
|
|
What repo I can use to share those XMLs?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-13 16:01</div><div class="msg">Meanwhile, here two charts for network architecture and protocols layers:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-13 16:02</div><div class="msg">I also started working on Status app components breakdown, but I need a bit more time for that.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-13 16:03</div><div class="msg">My original idea was to use the same colors for the same concepts (messaging, blockchain, discovery etc) on all charts (so they're connected), but it's not true for now and a bit messy.
|
|
|
|
Again, those above just pre-alpha drafts to discuss.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-08-14 10:37</div><div class="msg">Great job @divan! I actually like those 2 first diagrams, they're certainly valuable when introducing new people to our architecture.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-08-14 10:37</div><div class="msg">(btw, just noticed a type in `rendezvous`)</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-14 12:52</div><div class="msg">Thanks! I'll post xml files, so anyone can work on it just by uploading to <a href="http://draw.io">http://draw.io</a>. Should be easy.
|
|
Do we have a repo to host this kind of things?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-14 14:27</div><div class="msg">@divan Do you have some idea how first 2 diagrams would fit in the website structure?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-14 14:43</div><div class="msg">img tag :slightly_smiling_face: but actually no, I have no idea and would be glad to see how and where they are supposed to be placed</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-14 14:43</div><div class="msg">Also, current design is different from what we're aiming for, so I think it should be reflected as well.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-14 14:47</div><div class="msg">Do you mean design of the application itself?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-14 14:48</div><div class="msg">Both. Design of the network infrastructure (we going to ditch infura at some point) and app as well, yes ? at least, moving chat API into status-go (but that's fine for now)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-16 12:43</div><div class="msg">Hey @yenda how out of date is this doc, and could it be cleaned up for our new docs site? <a href="https://wiki.status.im/Status_Communication_Protocol">https://wiki.status.im/Status_Communication_Protocol</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-31/408248212533_6aab8328425c701a55ee_72.jpg" /><div class="message"><div class="username">corey122</div><div class="time">2018-08-20 06:41</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-08-24 07:57</div><div class="msg">Nice read
|
|
<a href="https://blog.stoplight.io/writing-documentation-when-you-arent-a-technical-writer-part-one-ef08a09870d1">https://blog.stoplight.io/writing-documentation-when-you-arent-a-technical-writer-part-one-ef08a09870d1</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-27 09:21</div><div class="msg">In the first part of the mainframe dev call their new doc site is discussed: <a href="https://www.youtube.com/watch?v=VQsfboMwt4c">https://www.youtube.com/watch?v=VQsfboMwt4c</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-08-27 15:15</div><div class="msg">```
|
|
YT stuff
|
|
YT stuff
|
|
5 days ago
|
|
So who is your main competitor? Discord or Telegram?
|
|
Mainframe
|
|
Mainframe
|
|
2 days ago
|
|
We don't actually consider either of those projects as primary competitors. While our work began in the messaging space, we're now building a platform that can support much more. Any kind of Dapp could live on the Mainframe platform, including dapps from Discord or Telegram. Our real competitors would be groups building competing platforms for decentralized, unstoppable dapps.
|
|
```</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-08-29 06:28</div><div class="msg">To reduce the potential for confusion I'd like to get rid of <a href="https://wiki.status.im/Building_Status">https://wiki.status.im/Building_Status</a>
|
|
Any objection?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-08-29 06:42</div><div class="msg"><a href="https://www.youtube.com/watch?v=grupR1xTLvc">https://www.youtube.com/watch?v=grupR1xTLvc</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-08-29 14:28</div><div class="msg">how can i deploy doc updates?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-08-29 14:31</div><div class="msg">should be auto-deployed when a PR is merged</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-04 18:27</div><div class="msg">hey! I'm going to be writing some runbooks for supporting our infrastructure, and I was wondering what would be the right place for that, considering it will involve details about our infra i'd rather not have it public</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-06 11:29</div><div class="msg"><a href="https://status-im.slack.com/archives/C9KT29ZK2/p1536233000000100">https://status-im.slack.com/archives/C9KT29ZK2/p1536233000000100</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-06 11:30</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-06 11:33</div><div class="msg">@ceri Thanks for the quick onboard: I seem to have successfully authenticated to everything @exiledsurfer asked for.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-06 11:50</div><div class="msg">Welcome @easye :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-06 11:52</div><div class="msg">Thanks! Starting to drink from the proverbial firehose?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-06 12:14</div><div class="msg">Welcome @easye!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-10 12:18</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-12 03:15</div><div class="msg">What's the plan for deprecating the old wiki? IMO this should be a goal for this swarm</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-12 06:12</div><div class="msg">We haven't got a chance to discuss that yet but probably yes. First step could be to remove references to it.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-12 06:12</div><div class="msg">There might be content there (like Status Culture) that does not fit <a href="http://docs.status.im">http://docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-12 07:44</div><div class="msg">There's a whole lot of work being done around our web properties now (with @exiledsurfer @cryptowanderer @ned @andmironov) that will influence the IA of our docs. A (re)kick-off meeting is being planned just to talk about docs, but in terms of content, @easye will be focused on Whisper docs to start.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-12 08:20</div><div class="msg">@oskarth @rachel for docs.status (and embark.status/docs, we'll continue serving from github updates on a theme which will be skinned with the new global navigation of the website(s) mini-refresh; right now embark and technikon are using different theme displays, and i spoke with @cryptowanderer in berlin about standardizing which theme will be used which shouldn't be a problem.
|
|
|
|
@jeluard if there's anything we want to save / perpetuate from Status Culture, that content could be served via people-ops.status
|
|
|
|
over coffee w/ @easye this morning we discussed the needs for an overall deprecation scheme with addressing to maintain the history of documentation to date to allow searchability and analysis, but that is a larger architectural / semantic discussion that will need to be had once we have an immediate visual solution and potentially changed url structure on the new site; "deprecating" the wiki will probably just mean no longer linking to it or updating it, and not retiring it. Easye mentioned to me that he's already dones some thinking around this, but plans to focus on getting the introductory whisper post out the door.
|
|
|
|
in my conversation w/ @stefania and @baofranca yesterday, they mentioned that they're still interviewing for additional tech writers (for studio and nimbus specifically), and it's clear that the burden cannot fall on @easye to write all that needs to be written. We will need a "docs lead" tho to coordinate the consistency in all of this as we move forward. My largest concern is that we have a set of standards an practices that we implement across all projects, as well as the seamless interlinking between them where they interface with each other.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-12 13:04</div><div class="msg">No idea really about `Status Culture`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-12 20:56</div><div class="msg">I :heart: these docs: <a href="https://coolguy.website/writing/the-future-will-be-technical/index.html">https://coolguy.website/writing/the-future-will-be-technical/index.html</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-13 11:03</div><div class="msg"><a href="https://status-im.slack.com/archives/C846J9HTJ/p1536720580000100">https://status-im.slack.com/archives/C846J9HTJ/p1536720580000100</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-13 11:03</div><div class="msg">mister mister</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-23/422058362675_dc3e307b6e9052d90b4c_72.jpg" /><div class="message"><div class="username">kim196</div><div class="time">2018-09-13 13:05</div><div class="msg">awesome:cry:. future pity party lol.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-09-13 13:54</div><div class="msg">Heya got a docs PR! <a href="https://github.com/status-im/docs.status.im/pull/47">https://github.com/status-im/docs.status.im/pull/47</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-18 06:51</div><div class="msg"><a href="https://status.im/">https://status.im/</a> now correctly references <a href="http://docs.status.im">http://docs.status.im</a> ! No more links to the old wiki</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 08:42</div><div class="msg">Woohoo awesome! Recap of our kick-off call yesterday with @cryptowanderer @exiledsurfer @easye:
|
|
|
|
- We'll separate Status contributor guides from Status developer tools documentation
|
|
- Status contributor guides may be grouped on the people ops site, since people ops is all about bringing contributors in to Status, and the community is as much a part of that as CCs are
|
|
- We'll drop Docusaurus for now and use the same generator as the Embark site (<a href="http://hexo.io">http://hexo.io</a>). We'd like to match Embark visually as well, for consistency.
|
|
- Andy will work on that; I'll get my thoughts together about the structure for Status developer docs, based on what we're preparing for the hackathon - as well as what needs to be written</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-18 08:44</div><div class="msg">- @easye will lead the way by example through the Whisper series</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-05-21/367025375940_c77cc650cdbe3bf5be5f_72.jpg" /><div class="message"><div class="username">ceri</div><div class="time">2018-09-18 09:10</div><div class="msg">Sounds good, let us know how we can help kick this off!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 09:22</div><div class="msg">Glad you guys are on board @ceri!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 10:42</div><div class="msg">What?s the difference between contributors and developers (tool users)?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 12:45</div><div class="msg">A contributor is involving themselves with Status in some way - open source, to the tech, or perhaps by helping with translations, voting with SNT, etc. A developer using dev tools is likely building a DApp or protocol.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 12:47</div><div class="msg">Hm, to me they seem like the same thing, from a developer pov, or at least closely related</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 12:50</div><div class="msg">There's definitely overlap</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 12:56</div><div class="msg">what's the journey for a contributor who wants to understand how to contribute to Status code base with PRs etc? does people ops have expertise in this or what's the plan around that?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 13:08</div><div class="msg">People ops doesn't need to write the content</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 13:09</div><div class="msg">It's just a matter of grouping</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 13:09</div><div class="msg">I personally think it's the domain of a technical writer still</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:10</div><div class="msg">maybe I'm not seeing it clearly enough and lack some context, but I'd be confused if I went to <a href="http://docs.status.im">http://docs.status.im</a> and it told me to go to some people ops blog to learn how to commit a PR and pick something to work on</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 13:18</div><div class="msg">Well, it's part of a re-envisioning of how all of Status' web properties will work - there's going to be a global nav with all those important CTAs accessible. So it might say "Contribute" and link directly into the issue/PR guidelines, but that article would grouped alongside other more general information about contributing to Status. However it works, I thought it made sense to separate contributing to Status from API/tools documentation, since there's a lot of content for both. My focus right now is just on the content for tools the DApp/developer team is building. @cryptowanderer and @exiledsurfer care to weigh in?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:20</div><div class="msg">gotcha</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:46</div><div class="msg">I have little snitch but it is on allow all</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:46</div><div class="msg">wait wat</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:47</div><div class="msg">omg...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:47</div><div class="msg">it was little snitch that bastard</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:47</div><div class="msg">there was a custom rule for Status outgoing connections, no idea wtf that was doing there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 13:48</div><div class="msg">oh wrong thread</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 14:34</div><div class="msg">lol what @oskarth I'm offended</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 14:35</div><div class="msg"><a href="https://status-im.slack.com/archives/CAM2RMY65/p1537273895000100">https://status-im.slack.com/archives/CAM2RMY65/p1537273895000100</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 14:35</div><div class="msg">This thread, I owned myself with Little Snitch app </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-18 14:36</div><div class="msg">@oskarth loves hijackin threadz when he's bored</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-18 14:36</div><div class="msg">:joy:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-18 14:36</div><div class="msg">I swear I didn't have anything to drink (yet)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-18 14:36</div><div class="msg">we're so disappointed</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 12:34</div><div class="msg"><a href="https://docs.status.im/docs/build_status.html">https://docs.status.im/docs/build_status.html</a> what happened with status-go instructions?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:07</div><div class="msg"><a href="https://github.com/status-im/status-go#build">https://github.com/status-im/status-go#build</a>
|
|
<a href="https://wiki.status.im/Building_Status">https://wiki.status.im/Building_Status</a>
|
|
^ @jeluard</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 13:09</div><div class="msg">AFAIK it never was documented in the wiki? For sure it's not in the new docs.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 13:09</div><div class="msg">@pedro Who can add go related docs in <a href="http://docs.status.im">http://docs.status.im</a>?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:11</div><div class="msg">I added at least part of it way back so there definitely used to be some stuff there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:11</div><div class="msg">I'm sure things have changed now, there are a lot of options related to building status-go now and different configs (bootnodes, whisper nodes, relays and oh my)</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 13:23</div><div class="msg">Surely. I will defer to go team to update the doc accordingly</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:33</div><div class="msg">@jeluard do you mean who can volunteer to add it?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:34</div><div class="msg">I don't recall seeing Go instructions in wiki personally, I've used <a href="https://github.com/status-im/status-go/blob/develop/README.md">https://github.com/status-im/status-go/blob/develop/README.md</a> (which is also a bit out of date)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:36</div><div class="msg">it's in need of a brush up. Should it be done here or in <a href="http://docs.status.im">http://docs.status.im</a>? If the latter, then we could just replace most of the README.md content with a link to <a href="http://docs.status.im">http://docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 13:37</div><div class="msg">At the very least <a href="http://docs.status.im">http://docs.status.im</a> should be self-sufficient, so pointing to the relevant status-go docs</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:37</div><div class="msg">yeah, I like the fact that the instructions are versioned together with the actual repo</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 13:39</div><div class="msg"><a href="http://docs.status.im">http://docs.status.im</a> is a repo too. That's a topic for a broader discussion but we probably want a unique view on that</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:40</div><div class="msg">yeah, but if I build a different branch of status-go, or an old commit, I'd like to have access to the precise build instructions for that version</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:55</div><div class="msg">we had status-go status-react bundle in wiki before, don't think that's in README</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:56</div><div class="msg">do you mean the reference to `bundle-status-go.sh`?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:57</div><div class="msg">yeah and possibly other instructions around it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:57</div><div class="msg">forgot what else was there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:58</div><div class="msg">I guess even more useful would be elaboration on what the different modes are, and how to build/run each type of thingy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:58</div><div class="msg">`bundle-status-go.sh` is only meaningful for status-react, it doesn't make sense for status-go repo</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 13:58</div><div class="msg">unless I misunderstood</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 13:59</div><div class="msg">it's meaningful in the sense of Building Status overall, which is one of the CTAs on <a href="http://docs.status.im">http://docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 14:01</div><div class="msg">true, there's a ton of improvements we can do in that respect, but so little time to do it...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:03</div><div class="msg">I was hoping this swarm would deal with this as that's one of top user stories identified, as reflected by it being a CTA on its front page and being one of the blockers for people who want to contributors. I don't understand why it seems like we deviated from this vision?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:17</div><div class="msg">To be clear I think <a href="https://docs.status.im/docs/build_status.html">https://docs.status.im/docs/build_status.html</a> is a great start and it awesome to see cleanup of status-react build process. It'd just be useful if we didn't throw away useful existing info that's vital to the entire pipeline. To me just basic build instructions is way more useful than a guide on Whisper or a coherent color scheme. This is what blocks people and makes them give up.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:22</div><div class="msg">Are these up to date TestTeam <a href="https://docs.status.im/docs/testing.html">https://docs.status.im/docs/testing.html</a>?
|
|
|
|
"If you are ready to help with testing then make sure you have a recent backup of your device as there is no guarantee that next build will not introduce critical issues that cause complete device reset and data loss." and "Current versions consume lots of traffic and battery, make sure you are using wifi for testing." seems both scary and wrong to me. Perhaps we can make this seem more welcoming?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-09-19 14:23</div><div class="msg">we should update it, totally :slightly_smiling_face: I will do it tomorrow</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:25</div><div class="msg">thanks!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 14:53</div><div class="msg">Certainly not throwing anything away. Same story here - without a technical writer onboard it's been difficult to get more momentum behind this. The focus of our conversation the other day was on the overall information architecture. And I think it was decided that Whisper was a good starting place for Mark to begin his trial because there was so much recent content in need of review, right @cryptowanderer?
|
|
|
|
Not to mention, an understanding of Whisper/Status chat will be important to anyone working with our JS API or extensions. I'm not sure how much interest there is, comparatively, in building status-go.
|
|
|
|
That said, helping with the status-go guide is another great starter project for Mark.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 14:54</div><div class="msg">Can you add an issue to this board for it @oskarth? <a href="https://github.com/orgs/status-im/projects/38">https://github.com/orgs/status-im/projects/38</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:56</div><div class="msg">What happened with having one person from each team? That'd be domain experts, as opposed to a tech writer figuring out everything by themselves</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-19 14:57</div><div class="msg">There wasn't enough interest :stuck_out_tongue_winking_eye: But SITG could change that! :mindblown:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:58</div><div class="msg">So to make sure, we tried to get Go people to join this effort but not a single one volunteered? I find that either difficult to believe or disappointing</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 14:58</div><div class="msg">@oskarth What is the scenario you are considering? To test changes in status-go itself? Current doc is definitely self-sufficient to build status from scracth</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-19 14:58</div><div class="msg">Yeah, whisper is first up and moving along swiftly. I have a re-skinned version of the docs in hexo @rachel but have begun to think I need to sync with @hazel and @andmironov about where they are at with the overall redesign, as it's likely that will effect some stuff. But, I do expect that we will have things looking spick and span before the hackathon</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:59</div><div class="msg">- building status-go
|
|
- bundling custom status-go into status-react (vital for any complex PR)
|
|
- building and running various types of basic status node / status-go services, such as bootnodes/whisper/etc with fleet and whatnot</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 14:59</div><div class="msg">Status != status-react, even if that's where most interest is right now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:01</div><div class="msg">Same applies for contracts btw (imo), even if it is just a pointer to a README that works</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 15:01</div><div class="msg">Apparently it never blocked any external contributions but makes sense! JIT documentation, only written when it's being asked ! :smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:02</div><div class="msg">I think that's because most new contributors give up when something seems undocumented :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:08</div><div class="msg">I agree with JIT documentation though, what bugs me is that we are regressing in our documentation in some areas despite this being an explicit user story</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 15:11</div><div class="msg">My bad then I deleted the wiki page without noticing the extra status-go information.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 15:11</div><div class="msg">And I will shamelessly confess I never built status-go myself :fearful:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:14</div><div class="msg">You should try it, it is exhilarating! :p</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:15</div><div class="msg">No worries it's not about any individual action, more that we have been on this project for a while and it seems to me like we are doing lots of extra stuff related to IA and themes and long blog series etc but not tending properly to the basics, which IMO is building the damn thing (its complex!). Possible I?m over sensitive and whisper guides are more bang for buck, don't know </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:18</div><div class="msg">As another example, yarn PR has been open for 3m <a href="https://github.com/status-im/status-react/pull/5056">https://github.com/status-im/status-react/pull/5056</a> and before that we had a community member who pushed this and gave up. This type of thing would make a huge difference for lowering barriers to entry for devs to contribute, imo </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:35</div><div class="msg">There was enough trouble with getting that yarn PR to work that we iceboxed it and moved on as I recall</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:37</div><div class="msg">If that's the case, maybe we can capture this in PR/issue and close it with explanation? Right now it looks like it was randomly abandoned, not like a conscious decision </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:37</div><div class="msg">^ @alwx </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:38</div><div class="msg">Anyway, the case with docs is that I'm spread thin enough that I haven't been focused on it. I've interviewed a bunch of technical writers and now that extensions/JS API are progressing, am focusing on the content we need to keep up with everything we're building there</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 15:39</div><div class="msg">Right as Rachel said. There were too much technical limitations and the potential gain was thin</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:39</div><div class="msg">Maybe @cryptowanderer can lead the project?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:41</div><div class="msg">Wasn't @anna also working on some test guideline docs?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 15:46</div><div class="msg">The <a href="https://docs.status.im/docs/build_status.html">https://docs.status.im/docs/build_status.html</a> page is also missing instructions specific to Desktop. I'll look into adding those as part of my PR for unifying desktop builds.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-19 15:48</div><div class="msg">@pedro See <a href="https://docs.status.im/docs/build_desktop.html">https://docs.status.im/docs/build_desktop.html</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-09-19 15:48</div><div class="msg">@pedro I think this page it already huge and maybe even scary for some of potential developers, and adding information about Status Desktop will make it even bigger. maybe it's better to add a new page instead?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-09-19 15:48</div><div class="msg">oh, there is a new page already</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-09-19 15:50</div><div class="msg">> If that's the case, maybe we can capture this in PR/issue and close it with explanation?
|
|
|
|
@oskarth yes, my bad. we discussed that we want to stop working on it during one of our sync calls, but I've forgotten to add this information to the story itself :disappointed: will do next time</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:50</div><div class="msg">There's also a big gap for automated testing and how to run it from what I can tell, as well as tests in general
|
|
|
|
cc @adan @george952 (IIRC you were working on some tests)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-09-19 15:50</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/412069438306_115e95832b53d8b4a242_72.png" /><div class="message"><div class="username">george952</div><div class="time">2018-09-19 15:50</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:51</div><div class="msg">@rachel so should we fork this channel into two then and make it explicit that right now there's no one leading documentation effort? I'd rather we don't just let this documentation effort slide and turn it into something else. If a set of people are working on other stuff that's seen as more prio for now that's cool, but let's make this explicit.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:52</div><div class="msg">why do we need to fork it into two channels?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 15:54</div><div class="msg">Well, right now I personall am or was under impression things are under control and we are making progress in vital documentation areas such as building/testing basic components, but just from looking and trying cursory things at <a href="http://docs.status.im">http://docs.status.im</a> it's clear there are lots of gaps and no one is pushing to fix them. I'd prefer if those gaps were explicit, so as to not give illusion of progress, when progress is on other problems such as dapp developer user story or whisper user story</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 15:58</div><div class="msg">I don't think we need another channel for that. We just need someone to give time to this?I'll take the blame for not going out to get more content written in the past month. I compartmentalised it as something that would happen when we had a writer onboard to help oversee.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:00</div><div class="msg">@oskarth set the channel topic: <a href="http://docs.status.im">http://docs.status.im</a> | In need of: swarm lead | Gaps: status-go etc; QA update; auto/regular tests; place for infra runbooks; yarn (simplify build pipeline)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/412069438306_115e95832b53d8b4a242_72.png" /><div class="message"><div class="username">george952</div><div class="time">2018-09-19 16:00</div><div class="msg">I'm currently working on a POC for clojure.spec integration to improve the unit test coverage situation and if I'm not mistaken @adan was working on E2E tests ? is that correct @adan? Just to make sure there's no duplication of effort.
|
|
|
|
Anyway, when this is done, I'll make sure to put together some documentation.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:00</div><div class="msg">Ok, let's keep it in one channel, added some stuff to topic.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:01</div><div class="msg">In terms of seeing efforts that are active and state of them it's my bad in not making sure we update <a href="http://ideas.status.im">http://ideas.status.im</a>, on its way with stubs like these <a href="https://ideas.status.im/ideas/306-core-dapp-developers">https://ideas.status.im/ideas/306-core-dapp-developers</a> - that way it could be explicit for everyone async that this effort didn't get enough attention due to other prios/constraints</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 16:06</div><div class="msg">Personally the main place I'm looking for insight into ongoing work is slack channels and project boards on github</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/412069438306_115e95832b53d8b4a242_72.png" /><div class="message"><div class="username">george952</div><div class="time">2018-09-19 16:15</div><div class="msg">I don't mean to derail this thread, but since the conversation happened here ? I don't think it's a good idea to abandon the yarn effort.
|
|
|
|
- there are issues with npm versions higher than 5.5.1 at the moment, where it simply freezes during `npm install`. I experienced this myself.
|
|
<a href="https://docs.status.im/docs/build_desktop.html#prerequisites">https://docs.status.im/docs/build_desktop.html#prerequisites</a>
|
|
|
|
- there is an `npm audit` feature that displays which currently installed dependencies have known vulnerabilities. Many of ours do, we should definitely have this. This was introduced with npm 6 however and we cannot use it.
|
|
|
|
- `yarn audit` is in active development and should be available soon:
|
|
<a href="https://github.com/yarnpkg/yarn/issues/5808">https://github.com/yarnpkg/yarn/issues/5808</a>
|
|
|
|
- npm has a terrible quality history, here are some horror stories from the trenches:
|
|
<a href="https://news.ycombinator.com/item?id=16913531">https://news.ycombinator.com/item?id=16913531</a>
|
|
|
|
In my opinion and from my personal experience, this isn't even a pros and cons situation, npm is a pain and a gamble and we should not be using it.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:16</div><div class="msg">100% agree @george952, thanks for bringing data to back up intuition! Would you like to take over that PR effort perhaps?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/412069438306_115e95832b53d8b4a242_72.png" /><div class="message"><div class="username">george952</div><div class="time">2018-09-19 16:17</div><div class="msg">It is a good match for my current efforts to improve the developer experience, so yes, I'll take it.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:18</div><div class="msg">awesome :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/412069438306_115e95832b53d8b4a242_72.png" /><div class="message"><div class="username">george952</div><div class="time">2018-09-19 16:22</div><div class="msg">I do plan to tackle this after the clojure.spec and remote debugging issues though, because I think they're painful in a more immediate way, so it'll be some time.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-09-19 16:26</div><div class="msg">Going through this mega-thread, a few things come to mind:
|
|
1. Ownership of docs by one particular person/team is not scalable. As we think of ourselves as maintainers of Status rather than contributors, documenting our workflow (e.g. building `status-go`) should be glaringly obvious as missing by the Go team.
|
|
2. afaik - This swarm/channel is focused on the platform to host documentation and the initial migration, rather than persistent upkeep of documentation. If thats unclear, then it should be communicated more clearly.
|
|
|
|
If people see things missing, then they need to take ownership and document themselves</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:33</div><div class="msg">1. It's not about ownership of writing docs, it's about making sure we meet basic user stories. This includes collaborating with devs, who should obviously write the specific instructions. But it has to be put together as a coherent whole, see <a href="https://facebook.github.io/react-native/docs/getting-started">https://facebook.github.io/react-native/docs/getting-started</a> for example
|
|
2. I think this is part of the problem - to me the platform is the least difficult and interesting thing, it's more of an implementation detail. What really matters is the content itself.
|
|
|
|
> If people see things missing, then they need to take ownership and document themselves
|
|
And last hour we already have 3-5 people who stepped up and did this, but it had to be pointed out that this is a set of specific things that we need and are missing. Right now there's still confusion about how authoritative <a href="http://docs.status.im">http://docs.status.im</a> is, we still have old wiki up, and old READMEs are still being referred to etc. To me this is what the #documentation should be about.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:33</div><div class="msg">A question about contribution guidelines?can we have them somewhere on here; otherwise i?ll have no idea what i?m OK with contributing. and what?s needed etc.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-09-19 16:36</div><div class="msg">> But it has to be put together as a coherent whole, see <a href="https://facebook.github.io/react-native/docs/getting-started">https://facebook.github.io/react-native/docs/getting-started</a> for example
|
|
I'm sure FB has tech writers on the RN team solely responsible for this. I guess my point is that the team responsible for documenting this glaringly obvious user story, should automatically have fixed it.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-09-19 16:36</div><div class="msg">The fact that nobody has noticed (for however long its been) is pretty worrying</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:36</div><div class="msg">EG. wikipedia contribution purpose - getting started etc. <a href="https://en.wikipedia.org/wiki/Wikipedia:Contributing_to_Wikipedia">https://en.wikipedia.org/wiki/Wikipedia:Contributing_to_Wikipedia</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:37</div><div class="msg">Or even more than that; seem like you could make issues for needed documentation / articles here. <a href="https://github.com/status-im/docs.status.im">https://github.com/status-im/docs.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:39</div><div class="msg">Or is that incorrect as a place that we?d assign ?doc tasks? @rachel</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:40</div><div class="msg">(that could be fulfilled by anyone hopefully) team / community etc.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 16:44</div><div class="msg">That could also work @hutch - I remember we created an org-level board for it so that we could add issues under any individual repo</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:46</div><div class="msg">I?m just asking as a member coming into the fold and seeing ?oh i can edit technikon live today in GitHub!? which i had no idea before.
|
|
|
|
How do we get that across to people wanting to contribute (particularly on the docs site itself) and also have a ?go-to? place for needs in terms of documentation and an open place for people to express those needs. Issues on github seem like a great way; i?ve seen it work for other projects (originally etherian.world which i helped start before i joined status, which was basically this except news about ethereum) Aragon, and a few others.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:47</div><div class="msg">Where is the board?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-19 16:50</div><div class="msg">Added a bunch of brief issues of things off the top of my head: <a href="https://github.com/status-im/docs.status.im/issues">https://github.com/status-im/docs.status.im/issues</a> they can be added to whatever GH board needed</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 16:54</div><div class="msg">I was also under the impression that Technikon was not in ?working order? enough to go live with more contributions. Is there any truth to that or was it just a false narrative i had in my head :laughing:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 17:03</div><div class="msg">> And last hour we already have 3-5 people who stepped up and did this, but it had to be pointed out that this is a set of specific things that we need and are missing.
|
|
|
|
The most qualified people to point this out are developers. Issues with building status-go haven't come up in #dev-status-riot in the past 3 months, to my knowledge. That would've been a helpful signal.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:03</div><div class="msg">Also :thanks: @oskarth for adding some issues; I think if we can just get a clear sense of what it takes for someone else to come in and contribute or have open issues for people to be directed towards it will make a world of a difference in getting more active documented being added (extra bonus for Bounties on docs; not many people love writing docs :stuck_out_tongue:)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 17:04</div><div class="msg">@hutch it's just in its infancy, but open to contribution. I'd be interested in hearing requests from the community if there is specific documentation they're lacking.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:05</div><div class="msg">Cool; would be good to have an open call for community members to check it out so far and give feedback</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:05</div><div class="msg">i?ll ping around some; maybe it can be part of the first commit survey as well (as a question if they?ve checked the docs site and if they can think of anything else) i?ll add it now.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-19 17:07</div><div class="msg">Any idea how many active contributors we've had outside of core contributors in the last couple months?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:09</div><div class="msg">heh; for status-react the last month tells me 0? <a href="https://github.com/status-im/status-react/pulse/monthly">https://github.com/status-im/status-react/pulse/monthly</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:10</div><div class="msg">But; there?s a lot going on in Embark with the bounty campaign.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 17:11</div><div class="msg">Which hopefully can translate into a good thing in status moving into october. We?re at about 20 active issues being worked on / completed from outside contributors on embark ATM.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 22:17</div><div class="msg">Regarding devs updating the docs, I would propose enabling this as the first item on the PR checklist on Probot. Having to check a box
|
|
```
|
|
- [ ] Have you updated the documentation, if impacted?
|
|
```
|
|
will bring it to top of mind to the PR owner as well as the reviewers, and hopefully less will fall through the cracks.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 22:17</div><div class="msg">Great idea @pedro! </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-09-19 22:18</div><div class="msg">Over-automate ftw </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-10/297564958950_752f7f4865590f38fffc_72.jpg" /><div class="message"><div class="username">pedro</div><div class="time">2018-09-19 22:18</div><div class="msg">This is precisely the type of thing that script is meant to help with</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-09-20 09:06</div><div class="msg">We are going to finish with desktop automated tests PoC on this week</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-09-20 09:08</div><div class="msg">I will take care of documentation right after finishing with desktop</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-09-20 19:08</div><div class="msg">Interesting thread about debugging our documentation: <a href="https://status-im.slack.com/archives/C8QP8S5UH/p1537455395000100">https://status-im.slack.com/archives/C8QP8S5UH/p1537455395000100</a>. Relates to the previous mega-thread in this channel, where when people encounter problems we document and fix them
|
|
|
|
_Note - I'm not saying it's this swarm responsible for fixing documentation, but perhaps it should be worth thinking about how we can increase the sense of ownership for CC's when things go wrong_</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-20 19:19</div><div class="msg">I'd really love to have something more useful to say, have even prepared a re-skin of our docs in Hexo so that Embark and us are using the same framework going forward, but don't want to complete and ship it before I know whether we will be using a static site generator, just with our own CSS (which I think we should do) or using our own framework which will provide the same functionality, but do inner pages etc according to @andmironov and @hazel's work...
|
|
|
|
<a href="https://status-im.slack.com/archives/C8EQ3SH0E/p1537369421000200">https://status-im.slack.com/archives/C8EQ3SH0E/p1537369421000200</a>
|
|
|
|
I agree that no-one really needs to lead this per se, but I am very willing to put more time and effort into it once I have a framework in which to push devs and CCs to care about this, see how easy it is, and play some SITG games with @oskarth</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-09-20 19:27</div><div class="msg">Dev docs 100% should be owned by devs. What is missing is a culture of updating docs on regular basis. To be honest, I almost forgot we have docs site. We lost some time while experimenting with MW (many just gave up on the idea of regularly updating docs), but with new docs site I see no reason of not nurturing this culture again.
|
|
|
|
I believe we need to clearly say (and make sure that all devs heard that) that we now have amazing docs site, which should be a single source of truth, and that it's easy to update docs. Maybe run a couple of calls with screencasts showing how to edit/update docs. I know it's easy process now, but some education on that matter will be useful.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-20 19:32</div><div class="msg">> we now have amazing docs site
|
|
|
|
Not true yet :sweat_smile: But yes, I agree strongly with this in general - just needs someone to motivate it consistently and I am more than willing to do that, just need a few more days to figure out the design & framework stuff :+1:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-09-20 19:46</div><div class="msg">I just updated "Build status-go" page and it was nice and easy experience. Something I would willing to do every now and then.
|
|
|
|
Not super-realtime editing like in Dropbox Paper, but good enough.
|
|
|
|
I also really love the overall look and feel ? super clean and tidy. It's so much better than previous wiki solution!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-20 20:09</div><div class="msg">fair enough, thanks :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-21 01:03</div><div class="msg">If everyone is responsible then no one is. Saying this is not helping and it is counter productive. That?s why it is useful to have a group of people, aka swarm, that have representative from each eng/domain team that makes sure relevant things for their domain is documented. As far I?m aware this was the initial idea, at least part of it (too many chefs...) In addition to this, old and confusing docs should be removed. To facilitate the above work, a coordinating role is needed, aka swarm lead. After the basics are in place - including platform, basic user stories from relevant teams, old stuff is deprecated, and there?s some process for making sure new docs are added (acceptance criteria) - the group can announce: here is where our docs are, if you see a problem please fix it.
|
|
|
|
If we feel right now it isn't a priority, or we are ok with just a tiny subset, that's cool. But it doesn?t mean this role isn't needed.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-21 12:29</div><div class="msg">hey @rachel wdyt? <a href="https://andytudhope.github.io/docs.status.im/">https://andytudhope.github.io/docs.status.im/</a>
|
|
|
|
Re-skinned to match Embark's current site and use the same generator so that it's easy to style both according to the designs. I have also added a bunch of things in there (still need to get to TtT and a few others) because I think that the swarm Oskar is pushing for will mean that we should just let people document on an ongoing basis and worry about user journeys once we have an actual, real, fully documented journey to go on for them, rather than the other way around.
|
|
|
|
cc @hazel because you're working on the designs today, @jeluard for general trolling, @andmironov just to see that the site generator works (very willing to change whatever needs to be changed though to match the overall web theme)</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-14/415844461921_fcb4f6c6c9c175142692_72.jpg" /><div class="message"><div class="username">hazel</div><div class="time">2018-09-21 12:29</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-21 12:36</div><div class="msg">Obviously, we'll need to add the global header and nav, and a bunch of other things, just wanted to get things moving forward again.</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-21 12:44</div><div class="msg">Very impressive work! Good job swarm lead ! :smile:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-21 12:45</div><div class="msg">Asking to clarify, but pretty sure it's fine: can we have regular HTML pages with arbitrary JS ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-21 13:00</div><div class="msg">Should be ok :+1: Files are generated in MD, but you can customise pretty much anything with <a href="http://hexo.io">http://hexo.io</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-21 13:31</div><div class="msg">kudos to @cryptowanderer for movin the web refresh one step closer!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-01-24/304281668629_99d09ae86c8e0a04b52d_72.png" /><div class="message"><div class="username">growbot</div><div class="time">2018-09-21 13:31</div><div class="msg">Values Breakdown:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-21 13:35</div><div class="msg">dude @cryptowanderer that looks legit</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-21 13:37</div><div class="msg">there's a user guide waiting for you @rachel :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-21 13:46</div><div class="msg">provacateur andy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-24 08:46</div><div class="msg">Hey @easye what is the status of your Whisper posts? Will we have something today or tomorrow?
|
|
|
|
@jakub you're gonna hate me, but I want to move our docs over to use <a href="http://hexo.io">http://hexo.io</a> as this is what the Embark team is using, it's a bit more powerful and customisable, and it's important we all use the same generator, and then style it the way the design team wants us to. Could you reserve a little time for me sometime this week to change the build pipeline to accommodate this?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-24 08:48</div><div class="msg">@cryptowanderer Yes, I am working on the first piece now. I need to share my outline of the series and the draft today, hopefully before the town hall.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-24 12:58</div><div class="msg">sure, whenever it's good for you my dude</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-24 12:58</div><div class="msg">I tried using hexo once to setup a portfolio site, but the docs were abysmal, I guess they must have improvecd</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-24 12:59</div><div class="msg">I'm happy setting it up, how do we do it right now?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-24 19:53</div><div class="msg">@easye any update on the draft? We have shared the intro blog last friday and want to follow up with the next in the series asap.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-24 19:53</div><div class="msg">Can you share a draft tomorrow please</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-25 07:26</div><div class="msg">@easye :point_up_2:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-25 07:27</div><div class="msg">Will do.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-25 13:52</div><div class="msg"><a href="https://hackmd.io/s/SJ4HanvYm#">https://hackmd.io/s/SJ4HanvYm#</a>
|
|
|
|
@cryptowanderer @jonny.z @exiledsurfer</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-25 14:03</div><div class="msg">This seems incomplete? It's also quite high-level. What I really want to see is a clear, concise, too the point technical document (or series of documents) on how Whisper actually works, not necessarily why metadata is bad. I also suggested working with @noman on a tutorial for interacting with whisper, even just something based off Siraj's video? <a href="https://www.youtube.com/watch?v=vVsIHCTGjsE">https://www.youtube.com/watch?v=vVsIHCTGjsE</a>
|
|
|
|
Technical documents, not discursive discussions...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-09-06/430098664084_d320a9b17f9da6b75744_72.png" /><div class="message"><div class="username">easye</div><div class="time">2018-09-25 15:39</div><div class="msg">Will check with @noman; will modify for more technical content.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-25 20:36</div><div class="msg">not what i was expecting either to be honest. Seems very introductory even though we have already shared the philosophical "Why" blog post created by Andy last week. Agree we need to now dive into the details of the protocol and through the details explain why this is important. Lets not forget the initial outline structure created by @rachel nearly 3 months ago <a href="https://status-im.slack.com/archives/CAJMDBQCD/p1529572002000591">https://status-im.slack.com/archives/CAJMDBQCD/p1529572002000591</a>
|
|
|
|
I feel the work Tonino had done followed this outline (was just poorly executed). I agree we need deep technical details, I think this should still be digestible for someone who is a non-developer.
|
|
|
|
@easye when do you think you can have another draft back to us? We really need to get something out this week to follow Andys post</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-26 07:49</div><div class="msg">Yeah, let me know if you need any help. Remember that there is also the Ethereum wiki on GH (which is a bad example, but is at least indicative of the kind of technical detail we need)...</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-26 13:50</div><div class="msg"><a href="https://github.com/status-im/ideas/pull/311">https://github.com/status-im/ideas/pull/311</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-31/408248212533_6aab8328425c701a55ee_72.jpg" /><div class="message"><div class="username">corey122</div><div class="time">2018-09-26 19:25</div><div class="msg">your ability to beat me at #307 is a testament to your knowledge of how things work in this company, or your ability to do good work... or both</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-26 19:37</div><div class="msg">no, sorry - you can have 307 @corey122 I changed it already</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-31/408248212533_6aab8328425c701a55ee_72.jpg" /><div class="message"><div class="username">corey122</div><div class="time">2018-09-26 19:39</div><div class="msg">I was willing to fight you for it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-31/408248212533_6aab8328425c701a55ee_72.jpg" /><div class="message"><div class="username">corey122</div><div class="time">2018-09-26 19:39</div><div class="msg">in a gentlemen's duel</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-26 20:02</div><div class="msg">I gladly accept this challenge :ninja:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-31/408248212533_6aab8328425c701a55ee_72.jpg" /><div class="message"><div class="username">corey122</div><div class="time">2018-09-26 20:03</div><div class="msg">@ericmastro can judge</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-10/345048961478_60c5a0cb079da69aa25c_72.jpg" /><div class="message"><div class="username">ericmastro</div><div class="time">2018-09-26 20:03</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-14/415844461921_fcb4f6c6c9c175142692_72.jpg" /><div class="message"><div class="username">hazel</div><div class="time">2018-09-27 05:03</div><div class="msg">@cryptowanderer @andmironov @jonny.z This is the design for the landing page of `<a href="http://docs.status.im">http://docs.status.im</a>` based on the current online docs (<a href="https://docs.status.im/">https://docs.status.im/</a>) --> <a href="https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=625%3A108">https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=625%3A108</a>
|
|
|
|
Yesterday, I had a chat with @cryptowanderer. We thought that if there are a landing page for people to access the documents and get a general ideas regrading each items, it would be helpful for people to understand and make a choice.
|
|
|
|
So the user flow will be:
|
|
- If you click the ?Docs? in the navigation bar, you will navigate to <a href="https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=625%3A108">https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=625%3A108</a> .
|
|
- Afterward, you click one of the boxes on the main page, you will navigate to <a href="https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=0%3A372">https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=0%3A372</a>
|
|
|
|
Do you think that makes sense? :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 07:07</div><div class="msg">@cryptowanderer I can see doc has been switched to hexo. Looks like we lost git history. Did you force push?
|
|
Recent merges have been lost apparently</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 07:17</div><div class="msg">Or are they in `develop` branch? I am confused which branch should be used.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-27 07:27</div><div class="msg">this makes sense to me @hazel. So just to confirm, we will have `Docs` in the global nav which will drive to a `Docs` landing page where people can see a list of all the documents regarding all our initiatives. Then each initiaties (status, embark, hardwallet, nimbus, etc) will have their own inner pages?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 08:33</div><div class="msg">sorry about losing some of the history, that's my bad... :disappointed: <a href="https://status-im.slack.com/archives/C5Z5NRYKS/p1538035146000100">https://status-im.slack.com/archives/C5Z5NRYKS/p1538035146000100</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 08:36</div><div class="msg">@hazel content for 2 other sections to go on the home page for a total of 6.
|
|
|
|
`Testing`
|
|
```
|
|
So you'd like to help us make sure we ship the best products consistently and that we maintain, as an open source community, the highest security and privacy standards we can? Learn how to get involved here.
|
|
```
|
|
|
|
`WIP Features`
|
|
```
|
|
We have an very fast-moving codebase. As a decentralised and remote community of people, there are often new <a href="https://ideas.status.im" target="_blank">ideas</a> being worked on by various different people. Follow the latest developments, research efforts, and open questions we have to answer in oder to deliver the mobile window onto Ethereum we all need.
|
|
```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-09-27 09:02</div><div class="msg">moving at the speed of software</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 09:32</div><div class="msg">@cryptowanderer Happy to see that `extensions` get a prominent place in the new docs! :sweat_smile:
|
|
We should probably clarify it's very alpha.. Also how it relates to DApps / status?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 09:33</div><div class="msg">It'll be moving away from the header when I get around to implementing the global header once it has been settled on, so slightly less prominent...
|
|
|
|
Feel free to clarify anything and everything with PRs to `develop` :wink:</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 09:35</div><div class="msg">I'm just a janitor here!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 09:52</div><div class="msg">```One key insight is that the responsibility of the swarm leaders is not so much managerial as it is janitorial. Nobody answers to them, and their task is to make sure that the swarm has everything it needs to self-organize and work its miracles.```</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-09-27 09:56</div><div class="msg">In all honestly, the goal is for all core contributors to shift mindset from being contributors to maintainers (aka janitors). If we get more and more community contributions, our job is just to grease the squeaky wheels and make sure everything is running smoothly.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:13</div><div class="msg">I found <a href="https://dev-docs.status.im/docs/ens_usernames.html">https://dev-docs.status.im/docs/ens_usernames.html</a> but I don't see any links. Does ENS work already on mainnet?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 10:14</div><div class="msg">Do you mean Status ENS DApp?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:14</div><div class="msg">I guess so.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:15</div><div class="msg">I want to reserve my name so that it will be resolved in the Status app</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:16</div><div class="msg">wonder why that share card is still coming up - I did change it to a build tools image...</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-09-27 10:16</div><div class="msg">@adamb Not on mainnet yet, no</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:17</div><div class="msg">ah ok</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:18</div><div class="msg">thanks @jeluard</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:18</div><div class="msg">but soon :+1: @adamb do you want me to rebase your status node PR quickly?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-09-27 10:19</div><div class="msg">maybe we could reserve names for core contributors</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:19</div><div class="msg">@cryptowanderer I'd like to first verify it if it works properly on <a href="https://dev-docs.status.im/">https://dev-docs.status.im/</a> but it does not refresh. Do I need to do something?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:20</div><div class="msg">@andrey I think it would be nice to give some time to core contributors to reserve some names before announcing that it's public :smile:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:22</div><div class="msg">@cryptowanderer ok, I found it and it's broken <a href="https://ci.status.im/job/misc/job/dev-docs.status.im/49/console">https://ci.status.im/job/misc/job/dev-docs.status.im/49/console</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:22</div><div class="msg">yeah, that site is not building for some reaon, I prob messed something up. Will wait for @jakub to wake up</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:29</div><div class="msg">just pushed a change @adamb because I might have overwritten the wrong file by mistake... Let's see if it builds now</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:30</div><div class="msg">looks good: <a href="https://dev-docs.status.im/docs/run_status_node.html">https://dev-docs.status.im/docs/run_status_node.html</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:30</div><div class="msg"><a href="https://ci.status.im/job/misc/job/dev-docs.status.im/51/">https://ci.status.im/job/misc/job/dev-docs.status.im/51/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:30</div><div class="msg">let me know and I will merge into `master` :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:31</div><div class="msg">Looks fine, I checked locally. Please do :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:31</div><div class="msg">btw. I submitted <a href="https://github.com/status-im/docs.status.im/pull/63">https://github.com/status-im/docs.status.im/pull/63</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:31</div><div class="msg">ugh, I need to rebase it something is off</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:32</div><div class="msg">probably me again :disappointed: working out the final kinks, I promise!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:33</div><div class="msg">I think merging from develop to master should be only with `--ff` (fast-forward) to make sure the branches are always in sync</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 10:34</div><div class="msg">OK, fixed my PR :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 10:37</div><div class="msg">ok, will make that the case from now on, thanks @adamb</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-27 11:25</div><div class="msg">@andrey @adamb there?s a discussion about reserved names here <a href="https://discuss.status.im/t/ens-usernames-unallowed-names-slashing-conditions/353/5">https://discuss.status.im/t/ens-usernames-unallowed-names-slashing-conditions/353/5</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-09-27 11:25</div><div class="msg">Would love to get more input</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-14/415844461921_fcb4f6c6c9c175142692_72.jpg" /><div class="message"><div class="username">hazel</div><div class="time">2018-09-27 12:41</div><div class="msg">> So just to confirm, we will have `Docs` in the global nav which will drive to a `Docs` landing page where people can see a list of all the documents regarding all our initiatives.
|
|
|
|
Correct!
|
|
|
|
> Then each initiaties (status, embark, hardwallet, nimbus, etc) will have their own inner pages?
|
|
|
|
They are still in the same inner page like @andmironov?s design. For example, if you click `Status`, the ?Status? accordion menu will expand, and the screen on the right side will show the content of Status.
|
|
|
|
I guess we will only have a document website which includes all the docs for each projects (status, embark, hardwallet etc.). If I am mistaken, please correct me :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-27 12:46</div><div class="msg">ok this makes sense. I hope this is inline with what @cryptowanderer is thinking. I know we also need a easy way to navigate to each individual initiative docs site. For example, if i am on the Nimbus landing page and I want to view all nimbus documentation, I should be able to easily navigate to nimbus docs</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-09-27 12:49</div><div class="msg"><a href="https://docs.status.im/wip/">https://docs.status.im/wip/</a> haha awesome @cryptowanderer</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-09-27 12:51</div><div class="msg">@cryptowanderer probably <a href="https://github.com/status-im/status-react/pull/6007">https://github.com/status-im/status-react/pull/6007</a> should be there too :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-27 13:31</div><div class="msg">so it works? no need for me to fix anything? =]</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-09-27 13:50</div><div class="msg">all works :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 14:43</div><div class="msg">No :facepalm:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 14:46</div><div class="msg">Embark needs its own docs site, Status needs its own docs site, Nimbus needs its own docs site. These are all hosted separately, in different repos, and different teams have responsibility for them - though the documentation swarm lead will coordinate it all.
|
|
Each site uses the same theme - <a href="http://hexo.io">http://hexo.io</a> which I checked with Andrei and the team - and is styled according to the global design framework. Teams are, of course, welcome to adapt the styles to their needs over time (but let's get something complete and coherent out first).</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 14:48</div><div class="msg">How that translates into what goes into the header is difficult to figure out exactly. But I should think that `Doc`, `Nimbus`, `Embark` and `Hardwallet` in the header don't need any drowdowns, they just take you to the relevant site.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 14:52</div><div class="msg">This is just my opinion, of course, you can feel free to design it some other way if that is the consensus, but I genuinely think that having all the docs together would be disaster :shrug:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-09-27 14:53</div><div class="msg">seems simple enough to just kill the initial docs landing page and drive direct to individual team docs sites. Will there be a use case in which someone will want to easily navigate between embark docs and status docs for example?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 14:55</div><div class="msg">Hey team, this is how i think a docs homepage should look like <a href="https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=0%3A372">https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=0%3A372</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 14:56</div><div class="msg">just like <a href="https://framer.com/docs/">https://framer.com/docs/</a> <a href="https://redux.js.org/">https://redux.js.org/</a> and all those docs websites, with no ?landing page? just straight to the point</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 14:58</div><div class="msg">i?m talking about Status Docs, not Embark Docs etc. If there is going to be a task to create a webpage for Embark docs, it would be completely the same, but with embark?s color palette and it's going to say ?Embark Documentation? instead of ?Status Documentation?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:00</div><div class="msg">Embark already has a bunch of stuff on their front page, do you propose we scrap that? <a href="https://embark.status.im/">https://embark.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:01</div><div class="msg">nope, it's Embark?s website, not Embark Docs website</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:01</div><div class="msg">i get you point, i agree, the hierarchy is a but different for embark</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:08</div><div class="msg">Yes, it is different, so what do we do about that? And how do you imagine the urls will work @andmironov? Will we have your custom react framework to generate each front page - `Status`, `Desktop`, `Studio`, `Incubate`, `Nimbus`, `Embark` and then have <a href="http://docs.status.im">http://docs.status.im</a> and <a href="http://docs.desktop.im">http://docs.desktop.im</a> and <a href="http://docs.studio.im">http://docs.studio.im</a> etc. living in separate repos, using hexo, and styled to meet the designs?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:18</div><div class="msg">nice question! i think status docs should live on `<a href="http://status.im/docs">http://status.im/docs</a>`, nimbus docs on `<a href="http://nimbus.status.im/docs">http://nimbus.status.im/docs</a>`</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:20</div><div class="msg">@jakub wdyt? Could we get the docs serving to that kind of url, or do they need their own subdomain if we're hosting them in GH and serving through GH pages?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:20</div><div class="msg">but the way to make it work indeed is not 100% clear. Yet i believe (form the user?s perspective) it makes sense for Nimbus Docs and Status Docs not to be in the same place</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:21</div><div class="msg">i am all for making it work the easiest way possible for now, so please let me know what you think would be the best approach?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:25</div><div class="msg">well, hexo already uses a url scheme such that you get docs at <a href="http://embark.status.im/docs">http://embark.status.im/docs</a>. So, we could build every site using hexo if that is the structure you wanted, and just make sure to re-use components and styles between them all. That would make editing any part of the site, not just the docs, easy for anyone.
|
|
|
|
However, I don't know if this fits into your desire to have react stuff so that we can re-use things between the app and wesbite? I am certain it's extensible enough to have pretty much any JS though, and could certainly include the fiddle, for instance.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:26</div><div class="msg">And we can set up each site how we have just set up the docs, so that any edit is done on `develop` gets merged in almost automatically, and then built to a staging environment like <a href="http://dev-docs.status.im">http://dev-docs.status.im</a> so people can see their changes and others can review super easily</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:26</div><div class="msg">this is awesome and let?s figure out if it's going to fit in this react thing once we start building it, i am pretty sure we're going to figure it out</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:26</div><div class="msg">But that's not how it has to be, just a suggestion. Keen to hear more about the react things?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:27</div><div class="msg">yeah, no doubt we will, and once we start building, it's really fun :wink:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:27</div><div class="msg">i mean the
|
|
>react stuff so that we can re-use things between the app and wesbite
|
|
by the ?react thing? :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:28</div><div class="msg">ah, but what `stuff` is it exactly?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:39</div><div class="msg">fully agree <a href="https://docs.status.im/wip/">https://docs.status.im/wip/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:39</div><div class="msg">:slightly_smiling_face: the idea is to keep everything as react componets, rendered on client, hosted open source on github</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 15:40</div><div class="msg">i am currently working only on the design-side of this, we are looking for someone to implement all of that</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-09-27 15:41</div><div class="msg">ok, and would you say the designs are nearly complete in Figma there, at least for Status, Studio, Desktop, Harwallet and Docs?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 16:07</div><div class="msg">nearly but not 100% ready</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 16:08</div><div class="msg">hard to evaluate the progress now, i suggest we have a web-refresh call and sync up with everyone who is taking part in it</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2016-11-16/104878545009_e6897ef62e65dc08f5b8_72.jpg" /><div class="message"><div class="username">andmironov</div><div class="time">2018-09-27 16:09</div><div class="msg">i created a call, Tuesday next week me and @hazel will try to finish up as much as we can by then and prep up the questions we have. BTW we are also waiting fo an illustrator to finish his work.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-09-27 16:11</div><div class="msg">Thanks a lot!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-27 16:16</div><div class="msg">Well, I could possibly add a redirect from <a href="http://status.im/docs">http://status.im/docs</a> to <a href="http://docs.status.im">http://docs.status.im</a>, but hosting it there would be a bunch more work</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-23/352364450583_84860327a35f2a5b0e5f_72.jpg" /><div class="message"><div class="username">jakub</div><div class="time">2018-09-27 16:17</div><div class="msg">since <a href="http://status.im">http://status.im</a> is already hosted on github, so we would either have to self-host <a href="http://status.im">http://status.im</a>, or somehow commit contents of `gh-pages` branch to a sub-dir in <a href="http://status.im">http://status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-11/344678860515_64490607960ebf85ac4a_72.jpg" /><div class="message"><div class="username">alwx</div><div class="time">2018-09-28 08:48</div><div class="msg">@cryptowanderer updated my PR: <a href="https://github.com/status-im/docs.status.im/pull/62">https://github.com/status-im/docs.status.im/pull/62</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 05:21</div><div class="msg">Oops! Needs a bit of mobile :heart:. Is the JS API documentation no longer published? </div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-01 06:47</div><div class="msg">same on nimbus docs site; hoping for @haunted.chris to clean the mobile templates up for the docs theme <a href="https://status-im.slack.com/archives/C8LPZBV61/p1538181786000100?thread_ts=1538181284.000100&channel=C8LPZBV61&message_ts=1538181786.000100">https://status-im.slack.com/archives/C8LPZBV61/p1538181786000100?thread_ts=1538181284.000100&channel=C8LPZBV61&message_ts=1538181786.000100</a></div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3d5ce1fcb757b31230ae58312a3953fd.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0021-72.png" /><div class="message"><div class="username">haunted.chris</div><div class="time">2018-10-01 06:47</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-10-01 09:54</div><div class="msg">hey @cryptowanderer how can i made changes in docs ? should i create branch from develop <a href="https://github.com/status-im/docs.status.im">https://github.com/status-im/docs.status.im</a> and create PR target to develop?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 10:24</div><div class="msg">hey @andrey - that sounds great :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 10:25</div><div class="msg">Yes, I know the mobile stuff sucks right now, and am getting there. @haunted.chris would you be able to help optimise first the header for mobile, and then there is a bunch of other things I could use some help with?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/3d5ce1fcb757b31230ae58312a3953fd.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0021-72.png" /><div class="message"><div class="username">haunted.chris</div><div class="time">2018-10-01 10:26</div><div class="msg">Sure. Will start tonight.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 11:11</div><div class="msg">You da best :heart: Am working on <a href="http://dev-docs.status.im">http://dev-docs.status.im</a> atm as well, will push a branch called `tmp` with the <a href="http://status.im">http://status.im</a> front page design from here: <a href="https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=787%3A200">https://www.figma.com/file/MHMQZfRpQZ6ScJYPYnsvquVY/Websites-v2?node-id=787%3A200</a> that my terrible html/css will also need some love for, especially mobile</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-10-01 13:11</div><div class="msg"><a href="http://docs.status.im">http://docs.status.im</a> has some broken nav links</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 13:34</div><div class="msg">Fixed :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 15:52</div><div class="msg">@cryptowanderer here?s how we're thinking (roughly) of regrouping the content for DApp developers: <a href="https://docs.google.com/document/d/1drG-WU1fMwgE8j_3ExTikfp0vAHWZDJTpgRcdsvP3k8/edit?usp=sharing">https://docs.google.com/document/d/1drG-WU1fMwgE8j_3ExTikfp0vAHWZDJTpgRcdsvP3k8/edit?usp=sharing</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 15:53</div><div class="msg">Not sure how it will fit into the wider nav yet but this list captures the suggested pages</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 15:54</div><div class="msg">This content all exists + can be cleaned up and reshaped if we all agree</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 15:56</div><div class="msg">Also, Julien?s extensions chat command tutorial can be reorganized. Talked about it in Berlin but need to revisit</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-07-24/217825278711_78582e61a53927136266_72.jpg" /><div class="message"><div class="username">adamb</div><div class="time">2018-10-01 17:27</div><div class="msg">Is anyone an owner of the documentation? Or rephrasing that, should I ping anyone to check what I want to publish?</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-10-01 17:31</div><div class="msg">@cryptowanderer is the swarm leader</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 17:56</div><div class="msg">@rachel ask and you shall receive: <a href="https://dev-docs.status.im/">https://dev-docs.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 17:57</div><div class="msg">click the `Extend Your DApp` button</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-01 19:04</div><div class="msg">Thank you @cryptowanderer!!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-01 19:14</div><div class="msg">for you Rachel, the :earth_africa:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-02 17:46</div><div class="msg">Hey @adan - can you take a look at this documentation issue when you get a chance? <a href="https://github.com/status-im/docs.status.im/issues/49">https://github.com/status-im/docs.status.im/issues/49</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 19:33</div><div class="msg">Let's try that again. We now have a fully mobile responsive docs site :tada: <a href="https://dev-docs.status.im/">https://dev-docs.status.im/</a>
|
|
|
|
@rachel and @jeluard if you would like to look over it (still not final design or anything, but am iterating towards the web refresh designs as we go. Have changed some copy on the front page because it will actually be the frontpage of <a href="http://status.im">http://status.im</a> when we are done, and have styled the docs page more like the design etc.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 19:41</div><div class="msg">all further discussion to happen in #status-documentation :stuck_out_tongue_winking_eye:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:28</div><div class="msg">One last thing @exiledsurfer here is the repo for <a href="https://github.com/status-im/incubate.status.im">https://github.com/status-im/incubate.status.im</a> with template code</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:29</div><div class="msg">Are you sure you want ones for Studio and Peopleops, seeing as there are literally no designs for those yet?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:33</div><div class="msg">yes; ned is starting w/ peopleops tomorrow</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:33</div><div class="msg">do you want anything in the submenu for peopleops yet?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:34</div><div class="msg">yes, one sec</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:36</div><div class="msg">@cryptowanderer
|
|
Our Principles
|
|
Working Here
|
|
Docs
|
|
Life at Status
|
|
Contribute
|
|
Jobs
|
|
Blog</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:38</div><div class="msg">thanks - links too, so I can be sure?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:39</div><div class="msg">yeah</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:40</div><div class="msg">those are individual docs subpages, except blog</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:40</div><div class="msg">will it be staged at <a href="https://status-im.github.io/incubate.status.im/">https://status-im.github.io/incubate.status.im/</a> ?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:40</div><div class="msg">no, will create a repo for it at <a href="http://people-ops.status.im">http://people-ops.status.im</a> - just give me some time here :stuck_out_tongue_winking_eye:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:41</div><div class="msg">oh, the incubate site, ya, one sec</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:42</div><div class="msg">also, would `Our Principles` not be linked to <a href="https://our.status.im/our-principles/">https://our.status.im/our-principles/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:42</div><div class="msg">you mean <a href="https://status-im.github.io/people-ops.status.im">https://status-im.github.io/people-ops.status.im</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 20:42</div><div class="msg">yeah, for now :+1:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:42</div><div class="msg">no, our principles are their version</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:43</div><div class="msg">wait, yeah, for now link them to blog version sorry</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 20:47</div><div class="msg">@cryptowanderer current submenus for incubate: <a href="https://docs.google.com/presentation/d/1RAjSHVJZEo22BG0GGdr0cmKWlPa01_c_PLLrGfmjRcg/edit#slide=id.g42c7fa939a_7_0">https://docs.google.com/presentation/d/1RAjSHVJZEo22BG0GGdr0cmKWlPa01_c_PLLrGfmjRcg/edit#slide=id.g42c7fa939a_7_0</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:08</div><div class="msg">just ping me with the repo and staging links when ya got em :slightly_smiling_face:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 21:09</div><div class="msg">yeah, but those don't match the global nav at all? Will just stick em in where I see fit :stuck_out_tongue_winking_eye:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:09</div><div class="msg">those are THEIR subnavs</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:10</div><div class="msg">they dont realize we're doing global nav</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:10</div><div class="msg">Incubate
|
|
-about
|
|
-etc
|
|
|
|
.... just like you did peopleops</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:11</div><div class="msg">that's the closest thing i had for their current state</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 21:11</div><div class="msg">yeah, all over it boss :angry_trump:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-01/375000796951_78d872be972af4441b52_72.jpg" /><div class="message"><div class="username">exiledsurfer</div><div class="time">2018-10-04 21:11</div><div class="msg">:sonic:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-04 22:06</div><div class="msg">ok @exiledsurfer here you are:
|
|
|
|
<a href="https://status-im.github.io/incubate.status.im/">https://status-im.github.io/incubate.status.im/</a>
|
|
<a href="https://status-im.github.io/people-ops.status.im/">https://status-im.github.io/people-ops.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-05 00:37</div><div class="msg">This is relevant - there?s an education ring forming, focused on how we onboard people to Ethereum and share knowledge: <a href="https://github.com/ethereum-magicians/scrolls/wiki/Education-Ring">https://github.com/ethereum-magicians/scrolls/wiki/Education-Ring</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-10-05 00:38</div><div class="msg">oh my gosh, cleaner, nicer, better</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-10-05 06:22</div><div class="msg">`cleaner, nicer, better`
|
|
Is that a new daft punk song?
|
|
<a href="https://www.youtube.com/watch?v=gAjR4_CbPpQ">https://www.youtube.com/watch?v=gAjR4_CbPpQ</a>
|
|
(sorry Friday morning :sweat_smile:)</div></div></div><br/>
|
|
<div><img src="https://secure.gravatar.com/avatar/2674ec9e762bcd011c9542c1b787ce13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0019-72.png" /><div class="message"><div class="username">jeluard</div><div class="time">2018-10-05 06:31</div><div class="msg">Great job Andy! Looks very professional now!</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 08:28</div><div class="msg">@ned, @exiledsurfer, @jonny.z and whoever else, the Studio skeleton awaits you: <a href="https://status-im.github.io/studio.status.im/">https://status-im.github.io/studio.status.im/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-05/394232370742_ad7884cfec10fe3457d9_72.jpg" /><div class="message"><div class="username">ned</div><div class="time">2018-10-05 08:28</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-10-05 09:31</div><div class="msg">cc @akshi.
|
|
|
|
We are working through copy here. Hoping the page template has some flexibility in terms of layout so all the pages dont look like carbon copies. Mostly just mean the order in which we present certain modules. <a href="https://docs.google.com/document/d/1Ftt5zsvNkbUstt5xeCe8uRYyNdD9gbtYo127yOk8GH8/edit">https://docs.google.com/document/d/1Ftt5zsvNkbUstt5xeCe8uRYyNdD9gbtYo127yOk8GH8/edit</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-07-04/392536263425_611ff881e27c6e943a37_72.jpg" /><div class="message"><div class="username">akshi</div><div class="time">2018-10-05 09:31</div><div class="msg">has joined #documentation</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 09:38</div><div class="msg">we can do whatever inner pages you need @jonny.z :heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 09:39</div><div class="msg">complete flexibility - this is literally just the skeleton, so let that mind run free! :charmander_dancing:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 09:41</div><div class="msg">Because making sites is now fun and easy: <a href="https://andytudhope.github.io/merrymerkle.africa/">https://andytudhope.github.io/merrymerkle.africa/</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-09-12/240066984213_b35ca6f6b9658bf5cabb_72.jpg" /><div class="message"><div class="username">jonny.z</div><div class="time">2018-10-05 09:42</div><div class="msg">you too good to me</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 09:45</div><div class="msg">the feeling is mutual :kissing_heart:</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-10-05 13:07</div><div class="msg">A few empty pages on the docs site linked from the side nav
|
|
Eg
|
|
<a href="https://docs.status.im/developer_tools/access_eth_provider.html">https://docs.status.im/developer_tools/access_eth_provider.html</a>
|
|
<a href="https://docs.status.im/developer_tools/detecting_status.html">https://docs.status.im/developer_tools/detecting_status.html</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 13:23</div><div class="msg">yeah, they're empty because no-one has written them yet :sweat_smile: Wanna help?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-10-05 13:27</div><div class="msg">I remember they were there before</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 13:27</div><div class="msg">I see what you mean, will add back in now :+1: But that's changing fast atm anyway and @andrey will document fully when it has settled, I'm sure</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 13:30</div><div class="msg">have pushed `detecting_stauts` back as that was def there (in another doc I split up). But still waiting for EIP1102 dust to settle before the `eth_provider` doc can be completed afaik</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-10-05 13:35</div><div class="msg">there is no dust , `eth_provider` EIP1102 is implemented in status</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 13:53</div><div class="msg">cool! Let's document it? Or did I mess something up in the migration?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-28/338213459126_9a2080e57364819a4d87_72.jpg" /><div class="message"><div class="username">andrey</div><div class="time">2018-10-05 14:00</div><div class="msg">i believe we had it before</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 14:01</div><div class="msg">can you rescue it from wherever it might have got consigned to?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-10-05 19:50</div><div class="msg">Found more docs! <a href="https://github.com/status-im/status-react/wiki/RN---GO">https://github.com/status-im/status-react/wiki/RN---GO</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-10-05 19:58</div><div class="msg">guillame ballet is asking @easye @yenda (and myself) for a call to sync up on documentation efforts regarding whisper (via email), anyone can pick that up?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 20:14</div><div class="msg">@roman this is out of date isn't it?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-05-11/181684552369_66f21f8981bdb0f83bdd_72.jpg" /><div class="message"><div class="username">cryptowanderer</div><div class="time">2018-10-05 20:15</div><div class="msg">Have been trying to ping @easye without any luck :disappointed: When is the call?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-10-05 20:15</div><div class="msg">that's what guillame wants to know. he's trying to organize some cooperation on this.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-10-05 20:16</div><div class="msg">he's asked twice now, and I don't have bandwidth to work on whisper docs, really, beyond maybe reviewing</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-27/423671855091_1b4f90cfbdd6a3ee2b6f_72.jpg" /><div class="message"><div class="username">roman</div><div class="time">2018-10-06 03:42</div><div class="msg">basically it should be similar if not the same atm, but better to ask someone from <!subteam^S9X6DHR1U|@go> because i haven't touched that part for ages</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-10-06 05:22</div><div class="msg">A few other pages on the repo wiki too</div></div></div><br/>
|
|
</div></body></html> |